Game Development Community

DRL totally breaks rendering on 1.0.1[solved

by Marc Dreamora Schaerer · in Torque Game Engine Advanced · 07/27/2007 (8:27 am) · 3 replies

With the new drivers of NVidia and an 8800 GTS on WinXP SP2, enabling DRL totally breaks rendering.

I tried different versions of the driver (158.22, 162.12 & 162.18 the official @ EVGA).

The 162.12 / 162.18 ends with a smearing effect (the moving object have some kind of trail effect, DIFs are working correctly)

With 158.22 I get that massive graphic error fragments that it looks like my GPU was overclocked by 10% too much, at least thats where I last have seen that many errors. (only the top left area is rendered somewhere correctly, the rest looks like some other buffer fragments, no idea where they should come from)

162.18 is the currently most current WHQL certified NVidia driver

This happens with the version that has different bugfixes from this board applied as well as with Stock TGEA 1.0.1


Sidenote: TGEA is incapable of retrive the correct driver version. It assumes that driver version < 100 which does not hold.

EDIT:

Retested it now under different circumstances and the problem with the newer driver is, at least in the demos, bound to any kind of glow.

they shimmer through other objects rendered in front (with and without DRL activated)
They create a smearing trail effect with enabled DRL

#1
07/30/2007 (7:45 am)
It's working here, though we don't have an 8000 series to test on. Can you post a screen shot?
#2
07/30/2007 (8:32 am)
Sure, here is one, with the bugged space orc smearing effect.
Smearing Error

And a second one with disabled DRL showing the shimmer through error
Shimmer / Glow through Error

The error is visible on the pants.
Its hard to get it as it has to do with the rotation of the camera and the wandering of the shimmering elements on the ground and wall.

took me some time as I've not been around much lately.
#3
07/30/2007 (10:41 am)
Addition:

I found the cause for this problem.

Its caused by a "overpowered" NVidia driver settings.

"Override any application setting" for the antialias will cause the 2 bugs above. If you set it to enhance application settings, it will work as expected without any problems.

the used antialias does not make a difference, tested with 4 up to 16 / 16xQ