BUG: RenderCollisionBounds freezes screen
by Frederic · in Torque X 2D · 08/15/2007 (1:04 pm) · 5 replies
When a game object's T2DCollisionComponent has RenderCollisionBounds enabled, the drawing system seems to freeze when the object collides with another game object.
In fact, it is sufficient to turn on RenderCollisionBounds some time after a collision happened to let the screen freeze.
The drawing system seems to behave normally again when RenderCollisionBounds is disabled, e.g. in a routine registered for listening to a key press as the keyboard event handling is not affected by this bug.
BTW: The open beta feedback forum is still active - is TorqueX already a final or still a beta version?
In fact, it is sufficient to turn on RenderCollisionBounds some time after a collision happened to let the screen freeze.
The drawing system seems to behave normally again when RenderCollisionBounds is disabled, e.g. in a routine registered for listening to a key press as the keyboard event handling is not affected by this bug.
BTW: The open beta feedback forum is still active - is TorqueX already a final or still a beta version?
#2
Thanks for the beta <-> final information, I was wondering about it because Torque X is still presented as beta on the GarageGames Product site.
08/16/2007 (5:02 am)
By "freeze" I mean that there is no drawing to the screen anymore. When you drag another Windows window over the "freezing" window, the "freezing" windows keeps the other window's traces and does not show the game contents.Thanks for the beta <-> final information, I was wondering about it because Torque X is still presented as beta on the GarageGames Product site.
#3
08/16/2007 (12:49 pm)
Hmm, that is strange. I've never had a freeze like that occur. Does this happen right out of the box with something like the StarterGame template and a simple object with collision bounds rendering turned on and have you tested it on multiple systems? 
#4
08/16/2007 (1:02 pm)
I have never had my game freeze and I use rendercollisionbounds all the time.
#5
Update: I ran the binary on another system and it worked just fine.
I tried to update my graphics drivers, but it didn't help. I will try to install another graphics card next week (the current one is an ATI on-board solution). Does anyone know what else could be the problem?
08/16/2007 (1:11 pm)
I tested it with the starter game template. I added a second object using TXB, turned RenderCollisionBounds on and the drawing system hangs as soon as a collision occurs.Update: I ran the binary on another system and it worked just fine.
I tried to update my graphics drivers, but it didn't help. I will try to install another graphics card next week (the current one is an ATI on-board solution). Does anyone know what else could be the problem?
Torque Owner Kzoink
TorqueX is 1.0 and the Open Beta Feedback forum should probably be either archived and another feedback forum created or renamed to remove beta from the title.