What resources are still needed?

#1 Hi Chris
This was my way when i started and i have come far with the game.
I did all basic things with the Head version ,did some maps and
made some basic characters and weapons and tested the functions.
After that i knew what was missing and what i needed.
If i wanted a teamgame function i searched the resources and
tried it out.
So i think start basic and add the stuff you only need.

Hope this help alittle :)

#2 Here is a quick list of resources which have been entered into the HEAD or have a version in the HEAD which now covers the same functions

2342 - Zip file fix for torque
2356 - better fluid rendering
2556 - Ogg Vorbis streaming
2563 - Add Alpha Channel support to ms2dtsExporter
2586 - Crash fix for non-console version
2615 - better Milkshape Materials
2660 - fxLight
2729 - In Game Music
2766 - Fix for Milkshape bug
2875 - Startup Gui Splash Screen
2952 - Fluid Improvements
3057 - fxFoliageReplicator
3166 - fxSunlight
3462 - Maya2Map Exporter
3561 - Lan Button
4231 - Fix GoToWebpage Function

#3 @David: That is great, now where did you find that information? I am a new TGE owner and but a long time member of garagegames, since May 2001 actually. I have been looking at the code snippets recently deciding what might get added to better support my game and in one post you answered my question, not much.

I agree, a single page showing all that has been added to the engine but most importantly by whom. Maybe even something that we subscibe to any time the HEAD changes, we get an email. Mailman anyone?

I must say that after buying "3D, Game Programming All In One" did it for me. There is no better getting started but Kenneth Finney doesn't really get into engine code changes or what is all in the engine.

Thanks...

#4 Something like this maybe?

#5 That's great, but my biggest problem is as I snoop around the forums and resources I stumble across all sorts of code and I'm like, "Hey, that sounds cool, maybe I'll put that in." So I spend a while trying to figure out what the heck I'm doing and how to get the code in when I find out it's already there. Melv's foliage Replicator is a perfect example.

#6 Chris,

This is a good idea, but it requires some work. It is too much for us to manually go in and edit/update resources when we add them to the HEAD.

Still, this would definitely be useful. Maybe if we get a CVS email notification system going, we can use that to ask resource authors to update/modify/delete their resources when they get added to HEAD.

For now, I don't think it's too awful to just check yourself whether a given resource has made it's way in. :) It can be a good learning experience too, since you see which parts of the engine need to be modified to do different things.

#7 You know, I was thinking, which is generally dangerous.

Is there any way to add a required section for each resources stating which version of TSE/TGE the resource was written for or code was tested on?

Better yet, how about a capability to search the resources by version number? Then I could pull up all resources about a topic that I'm sure will work with the version of the SDK I'm using.

#8 That, again, would be quite an undertaking...