Committee Meeting Notes: 04/29/2013
by David Wyand · in Torque 3D Beginner · 05/07/2013 (10:13 am) · 6 replies
Old Business
- Dave
- FPS Tutorial: All done except section 8 has not yet been removed. Working to get it taken down.
- Project Manager: Can choose modules for new project. Working on changing modules for existing projects. Aiming for release this week.
- 3.0 QA Testing: Testing to be complete this week.
- Dave
About the author
A long time Associate of the GarageGames' community and author of the Torque 3D Game Development Cookbook. Buy it today from Packt Publishing!
#2
But hopefully the modular template base we are wanting to move towards will make the need/desire/want of a barebones template superfluous.
05/07/2013 (10:41 am)
Daniels barebones template is a stripping down and rewriting of the Template restructuring work that I abandoned. He has my full permission to do with it what he will. It will not added to 3.0 for I doubt it will be done. But hopefully the modular template base we are wanting to move towards will make the need/desire/want of a barebones template superfluous.
#3
05/07/2013 (10:42 am)
And by the way, the Empty Template contains no FPS elements. 
#4
My own barebones was based on Mike's work for the original 3.0 template refactor, the biggest part of which included getting rid of the core/ directory, which was a massive leg up for me.
My goal is a bit different to the modular template: I'm tearing everything down, trying to get a level to run with the minimum amount of script possible. That means no menus, no GPU profiles, no PostFX. About the only thing I've left in is the console.
It probably won't be done for 3.0, but I'll let it out as soon as I feel like it's ready.
And, just to say, doing this teardown has brought me face-to-face with just how much work has been put into these script templates. Seriously! I have a new appreciation for them, and I've learnt heaps and heaps about them. If anyone else wants a deep understanding of the templates, I highly recommend taking them apart to see what makes them tick. Start with Empty, then subtract.
Mike: Empty doesn't contain FPS elements, but it does have a lot of assumptions about a mission-based server structure and so on. And core/ still contains all this Tribes stuff everywhere:
05/07/2013 (3:48 pm)
Yeah, I'm looking forward to this modular template as well!My own barebones was based on Mike's work for the original 3.0 template refactor, the biggest part of which included getting rid of the core/ directory, which was a massive leg up for me.
My goal is a bit different to the modular template: I'm tearing everything down, trying to get a level to run with the minimum amount of script possible. That means no menus, no GPU profiles, no PostFX. About the only thing I've left in is the console.
It probably won't be done for 3.0, but I'll let it out as soon as I feel like it's ready.
And, just to say, doing this teardown has brought me face-to-face with just how much work has been put into these script templates. Seriously! I have a new appreciation for them, and I've learnt heaps and heaps about them. If anyone else wants a deep understanding of the templates, I highly recommend taking them apart to see what makes them tick. Start with Empty, then subtract.
Mike: Empty doesn't contain FPS elements, but it does have a lot of assumptions about a mission-based server structure and so on. And core/ still contains all this Tribes stuff everywhere:
// Save client preferences on the connection object for later use. %client.gender = "Male"; %client.armor = "Light"; %client.race = "Human"; %client.skin = addTaggedString( "base" ); %client.setPlayerName(%name); %client.team = ""; %client.score = 0;
#5
At the moment it loads a level with a groundplane and sun. This is all done in main.cs; the idea of the exercise was to see how transparent I could make the entire affair. Of course, for actual use, you'd want to create, you know, a scripts/ folder or something with some callbacks to load the level and so on.
EDIT: Be warned that I removed pretty much every safety/sanity check I could find in the name of making something comprehensible. So if you're playing around with this, you should probably do it with a debug build :P.
I'll probably blog about this sometime.
05/07/2013 (10:44 pm)
It's up. Not completely done, but nearly there. Got it down to 1.45MB, of which 1.06MB is a mess of graphics config scripts and shaders which I'm not brave enough to delve into.At the moment it loads a level with a groundplane and sun. This is all done in main.cs; the idea of the exercise was to see how transparent I could make the entire affair. Of course, for actual use, you'd want to create, you know, a scripts/ folder or something with some callbacks to load the level and so on.
EDIT: Be warned that I removed pretty much every safety/sanity check I could find in the name of making something comprehensible. So if you're playing around with this, you should probably do it with a debug build :P.
I'll probably blog about this sometime.
#6
I could not find a blog on this so I will post here. I really like your t3d-bones. I am using it to test the console optimizations along with the normal startup and the minimal startup. I have my main.cs setup to allow selection of 1 of the 3 startups.
I found one humorous issue with putting the zip file in the main game directory. It kept only running from that. So don't put the zip file in the main game directory lol!
08/14/2013 (4:31 pm)
@dB,I could not find a blog on this so I will post here. I really like your t3d-bones. I am using it to test the console optimizations along with the normal startup and the minimal startup. I have my main.cs setup to allow selection of 1 of the 3 startups.
I found one humorous issue with putting the zip file in the main game directory. It kept only running from that. So don't put the zip file in the main game directory lol!
Torque Owner Lukas Joergensen
WinterLeaf Entertainment
T3D really need a barebones template, it's full of FPS stuff thats just useless for other genres.
Only info I got on it