Game Development Community

Screen corruption issue that got my game rejected

by Amjad Yahya · in Torque Game Builder · 05/31/2013 (3:42 am) · 9 replies

I have submit my game to Bigfishgames.com a while ago and they just got back to me with this issues that need to be addressed before they could release the game (game was built using TGB 1.7.5 pro):

The game screen corrupts when launched on XP
Description: When the game is launched, the screen will appear corrupted for a moment before going to the big fish splash screen. If the game had been launched previously, the last image on the screen before the game had been closed will display. This image might also be corrputed.

screen shot:


s14.postimg.org/ucv7tla1t/scr_Shot.jpg

I never encountered this problem on my PC (I'm using XP, SP3) but the testers at bigfishgames.com did, I have no idea how to fix this, please help.

#1
05/31/2013 (6:50 am)
Did they tell you what graphics hardware they're running on? Exact version of Windows? Any really useful information? It sounds like they think "a picture is worth a thousand words" but most bugs take more than a thousand words to get the whole picture. If they didn't give you full information bug them for it - if they did, pass it on to make it easier for everyone to help.

For the record, I've been using Torque for almost 10 years and I've never seen this issue. Across TGE, TGEA, TGB (1.5 and later) and T3D - and TGE is probably closest to TGB's rendering code.
#2
05/31/2013 (6:54 am)
Never seen this in TGE either and I'm also a long time user. Was it reproducable? Looks like a driver issue to me.
#3
05/31/2013 (9:22 am)
My bad, I forgot to post information on the video card and exact version, It's just I was so shocked to learn that TGB can do such corruption, knowing that the system on which I was developing the game is XP and I never seen such a thing too. Anyways, here is the info:

System Model: HP Compaq 6530b (FN025UT#ABA) (also weird because my system is also an HP).
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.130107-0416).
Processor: Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz (2 CPUs)
Memory: 2972MB RAM
DxDiag Version: 5.03.2600.5512 32bit Unicode
Card name: Mobile Intel(R) 4 Series Express Chipset Family
Display Memory: 128.0 MB
Chip type: Mobile Intel(R) 4 Series Express Chipset Family
DAC type: Internal
Monitor: Plug and Play Monitor

There was loads of other info, but I've chosen the most relevant.
I hope this will help.
Thanks.
#4
05/31/2013 (9:49 am)
Quote:Display Memory: 128.0 MB

Is it just me, or does this seem like a really small number?
#5
05/31/2013 (6:38 pm)
Yes, Mobil Intel 4 Series Express Chipset Family says it all - Big Fish is aiming for an audience with small-fry hardware. I think they may actually own the last functional card of that lousy line....

You could try clearing the screen to black immediately on launch and as the final act before exiting, hopefully that would at least make the corruption invisible.

I love how "the game screen is corrupted when launched on XP" - not "the game screen is corrupted when launched on ancient, crappy hardware." Even players with older machines are unlikely to have that old, busted-ass mobile chipset.
#6
06/01/2013 (4:10 am)
Thanks guys. You know, it's easier to blame others for your crappy hardware... BFG aims people with an age of 35 and above, so that might explain the ancient hardware.

I guess I will try to render a black screen on launch and exit.
#7
06/01/2013 (6:48 am)
BFG is really going out on a limb with that claim. It's a mobile chipset, probably rare as hell on an actual PC - did they tell you what the market penetration was on that particular video controller? I'm 45 and I've never owned one of those. Ever. And that issue might go away if they go to Intel and download their latest drivers for that series instead of using the latest drivers from the card manufacturer.

They just don't want to have to explain to someone how to upgrade drivers.
#8
06/01/2013 (11:48 pm)
@Richard, I appreciate your input.

I have used a "resetSceneGraph()" function on launch and exit and submitted the game back to BGF. Let's wait and see what happens.
#9
06/08/2013 (8:19 am)
I ran into this issue with my game when working on it. It's been quite a while, but I think I fixed it by either removing just about everything from the datablock.cs, to load up later in the process... or I added a forced redraw after the canvas was initially loaded up.