Fatal: bitstream.cc@194 error on debug only?
by Infinitum3D · in Torque Game Engine · 10/21/2008 (12:37 pm) · 21 replies
I tried editing the source, specifically player.cc among others, and now I get an error EVERYTIME.
Fatal : (c:\torque152\engine\core\bitstream.cc@194)
Out of range write
So I tried to restore my old player.cc file and got a successful build, but same error when I try to debug.
So I deleted the entire ENGINE folder and replaced it with my backup. Again a successful build. Again the Fatal error.
So I tried a fresh install of Torque. Opened the new solution. Successful build , Fatal error...
Did I mess up my compiler? (VisualC++2005EE)
If I just run the torqueDemo.exe, everything loads fine, and no console errors. I can MOD the game, but not make any source changes...
Help!
Tony
Fatal : (c:\torque152\engine\core\bitstream.cc@194)
Out of range write
So I tried to restore my old player.cc file and got a successful build, but same error when I try to debug.
So I deleted the entire ENGINE folder and replaced it with my backup. Again a successful build. Again the Fatal error.
So I tried a fresh install of Torque. Opened the new solution. Successful build , Fatal error...
Did I mess up my compiler? (VisualC++2005EE)
If I just run the torqueDemo.exe, everything loads fine, and no console errors. I can MOD the game, but not make any source changes...
Help!
Tony
Torque Owner Infinitum3D
It must have something to do with this one specific model because even if I take out Kork, and the elf girl, and only try to load this other PlaceHolder.dts with its .dsq's, I still get the error.
Short of throwing out the character model, are there any ways to get around this problem? Can't rember, but someone said I have to stay below 32 bits? Can I increase beyond the 32bits by upping it in the source somewhere or is that a resource killer?
Its just one model, so I can scrap it if need be. I was planning on replacing all my models with original ones in the future anyways, but I didn't want to buy a bunch of models now that will be outdated in five years (since my personal game will never been ready for at least five years, probably 10).
Thanks for any advice!
Tony