|
|
#1 | |
|
Registered User
Join Date: Mar 2003
Location: Berlin, Germany
Posts: 17
|
Hi,
till now I have been using the following hack in an application to achieve best possible v-syncing export __GL_VSYNC_TO_BLANK=0 in app I was calling glXGetVideoSyncSGI(&nCounter); before call to glXSwapbuffers. This constellation did a great job in getting smooth motion in full-field motions inside a heavily textured cylinder ... Now, after installing 4496 the application gets stalled when calling glXGetVideoSync Any idea how to bypass this? using export __GL_VSYNC_TO_BLANK=1 does not do the job at the same quality which I had before ... hartwig |
|
|
|
|
|
|
#2 | |
|
Registered User
Join Date: Sep 2003
Posts: 1
|
Hi!
I just ran into the same problem that my application stalls whenever 'glXGetVideoSyncSGI' is called. Have you already found a solution to this problem. Stefan |
|
|
|
|
|
|
#3 |
|
Registered User
Join Date: Mar 2003
Location: Berlin, Germany
Posts: 17
|
Hi Stefan,
I found no solution so far. What I did is to remove the call to glxGetVideoSyncSGI and activated export __GL_SYNC_TO_VBLANK=1 This is working reasonable well with the latest driver on the FX 5900 (guess might do on any FX), however for "older" nvidia cards using the latest driver I found no solution, since any motion given the above solution is jerky ... For Ti4800 based or less I reverted to previous version of driver ... hartwig |
|
|
|
![]() |
| Thread Tools | |
|
|