Game Development Community

TGB 1.7.5 torsion problem (binary fix available) - RESOLVED

by Afan Olovcic · in Torsion · 05/03/2010 (1:08 pm) · 46 replies

I have problem to start my project from Torsion Error msg : Connection to executable failed.

Configuration settings are OK.
Page «Previous 1 2 3 Last »
#1
05/03/2010 (11:55 pm)
Yeah! It wasn't just me...
Sometimes it works, sometimes it doesn't...
I'm also not not getting anything in the output window when I use f5 to start a debug build.
#2
05/04/2010 (2:46 pm)
I'm having the same issue. It works when launching without debug on, but not with.
#3
05/05/2010 (3:36 am)
Thanks yep it ctrl+F5 works but F5 doesn't.
#4
05/06/2010 (1:58 pm)
I have the same problem: [ctrl]+ [F5] works but F5 or F11 doesn't.

Every Project that I start in TGB runs without a problem. But if I start (run or step debugging) the project in Torsion I always get the message "Connection to executable failed!" directly after the connect dialog. Why? What does this mean?

In the Windows XP Firewall the Torsion.exe and the Game.exe are excluded!

So what is wrong?
#5
05/07/2010 (12:12 pm)
FYI: Dave of GG has passed my bug report to sickhead games!
#6
05/10/2010 (3:22 pm)
I found the solution to the problem in the source code. In telnetDebugger.cc line 327 it currently is:

Net::Error err = Net::NotASocket;
      
if ( mDebugSocket != InvalidSocket )
      Net::recv(mDebugSocket, (unsigned char*)(mLineBuffer + mCurPos), MaxCommandSize - mCurPos, &numBytes);

It should be:

Net::Error err = Net::NotASocket;
      
if ( mDebugSocket != InvalidSocket )
    err = Net::recv(mDebugSocket, (unsigned char*)(mLineBuffer + mCurPos), MaxCommandSize - mCurPos, &numBytes);

Mod Note : Just use the [ code ] and [ /code ]tag (no spaces) :)
#7
05/11/2010 (3:09 pm)
Nice catch Patrick! Worked like a charm
#8
05/11/2010 (3:27 pm)
Confirmed and logged. TGB-505
#9
05/12/2010 (6:30 am)
lol ;)
#10
05/12/2010 (2:04 pm)
Thanks Patrick for the catch, now I can use 1.75 for daily work.
#11
05/18/2010 (1:03 pm)
So I searched my computer for the telnetdebugger.cc file and only came up with telnetdebugger.cpp. Is this the same file that needs edited?

I am running Windows 7 Ultimate 64-bit. I am also pretty new to torque.

Thanks
#12
05/18/2010 (1:14 pm)
@Matthew
Unfortunately this fix can only be applied by Pro owners as it's a bug at the source code level. The telnetdebugger.cpp you found was for T3D Pro. We've got the bugs all collected now and we're finding the resources to allocate to getting them fixed as quickly as possible.
#13
05/19/2010 (4:01 pm)
Well spotted indeed, was going mental with having to debug via echo lines in script! I owe you at least one alcoholic beverage of your choice.

Life is going to be so much easier now!
#14
05/24/2010 (8:39 am)
The bug comes from Torque source code or Torsion code ? I wanted to buy the Indie licence of Torque2D, will I have the bug if I don't buy the version with source code or do I need to buy Torsion aside with the source code to fix the bug ?
#15
05/24/2010 (9:17 am)
@Frederick
The bug was in TGB and not Torsion. The source code for Torsion is not available for purchase. Torque Game Builder Pro owners can apply this fix to the source code themselves, but Binary owners cannot. We're working on an update that will fix it for everyone.
#16
05/24/2010 (10:07 am)
Thanks for your reply ! Do you know if there is an approximation of time before the fix will be release with the binaries ?
#17
05/28/2010 (11:18 am)
Any ETA?

Thanks,
ppl
#18
06/01/2010 (2:48 am)
Hi guys, In the meantime - i have spoken with Matt and others in regards to this, and i will host a binary fix for now. All the zip contains is new trial executables that you can use with your ignition key to work from.

Link is back : Download

Note : This is the binaries only, copy them where they should go for them to work. At the moment, it only contains this torsion fix.
#19
06/01/2010 (12:51 pm)
pardon the (seemingly stupid) question.

Where do I put these ?

I put TorqueGameBuilder.exe in TGB folder
and TGBGame.exe in tgb\gameData\T2DProject folder
but nothing changed !!

I still can't debug.
(I kept backup copies of my original executables & reverted to them for the moment)

Thank you
#20
06/03/2010 (7:26 am)
Any way to get the binary fix? Or any idea on when a fix is coming to the indies? :(
Page «Previous 1 2 3 Last »