Torque 3D Open Source 3.5 Launch
by Dave Wyand · 11/13/2013 (4:48 pm) · 62 comments
Torque 3D Open Source 3.5 Launch
On December 19, 2012, we launched T3D v2.0 as the first new release under an open source MIT license. Then on May 9, 2013, we launched T3D v3.0, our second MIT release. Since going open source in September 2012, we’ve had over 1,400 people star and nearly 600 people fork our main repository.
Back in the Spring the Steering Committee proposed to the community a roadmap for T3D 4.0. Unfortunately, due to a number of reasons that have been outlined in the Committee’s meeting minutes that roadmap became unattainable. In the Fall the Steering Committee decided to package up what it could and release it as v3.5 to allow those that rely on the precompiled package to take advantage of the bug fixes over the last six months.
What’s New for 3.5
Torque 3D 3.5 is largely made up of bug fixes submitted by the community and Steering Committee, along with a couple of new additions. Here are some of the larger changes:Recast Integration
Daniel Buckmaster took his Recast/Detour resource and submitted it for inclusion into T3D 3.5. This allows you to generate navigation meshes and find paths across these meshes. You may read more about this work on the resources page (login to the GarageGames website required).
Blinn-Phong Shading
Ryan Mounts had posted a Blinn-Phong shading resource a couple of years ago and Ron Kapaun created the pull request. With v3.5 we’ve moved over to the Blinn-Phong technique which provides much improved specular highlights. You may see some examples of this in action on the resource’s page.
Oculus Rift and Viewport Corrections
In addition to updating Torque 3D to make use of the latest Oculus VR SDK that includes magnetometer-based drift correction, a standard method of obtaining the user’s IPD and chromatic aberration correction, Torque 3D’s rendering pipeline has been updated to better handle the side-by-side rendering required for the Rift. These fixes include all water rendering, reflective and refractive surfaces, as well as the glow and SSAO post effects.
These Oculus Rift fixes have the side benefit of also correcting a number of viewport issues with these systems that non-Rift games may have experienced. These objects and post effects now respect the boundaries of the current viewport and should not spill into the rest of the screen or cause other strange rendering artifacts.
In addition to these rendering changes, the scene culling routines have been improved to take into account the projection offset required for Oculus Rift side-by-side rendering. This means that small or distant objects (including terrain chunks) should no longer visibly pop into and out of existence at the screen periphery.
Improved Underwater Turbulence and Caustics
The turbulence and caustics post effects have been updated for both speed and to respect the boundaries of the current viewport. Caustics now also correctly turns off when leaving any body of water. With these changes the caustics shader has now been turned back on by default.
Gamepad and Joystick Dead Zone Correction
The gamepad thumbstick’s and joystick’s dead zone calculation was incorrect causing a jump in speed once you left the dead zone. This made the joystick range from 30% to 100% and had the player suddenly start moving. With this fix the joystick’s range outside of the dead zone now produces the correct 0% to 100% range.
Missing Decals
When using a relatively short visible distance in your level you could end up with decals disappearing at particular camera angles or not show up at all. The decal manager has been corrected to work under all circumstances.
Player Footstep Sounds and Dust
This one has been missing for a while and has been brought back. The default terrain materials have been set up once again to allow for footstep sound effects and kicked up dust.
Change List
Below is a list of all changes that have been made to the development branch of the Torque3D repository since the 3.0 release and are now part of Torque 3D 3.5.- Theora texture for cloned material fix (Issue 382)
- Elastic ease: incorrectly uses arcsin, should be sin (Issue 347)
- Clean up SFXSources in Player class (Issue 394)
- Allow T3D to compile against the latest version of FMod (Issue 364)
- Groundcover doesn't take terrain's rotation into account (Issue 330)
- Trigger a terrain signal when its transform is changed (Issue 407)
- Bullet Library v2.81 (Issue 434)
- Recast part 1: librecast (Issue 431)
- Recast part 2: PLC_Navigation (Issue 432)
- Recast part 3: wrapper classes (Issue 433)
- Expose ShapeBase blowUp method (Issue 452)
- Replacement of turbulence PostFX improves visual quality of underwater scenes (Issue 450)
- Let projectiles collide with objects without being armed (Issue 387)
- Increase terrain editing and painting brush max sizes (Issue 447)
- Particles (Issue 460)
- Created Header file for net.cpp (Issue 410)
- AIPlayer slows down at each path node (Issue 60)
- Var rename fix (Issue 476)
- There is no /shape/ subdirectory in art/particles any more (Issue 417)
- Allow audioData.cs.dso to execute (Issue 477)
- fixed camera code not checking for invalid/missing datablock (Issue 420)
- Added checks for valid pointers after locking (Issue 424)
- fixed pointer problems and guard in material files (Issue 423)
- compile fix for rift sdk ver 0.2.2 (Issue 422)
- DecalManager not in proper scene container (Issue 474)
- Gamepad and joystick dead zone calculation incorrect (Issue 468)
- Mounted image weapon light fix (Issue 494)
- Fix BitVector copy constructor (Issue 415)
- GameBase WhiteOut and DamageFlash defaults (Issue 395)
- ShapeBaseData::damage() wrong parameters (Issue 484)
- RenderMeshExample won't render transparent materials properly (Issue 470)
- Heap corruption caused by incorrect Torque Script naming (Issue 84)
- Particle Editor - New particles are not rendered correctly (Issue 365)
- Player dust support (Issue 491)
- Make GuiShapeNameHud frame and fill rendering useful (Issue 478)
- Oculus Rift Improvements (Issue 497)
- Don't require ClientMissionCleanup to exist (Issue 384)
- Oculus Rift Sensor Data Comparison Change (Issue 500)
- Frozen rigidshapes still generating collisionsets (Issue 393)
- Arm range fix (Issue 427)
- Viewport Fix for Glow PostFX (Issue 502)
- Viewport fix for PostFX and SSAO (Issue 503)
- Expand PostFX Viewport Options (Issue 504)
- PlaneReflector Support for Side-by-Side Rendering (Issue 505)
- Added default parameter to GuiMLTextCtrl::addText (Issue 466)
- Frustum Comparison Fix (Issue 506)
- GuiObjectView does not initialize mCameraRotation (Issue 507)
- Removing a duplicate CorrectMuzzleVector initPersistFields() entry (Issue 509)
- Vector parse order within Trigger::castRay is inconsistent (Issue 510)
- Redefinition of ::UUID (Issue 448)
- Managed Particle Location Fix (Issue 513)
- Blinn-Phong Specular Changes (Issue 515)
- Bug in TSShapeInstance::MaskNodeHandsOff (Issue 83)
- Update ReflectionManager on Scene Field Change (Issue 516)
- Turbulence respects viewport and projection offset (Issue 519)
- Default value for WaterFogData plane distance (Issue 520)
- Underwater Fixes (Issue 521)
- Update pxMultiActor.cpp (fixed) (Issue 518)
- Revert Player Buoyancy Change (Issue 522)
- TSMesh::castRay() and small collision meshes (Issue 485)
- Collada import leads to wrong data in DTS (with second UV or vertex paint) (Issue 230)
- RectF::intersectTriangle() -- wrong parameter for testing (Issue 512)
- Over Agressive Culling Frustum with Rift (Issue 525)
- ITickable supports object deletion (Issue 529)
- Ground cover banks with camera (Issue 527)
- NavPath may fail to find path with no error (Issue 530)
- ArrayObject numerical sorting is backwards (Issue 228)
- Negative VRAM for cards with greater than 2GB memory (Issue 226)
- Fix for simulated Oculus Rift (Issue 535)
- Update version reporting to 3.5 (Issue 536)
- Fix for Bullet frustum reference (Issue 537)
Where to Find Torque 3D 3.5
As always you may find Torque 3D over on GitHub. Here is a list of all repositories:- Main repository: Torque3D
- Documentation: Torque3D-Documentation
- Project Manager: Torque3D-ProjectManager
In addition to GitHub we also have our own ZIP package that combines the Torque3D repository with the updated TorqueScript documentation, the Project Manager, and compiled versions of each of the templates. This package is ideal for those that do not wish to compile Torque 3D on their own, and is available here:
In Closing
With another Torque 3D release now behind us I wanted to end with a long time community member’s game that was recently released into the wild. Steve Acaster’s Airship Dragoon was built with Torque 3D and is now available for sale from his web site www.yorkshirerifles.com/webpages/store.html.- Dave
About the author
Producer at GarageGames LLC
#42
Okay, yeah, when I get the time to work on it I'll probably learn what I need to so I can port it to Mac myself or with the community. It just sucks, normally when I don't have the time or skills to complete a job I pay someone else to do it and they actually do it.
11/21/2013 (8:54 am)
@ Dave WyandOkay, yeah, when I get the time to work on it I'll probably learn what I need to so I can port it to Mac myself or with the community. It just sucks, normally when I don't have the time or skills to complete a job I pay someone else to do it and they actually do it.
#43
11/22/2013 (5:48 am)
@Shaolin Dave: Who are you paying to port T3D to the Mac? 
#44
11/30/2013 (2:23 am)
For Mac, you may be able to use, http://wineskin.urgesoftware.com/tiki-index.php
#45
Thanks for the suggestion. I'm familiar with Wine apps, but for those who aren't I'll follow-up so they'll know if your suggestion is good for them.
Wine isn't technically an emulator, but it behaves like one. You "wrap" your Windows app so it'll run on Mac, but there's a lot of wasted resources and glitches associated with it. Wine has only worked on about 10% of the apps I've tried, and none of them (not ever Torsion) has worked without issues. I haven't gotten any indie games to work.
It might be a good tool for Windows developers to port completed Torque games to Mac after the Windows version is completed, but even not ideal.
For Mac developers who want to develop Mac apps on a Mac, not so much.
11/30/2013 (12:46 pm)
@ xGamerThanks for the suggestion. I'm familiar with Wine apps, but for those who aren't I'll follow-up so they'll know if your suggestion is good for them.
Wine isn't technically an emulator, but it behaves like one. You "wrap" your Windows app so it'll run on Mac, but there's a lot of wasted resources and glitches associated with it. Wine has only worked on about 10% of the apps I've tried, and none of them (not ever Torsion) has worked without issues. I haven't gotten any indie games to work.
It might be a good tool for Windows developers to port completed Torque games to Mac after the Windows version is completed, but even not ideal.
For Mac developers who want to develop Mac apps on a Mac, not so much.
#46
BTW - I also installed to a flash drive to easily move between PC's, dunno if that's desirable or even do-able, but here's hoping.
--Rob
12/01/2013 (11:48 am)
Just coming back to T3D (used to have the commercial 'Pro' license). Just dl'd the 3.5 package at the head of the thread and no "tool-box" (at least I don't see it anywhere - maybe buried in some other folder?). Do I need to get the 3.0 version and overwrite with 3.5 in order to get the 'toolbox' interface?BTW - I also installed to a flash drive to easily move between PC's, dunno if that's desirable or even do-able, but here's hoping.
--Rob
#47
"Toolbox" is now "Project Manager". It's in the main Torque3D folder on the 3.5 download and has it's own github section at github.com/GarageGames/
12/01/2013 (12:24 pm)
@Rob Lowe"Toolbox" is now "Project Manager". It's in the main Torque3D folder on the 3.5 download and has it's own github section at github.com/GarageGames/
#48
12/04/2013 (6:06 pm)
torque requires a successful war game. So as to allow the engine torque obtained recognition loudly again. Can bring vitality. 
#49
12/05/2013 (11:24 am)
AFX 2.0 for Torque 3D support!?! 
#50
12/11/2013 (7:51 pm)
I see people helping with the programming side of things, is there a virtual art department? I wouldn't mind donating some assets at some point if I have some extra stuff, or helping in some way like that. 
#51
We will need quite some art for demonstration purposes, if you want to donate something, better contact me and/or J0linar first, so we can make a plan what we will need, there are currently some people already working on things.
12/12/2013 (2:17 am)
Currently there is no official development team for Torque3D, but we founded a group to continue improving the engine as open source.www.garagegames.com/community/forums/viewthread/135730/9We will need quite some art for demonstration purposes, if you want to donate something, better contact me and/or J0linar first, so we can make a plan what we will need, there are currently some people already working on things.
#52
* Unfortunately Henry Todd's rock solid collision code for Rigid/Rigid and Player/Vehicle didn't make it into the branch and the stock Rigid/Rigid function (now uncommented :-) does crash the game when vehicles collide.
www.garagegames.com/community/resources/view/20727
I'm no expert in git and probably too stupid to open a pull request - but i'd jump in if desired.
* Now with the new and good Project Manager we have an easy selection option for different physics. I'm now quite familiar with Torque physics but is there an explanantion about bullet physics for a simple mind like me?
01/08/2014 (2:01 am)
2 ct from me: The new release does compile nicely with VS Express 2010 but there's still a few open ends:* Unfortunately Henry Todd's rock solid collision code for Rigid/Rigid and Player/Vehicle didn't make it into the branch and the stock Rigid/Rigid function (now uncommented :-) does crash the game when vehicles collide.
www.garagegames.com/community/resources/view/20727
I'm no expert in git and probably too stupid to open a pull request - but i'd jump in if desired.
* Now with the new and good Project Manager we have an easy selection option for different physics. I'm now quite familiar with Torque physics but is there an explanantion about bullet physics for a simple mind like me?
#53
your work look nice and has a lot of helpful information.
Great working If you have not any team or community you can join us at http://cglegions.com/
01/11/2014 (11:56 pm)
Awesome!your work look nice and has a lot of helpful information.
Great working If you have not any team or community you can join us at http://cglegions.com/
#54
Dave, let's be clear. I'm a Mac developer. I adored the Torque ecosystem for the better part of a decade, and got screwed for it (wasted a whole lot of time and resources developing under 1.0.1 based on assurances that "the next release will fix things, the Mac version is just down the road"). I understand that you guys got burned too by way of a flaky contractor or something like that. At this point I don't care. There was plenty of love to go round on this side of the table, and as Shaolin Dave pointed, you guys blew it with broken promises.
"""I even handed an WIP version of T3D that was running on OS X to some community members to clean up, in hopes of a port. I don't know if they are still working on it or they have stopped, either way it's a community project."""
Michael, you handed off a version that couldn't be open sourced because it wasn't based on the MIT licensed release. The hope for a successful community project out of that was essentially nil. I've looked in a couple times over the last year, just out of curiosity, and the two guys who tried to solo their way through both seem to have burned out and disappeared.
I don't mean to sound overly bitter, because by and large I had good experiences here (and some really very awesome help from Eric when I was struggling with licensing related issues in the pre-MIT days). But I am bitter, on this particular subject, so it shows.
01/19/2014 (11:21 pm)
"""Mac developers have no love for Torque 3D"""Dave, let's be clear. I'm a Mac developer. I adored the Torque ecosystem for the better part of a decade, and got screwed for it (wasted a whole lot of time and resources developing under 1.0.1 based on assurances that "the next release will fix things, the Mac version is just down the road"). I understand that you guys got burned too by way of a flaky contractor or something like that. At this point I don't care. There was plenty of love to go round on this side of the table, and as Shaolin Dave pointed, you guys blew it with broken promises.
"""I even handed an WIP version of T3D that was running on OS X to some community members to clean up, in hopes of a port. I don't know if they are still working on it or they have stopped, either way it's a community project."""
Michael, you handed off a version that couldn't be open sourced because it wasn't based on the MIT licensed release. The hope for a successful community project out of that was essentially nil. I've looked in a couple times over the last year, just out of curiosity, and the two guys who tried to solo their way through both seem to have burned out and disappeared.
I don't mean to sound overly bitter, because by and large I had good experiences here (and some really very awesome help from Eric when I was struggling with licensing related issues in the pre-MIT days). But I am bitter, on this particular subject, so it shows.
#57
01/20/2014 (6:57 am)
@Thomas - The code drops occurred before and after the MIT launch. The coders were given permission to use, improve, and distribute. Nothing came out of it, even when we gave permission to fix the OS X port for a MIT release. I understand what is being said about the commercial past. However, that is the past, hence my original reply. Being a community project now, "still no love" comments reflect on the Torque users and community, not GG. As shown by Louis, the port is feasible if people will simply code and share it.
#58
@Michael: sorry - I should have been more clear. I understand that the long term goal was for the code drops to end up open source. The problem is that they couldn't be from the start, meaning that the recipients had to try and go it alone. Jeff Yaskus was asking for help at one point and I had the free time to at least take a look, but coordination was a nightmare because the code had to stay private. I tried my best to support Mac development peripherally with porting over deprecated code to Cocoa and fixing the logging layer to use proper etiquette, but without a central repo for the Mac devs to coordinate it just wasn't going to happen. The Mac code should have been in a branch of the primary github repo from the get-go. Anything else is horrifying mismanagement of resources. I think Luis is the third person I've seen post screenshots of it working correctly. The other two disappeared without releasing anything.
01/20/2014 (9:24 am)
@Luis: nice! I hope for everyone's sake you get that released soon. Is that still only Basic lighting?@Michael: sorry - I should have been more clear. I understand that the long term goal was for the code drops to end up open source. The problem is that they couldn't be from the start, meaning that the recipients had to try and go it alone. Jeff Yaskus was asking for help at one point and I had the free time to at least take a look, but coordination was a nightmare because the code had to stay private. I tried my best to support Mac development peripherally with porting over deprecated code to Cocoa and fixing the logging layer to use proper etiquette, but without a central repo for the Mac devs to coordinate it just wasn't going to happen. The Mac code should have been in a branch of the primary github repo from the get-go. Anything else is horrifying mismanagement of resources. I think Luis is the third person I've seen post screenshots of it working correctly. The other two disappeared without releasing anything.
#59
For Mac people and others :P
Torque3D Crowdfunding for Linux, SteamOS, OSX, iOS, Android
Info about OSX branch
01/20/2014 (12:44 pm)
@Thomas, Advanced LightingFor Mac people and others :P
Torque3D Crowdfunding for Linux, SteamOS, OSX, iOS, Android
Info about OSX branch
Employee Dave Wyand
In this blog I've been talking about the open source version of Torque 3D. If Mac developers want to see this version of Torque 3D run under OSX then they will have to step forward and make it happen.
I see three possible choices for anyone that wants Torque 3D to run on a particular platform:
- Make it happen themselves (individually or with the community)
- Wait for someone else to do it
- Find another piece of technology that fits your needs
You'll have to decide for yourself which of these works for you.- Dave