Tweet
With the release of the 5.21 drivers, Matrox fixed the issue of vsynch in their OpenGL ICD. With previous versions of the drivers, vsynch was always disabled. There has been a registry hack available to enable/disable vsynch for some time, but it had no affect on OGL, only D3D. Now, with 5.21, this hack will enable/disable vsynch for both D3D and OGL.
<A HREF="http://www.murc.ws/Utils/PD5RegHAcks.zip" target=_new>Registry Hacks</A>
One critical thing about these hacks that is often overlooked (and it is very, very easy to overlook), is that it depends on this hack being applied to the correct registry key. By design, the vsynch reg hack goes to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\Class\Display\0000\
Many people are finding that the registry hack is not having any affect on their performance. In many of these cases, that is because the registry key is incorrect. Often there are remnants of old drivers occupying the \0000 key, and the Matrox driver settings are residing in \0001 or \0002 (or whatever). Even running the Matrox uninstaller does not guarantee that all \000* will be cleared. Other video cards also use these keys, and the uninstaller does not always clear them all out.
So, there are two options.
The preferable option is to uninstall the drivers, boot into safe mode, edit the registry, and manually remove all \000* keys that remain in that section. Then re-install the drivers, and they will go to \0000, and the reg hacks (and other misc. utils that look for \0000) will work properly.
The quicker option is to determine which key the Matrox drivers are actually using (the highest number), and edit the registry hacks to apply to the appropriate key. This will not get other things like MGATweak though...
I guess the third option would be format c:, but I hate that, and would never want to suggest it over video drivers
Hope this helps get some of your speeds back up where you want them.
[This message has been edited by Kruzin (edited 09-03-1999).]
<A HREF="http://www.murc.ws/Utils/PD5RegHAcks.zip" target=_new>Registry Hacks</A>
One critical thing about these hacks that is often overlooked (and it is very, very easy to overlook), is that it depends on this hack being applied to the correct registry key. By design, the vsynch reg hack goes to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\Class\Display\0000\
Many people are finding that the registry hack is not having any affect on their performance. In many of these cases, that is because the registry key is incorrect. Often there are remnants of old drivers occupying the \0000 key, and the Matrox driver settings are residing in \0001 or \0002 (or whatever). Even running the Matrox uninstaller does not guarantee that all \000* will be cleared. Other video cards also use these keys, and the uninstaller does not always clear them all out.
So, there are two options.
The preferable option is to uninstall the drivers, boot into safe mode, edit the registry, and manually remove all \000* keys that remain in that section. Then re-install the drivers, and they will go to \0000, and the reg hacks (and other misc. utils that look for \0000) will work properly.
The quicker option is to determine which key the Matrox drivers are actually using (the highest number), and edit the registry hacks to apply to the appropriate key. This will not get other things like MGATweak though...
I guess the third option would be format c:, but I hate that, and would never want to suggest it over video drivers
Hope this helps get some of your speeds back up where you want them.
[This message has been edited by Kruzin (edited 09-03-1999).]
Comment