Stops Creating .dso Files
by David Demaree · in Torque Game Engine · 09/05/2006 (9:00 am) · 4 replies
Sometimes, for no apparent reason, the Torque Game Engine will just quit making .dso files. This is frustrating because you can't see any changes that you've made since the last .dso was created. Does anyone know how to fix this?
#2
So basically, I just don't know how to script in Torque. Does anybody have a link to some nice tutorials that might give me some insight into making variables to track data?
09/05/2006 (9:31 am)
Well, the problem as I have narrowed it, and maybe incorrectly, is that I was using "int points = 0;" and using points throughout the file that wasn't making a .dso... The problem here is that I don't think my .cs was able to compile due to the use of "int". I need to track a variable, and I still haven't figured out how to do that, but I did get the dso to create again by simply commenting out my lines that used the "int points" related stuff.So basically, I just don't know how to script in Torque. Does anybody have a link to some nice tutorials that might give me some insight into making variables to track data?
#3
look at surrounding script code .. you'll notice that there's no type-declarations like "int", "float", whatever,
and also that local variables all start with "%".
so try "%points = 0;".
Probably the best way to learn torquescript is via either of these books: "The Game Programmer's Guide to Torque" or "3D Game Programming All In One".
Somewhat more immediate tho is checking out TDN. I'm sure there's some scripting basics in there.
09/05/2006 (9:53 am)
Oh right, a syntax error will do it too.look at surrounding script code .. you'll notice that there's no type-declarations like "int", "float", whatever,
and also that local variables all start with "%".
so try "%points = 0;".
Probably the best way to learn torquescript is via either of these books: "The Game Programmer's Guide to Torque" or "3D Game Programming All In One".
Somewhat more immediate tho is checking out TDN. I'm sure there's some scripting basics in there.
#4
09/05/2006 (2:32 pm)
Thanks, Orion. All very helpful information. =) 
Associate Orion Elenzil
Real Life Plus
1. somehow the .dso has a more recent timestamp than its .cs file
- this can happen if you "roll back" a .cs file via some sort of source control, or if you "touch" the .dso file somehow without touching the .cs file. ("touch" as in the unix command touch).
this situation can be fixed by blowing away the .dso file.
- some folks blow away all .dso files every time they launch the app. (not me, but some folks)
2. somehow the .cs file is no longer being exec'd.
- if you suspect this is happening, find the exec() call which should be exec'ing your .cs file, and put an echo statement by it. Keep tracking the problem backwards that way.
here's a handy DOS command to recursively delete all the DSOs under a folder:
(Thanks to Lateral Punk)
- just put that line inside a batch file like "deleteDSOs.bat" and it's a handy way to blow away all the DSOs.