Game Development Community

TSE is just plain wrong

by Andy Hodges · in Torque Game Engine Advanced · 12/02/2006 (8:42 am) · 17 replies

Milestone 4.1 is a complete nightmare. Is there anyway possible that I can still get the previous Milestone to download?

-Andy

#1
12/02/2006 (9:32 am)
Q1 - What was called TSE was renamed Torque:AT but everyone hated it so it was renamed TGEA.
Q2 - I have no idea. ;)
#2
12/02/2006 (10:03 am)
@Andy Hodges

If you don't need to make engine code changes right now, download the latest TSE/TGEA demo and use that.

By the way... TGEA stands for Torque Game Engine Advanced.
#3
12/02/2006 (12:24 pm)
This does not motivate me to buy TSE aka TGEA. Regarding the name, I prefer TSE, it's just easier on the tongue.
#4
12/03/2006 (8:54 pm)
Early Adoption means stuff will break. I know it is disappointing but GG's was upfront in explaining that. Never delete a previous milestone that is working for you. You just don't know if something crucial will break when new features are added.
#5
12/03/2006 (9:06 pm)
Michael's words are words to live by in development:

www.reallyreallygoodthings.com/resources/folders.jpg
I've been working with Torque for about 23 months. I can go back to any major build change I've made in that time. Not only with the evolution of an engine (like TSE to TAT to TGEA), but with your own work, *NEVER* over-write or delete a previous build, create a new directory. I can't begin to stress how much grief this will save you.
#6
12/03/2006 (9:36 pm)
I understand that things will break, but never thought that GG would eliminate the common "Save as" and other functions needed to operate.
#7
12/03/2006 (9:45 pm)
Sorry for your luck.
#8
12/03/2006 (11:06 pm)
This is public forums too, and not really the place for discussion of compiling specifics or missing files or issues
#9
12/03/2006 (11:27 pm)
If you do not have "the space" then you should look into your own subversion or CVS solution that stores only the changes. Sure, it will get big...but not as big as a manual copy. And you can roll-back if needed (and it will be needed).

This is neither lecture nor debate but good, sound practice. Were you not doing this, as I have been involved in MANY projects that have not, then you need to from now on to avoid such problems in the future.

The problems that you mention should be addressed as well. But indie software developers using a source repository solution should also be addressed to avoid major headaches.
#10
12/04/2006 (2:02 am)
@Alan James - Yea... definitely look into Subversion. ;)
#11
12/04/2006 (2:03 am)
Aye, gotta agree. Always keep recent or previous releases somewhere. I keep latest 3 milestones stored at all times, and that's like what, 190 megabytes for all three?

But I also agree that compile errors is something I never expected. I mean, it has been claimed that the dedicated server setup is tested on each release, yet it is has not been working for as long as I remember. Same thing here, one would assume compile errors not to be there when things are tested before going out to the testers. I understand things slip trough the cracks sometimes (compile errors) but there has been no new version with corrections yet.

Which gets me back to my point: Always keep old versions so you can use them instead of the newest.
#12
12/04/2006 (7:23 am)
It would be nice if GG allowed us to download previous Milestone versions. Atleast the previous incase the latest doesn't work (in this example, Milestone 4 is useless right now).
#13
12/04/2006 (7:36 am)
.
#14
12/04/2006 (7:49 am)
Well to my knowledge, GG took down the CVS as of October 31st, and they're making people download it from their account page

-Andy
#15
12/04/2006 (8:17 am)
.
#16
12/04/2006 (8:22 am)
.
#17
12/04/2006 (9:10 am)
I agree that at the very least tse (tgea) should compile. I stopped working with tse right after I bought it because I couldnt get it to compile. I dont feel like I wasted my money yet as I'm awaiting new releases, and I knew there would be problems with it when I bought it since its still EA. I just hope the compiling problems will be ironed out soon so I can get back into it. I dont have the time to fix it myself.