Game Development Community

TGB 1.7.2 Issues

by Jake Seigel · in Torque Game Builder · 03/08/2008 (3:56 pm) · 2 replies

Hey there,
I've been having problems with a couple bugs in the program. I've gotten around them at the moment but they're still there. Has anyone experienced/fixed theses?

1) Random crashes; when I click exit before saving (thus getting the "save your work" menu), I get random crashes sometimes. Also, sometimes when I reload the project after editing code it'll do this but it's not 100% of the time so it could be anything. Anyone narrowed this down at all?

2) Building errors; After spending a great deal of time on a project, I tried to build it and got some really odd behaviour. The sprites were distorted in the game, and it was ignoring my code. It almost seemed like it was using DLLs from a very old version of TGB. The best I can guess is that it crashed at the behaviours and then ignored my code that did work such as dynamically creating sprites. It all works fine in the IDE but it seems that the build doesn't share the same success. A friend took a look and we figured out that it works fine if you include the source code in the build, but that's pretty flaky. is there another way around this? Has anyone come across this?

#1
03/08/2008 (4:05 pm)
Jake,

1.) Today I've nailed down one of the things that causes TGB to crash:

*Holding down a key bound to an action map, popping the action map, then releasing the key. This crashes TGB consistently.

2.) With TGB 1.1.3 I experienced something similar, but the project builder back then was barely functional. It kind of seems like your compiled .dsos weren't up to date. I'd suggest using cleandso.bat, but I don't know if it works with TGB 1.7.2 -- it was a nifty tool in 1.1.3. The batch file itself is in the tgb directory in the base TorqueGameBuilder folder.

EDIT:

I'm curious as to what IDE stands for, I've seen it a lot, and I don't know what it means, lol.

;)
#2
03/08/2008 (4:10 pm)
IDE = Integrated Development Environment (I guess "editor" is a better term for it in this case though).

2) I had a hunch that it could be related to that but I didn't want to waste a bunch of time to clean out the folders (or worse, rely on something that could eat up my project) so I looked for better solutions. If it can be verified (by me or someone else) that that would fix the issue then i'm fine with that.