Bug Reports

by eihrul on 09/03/2008 01:41, 1175 messages, last message: 12/31/2023 08:39, 929888 views, last view: 05/21/2024 07:00

Please post your bug reports in here.

With your bug report, please submit the following information:

1) OS: Your operating system, i.e. Linux, Windows, or otherwise and what version you are using.

2) 3D card: The 3D card you are using. If you do not know, this is printed on the "Renderer:" line in the console when Sauerbraten starts up.

3) The edition of Sauerbraten you are using, i.e. Assassin edition, CVS as of a particular date, or otherwise.

4) Error information: If you are on Windows, a pop-up message showing filenames and line numbers should show up when Sauerbraten crashes; if possible, post a screenshot or a copy/paste of this. If on Linux, post a log of the startup info from the console, including relevant errors or any info you might have discovered. If on MacOS X, please post the crash log if applicable.

5) A description of the problem and how to reproduce it. Please give as much detail as possible on how someone can recreate the problem, in as certain terms as you can. If someone else can't reproduce the problem, it is unlikely he can fix it or tell you what is wrong.

   Board Index   

#1100: Sauerbraten hangs

by PowerKiller on 03/05/2014 08:56

I'm using Windows 8 pro with Media Center

My 3D card is GeForce 6150SE nForce 430/PCI/SSE2/3DNOW! (NVIDIA Corporation)

my Sauerbraten edition is Collect Edition

Bug - When i open sauerbraten.bat my sauerbraten hangs with black pointer and i can't move my mouse I'm stuck with black mouse and i have to power off my computer then restart again and when i again open sauerbraten the same problem happens again

reply to this message

#1101: Re: Sauerbraten hangs

by eihrul on 03/06/2014 10:08, refers to #1100

No idea. It sounds like the bug is in your video card driver. There is nothing much I can do, since nvidia almost always ignores these sorts of bug reports.

reply to this message

#1102: Re: Sauerbraten hangs

by PowerKiller on 03/06/2014 13:44, refers to #1101

And one thing the sytem hangs before sauerbraten.exe opens

reply to this message

#1103: ..

by Papriko on 03/10/2014 17:15

1. Ubuntu 12.04 Precise Pangolin, 64-bit

2. GeForce... Something, it is no graphics bug.

3. Collect Edition

4. No errors

5. It appears that my sauer does not create a logfile while running, at least I could not fine one. Searched my entire home folder for it (the sauer install itself is in my home directory too, since it is downloaded by hand and not from the packet repos)

reply to this message

#1104: Re: ..

by eihrul on 03/11/2014 13:26, refers to #1103

It's not supposed to create a log file by default, except on Windows.

Use -glog.txt option or similar in your sauerbraten_unix script.

reply to this message

#1105: Re: ..

by Papriko on 03/11/2014 14:55, refers to #1104

That explains a lot.
Anyways, it worked. Thank you!

reply to this message

#1106: ..

by Papriko on 09/29/2014 19:05

1. Ubuntu 12.04 Precise Pangolin, 64-bit

2. GeForce... Something, it is no graphics bug.

3. Collect Edition

4. No errors

5.
/echo (* "00" 1) = 0
/echo (* "01" 1) = 1
/echo (* "02" 1) = 2
/echo (* "03" 1) = 3
/echo (* "04" 1) = 4
/echo (* "05" 1) = 5
/echo (* "06" 1) = 6
/echo (* "07" 1) = 7
/echo (* "08" 1) = 0
/echo (* "09" 1) = 0

Why do most of those work as they are supposed to, just the last two suddenly return 0 again? If it were some conversion problem regarding the 0s, shouldn't it affect all of them and not just 08 and 09?

reply to this message

#1107: Re: ..

by eihrul on 09/29/2014 20:54, refers to #1106

Numbers prefixed with 0 are octal, not a bug, and must have digits in the range of 0-7 or else it stops parsing.

reply to this message

#1108: Re: ..

by Papriko on 09/29/2014 21:13, refers to #1107

Alright, thanks for the tip. Not really an error or bug, but is there also a function which forces numeric output to be octal/hex?

reply to this message

