Maybe Beau made a slip on the Prepar3d forum.

"

. We are revamping the menus in v3 to avoid this issues moving forward."

 

A possible indication thatt they are moving to v3 ?

I think we need to create a "drama" tag to avoid rumors, hearsays and issues.

Well frankly if companies were a bit more forethcoming with their plans and hoped for developement release dates (though we all know they can slip) there would be no need for rumours and guesses.

We are expected to outlay a considerable investment in add in software to use on these platforms and it would be nice if we had the information to do so.

Even other developement companies complain when they are not told, why should not consumers....Sharing guesses and how they are derived helps provide the information we should have anyway.

If   we  put  more   space  between  the  words ,  does  that  mean  we  can  read  more  between  the  lines   ? 

If   we  put  more   space  between  the  words ,  does  that  mean  we  can  read  more  between  the  lines   ? 

 

 

 

Maybe an extra carriage return, would give pleny of room for a good read between the lines.

Out of interest, what was 'the issue' he's referred to?

Hopefully they won't go straight to 3.0 yet. 2.x is a very nice platform, but it deserves a 2.6 for one more round of bug fixes and improvements.

I personally would prefer a version 2.5.7.124.9.768.545.345b SP1.32 with several hot fixes on the side!! 

Well frankly if companies were a bit more forethcoming with their plans and hoped for developement release dates (though we all know they can slip) there would be no need for rumours and guesses.

We are expected to outlay a considerable investment in add in software to use on these platforms and it would be nice if we had the information to do so.

Even other developement companies complain when they are not told, why should not consumers....Sharing guesses and how they are derived helps provide the information we should have anyway.

Anyone who's been around a long time would know the problem with that approach Harry. In the past there were a lot of dev's who would publish expected release dates and features. And God help them when they missed the date or didn't include a promised feature!! Talk about flaming! There was one developer, can't recall his name, but he finally had enough and said screw you and stopped making product.

 

Openness SOUNDS just nice as pie but I doubt that ANY developer will do anymore that generalize about dates and features - and I agree.

 

Vic

I avoid "release dates" and timelines as much as possible with anyone outside development teams   If I am forced I always use the project managers rule and multiply my best expectation by THREE  That way people are upset when we get about half way through   (spilled drink on my keyboard and period is not functioning)

Internally in my business role, my teams all know what the deadline is. It's fixed and immutable. However, if they can finish the job early I have no problem if they go and take a week or two off, it's far better than a financial incentive when your bonus is mullahed by someone elses failure outside of your control. 

 

Sim developers need to be more goal-orientated and meet their stated deadlines. Or simply stop making promises their skills can't keep.

 

The latest A2A release was I suspect, banked and completed, finalised and shipped before the first video promotion was released. The palpable sense of anticipation was then met, as well as multiple vendors available from almost Day One. An absolute lesson in under-promising and over-delivering.

Your marketing `buzz` will be 300% larger, your volume sales higher and condensed into a far shorter ROI period, if you match the anticipation to the delivery.

 

PMDG/AH/Aerosoft/Milviz/ORBNX/place developer here take note. 

 In the past there were a lot of dev's who would publish expected release dates and features. And God help them when they missed the date or didn't include a promised feature!! Talk about flaming! There was one developer, can't recall his name, but he finally had enough and said screw you and stopped making product.

 

Openness SOUNDS just nice as pie but I doubt that ANY developer will do anymore that generalize about dates and features - and I agree.

 

Vic

So set your date and work to it.  You may need more resources but if you do it is bad planning not by the customer but by the developer.

I cry real tears about the developer that stoped developing. That kind of attitude may be fine for freeware where you are doing it for your benifit but otherwise not.

Customers should be first and if they are the developer will reap the rewards.  For too long this industry has acted like a lot of spoilt amatures

I wonder what their operating capital is and how much they took in with licenses. Knowing this, might allow one to figure out how soon 3.0 will come.

 

Bob

Either there are some big changes coming to jump to V3.0 and or they need more funds. I would imagine we have to pay again for version 3+.

If its 64bit then im all for it as we badly need extra VAS room, but will mean alot of addons breaking and charges to upgrade them. But it will have to be that way at some point in time. But I thought 64 bit is still a year or two more away. So what other major changes are in the pipeline to justify a jump to V3?

Ramp up the speculations lol

Am I the only worried about the performance of the 3rd party addons we're going to get when developers know they have an almost unlimited amount of VAS to work with?