TGB 1.7.5 torsion problem (binary fix available) - RESOLVED

#21 I reposted the links, all permissions cleared. This is temporary, keep in mind!

here

#22 You are a gentleman and a scholar, Sven. Thank you very much.

#23 Thank you Sven.

just in time to stop me from plucking my hair :P.

#24 Gah. And I come back today and it's doing it again. I tried replacing those files again, but to no avail. ~>:(

Just to be sure--I need to put those files into
C:Program Files (x86)TorqueTorque Game Builder 1.7.5tgb

Is that correct?

Builds from TGB work, and Non-debugger options from Torsion work too.

EDIT: So I found that the C:Program Files\(x86)TorqueTorque\Game Builder 1.7.5\tgb directory was marked read-only. Although it seemed to be copying one of the files, it wasn't copying the other. At any rate, it's working now. I'll see if it reverts to the old one tomorrow.

I hope my system isn't haunted! Scary!

#25 I made the change to the source code and compiled new release and debug executables... but no luck. Although it gets rid of the "connection to executable failed" message, I still get no breakpoints and nothing in the Output window.

I also downloaded the trial .exes from the link and dropped them into the correct folders, and no breakpoints or Output.

Is there an ETA on the fixed .exes (non-trial) being available?

#26 The binaries provided work for me - breakpoints, output, and variable watches all work. All I did was replace the .exe in my project folder with
this binary fix.

#27 I did the same thing and it seems to be working now. The level editor says "Trial Version". What are the consequences of that?

#28 I am a noob at torque, I have tgb, and am trying to use torsion to debug scripts, but I just get connection to exe failed. I noticed a little connect window pop up and disaper first, its trying to connect to 127.0.0.1, port 6060. my local ips are in the 192.168.0.X range, so it has no chance of connecting to anything?. What is it trying to do, does that explain why the debugger wont run, I read the comments above, but they were posted in may/june this year, its now october, and I just downloaded the latest versions of torque and torsion. Remember I am a noob, so any, grab this file put it here etc, please be noob friendly :). (ps I dont have the pro version)

Ok, after a bit more messing arround and reading and loss of hair, im still none the wiser.

So here it is in a nut shell.
I open tgb, choose new project.
Select adventurekit as my template, and call it adventure1.
it then creates a folder in C:\adventure1 (for ease)

amoungst other things i now have
C:\Adventure1\adventure1\project.t2dProj
C:\Adventure1\adventure1\adventure1.exe
C:\Adventure1\adventure1\Game.torsion

I double click Game.torsion and torsion loads, sets up somthing then gives me a list of files and folders.
common (folder)
game (folder)
consol.log
main.cs
project.t2dProj

At this point I hit F5. and it comes back with an error screen,
"connection to executable failed".

Please reply for a total noob.

#29 Downloaded new trial EXEs and placed where they needed to go. closed down, rebooted and re ran. Still not working for me.

#30 Andrew, I see that you own the Pro license. Have you tried rebuilding with the changes in the previous page? I just solved this issue by doing that.

#31 I made the change to the source code and compiled new release version but I still get the "connection to executable failed" message.
And the new EXEs do not work either....

Can anybody help? Please!!!

#32 Doesn't work for me either. It started once, after having deleted all and created a new project. Then once it had ran, it never started again. This needs more immediate attention because I (and probably more) just bought Torsion and this doesn't exactly elevate my impression. I also added the fix, tried the binaries, nothing works.

#33 It is not Torsion problem. It works for me

#34 (Edit)

I found the problem..

In the project folder there is an exe file for your project. If you don't "build" to the same folder, that exe never gets replaced with the fixed .exe binary. However, torsion still uses that one and not the one in the folder you just built. Hence, the old file without the fix is always used.

So the solution is to remove that exe and either build to your project folder, or copy the built one over the old file. Either way should fix it.

But the problem here is basically that Torsion doesn't use the file in your "Output directory" from T2D if it differs from the assumed one.

I suggest the Torsion developer to actually look where the last build is, before hooking in to the exe.

#35 @Michael: You need to set up Torsion for your project - and set the executable as well. It won't make any guesses at which file to debug. It debugs what you tell it to. See Project > Properties > Configurations. I imagine that perhaps you've not changed the filename in your Torsion project config after you made this fix. (Edit: Or perhaps compiled RELEASE and debugged DEBUG)

I'm glad that you got it figured out. Torsion is a great tool, and now that debugging is working for you, it's gonna get significantly better. :) Good luck!

#36 @Konrad, thanks for the feedback :)

Hopefully this might help someone else too with the same issue.

#37 I've copied the binaries linked in this thread and I'm still having the issue.

Do I need to re-install everything or?

#38 So on my new computer I downloaded my project from .SVN and it worked fine.

Then I started a new project and suffered the dreaded "Connection to executable failed"

And now my older project also suffers from the failure, preventing script debugging.

Start with no debugging works (Control+F5).

But every once in a while, the project will start with F5 (maybe 1 out of twenty times). Usually the first time after recreating the project configuration. But after that, more failure.

The code base has the code fix in telnetDebugger.cpp outlined earlier in this thread.

I added some message boxes to see if any of the functions in there were even getting called and it looks like they don't.

I tried connecting via dbgSetParameters (after starting without debugging). If I set to wait for client, the program sits there on an hourglass cursor. If not wait for client the program continues to run but a subsequent call to dbgIsConnected() returns zero (not connected).

I also tried uninstalling and reinstalling both TGB 1.7.5 and Torsion. No change.

Any hope for fixing this? Any ideas? Thanks in advance.

#39 I dont want to be funny, but Torsion/TGB is not working, it worked fine when I bought it, but for over a year now, its been eratic as hell. I have paid for a software that just doesnt work. Its supposed to debug TGB scripts. It doesnt bebug anything. So disappointed in GarageGames for not sorting this out. One would assume the compiled version would do the job as stated.
Come on people fix the damn thing for once and for all.

TORSION/ TGB IS BROKEN, FIX IT PLEASE !!!!!!!!!!!!!!!!!!!

#40 @Andrew
Explaining the issue you're running into would be more helpful than ranting and cursing.