Game Development Community

Graphical and cutscenes issues

by Suharian Ramadi · in Torque Game Builder · 08/16/2011 (9:59 am) · 3 replies

i have been submit my game into game portal, and then, got some feedback/report:

1) Game launches with major graphical corruption on some systems
Description:
"This issue has been the most apparent on my HP 6530b laptop and has occurred on occasion in Vista on my Acer as well. It occurs most frequently if you quit in the middle of a Match 3 level - the last played level will appear, partially, on the game window that pops up on launch, before the game loads in full screen."

2) Cutscenes are often slow, animation appears to "stutter"
Description:
"On certain machines, the cutscenes appear to "stutter" when playing and will flash occasionally. This was most apparent on the HP 6530b laptop and in Vista 32 on my Acer. Cutscenes played perfectly on the HP"

the second one, cutscene made in Theora files..

anyone can help me... :)

#1
08/16/2011 (10:58 am)
1. I wouldn't call that a 'major graphical corruption'. It's just contents of video memory displayed before engine begins rendering frames. You'll have to add some clearing code to the engine where GL context is created.

2. TGB has some issues with streaming stuff, most of casual machines will be unable to process fullscreen videos fast enough. Make your videos smaller, decrease framerate.

3. Test your game on different computers, wherever you can, pay more attention to the results with the slower ones. Games made with TGB are rarely played on high-end desktops.
#2
08/16/2011 (11:36 pm)
1. this issue really hard to reproduce in my computer... so, with this following code, can i make what you mean ?

function endGame()
{	
   sceneWindow2D.endLevel();
   moveMap.pop();
   moveMap.delete();
	
   flushTextureCache();
   clearTextureHolds();
}


2. my video is 800x560 30fps... i'll try to decrease its framerate.
#3
08/17/2011 (12:35 am)
No. You have to clear the screen upon startup, right after game window is created. Not sure if this can be done through script, normally it should be a part of OpenGL initialization code within engine.

Also, it is not a bug. It's how your video card/driver designed to do it's job. If it does not happen to you, you will not be able to reproduce it.