Sauerbraten - Bug reports

by Gilt on 11/28/2004 19:49, 574 messages, last message: 06/30/2007 22:00, 487100 views, last view: 05/16/2024 13:51

So yeah, since I don't feel like doing a whole lot of testing anymore, I may as well leverage my resources, and shove that responsibility to all of you. Hopefully, this will allow for more updates, and a less buggy engine.

The Format:
-----------
What: A *short* description of the bug / problem.

How: point form of relevant steps to reproduce the bug.

When: revision of exe. OS, video card... yeah I don't know, anything that might be relevant. keep it short.

Detail: any other stuff that might be relevant. like pics. http://www.imageshack.us/ if needed.
-----------

new releases here:
http://cvs.sourceforge.net/viewcvs.py/sauerbraten/sauerbraten/sauerbraten/bin/sauerbraten.exe?view=log

for each new version, I will list fixed bugs. you are then responsible to make sure that it really is fixed, and then confirming it in this thread.

!!! NOTE !!!: this thread is not for feature requests, design discussion, bitching, moaning, yadda yadda, etc. there are other threads for that. plus, a forum thread already does not afford great organization. please no garbage.

Keep reports short. I have a habit of skimming large blocks of text.

Focus on the WHAT, not the WHY. There is a tendancy in people to want to be too helpful. They try to diagnose the problem instead of very clearly describing what is wrong. at the very least, keep theories in the detail section.

some examples are below:

   Board Index   

#401: Re: 9000

by Aardappel_ on 04/26/2006 08:02, refers to #400

sauer shaders require shader model 2, anything lower (such as 9000/9200, gf4 etc) falls back to no-shaders automatically. see docs.

reply to this message

#402: ..

by enigma_0Z on 04/26/2006 17:49

Well, lesse,

1. This is the "shader edition"
2. I am running linux.
3. Adding -f to the script or to the commandline doesn't help
4. I am sure that my drivers are working properly, old cube works great (and see no. 5 & 6)
5. 9000 is a no-shader card, but "disabling shaders" doesn't speed anything up.
6. The "Physics Edition" ran at full speed beautifully with ATI's latest drivers (linux, remember)
7. If it falls back automatically or with the -f switch, then it should run as fast as previous versions of sauer, right?

I think that's all of the questions that have been posed.

---- THIS IS IMPORTANT ----
Finally (to eihrul)
I tried poking around in the source (something different), but it won't compile. I need -lenet (The enet libs). Are they included with Sauer, or do I need to go get them... and where would I get them if I need to?

reply to this message

#403: A few more details

by enigma_0Z on 04/26/2006 17:57

1. I was in err, the last one to work good was the MP edition. I skipped physics. I can't imagine that that edition had probs too, but I will go see...
2. I'm downloading the new new (occlusion) edition to see if it is fixed there...

reply to this message

#404: Re: ..

by Passa on 04/26/2006 18:04, refers to #402

sounds exactly like the problem I am having with my 9250 card

reply to this message

#405: A few few more details

by enigma_0Z on 04/26/2006 18:11

Sorry for the triple post, but I keep remembering details that need to be remembered....

eihrul:
Linux is your forte, right? I compiled and installed the enet libs, but for some reason, I can't find ati_texgen_bug in any of the files:

-code-
$ pwd
/games/sauerbraten_shader_ed/src/engine
$ grep ati_texgen *
$ grep bug *
octarender.cpp: // KLUGE: workaround for buggy nvidia drivers
$ cd ../fpsgame
$ grep bug *
$
-code-

Am I just looking in the wrong spot?

reply to this message

#406: Re: More shader problems

by enigma_0Z on 04/26/2006 18:21, refers to #395

Eihrul,

Occlusion edition:
You were talking about this line, right?

--code (rendergl.cpp)--
// if(strstr(vendor, "ATI")) ati_texgen_bug = 1;
--code--

Commenting borked the compile (because of the else if below), so I changed the 1 to a 0

