User panel stuff on forum
  8 posts on 1 page  1
Client Talk
2007-09-27, 07:35
Moderator
383 posts

Registered:
Jan 2006
Ati catalyst 7.9.
DirectX 10.
Microsoft Vista 64bit.
Latest nquake.

Result:
http://b1aze.com/files/ezquake001.jpg

http://b1aze.com/files/ezquake002.jpg


Any advices?
With best wishes, B1aze.
2007-09-27, 08:41
Member
628 posts

Registered:
Jan 2006
I am maybe dumb, but i don't think vista handles opengl "(that well)" and are using dx10 drivers insteed?
2007-09-27, 09:22
Moderator
383 posts

Registered:
Jan 2006
I had no troubles when used Vista+dx10+nvidia.
And according to Ati press releases, they support opengl for vista.
With best wishes, B1aze.
2007-09-27, 09:35
Member
271 posts

Registered:
Feb 2006
phrenic wrote:
I am maybe dumb, but i don't think vista handles opengl "(that well)" and are using dx10 drivers insteed?

Depends if your vendor actually supplies drivers or not.

The rest of us already upgraded to an earlier version of windows.

When I briefly had vista on my laptop with nvidia 5400 go, fte+opengl ran fine. it was d3d apps that randomly went pure black and didn't recover even after restarting them.
I then upgraded to windows 2000, but had great dificulty finding working drivers.
Seriously, Linux has better driver support these days.

Looks like issues with the depth buffer not being cleared, considering that the centerprint text has no problems appearing.
I'm not sure why the status bar has a nice clear bit around it.

I assume you've already tried toggling the value of gl_ztrick? If not, try doing it. On modern hardware, a value of 0 typically gives better performance, with 1 as the default in ezquake. Toggle it, see if anything magically gets fixed.

I've not tried ati drivers myself in vista, so I'm probably going to be compleatly wrong here. Aaaanyway, if you're really lucky, you might have a control panel thingie for your display settings. If you're lucky, you might find some setting to force the depth buffer precision, which might help. Alternativly, you could find that enabling antialiasing will help too. Then again, you might also find that Vista is such a pile of crap that the drivers are no longer able to support such overrides.
I believe that ezquake uses a stencil buffer, while fuhquake does not. Thus, switching engines might fix it (wether then engine is written correctly or not). You could also try FTE and tell it to use antialiasing in the engine. Just anything to change the number of different planes in the video/depth/samples/stencils buffer.
If you're still stuck, then you might be lucky enough to find a version of FTE that has d3d support, but beware that those builds are quirky, and d3d is currently broken in the FTE source tree.
you may even have to wait it out and just constantly keep updating your video drivers until it finally works correctly. Good luck if you have a laptop chipset. :/

But even so, Vista is such a pile of poo that you'll have inconsistant framerates whatever you do. Linux easily has higher framerates.

Apparently, Vista no longer has 3d hardware acceleration of DirectSound either (not that quake uses that anyway).
moo
2007-09-27, 10:14
Member
75 posts

Registered:
May 2006
I doubt he's getting 241 fps with OpenGL calls getting translated to DirectX calls... Here's som articles about OpenGL on vista, a lot of rumours are going around about it:
http://www.opengl.org/pipeline/article/vol003_7/
http://www.opengl.org/pipeline/article/vol003_9/

Quote:
OpenGL hardware acceleration is handled in exactly the same way in Windows XP and Windows Vista - through an Installable Client Driver (ICD) provided by graphics card manufacturers. Without an OpenGL ICD installed, Windows XP and Windows Vista both revert to rendering OpenGL in software on the CPU rather than using GPU acceleration.

Basically, if there's a problem, it's because the OpenGL drivers for your particular gfx card are dodgy. The driver model has completly changed, so they are less stable/tested than the XP ones. Bugs like these are probably due to ezquake doing something that the new drivers handles a bit different than on XP. Just like with the Intel 9xx OpenGL drivers on XP not allowing you to write directly to the front buffer, when pretty much every other card does.
2007-09-27, 10:17
Member
75 posts

Registered:
May 2006
Spike wrote:
I assume you've already tried toggling the value of gl_ztrick? If not, try doing it. On modern hardware, a value of 0 typically gives better performance, with 1 as the default in ezquake. Toggle it, see if anything magically gets fixed.

Actually, this has now been changed to 0 by default, cause of all the bugs that are caused when not clearing the depth buffer.
2007-09-27, 10:50
Moderator
383 posts

Registered:
Jan 2006
toggle gl_ztrick to 0 helped me .
Thank you!
With best wishes, B1aze.
2007-10-10, 00:23
Member
47 posts

Registered:
Feb 2007
gl_ztrick 0!!! all the way!
  8 posts on 1 page  1