Optimized? TBE versus C++ NET 2003, reduced framerate

#1 I may be completely wrong on this, but doesnt .NET produce interpreted code which then uses a JIT compiler at runtime, instead of compiled code? I thought I remembered reading this somewhere.

There may also be settings in your project options to set optimizations in .NET to allow the use of specialized instruction sets like MMX and SSE. These options were probably preset in TBE for torque, but wouldnt be in a .NET project. The other thing I would check is the graphic libraries that .NET is trying to use. Are they the same libs that TBE was using? Just a few guesses on my part.

#2 The .NET framework is bytecode interpreted in many areas. But the compiler itself can produce non-.NET code just fine.

#3 2 things to check, first and foremost a the top it will tell you which kind of build you want to do a debug or final, debug will greatly reduce framerate.

Also you can DL the VS 2003 optimized compiler and replace a few files from there to your install and viola you have the real optimizing compiler.

#4 You're only using bytecode if you're using Managed C++ or C# or something. If you got Torque to compile at all, you're not doing that.

#5 Thanks much for the quick replies. It is building tourque_debug.exe, so I assume that it is building the debug version (not final). How would I change the settings in C++ NET so that it would compile a final version?

Also, Jonathan made a point I didn't investigate. There probably are project setting that are not set (versus those preset in TBE). This is something I'll check shortly. Same with the graphics libraries: I believe they are the same but I will check this.

Thanks again for the help.

#6 In the target drop-down, change it from debug to release.

#7 That did it, David. I changed to Release, compiled, runs great now. Thanks!

#8 I thought the version that came with books was some form of a limited compiler with less that superior (or none at all) optimization...

-Ron

#9 @Ron

While I'm not sure what version comes with the book, you can download the optimized compiler and setup VS 2003 to use it as David stated.

#10 The book version simply doesn't include many of the optimization algorithms. You can still access debug and release information (as a compiler without debug options is rather worthless). You just don't get the optimizations. MS did release a download of it, though. I'm not sure about the specifics of the licensing.

#11 C++.NET 2003 Standard does not come with the optimizing compiler. Only C++.NEt 2003 Professional does (which only comes in the Visual Studio.Net Professional package). Though you can still do as David stated.