FreeBSD user problem

[nomoo]

Hello.
On the first box with gf 4200ti vdrift runs good but it doesn't support shaders, today i've tried to run it on another computer with 8600gt.

It said something like this:

Code:

EXCEPTION: src/graphics.cpp, line 1072:  OpenGL error on FBO end

What's wrong?

P.S. thanks for a great project, its the best autosim for *nix nowadays..

[joevenzon]

Can you try the release now in sourceforge (or SVN R1910 or higher)?

[nomoo]

i've got 1913

uname -a
FreeBSD pcbsd 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #2: Wed Nov 7 11:08:55 EST 2007 root@pcbsd:/usr/obj/usr/src/sys/PCBSD-SMP i386

nvidia driver: 100.14.19

[onety-three]

Same here on Kubuntu Gutsy with a Geforce FX 5700, driver version 100.14.19 (same as nomoo). It behaves like this in the recent release as well as with current SVN code (but with the release's data).

With RC1 the game ran fine although none of the shader effects worked; I can't remember exactly anymore, but in the console there was a warning or error about the "for" statement not being supported and unrolling not being possible.
I can get you the exact message if you want me to.

[edit]
The SVN data finally finished downloading, no change in behaviour.
And I noticed I still get the message I got with RC1... Strange how I didn't see it the last time.

(42) error C5013 profile does not support "for" statements and "for" could not be unrolled.

And just in case
Card supports drawbuf1 auxbuf4 antialiasing anisotropy8 cubemapping shaders multitexturing16(4) texture_rectangle depth_texture shadow framebuffer_objects
Card does not support

[joevenzon]

I meant to make all of the OpenGL errors result in debug prints instead of exceptions but I guess I missed one... try R1914.

As for the "shader profile does not support" message, that's due to your geforce FX not supporting (and my code not detecting your card doesn't support) the more advanced shaders that kick in when shadows are enabled. Try disabling shadows.

[thelusiv]

onety-three, unrolling for loops is a compiler optimization. When are you getting this message? Maybe you would have better luck with the release option set to 1 when you run scons. This will turn off compiler optimization and perhaps avoid this problem.

[nomoo]

R1914 runs printing "OpenGL error on FBO end",
menu isn't full-colored (?)
http://pic.rapidshare.ru/533170/
game with max graphics configuration runs without shaders (as far as i see), no shadows..

After recompilation with 'release=1' vdrift crashes with:

Code:

EXCEPTION: src/shader.cpp, line 311:  Error on parameter upload to shader "blurpass" for "prev_modelviewproj"

[onety-three]

thelusiv: I guess Joe is right concerning the message; release=1 doesn't seem to change the behaviour.

Joe: I'm a bit surprised the shaders won't work with this card as I didn't have any problems like that anywhere else - but then again I've more or less quit the gaming upgrade loop three years ago.

It's like nomoo wrote;
revision 1914 gets me to the menu again, but I get this message all the time:

OpenGL error on FBO end

When trying to start a race with shadows enabled it crashes printing this message:

EXCEPTION: src/shader.cpp, line 311: Error on parameter upload to shader "blurpass" for "prev_modelviewproj"

With shadows disabled it runs. The switches for shaders and/or motion blur seem to be inverted as the game crashes again if I switch them off, too.

[thelusiv]

R1914 runs printing "OpenGL error on FBO end",
menu isn't full-colored (?)
http://pic.rapidshare.ru/533170/
game with max graphics configuration runs without shaders (as far as i see), no shadows..

After recompilation with 'release=1' vdrift crashes with:

Code:

EXCEPTION: src/shader.cpp, line 311:  Error on parameter upload to shader "blurpass" for "prev_modelviewproj"

That's a strange error, I don't know much about shader.cpp, maybe Joe can provide some more insight.

Your link doesn't work for me.

[joevenzon]

onety-three, unrolling for loops is a compiler optimization

Yes, but in this case it's referring to the GPU shader compilation (which happens at runtime by the graphics card driver). Compiling VDrift source with release=1 won't affect this. nomoo, the reason you saw a change is probably because changes to shader or shadow or motionblur settings only take effect after quitting all the way out of VDrift and restarting it, which we should probably make explicit in the game whenever you change those settings.

I'm a bit surprised the shaders won't work with this card as I didn't have any problems like that anywhere else

Unfortunately the geforce fx line has pretty limited shader support. Right now shadows are either complex or off... I could try to add a simpler mode that would perform better and work on FX cards (but it wouldn't look as pretty).

When trying to start a race with shadows enabled it crashes printing this message:

EXCEPTION: src/shader.cpp, line 311: Error on parameter upload to shader "blurpass" for "prev_modelviewproj"

The blurpass shader should only be getting executed if you have motion blur turned on. My initial guess is that the error you're getting about the parameter upload is probably because your card doesn't support enough variables being sent over to send over a big 4x4 floating point matrix -- but that doesn't make sense if nomoo has the same problem with an 8-series card.

menu isn't full-colored (?)
http://pic.rapidshare.ru/533170/

The link is 404... can you post it again?

[nomoo]

onety-three, unrolling for loops is a compiler optimization

Yes, but in this case it's referring to the GPU shader compilation (which happens at runtime by the graphics card driver). Compiling VDrift source with release=1 won't affect this. nomoo, the reason you saw a change is probably because changes to shader or shadow or motionblur settings only take effect after quitting all the way out of VDrift and restarting it, which we should probably make explicit in the game whenever you change those settings.

Thanks for rather detailed explanation.

menu isn't full-colored (?)
http://pic.rapidshare.ru/533170/

The link is 404... can you post it again?

http://pic.rapidshare.ru/533170 Got it?

[onety-three]

Yes, the screenshot link works now.
This problem doesn't occur on my system, the menu looks fine.

[nomoo]

I've got this error and color issue only with shaders+motion blur+shadows turned on.
motion blur+shadows: no car shadow, everything seems dim, i didn't see any blur
http://pic.rapidshare.ru/535537

shaders only: it's more "sun" and that's all..

After every option changing i've restarted vdrift.

[joevenzon]

Hmm, one more clarification: shaders need to be turned on for motion blur or shadows to work; otherwise they are quietly disabled. So, to summarize, there are basically 5 rendering modes:

1) shaders disabled
2) shaders enabled, blur disabled, shadows disabled
3) shaders enabled, blur enabled, shadows disabled
4) shaders enabled, blur disabled, shadows enabled
5) shaders enabled, blur enabled, shadows enabled

I took some screenshots to show the differences:
1) shaders disabled
http://vdrift.net/Gallery/media.php?f=0&...1123044577

2) shaders enabled, shadows disabled
http://vdrift.net/Gallery/media.php?f=0&...1123047720

4) shaders enabled, shadows enabled
http://vdrift.net/Gallery/media.php?f=0&...1123050320

3 looks identical to 2 and 5 looks identical to 4 when not moving so I didn't include screenshots for those.

In the http://pic.rapidshare.ru/535537 screenshot the error message you were getting disables shaders, which is why it looks like #1, above.

[nomoo]

Thanks a lot for shots, they are so good-looking, mm
So what we have to do? or just wait?