Ok I have done some further investigation into the problems I am having. I have set some -d handles, that enable/disable the physics within my game. Also running the game on the target platform in a window, I find that it is not just locking up the computer, but is actually generating an invalid instruction.

I don't know if this means anything to anyone, but here is that error anyway.

Code:

3DGS_6_23 executed an invalid instruction in
module 3DGS_6_23.EXE at 0167:004eacee.
Registers:
EAX=44e1d271 CS=0167 EIP=004eacee EFLGS=00010203
EBX=028a1cf8 SS=016f ESP=01bef494 EBP=028a1c98
ECX=028a1be0 DS=016f ESI=028a1cec FS=2fd7
EDX=44c6d275 ES=016f EDI=028a1d04 GS=0000
Bytes at CS:EIP:
db c1 db f2 db c2 d9 5c 24 14 de d9 d9 44 24 14 
Stack dump:
035aa594 028a1be0 00000008 08471af0 006b4e20 03bb9d6c 44e1d271 44c6d275 44c619e3 0000000c 0000b38c 0044c1cd 00000000 3d0a0c4a 01bef634 03b69c44


My real question is this due to poor code on my behalf, a bug in the physics engine, the solver 256MB that Ventilator mentions or something else?

The Target Platform is a Celeron 900Hmz 256MB Micro-PC (Just means small).

The Art of Conversation is dead : Discuss