Get jetting!

#41 Bah, I'm so silly. I executed the wrong exe. Works great! Thanks Sam. :)

#42 I've just implemented this and it didn't work. Has anybody had any problems with it in torque 1.5 by any chance?

#43 Did you use the Torgue 1.5 verison of the resource?

http://www.garagegames.com/index.php?sec=mg&mod=resource&page=view&qid=11314

#44 Great jetpack. Definitely has a Tribes feel to it. Had no problems using 1.5. Haven't tried a jetsound yet but particles and physics make this one better than other player jetting resources I've tried.

#45 Hey thanks guys for making this the 'Plastic Gem #22: Get Jetting' Gem. Its an honor.

#46 Sam - your very welcome. Was a great resource. Happy to do it.

#47 I tried this great resource and it works great in TGE 1.5.2.
Just one but. If a player lands rough on the terrain the particle emitter "splits" into two.

I guess this is similar to the problem that Nick Matthews described. Any ideas to fix this?

#48 I am getting the emitter problem too, but if I damage myself with the crossbow it fixes it..
so must be in the onDamage code..
going to look and see if I can find it..

#49 Thanks for posting, i'll have another look at my code too.
Hope we can fix this problem in this great resource.

#51 did you attach a new bind?

#52 I am having problems with the code and not sure if I am just doing something stupid or what. I followed the code as instructed, everything compiled fine and I got the key bindings, but nothing happens in game when I click on the right mouse button like it should. I put an echo in the script and it registers that it is pressed, but nothing happens the character just stands there. Please help if you can.

I editted the engine game code and am just trying to run it in the starter.fps version which is where I made all the scripting adjustments. I am running 1.5.2 any thoughts as to why it won't run?

#53 @Jeremy Dull

I'm guessing that your compiler compiled the project as torqueDemo_DEBUG.exe. Either change the compile mode to release, or rename the torqueDemo_DEBUG.exe to torqueDemo.exe. I would recompile, as I think Visual Studio (which you're probably using I'm guessing) puts in some extra stuff for the debug version which might slow things down. I could be wrong, but why not play it safe.

#54

Quote:I would recompile, as I think Visual Studio (which you're probably using I'm guessing) puts in some extra stuff for the debug version which might slow things down.

Yep. Debug versions are slower, but when your code screws up, instead of just crashing, you break and get to see some useful debug information. (Also, you can only use breakpoints in a debug build.) A simple change like this isn't likely to need a debug build, but it's a good idea in general to compile in debug first to test things out, then compile in release once you're pretty sure things are stable.

#55 the link is dead, you can download the resource from here:

drive.google.com/file/d/0B9GUwtDHCp_eSUVDT1I5LTdndHc/view?usp=drivesdk