Running 2 TGE applications together

#1 You could give each application its own lock, but they still might collide on the output directory, since on unix all torque apps store output dsos in ~/.garagegames/torqueDemo by default.

So if you change the lock name for one of the applications you should also change the default output directory. The path is defined in one of the header files, can't remember which one (maybe platformX86UNIX.h)

On linux, You can also run the executable with -nohomedir. it will then write its output files out to the executable working directory in the same way as windows.

You can also recompile with the NO_FILE_REDIRECT flag (see conf.UNIX.mk) to permanently turn off file redirection to the home directory.

If the lock stuff is really bothering you, you can comment out the call to platform::excludeOtherInstances, which happens when canvas is created I think.

Other than the files colliding, there shouldn't be any issues with two Torque apps running at same time. Your opengl driver might prevent you from having two application windows open. But if so, it sucks.

#2 I commented out the content of platform::excludeOtherInstances in the ~/TGE/engine/platformX86UNIX/x86UNIXWindow.cc, yet still produce the lock file error when starting the 2nd application.

...
--------- Initializing Client ---------
Loading compiled script common/client/ui/customProfiles.cs.
Loading compiled script common/client/message.cs.
Loading compiled script common/client/mission.cs.
Loading compiled script common/client/missionDownload.cs.
Loading compiled script common/client/actionMap.cs.
Loading compiled script common/editor/editor.cs.
Loading compiled script common/editor/particleEditor.cs.
Loading compiled script common/client/scriptDoc.cs.
Couldn't lock file: /tmp/TorqueTest.lock, Resource temporarily unavailable
Lock owned by pid: 20730
Remove the file if lock is stale
% Exiting

#3 For debugging purposes I often run two instances of my TGE game on my computer. In visual studio I compile both the release and debug builds, run the debug within the ide, and run the release normally.

The only files that collide (in my experience) are the .DLL files, but the release and debug builds use their own versions. Aside from compiling both builds, I don't make any other changes.

Without being able to run two instances, I would have gone insane trying to debug client/server code ages ago. I'm not sure if this was the same problem you were having, though.

#4 This will work for the developer, who has the source code to be able to run 1 TGE application in debug mode of the C++ IDE and the other normally.

For the End-User needs to be able to have 2 or more TGE applications (not just clients of the same application, but two or more applications that make use of TGE) running together at once. Even though TGE is designed for gaming purposes it also does have other uses, particular for walk/fly around design models, etc.

The DSO working directories for the applications is already solved, just need to resolve the file lock issue. Still looking for this lock.

#5 Don't bother it's a waste, just make 2 seperate binaries, your using SuSE, so look at my post here
Create each binary with it's own output directory and name them seperately, this will give you the most flexibility and probably the most ease of use in debugging.

#6 Yep, done that and it works well in allowing to have different clients for an application.

Only problem I having now is that I can't run 2 or more TGE applications at the same time, due to file locking error mentioned above.