1.1 Release Timeline

#1 also, i am curious as to how so many of these huge glaring bugs have slipped through? We have a public beta why? and then see 1.0 pretty much rearranged, AL bugged, Water bugged, Audio still bugged, you can refer the list of 1.0 bugs that have popped up.

Now 1.1 is coming with all these great additions planned, why isnt this release pushed till then. So that leaves me with 2 thoughts.

GG has mentioned that some of the future updates will possibly be paid updates(no firm release on when these paid updates will be, but they have been repeated a number of times in varies blogs and such) Is the plan that they have the content planned for 1.1, so they will release this version, then push out the 1.1 as your update, then 1.2 will be the paid update?

Im trying to get a grasp on whats on the milestone charts for GG, we have some idea whats on 1.1, but with the release of 1.0 (which doesnt include much of the beta 5 material and stablity, ie fps kit).

I really would like to use t3d, but if were going to have a new update ever 2-3 months like TGEA (and we remember that roller coaster. I cant really plan ahead the 6 months or 1 year it might take. As it is, I can see no reason to actually use 1.0 version with so much being planned for 1.1. Or am i wrong in my view of 1.0 t3d?

#2 I'm pretty disappointed with the 1.0 release as well.

The beta started so great and progressed great and then out of the nowhere beta 5 and now 1.0, both beeing significantly more bugged than the previous betas with the 1.0 basically dropping so far that it would qualify as a sibling to beta 2 ...

I really assumed that if the engine costs $1000 per seat, no longer $300 per source dev, that the errors from the TGEA release are finally learned and that the engine is released when its done and stable, yet exactly the same thing as with TGEA MS4.x and the release happened again ...


For that reason I would like to hear the plan and get legally binding statements as to when these things will be adressed and for how long we receive free updates for this technology.

#3 There are always going to be bugs, that doesn't imply that all of them slipped through. We have to choose which known bugs are acceptable to launch with and which are blockers. This is nothing new to software development. We are aware of the bugs, are tracking them, and are working on fixing them. As any new bugs crop up, we will track them and fix them as well. If something is blocking you from moving forward, let us know and we will endeavor to help you.

#4 I agree with you Marc, I do make statements in other blogs that are to champion those that are less fortunate then myself, but as you notice im a t3d owner too. I can only hope that GG will start being more serious and give us some firm development path of their engine, so those of us that are already planning sequals can have a accurate picture of future endevours. We cant have engine announcements like yesterday, with the removal of TGE and TGEA from the list, and the release of 1.0(see comments above). We as GG arent paying for the old GG. We are paying for a new GG. Lets see some of that new GG.

#5 I didn't really mean this thread to turn into a I hate T3D 1.0 thread.

Personally, the bugs in 1.0 don’t upset me since the betas have been pretty great, Beta 5 has been rock solid on my computer and I’m not anywhere near actually releasing (so I mostly need a stable environment for development). Really the problems with 1.0 mostly impact GG and the potential sales they’ll have as people try the demo and have issues, but that’s not really what this thread is about...

My question is more related to the fact that this is my first GG engine, so I’m not really sure what to expect in terms of release schedules after the 1.0 release. Does the release schedule slow slow down or stay about steady with the beta releases?

#6 We are all actively at work on 1.1 and will endeavor to keep you in the loop as we get close to releasing it. As stated before, it's not going to cost anything, and should address a lot of bugs, as well as add performance among other things.

Welcome to GG and thank you for purchasing T3D!

#7 really Kenneth? You guys knew about the AL bugs? and still released? I am really find it hard that with the advantage of having a open beta, that you didnt take advantage of it. We already own the engine. Having a Beta 6 wouldnt have killed anything? or would it? Some of the commenting and responses the last 24 hours has made me wonder what is going on in the administation level of GG.

#8 and no Gary, i dont mean it to sound like a 1.0 Hate thread, but its a acknoledgement of items that you and marc mentioned, which are valid points imo. I see alot of potential in 1.1. Its just 1.0 is not really usable out of the box in a few items.

#9 Thanks for your feedback, Edward. We'll keep you posted on 1.1. In the mean time, feel free to post any bugs in the Torque 3D forums and we'll see what we can do to help.

#10 Not to be a pain, but I’m going to ask my question again since it seems to be getting ignored in this discussion.

Is the 1.1 release *planned* for the
a) 1-2 month range
b) 3-6 month range
c) 6-9 month range
d) > 9 month range
e) all of the above... err wait... how about Blizzard style "it’ll be done when it’s done" because we don’t even know :)

