When will the 1.02 out?

#181 I don't think we need to worry about the "updates for 1 year thing." Although the TGEA license does say you are only guaranteed free updates for 1 year, I don't think GG is going to "drop the hammer" in enforcing that. In fact, I'm pretty sure that TGE operated under the same restriction, and it was 3 years before I had to buy my first update for it.

#182 Heh truth is were screwed according to legal EULA for future updates and what not. They don't have to bend to the will of customers. We have been banking on good faith that there would be fixes and additions(mostly the purchase yearly upgrade)

So is this why the bounty system was created to help somewhat counter that clause? Only bad thing is there aren't enough programming guru's vets to put it in full swing, but then again they could just keep the code for themselves. Then were back to square one again.

/Gets crackn on trying to be a programmer.

#183 Speaking of the bounty system, are the ones still up there still valid to work on? I wouldn't mind trying my hand at a few of them.

#184 Stephen

I don't know the US rights well enough.
But within europe, there is a further part of the contract and thats advertisement.
According european right, the features advertised for anything sold have to be fullfilled. If they aren't the costumer has the right to get his money back when he/she returns the bought object. This is not bound to some specific kind of thing actually.

So in case the USA has similar laws, the advertisement page of TGEA would be part of the contract as well.
And there are some parts advertised that are clearly outdated or broken at the moment, without the least note on when they are planned to be fixed.

Thats the point that actually makes me angry, not the fact that they are broken. I can life with the fact that there are bugs during build up as long as a later version has the fixes we can merge back in. But right now, there is nothing to count on and nothing to calculate with.

I don't know why it is that hard to keep people up to date when it takes months to do something. You most likely do changelogs internally, why not make them accessable to the license owners? (similar to the other topic where an employee actually posted the changelog for 1.02 which is in QA queue right now).
I don't need ultra cool new feature threads with zillions of cool pictures, they are something for companies like TheGameCreators that only can survive with eye candy advertisment.
I don't think we, the licensees, bite off your head if we know whats worked on and what has been fixed and therefor can concentrate on expanding TGEAs capabilities for our needs instead of fixing things fixed in the next release anyway.

#185 I bought TSE 26 May 2006, as it was to be supporting OpenGL!

- o -

Stephen, there's 3 things that a GG sale to any customer has to adhere to.

1: The advertisement!
2: Contract/Eula
3: International laws!

Instead of trying to argue with customers whether they got what was sold, the last part of this thread communicating around the issues at hand, trying to clarify when issues are solved and milestones reached is a very good and professional approach. You guys should stick to this and keep the product owners informed of planned stuff and its progress.

That way those that have bought an engine, could also plan development of it, and releases. That would give us the toolset we are here for, and keep the high end of your product range at a mature state.

/edit: morning type errors!

#186 I'd just like to say that I thought the advertising was very misleading as well. Sure you, can say that you buy it AS IS, but there is no way to see how AS IS is until you actually buy it.

The terrain was the biggest draw for me to the advanced engine, and there is all this jazz about how it is easily editable and deformable and has dynamic lighting and whatever (please don't pick that apart), it wasn't until I bought the engine that I found out what 'legacy' and 'atlas' were. You read the advertisement thinking terrain is terrain, but then you go back after buying it and find, well, the one terrain system can do this, but the other terrain system can only do this. For the person who cannot see the engine and is only looking to buy the engine from its 'Features!' page, I find this intentionally misleading.

When you promote something, and the only way to tell what AS IS really means is to go by a flashy, yet vague, fairly misleading features page, and perhaps a video demo, it's quite easy to see how someone could feel that they did not get what they thought they would.

Also, could you maybe hire someone dedicated to making documentation. Seriously, if we could just read up on how this hunk of code actually works, it would probably make these kinds of threads less frequent, and I wouldn't be left wondering why the most basic parts of the engine aren't documented after several years, many of which carry over from the predecessor engine.

#187 Now? :D

#188 Hey guys, just keeping you up to date. We are still testing on it, currently testing some lighting stuff. Still can't tell you exactly when it will be ready, but in the spirit of open communication I am letting you know I hear ya and want to get it out to you as soon as I can :)

#189 Thanks Ken! You rock!

#190 Ken,

Thanks for the post! Even something that short and sweet lets us know and feel like progress is being made and that we've not been forgotten.

James

#191 Thanks very much for the update, Ken. It's very much appreciated.

#192 Thank you very much for this update Kenneth

#193 Sweet... :-D

#194 Good man K... thx

--Mike