Yes, I've wondered if the current approach is best. But then in my real job I worked in a very regimented environment where the product would not be accepted without the whole package -- bugs fixed, performance criteria met, and documentation up-to-date. With minor exceptions, you (the company) don't get paid until the job is completed.
Of course there's limited TG2 developer resources, but maybe there comes a time when getting the documentation on par with the current release would be a good thing?
Another thought is the 64 bit question. Is it better to continue development/maintenance on the 32 bit code and then make the 64 bit version? Or should the 64 bit version be developed to where the 32 bit version is now (and then continue development of both)?
How many extra sales of TG2 would there be if there were a 64 bit version and/or the documentation was up-to-date?
I'm sure the Planetside folks have discussed these issues many times and are making decisions based on their "real world." I think most of us post our concerns because we have love the program and want to see it contunue to be successful and move forward.
You only have to look to an application like Bryce to see what happens to a very good product (in it's time) that had some bad luck/management. I believe they would have to do a complete re-write to get it close to a modern application.
Personally, I like the way TG2 is positioned. I don't like the "Swiss Army knife" approach (Vue.) A good Scripting/plugins implementation can provide the more specialized things like tornados, rainbows, waterfalls, starfields, etc.
Anyway, I'm sure it will be an interesting ride.