Just looking for a more direct answer.

#11 Really there is no conspiracy going on here. We pushed out Beta 5, started working for 1.0 and put it through the same testing and fixing process. There are always known issues and we are already hard at work on them. Keep in mind that not all issues happen to everyone. We could all test something, be fine, push it out and a user with a specific OS + hardware set up will run into a blaring issue that we simply don't run into.

Again no conspiracy, we are working just as hard as we have been during beta and the 1.0 release only gave us about a single breath of fresh air before going heads down again for 1.1. There will always be issues and we are more than willing to take feedback and do what is needed (even if that means releasing a 1.0.1 with some fixes to some primary issues), but no we didn't take a sledge hammer to 1.0 after beta 5 and it did in fact run quite stable during our tests (albeit some known issues) :)

#12 @Gary: We try not to give big deadlines since we've done that in the past and if we decide to delay then we get hammered for giving out false release timelines... I will say we're targeting a. though b. is possible.

#13 @Edward - As a developer currently working on 1.1 I stand by Kenneth's responses. I can comprehend that your upset about 1.0; but the question in my mind is why. We want to do everything we can to ensure you have a good experience; but, we have to know specifics or we can't help you. Please be more specific about AL bugs; just saying "AL Bugs" in a rant like fashion doesn't help =( . I'm not talking rainbows here; you can still be angry/mad/pessimistic, but please be more specific so we can help you.

#14 Perfect & thanks! I'm not trying to get you guys to commit to date or anything. I just want to set my expectations appropriately.

#15 Hi Gary,

More than 1 less than 6, possibly sooner but, yes "when it's done."
1.1 will be a free update.

#16 The engine is sweet and I think the next update will be awesome.

I just think it's kinda silly (or, dare I say, devious?) to rename beta6/RC1 as 1.0 in order to lure in more customers.

I know, everyone's gotta eat. I'm just sayin.

#17 @Steven Garcia -- ok do i really need to post all the bugs that have been reported for 1.0 release. Apparently I do.

http://www.garagegames.com/community/forums/viewthread/102533 // NO Transparencies in Advanced Lighting mode, conflicting also DIFs as well as particles.
http://www.garagegames.com/community/forums/viewthread/102637 // Cant move the terrain?
http://www.garagegames.com/community/forums/viewthread/102673 //Shape Replicator error?
http://www.garagegames.com/community/forums/viewthread/102667 // A GUI bug / fixed buy Rene
http://www.garagegames.com/community/forums/viewthread/102623 // Hardcoding returns to T3d even though it was different in previous versions.
http://www.garagegames.com/community/forums/viewthread/102521 // Black Clouds?

http://www.garagegames.com/community/forums/viewthread/102525 // returned to a different file structure // not a deal breaker, but 5 betas and suddenly we go back to the original file setting?

http://www.garagegames.com/community/forums/viewthread/102549 // how about some QA just to sum up a list

Now i could post a bunch more but this was just int he 3 minutes i took to look at the first page of the private forums.. sO Steven, do i need to start posting the bugs, or should we look at the stack of existing ones?

And thanks Davey. 1.1 will be a free update, that is good news? and 1.2?

#18 I think having to pay for anything 1.x would be a travesty.

#19 Has there been consideration of putting out a 1.0.1 release to fix up a few of the bugs reported already in a few weeks? Sure it wouldn't hurt too much and I am sure 1.1 will introduce new ones since it is adding more features.

#20 Edward, no, you don't need to repost the bugs from the forums. What Steven is asking is what specific bug is causing *you* a problem with the game or project *you* are working on. Just reiterating already found bugs, is more akin to complaining for the sake of complaining.

We are tracking those bugs and working on them.

What bugs are you specifically running into in your project that are holding you back.. if you can answer that, we can try to help you.

Thanks.