Game Development Community

Layering of tile layers problem on specific machines

by Richard McKinney · in Torque Game Builder · 10/10/2006 (12:01 pm) · 1 replies

Our game has been tested on about 200 different system configurations and this problem only appears on two of them. One is a P3 500 running Windows 98 with a Riva TNT2 (my minimum spec test machine) and the other is an Intel Celeron 1.0gHz laptop running XP with 256 meg of ram and a Trident CyberBlade XP Ai1 v6.4 video card.

We have a scene graph with a tile layer in it. There are additional objects (t2dStaticSprite and t2dAnimatedSprite) which get added to the scene graph, all on different layers. Everything looks fine on almost every machine and the objects can render on top of the tile layer, but on these two machines for some reason all of the objects are pushed off to the side and rendered almost as if 0,0 was the top left of the screen instead of the center.

The tile layer has a layer of 30. All other objects added to the scene have layers less than that so that they appear on top of it. When the tile layer's layer property gets set to less than the layer of any of the other objects in the scene, that object jumps back into place where it should be (eg: there are objects at layer 10, call %tileLayer.setLayer (<=10) and those objects at layer 10 then display in the correct position), so as long as it's being drawn on top of something it doesn't push that thing around.

None of the properties on any of the objects are changing while this is happening, so it's not like their positions are actually getting changed, they're just rendering in the wrong place. They are still set to what they should be.

If I add the tile layer to scene graph after the other objects, it has the opposite effect of pushing the tile layer off the screen while the other objects all render at the correct place. Also, if I delete the tile layer, everything else then renders where it's supposed to.

Every other scene graph in our game works fine. We're only using a tile layer in this one.
Any help on why this could be happening is appreciated. It's a very small percentage of machines to be happening on, but since it makes the game unplayable on those machines, I'd like to find a way to make it work for everyone if possible.

Thanks!
Richard

#1
10/12/2006 (1:00 pm)
Updated with specs on the second machine seeing this problem.