#1109: shader issues

by suicizer03 on 10/17/2014 00:08

1) Windows.
2) I'm rendering on a GeForce 8800 GT/PCIe/SSE2 with driver updated to 3.3.0
3) Collect Edition.
4) No error log.
5) The shaders and their respective settings are messed up when taking different resolutions.
For example, using the decalworld shader works perfectly for high resolutions (on my computer at least), but they stop being rendered on resolutions like 1024x768, 1280x800, 1280x720, 600x480, 1280x768 and anything lower than that.
It seems to matter also what size of decals you've used; one which is only 256x256 (calling up "cube.png" on a 128x128 texture for example) has not such problems, but 512x256 has (calling up "logo.png" on a 256x128 textures for example).
Anti-aliasing seems to have no effect, neither forcing to another rendering mode.
If you try to take your previous resolution after the one which doesn't work; the new resolution isn't showing off correctly also (like going from 640x480 to 1280x960). You have to start up Sauerbraten entirely.
Rendering fullscreen or windowed doesn't matter at all.
The pulseworld shader isn't working in GLSL rendering mode; no matter what resolution (neither fullscreen or windowed).

So is this a bug in the code or due the driver? Will it be fixed? Can I fix it on my own version? Please some answer.

reply to this message

#1110: Re: shader issues

by suicizer03 on 10/17/2014 00:10, refers to #1109

But a decal of 512x256 has issues being rendered with those resolutions or lower (calling up "logo.png" on a 256x128 textures for example).

reply to this message

#1111: Re: shader issues

by suicizer03 on 10/20/2014 00:06, refers to #1110

For those who want to experience it, put the next line within a map-cfg and select the textures;

setshader "decalworld"
texture 0 "jf1/jfwall.jpg"
texture d "../data/logo.png"

texture 0 "jf1/jfyellow.jpg"
texture d "../data/cube.png"

setshader "pulseworld"
setshaderparam "pulsecolor" 1 1 1
setshaderparam "pulsespeed" 0.5
texture 0 "jf1/jfflr.jpg"
texture 1 "jf1/jfrust.jpg"

reply to this message

#1112: Re: shader issues

by Pyccna on 11/01/2014 00:37, refers to #1111

The root cause might be because you're changing resolutions. What do you need to do that for anyway?

P.S, nice to know how decalworld works now!

reply to this message

#1113: Re: shader issues

by suicizer03 on 11/01/2014 01:04, refers to #1112

It also occurs when not changing the resolution; so loading right after start up.

reply to this message

#1114: Re: shader issues

by Pyccna on 11/01/2014 03:12, refers to #1113

You lost me now.
Most likely this is a driver issue.

reply to this message

#1115: Re: shader issues

by suicizer03 on 11/02/2014 17:10, refers to #1114

Doesn't seems so as I've tried it on my laptop with the very same results.

I'm rendering on a GeForce 610M/PCIe/SSE2 with a driver version of 4.3.0 on my laptop, using Windows 7 Home Premium also.

So is it an issue in the code or so??

reply to this message

#1116: Crashes with Mac OS X 10.10 Yosemite

by el_tars on 12/05/2014 03:43

1) Mac OS X 10.10 Yosemite

2) Intel Iris HD

3) Collect Edition

4) Sauerbraten crashes immediately upon launch. The default Mac error "Sauerbraten quit unexpectedly" appears.

reply to this message

#1117: ..

by Papriko on 12/13/2014 22:50

1. Ubuntu 12.04, 64-bit

2. NVidia GeForce GT 640

3. Collect

4. You apparently no longer collide with SP ents (boxes, barrels, platforms, elevators)

5. Try playing platform_demo or box_demo. Alternatively, try to play a SP map like lost and die because you suddenly phase through the platform into doom.

reply to this message

#1118: Re: ..

by Papriko on 12/13/2014 22:52, refers to #1117

Additional information: apparently those ents no longer collide with each other either.

reply to this message

#1119: Re: ..

by Papriko on 12/13/2014 22:59, refers to #1117

OOPSIE! Sorry, forget this! I messed up something in the source code! My fault XD

reply to this message

   Board Index