Torque3D 3.5.1 GMK Port
by raa brubb · in Torque 3D Professional · 02/07/2014 (10:01 am) · 33 replies
Hey all,
My first beta is out here, currently the templates do NOT work and I need help from the community. Right from the box, bullet and GMK will work together. When you make a FULL (GMK is only implemented in full due to requiring full meshes), Bullet build, it runs fine. Again the only problem is the templates aren't working and I will need help fixing the problems. Go ahead and download the file and see if you can get it to work. Thanks and see you later!
My first beta is out here, currently the templates do NOT work and I need help from the community. Right from the box, bullet and GMK will work together. When you make a FULL (GMK is only implemented in full due to requiring full meshes), Bullet build, it runs fine. Again the only problem is the templates aren't working and I will need help fixing the problems. Go ahead and download the file and see if you can get it to work. Thanks and see you later!
About the author
#22
05/06/2014 (12:54 am)
If anyone wants to try help fixing issues with the port, feel free. 
#24
05/11/2014 (11:10 am)
I restarted the 3.5 (now actually 3.5.1) port because of too many bugs with basic engine functionality. I also integrated the Verve editor for dynamic cutscenes into the port. I finished everything except the GUI, but the engine bugs seem to be gone. The only thing left is the annoying GMK GUI I had problems with earlier. However, the bugs are gone. I'll upload the files later. 
#26
06/01/2014 (3:50 am)
If you used github and posted links then maybe others could help, but in the meantime it would at least allow people to see the progress and save you having to upload files
#27
06/01/2014 (11:17 am)
It's really hard to put stuff on Github and I couldn't figure it out. If this uploading thing is an annoyance, I'll see if I can get it on Github again. 
#28
On the github thing: it is easier to follow along with thoughts, methods, and possible missteps, which in turn makes it easier to chip in on if things are rolled in and documented as they are altered, rather than large chunks of files with a 'try this' request.
06/05/2014 (4:13 pm)
Haven't really had time to dig into GMK m'self, so don't really know what it is we're missing. On the github thing: it is easier to follow along with thoughts, methods, and possible missteps, which in turn makes it easier to chip in on if things are rolled in and documented as they are altered, rather than large chunks of files with a 'try this' request.
#29
This may help you with some of the basics. The web is full of git tutorials, so it's a bit difficult knowing where to start!
06/05/2014 (5:35 pm)
And for those of us who do use GitHub, it becomes very easy to roll in your changes - it's a matter of `git fetch username && git checkout gmk-branch`. I highly recommend getting comfortable with git and GitHub if you want to be a software person, and especially if you want to contribute to Torque :).This may help you with some of the basics. The web is full of git tutorials, so it's a bit difficult knowing where to start!
#30
06/05/2014 (6:37 pm)
just to also point out that sourcetree(sourcetreeapp.com) will install a sandboxed version of git when you install it (sourcetree) so you dont even need to know everything to just get started.
#31
Also thanks for the link Daniel, it actually really helps :)
06/05/2014 (7:24 pm)
Has anyone fixed the GUI problem though, I will work on getting it on Github. Just package up the fixed Full and Empty templates if you get it working.Also thanks for the link Daniel, it actually really helps :)
#32
www.hackersontent.com Also thanks for the link
04/23/2015 (7:56 am)
I have fully working version for 3.5www.hackersontent.com Also thanks for the link
Chris DeBoy
Whoa, you're in the hospital? What for?