Running 2 instances at once?
by Jacob Wagner · in Torque Game Builder · 08/10/2008 (1:29 am) · 2 replies
I am having trouble testing networking by running 2 debug builds at once.
It's a very strange thing,
I have an execs.cs that loads my scripts for the games,
I have 2 projects, in seperate directories...
When I open them both at the same time, one of the instances will load the execs.cs from the other project.
I can't explain that, but when it shows which scripts were compiled, one of the instances will have been compiling scripts from the other exec's list, and not its own. It does show that it is loading the correct exec.cs, which is really weird.
I have tried cleaning dso's. The only thing that seems to fix it is deleting the execs.cs file and not running them both at the same time.
Do I need 2 machines to test networking?
It's a very strange thing,
I have an execs.cs that loads my scripts for the games,
I have 2 projects, in seperate directories...
When I open them both at the same time, one of the instances will load the execs.cs from the other project.
I can't explain that, but when it shows which scripts were compiled, one of the instances will have been compiling scripts from the other exec's list, and not its own. It does show that it is loading the correct exec.cs, which is really weird.
I have tried cleaning dso's. The only thing that seems to fix it is deleting the execs.cs file and not running them both at the same time.
Do I need 2 machines to test networking?
#2
You don't need two machines to test networking, but you may be slightly on the wrong path.
I think your problem might be using separate projects. Instead use the same project and open it up once with the debug exe and then again with the release exe. This will avoid having to keep two separate projects synced up and should allow you to test the networking.
08/12/2008 (6:47 pm)
To repeat what Phillip said...You don't need two machines to test networking, but you may be slightly on the wrong path.
I think your problem might be using separate projects. Instead use the same project and open it up once with the debug exe and then again with the release exe. This will avoid having to keep two separate projects synced up and should allow you to test the networking.
Associate Phillip O'Shea
Violent Tulip