... it's compiling now ...

FIXED IT!!!!!

So... does that help any?

So what significance does that have?
What does "ati_texgen_bug" control exactally, assuming that nonzero is "on"

reply to this message

#407: Re: More shader problems

by Aardappel_ on 04/26/2006 19:19, refers to #406

so it seems on linux switching texgen is hugely expensive?

reply to this message

#408: Re: More shader problems

by enigma_0Z on 04/26/2006 20:17, refers to #408

'k...

So what does texgen do, is it just one of the shader functions?

reply to this message

#409: so

by Aardappel_ on 04/27/2006 00:26

..

reply to this message

#410: Re: so

by Aardappel_ on 04/27/2006 00:28, refers to #409

is there anyone here who has a older ATI card (9250 or lower) that can run the latest sauer at above 10 fps? On what platform?

Because if not, like eihrul says, we have no option but to disable the fix.

I will report the bug to ATI however.

reply to this message

#411: Re: so

by Pxtl on 04/27/2006 01:48, refers to #410

I've got a 9600 and it runs fine under win32. Afaik, the 9250 is just a 9600 with some stuff ripped out.

reply to this message

#412: Re: so

by Passa on 04/27/2006 02:43, refers to #410

While my 9250 has probs with the shader edition (i havent tested occlusion edition with the fix yet) my laptop has a radeon 7000 (it sometimes calls it a M6 depending on my drivers). it runs normally without shaders obviously, getting about 15fps average on metl3 and 30-40 fps on aard3.

ill post back here soon with my results with that ati fix disabled on the 9250.

reply to this message

#413: Re: so

by enigma_0Z on 04/27/2006 04:30, refers to #412

Yeah, try the occlusion edition, if the variable doesn't fix it, I can build you a linux version if you want...

You'd have to ask someone else for a windows version...

BTW: Is there anything that I can do to help coding Sauer? I'n not an _expert_ coder but I am fairly good, I'd like to be able to understand cube's code a bit more, but all of the macros get me confused...

reply to this message

#414: Re: so

by Aardappel_ on 04/27/2006 04:40, refers to #411

again, there are fundamental architectural differences between 9500 or above and whats below it. The 9500+ cards have shader model 2, below is 1.0 to 1.4, which is a big difference in capabilities.

reply to this message

#415: Re: so

by enigma_0Z on 04/27/2006 04:57, refers to #414

So does this mean that we have shaders in both linux and windows? (I'm just starting to drool for when I get my new laptop)...

reply to this message

#416: Re: so

by enigma_0Z on 04/27/2006 04:57, refers to #414

So does this mean that we have shaders in both linux and windows? (I'm just starting to drool for when I get my new laptop)...

reply to this message

#417: Re: so

by rancor on 04/27/2006 05:22, refers to #416

Very yes!

reply to this message

#418: Monster models increase the load significantly

by enigma_0Z on 04/27/2006 19:35

What: SP maps increase the load significatnly, FPS on SP maps (stsp1 as example) is ~15 in SP mode (with monsters), ~75-100 in mode 0

How: Play an SP map with an older video card, I guess... I don't know if it affects just me or not

When: Sauer Occlusion Edition, Ubuntu Linux, ATI Radeon 9000.

Details: I know that SP maps were running fine in the older versions. MP Edition in particular, ~25 FPS instead of 10. I'd at least expect similar performance, or a performance boost... ** HOWEVER ** the MP edition had the invisible hellpigs bug... If that matters.

reply to this message

#419: Re: Monster models increase the load significantly

by eihrul on 04/27/2006 20:57, refers to #418

Your card just is too old to support occlusion. Nothing we can do.

reply to this message

#420: Re: Monster models increase the load significantly

by enigma_0Z on 04/28/2006 04:12, refers to #419

Well, that's nice...

I'm just wondering if I can squeeze any more FPS out of it. I got (for comparision) ~20 fps in the MP edition

reply to this message

   Board Index