Game Development Community

Connection to executable failed!! - in 1.7.6 / Torsion / 64 bit machine

by Andy Hawkins · in Torque Game Builder · 02/21/2012 (9:38 pm) · 9 replies

Connection to executable failed!! - Getting this again using 1.7.6 / Windows 7 / 64bit - thought they fixed this?

It works at work ie on our school computers that are 32 bit, XP machines, but I can't get Torque 2D 1.7.6 and Torsion to debug files on my rig.

Any help would be appreciated.

I think it might be a 64bit thread thing.

I downloaded Torsion and Torque on my 32 bit Windows 7 machine and it works as designed.

I think this might be a bug.
NextNext Thread
PrevPrevious Thread
More from Torque Game Builder


Torque Owner Richard Ranft
Roostertail Games
#1
02/24/2012 (1:02 pm)
Just in case - is your project set up to connect to the release version in the dropdown menu?

Associate Scott Burns
GG Alumni
#2
02/24/2012 (1:33 pm)
If it isn't trying to connect to an .exe that doesn't exist, as Richard suggested, then it's likely a system issue local to that machine. Torsion debugging and 1.7.6 work in both 32 and 64 bit.

Associate Andy Hawkins
DrewFX
#3
02/24/2012 (11:05 pm)
I tried the same game on both 32 and 64 bit machines. It works fine on the 32 bit one, and the exact same game / files / setup doesn't work on the 64bit machine.

Is there anything I test to see why it doesn't work on my 64bit machine?

Associate Andy Hawkins
DrewFX
#4
02/26/2012 (7:27 pm)
I tried this test once more on my 64bit machine then repeated the process on my machine at work, a 32 bit machine. 32 bit works fine.

I tried to find the string "connection to executable" in T2D source but to no avail. How can I debug the engine to find the source of the problem?

Associate Andy Hawkins
DrewFX
#5
03/12/2012 (3:23 am)
I ended up removing all Torque products then reinstalled all of them including Torsion. Still got the same problem. Why is the connection to executable coming up? Is that a Torsion thing or in Torque code? Perhaps if I knew I could check through the source code to find a solution.

Reinstalling Windows to make the problem go away is not a proper fix.

Torque Owner RollerJesus
Dream. Build. Repeat.
#6
03/12/2012 (6:57 am)
@Andy,

Have you tried this?


Associate Andy Hawkins
DrewFX
#7
03/12/2012 (4:20 pm)
Thanks Patrick but that would roll me back to 1.7.5 + patch. I want to keep using 1.7.6 - there shouldn't be an issue as the connection issue was supposed to be fixed in 1.7.6 however it seems in some cases such as mine it doesn't work.

Associate Scott Burns
GG Alumni
#8
03/12/2012 (4:35 pm)
Do you have access to any other 64 bit machine to test on?

Associate Andy Hawkins
DrewFX
#9
03/13/2012 (2:51 am)
Well I had some success finally.
1. Removed all Torque2D installs, and Torsion. Restarted machine.
2. Installed T2D 1.7.6 and Torsion. Restarted machine.
3. Made new t2D project, opened Torsion project, set a break point, and after allowing access via firewall it ran a debug session.
4. Imported an old session (1.7.5) upgraded it and tried it but it didn't work. Copied over 1.7.6 exe and didn't work.

Only newest 1.7.6 exe's work. If I hibernated the computer sometimes the known working versions still had the "connection to exe failed" issue. A restart fixed it. So in general I know enough of a workaround to make it work. Not possible to import old 1.7.5 projects though - just have to rebuild them.

Thanks for everyone's advice.