Game Development Community

Why recent TGE 1.5 so bad?

by Sammy · in Torque Game Engine · 04/20/2007 (4:42 am) · 8 replies

Hi all,

I use TGE 1.4.2 once in a while.
Recent devmaster net on TGE 1.5 was so bad. Is this true?
http://www.devmaster.net/engines/engine_details.php?id=3

Could any 1.5 user prove it wrong?

Thanks in advance

#1
04/20/2007 (5:23 am)
1.5.1 has a number of bugs that were created when they introduced the constructor adapters. Personally im no going to use constructor for a bit with 1.5.1. In fact im keeping the constructor seperate and porting those items over. Its just too buggy for me
#2
04/20/2007 (5:55 am)
Most people complain about new versions of Torque as they always contain a considerable amount of bugs, more than what should be acceptable. It gives the impression that code is not properly tested before release, which is most likely the case. In my years of using Torque, I've noticed an annoying trend... New builds break previously working features. On top of this, new features are added which don't work well. This is very frustrating. My favorite build of Torque is version 1.3 combined with TLK believe it or not. I still have a copy of this build and it contains less bugs and is more stable than any of the future versions I own. I often use this build as a reference to fix features that have always worked fine but are broken in new builds. I have not upgraded to version 1.5, and most likely never will due to, in part, the reasons I briefly outlined here.
#3
04/20/2007 (6:07 am)
While everyone's dev experiences will probably vary, I've never had an upgrade problem with the exception of the fxReplicator lock-ups, which I fixed myself and was later patched by GG for the next upgrade. Other than that, I always felt my TGE experience was more stable and had better features with each iteration of the engine.

I also have a tendency to break things.
#4
04/20/2007 (6:14 am)
Personally the 1.5.0 has been very very stable for me. its just recently with 1.5.1 that there has been a number items that has caused problems, AFX is a good release too.
#5
04/20/2007 (6:30 am)
There were a number of optimizations in the latest versions as well, I believe these increased performace for some users while some of these caused a few unnexpected side effects that will most likely be ironed out soon enough through support from the Garage as well as our awesome community members.
#6
04/20/2007 (7:40 am)
1.5 crashes ALOT on my older system and I have no idea why. the crashes are pretty erratic. on my current project, the 1.5 exe crashes about 80% of the time I try to run it and the crash only happens right after the mission finishes loading with no perceivable console errors. 1.5 seems to run fine on my new vista system though.

1.3 on the other hand never crashes. I'm with Tim Heldna, I've found 1.3 to be the most stable version of torque released.
#7
04/20/2007 (7:47 am)
I've had no problems with 1.5, its pretty darn stable, and Constructor is awesome for an initial release, there are a few bugs but mostly it rocks, I've been pretty damn productive with it, whole orders of magnitude more productive than with Quark. :D

I see just as many positive reviews on that site as negatives, so....why not try for yourself?
#8
04/20/2007 (9:03 pm)
I like to be straight forward with anyone considering buying this, if you do not have a background in programing this engine is going to be difficult for you to make things with. It's the truth and I speak from someone that has a very very limited background in c/c++. The scripting language is very easy for me to use (fit right in with my limited limited c/c++ knowledge for structure) and very easy to do some things with but there is a LOT you won't be able to do in the scripting language.
I'm not saying this as a bad thing about the engine but as a truth to pretty much all game engines. And if you want to do something besides a fps your going to have to get into the code a bit.

That being said it is a stable engine, the graphics are pretty good, the stuff people are showing with the MK is amazing, hopefully they'll work the mk right into the engine someday for an official package.

The quick resposne is if you are not a coder there is a steep learning curve to this engine, how steep? I'll let you know if I reach the top. But there is a lot to learn from and a lot to play with. Also a lot of the stuff you want to do in code you can find resources for but you still have to read through the hundreds of resposnes for little fixes here and there to get it all together.