This is an odd question, I know, but is there any difference at all between executing a project in VS2005 verses running the .exe directly in the /bin folder?
I would have said no myself, but I notice tonight if I run my project within VS, all orxOBJECT elements are fine.
If I run the .exe directly, I notice some of my minor elements lose their position values and stick to 0,0,0.
It's not a big deal, I can fix this stuff up probably but I'd like to know why it would be different. I can't see how it could be. A pathing thing? The initial positions being picked up in the config perhaps?
The debug logs generated between the two execution methods were identical.
If it's none of these, I'm all for some printf (or orxLOG, in this case! ) debugging!
I'll do some orxLOG outputs and pinpoint the difference. I'll report back when I have something.
I'll have to find out how to enable that as a warning in VS.
You know, in my day, we used truckloads of uninitialised variables and it didn't hurt us a bit. We carried them to school, uphill, both ways.
There's probably a warning to enable in VS, but you need to check MSDN to find its number. If it were me, I'd go with CppCheck which is a great static code analysis tool which will find much more issues than VS's compiler.
*cough* erm... sorry, vs2008 and vs2010 also have considerably better error/warning/whatnot handling, just curious, is there any particular reason you're sticking with 2005?
vs2010 spends too much time contemplating it's own navel, and vs2008... I don't like it's startup image. Kidding of course. I'll eventually use vs2008 more, but not vs2010 though.
(*edit* dang I used the word "drive" a lot )
Still, to each their own I suppose I'd love to have vs2010's interface (not sure why, just like it... go figure) with LLVM and Clang's compiler&errors, and N-brain's collaborative ide tools... -that- would be bliss ... too bad n-brain's now dead, and Microsoft are infested with the 'not invented here' syndrome ... ahh, dreams and their crushing defeats