Reply 80 of 89, by dr.zeissler
TurbiGL is better than native Ogl-ICD ?
Retro-Gamer 😀 ...on different machines
TurbiGL is better than native Ogl-ICD ?
Retro-Gamer 😀 ...on different machines
For Quake-engine games - yes.
I must be some kind of standard: the anonymous gangbanger of the 21st century.
The Serpent Rider wrote on 2023-09-15, 12:16:For Quake-engine games - yes.
thought it was a slow D3D OGL wrapper...
Retro-Gamer 😀 ...on different machines
dr.zeissler wrote on 2023-09-15, 14:27:thought it was a slow D3D OGL wrapper...
No, TurboGL is pretty good on G400 cards in supported games.
Here are some period correct benchmarks from Anandtech.
Joseph_Joestar wrote on 2023-09-15, 14:38:dr.zeissler wrote on 2023-09-15, 14:27:thought it was a slow D3D OGL wrapper...
No, TurboGL is pretty good on G400 cards in supported games.
Here are some period correct benchmarks from Anandtech.
pretty interesting....some games that support opengl and d3d work bad on opengl on G550.
so in short, any use of turbo gl on g550?
Retro-Gamer 😀 ...on different machines
dr.zeissler wrote on 2023-09-15, 16:30:so in short, any use of turbo gl on g550?
Don't have one, so I can't really say.
I do vaguely remember that TurboGL enabled drivers (5.52 and such) on a G400 seemed faster in Quake games than the latest official driver version for that card which had full OpenGL ICD.
It's possible TurboGL is faster because of reduced image quality. People didn't really look closely back then.
Also, G400 had some early variations that weren't capable of 4X. Maybe that could trip up a 1.5v motherboard.
http://www.murc.ws/showthread.php?22558-What- … 0-MAX-Revisions
TurboGL is Win9x, currently I have G550 and Win2k installed. I had 5.84 installed, now went down to 5.71 (first G550 support)
this 5.71 seems good in D3D but very slow in OGL. I upgraded to 5.72 which is much better...seems to have nearly doubled in ssam1 from 5.71 to 5.72.
Init-dialog is broken on 5.7x on Retro-Remakes of old Cracktros but it seems that vsync issue is still present. seems to be never got fixed, but older versions tend to be smoother...as I saw in gunman intro.
I am using DX7 because more is not needed.
Retro-Gamer 😀 ...on different machines
dr.zeissler wrote on 2023-09-15, 21:23:... it seems that vsync issue is still present. seems to be never got fixed,.....
Just to clear things up about VSYNC: […]
Just to clear things up about VSYNC:
Yes, there is a way to turn VSYNC off, but it is a little tricky. Hopefully we'll see something in Matrox's powerdesk soon to allow people to do it easily!
Be warned, this requires you to mess with your registry, so only do this if you are comfortable with the registry and hacking with your computer!
Traditionally, and according to the "swapinterval" OpenGL extension, applications (and games) must decide whether or not to use VSYNC. Unfortunately, many games choose incorrectly, so Matrox and many other companies force VSYNC off for performance reasons, probably because people running benchmarks are so ruthless and every fps counts!
There are two variables to consider: 1. Does VSYNC default to ON or OFF, and 2. Whether or not the ICD allows the app to change this.
According to the OpenGL spec, vendors should do the following:
1. VSYNC defaults to ON
2. Applications MAY change it.By default, Matrox's ICD does not behave this way. Instead they do this:
1. VSYNC defaults to OFF
2. Applications MAY NOT change it.But the good news is you can change this in the registry!
[Here is the good stuff]
The path for Windows NT/2000 is:
HKLM\SYSTEM\CurrentControlSet\Services\mga64\Devic e0
For Win95/98 it is:
HKLM\SOFTWARE\Matrox\Powerdesk\Current Settings
The key to control "1. Does VSYNC default to on or off", is User3D.SwapIntervalExtFlags To default to VSYNC ON, use DWORD value 1. To defualt to VSYNC OFF, use DWORD value 9.
The key to control "2. May the application or game change this", is User3D.SwapIntervalExtEnable To allow applications to choose VSYNC or no-VSYNC, set this to 1. To force it either on or off (depending on how you set the above flag), set this to 0.
If you want to enforce _correct_ OpenGL behaviour (unlike how the driver ships), use these settings:
User3D.SwapIntervalExtFlags = 1
User3D.SwapIntervalExtEnable = 1
Retro-Gamer 😀 ...on different machines
Tested these entries on G550 Win2k and it did not work for OpenGL. D3D vsync worked when forcing via mga-tweaking-tool, but OpenGL still no vsync.
Retro-Gamer 😀 ...on different machines