-=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- (c) WidthPadding Industries 1987 0|620|0 -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=-
SoCoder -> Snippet Home -> Misc

 
Evil Roy Ferguso
Created : 13 March 2009
Edited : 13 March 2009
Language : Blitz

Disable Desktop Compositing

Disable Vista/7's desktop compositing in your Blitz classic game.On
On many computers, Blitz games do not function properly with desktop compositing enabled on Vista or Windows 7. This (not-particularly-future-proof) function will disable compositing while your game is running, freeing the end-user from the tedious, difficult chore of right clicking an executable. Compositing will be re-enabled if appropriate when the game is exited. The function is a no-op on Windows XP and lower (unless somebody has an inappropriately named DLL), so it won't break your game if you use it.

Maybe this will be useful to somebody else with the same problem.

 

Comments
Friday, 13 March 2009, 19:23
Jayenkai
 		Never noticed these issues.. But then, I turned all that crap off, to be honest.
I'm using Good old Classic!

So, is this a nasty issue, or what?
Friday, 13 March 2009, 20:11
Evil Roy Ferguso
 		Fairly nasty.

A game that runs at a solid 60FPS on a 400MHz Celeron alternates between 15FPS and 50FPS on an up-to-date, though not "top of the line" computer affected by this issue. The slowdown would be bad enough, but the alternation means that games are remarkably jerky. Turning off desktop compositing makes the problem go away, so it's probably responsible.
Friday, 13 March 2009, 21:40
JL235
 		Plenty of (non-OpenGL) games don't suffer from this problem. So this might be a B3D issue, not a Vista one.

Has it been filled as a bug with Blitz Research Labs?
Friday, 13 March 2009, 22:06
Evil Roy Ferguso
 		Yes, it's definitely a B3D issue -- I meant that the bug occurs only under Vista, although I see my wording was muddled in my second post (the original is a bit closer). To date, BRL has not responded to any of the bug reports dealing with this issue, so it seems unlikely to be fixed.

It's especially noticeable in programs that draw to buffers other than the back buffer.