Game Development Community

Eeeee, it's an InvalidOperationException! Run, Run, Baby.Run()

by Zilla · in Torque X Platformer Kit · 06/25/2008 (3:15 am) · 4 replies

I am experimenting with XNA and TorqueX 2.0 on a Asus Eee PC 900.

Everything works fine (Tankbuster etc.) except the Platformer Kit.
The build is o.k. but I get the following Debug Error:

InvalidOperationException: This device does not support 32-bit-indices. Use IndexElementSize.SixteenBits or a type that has a size of two bytes.

The error occurs at the follwing lines:

GarageGames.Torque.PlatformerDemo.Game game = new GarageGames.Torque.PlatformerDemo.Game();
game.Run();

I realized that all the other projects that do not produce this exception have another approach for game.Run();
NextNext Thread
PrevPrevious Thread
More from Torque X Platformer Kit


Associate John Kanalakis
EnvyGames
#1
06/25/2008 (8:28 am)
Since the other games work, but not the Platformer Kit, how about comparing the TorqueSettings.xml file. I'm guessing that one of those settings, like is set differently between the demos and the Platformer Kit. If that doesn't do it, try creating a new 2D game that has a basic tilemap. Maybe the graphics card within the Asus isn't happy about how tilemaps are being drawn.

John K.

Torque Owner Zilla
#2
06/25/2008 (2:27 pm)
Quote:try creating a new 2D game that has a basic tilemap
Exactly! John, you are a genius! As soon as I create a tilemap in the starter game 2d, this error will occur again.

Quote: is set differently between the demos and the Platformer Kit
Unfortunately, SimulateFences = true or false will produce this error.

I assume because this is a device dependent error (Asus display), there will be no solution except to avoid tiles when I work on the Eee?

Torque Owner Zilla
#3
06/30/2008 (3:18 am)
Quote:there will be no solution except to avoid tiles when I work on the Eee?
1. Does anybody have a better idea?

2. Besides: What is doing? Setting it true or false didn't make any difference.

Torque Owner Robert Finnie
#4
10/21/2008 (6:38 am)
Im getting exactly the same error on my lenovo laptop...
any fixes for this problem yet?