GLBasic forum

Main forum => Bug Reports => Topic started by: spacefractal on 2012-Mar-15

Title: Screen tear (again), but for Windows.
Post by: spacefractal on 2012-Mar-15
I in some month ago seen some screen tear for MacOS, but my friend also seen that issue with his ATI, which might have accour in one of the recently released glbasic. If he force the graphicsdriver to VSYNC on, its disappear.

for MacOS I use this code and works nice:

Code (glbasic) Select

FUNCTION enablevSync:
?IFDEF MACOSX
INLINE
SDL_GL_SetAttribute(16, 1);
ENDINLINE
?ENDIF

?IFDEF OSXUNI
INLINE
SDL_GL_SetAttribute(16, 1);
ENDINLINE
?ENDIF

ENDFUNCTION


If a adapt this code for PC, its I get a FATAL error.

PS. I does not see this issue on my PC at all, so its something odd and can been some driver issue or such (he have a ATI, i have a NVIDA card)?
Title: Re: Screen tear (again), but for Windows.
Post by: Kitty Hello on 2012-Mar-19
it's not easy. V11 will have it implemented. You must query the function using wglGetProcAddress...
Title: Re: Screen tear (again), but for Windows.
Post by: Kitty Hello on 2012-Sep-05
in V11, LIMITFPS has an optional parameter added for this.
Title: Re: Screen tear (again), but for Windows.
Post by: spacefractal on 2012-Sep-05
I have forgotten this post complety and have oversaw that, while that optiomal parameter should fix the LIMITFPS issue as well (etc LIMITFPS -1,1 skips timing, but wait for vsync). Its same thing :-D.