Debug vs. Release
by DIAG · in Torque Game Engine · 09/30/2004 (7:19 am) · 3 replies
Hey guys,
Ive been working with the release version of torque for the past while. However, I just noticed that when i try to run the same executable twice at the same time, the second one just crashes out without displaying anything. If i use the DEBUG version, the two start up just fine! Weird! Would anyone know some of the reasoning behind this????
Damien
Ive been working with the release version of torque for the past while. However, I just noticed that when i try to run the same executable twice at the same time, the second one just crashes out without displaying anything. If i use the DEBUG version, the two start up just fine! Weird! Would anyone know some of the reasoning behind this????
Damien
#2
In regards to:
09/30/2004 (9:49 am)
@Owen Ortmayer: We needed to run two instances on the same computer to test the loginpart of our build. That's not possible with the debugbuild, as the MySQL implementation breaks on that when compiling.In regards to:
Quote:
It doesnt really make sense to run two instances of the application on one machine. Except for testing purposes, in which case it makes more sense to use a DEBUG build.
#3
This is pretty nice actually, b/c the machine I'm on struggles when running 2 debug builds.
09/30/2004 (10:27 am)
I tried compiling with the call to Platform::excludeOtherInstances("TorqueTest") commented out and I am able to run 2 instances of a RELEASE build on my machine.This is pretty nice actually, b/c the machine I'm on struggles when running 2 debug builds.
Torque Owner Owen Ortmayer
The code for it is run in main.cc is you want to change it to allow yourself to run multiple RELEASE instances.
#if !defined(TORQUE_DEBUG) && !defined(INTERNAL_RELEASE) if(!Platform::excludeOtherInstances("TorqueTest")) return false; #endif