5 minutes ago, DChockey08 said:

I would be fairly confident that sceneries will be largely compatible, but it's the FSLabs and PMDG aircraft that have me worried. Need those aircraft to be able to be flown in v6 to make it worth it. 

You don’t spend five years developing a 64-bit Concorde originally for v4 then switched to v5 and then stop. I’m pretty sure the changes required to make it v6 compatible aren’t significant especially when several sources are saying LM ensured backward compatibility was vital.

7 minutes ago, Ray Proudfoot said:

You don’t spend five years developing a 64-bit Concorde originally for v4 then switched to v5 and then stop. I’m pretty sure the changes required to make it v6 compatible aren’t significant especially when several sources are saying LM ensured backward compatibility was vital.

I would tend to agree, but the comments from Andrew Wilson at FSLabs were perplexing. 

When someone posted stating that all that should be required is a simple update, he stated this was "quite incorrect" and that he was "setting expectations".

I am, however, semi-confident that FSLabs will port their addons to v6, but i am somewhat worried about PMDG. 

12 minutes ago, Zangoose said:

Yeah that was mentioned and also the fact that Microsoft have Azure and Bing. 

Regarding 3rd party airports - I expect most will probably work but what you may find is that they may need updates if they have made changes to the lighting system so you may see some issues there. 

Thanks for the reply. I am also curious which developers will update there aircraft and scenery installers. Many of the installers like FSLabs, PMDG, FSDT, Flightbeam, FlyTampa, etc will need to know about V6 in order for the configurators to work correctly. 

1 hour ago, DChockey08 said:

Well if this is the case, then my excitement just went down to zero. 

Actually, my excitement increased: this means they are aware of v6, may know the needed changes, but can't say anything because of the NDA they signed. Maybe that was why FSL delayed their update to v5.4? Just my naïve opinion.

4 minutes ago, Luis Hernandez said:

Actually, my excitement increased: this means they are aware of v6, may know the needed changes, but can't say anything because of the NDA they signed. Maybe that was why FSL delayed their update to v5.4? Just my naïve opinion.

I admire your optimism. Could be true. I tend to look at it as: more serious changes are needed than pointing the installers at v6 (for FSLabs aircraft at least). 

Worried that some developers that require some amount of updates will not release v6 versions. 

1 minute ago, DChockey08 said:

I admire your optimism. Could be true. I tend to look at it as: more serious changes are needed than pointing the installers at v6 (for FSLabs aircraft at least). 

Worried that some developers that require some amount of updates will not release v6 versions. 

Or FSL is laying the groundwork to announce that they won't commit to V6 and they're canceling the NEO for V5. 

33 minutes ago, Ray Proudfoot said:

You don’t spend five years developing a 64-bit Concorde originally for v4 then switched to v5 and then stop.

An example of 'sunk cost fallacy.' A smart business reviews whether the market conditions remain favourable to continue with a project or pivot resources to something that will gain a better ROI (think airlines who close a route after only 3-5 years and redeploy the aircraft on a well-served major trunk route instead).

 

Follows-on from my comment above.

I really hope for Concorde fans that FSL's 64-bit version makes an appearance for v5 and/or v6. Yet, that comment by Andrew at FSL is concerning without further explanation. Just have to wait until 3rd July.

 

Edited June 25, 20232 yr by F737MAX

21 minutes ago, DChockey08 said:

I would tend to agree, but the comments from Andrew Wilson at FSLabs were perplexing. 

When someone posted stating that all that should be required is a simple update, he stated this was "quite incorrect" and that he was "setting expectations".

I am, however, semi-confident that FSLabs will port their addons to v6, but i am somewhat worried about PMDG. 

They’re still under an NDA until 2 July. They’re just covering their bottom. 😁

My source has the PMDG 737 and confirmed no issues.

1 minute ago, Ray Proudfoot said:

My source has the PMDG 737 and confirmed no issues.

Ray to the rescue to calm my anxieties! 

Cheers

I suspect there is atleast a decent chance that dynamic lighting on payware airports could be impacted.  But maybe not.  

24 minutes ago, F737MAX said:

An example of 'sunk cost fallacy.' A smart business reviews whether the market conditions remain favourable to continue with a project or pivot resources to something that will gain a better ROI (think airlines who close a route after only 3-5 years and redeploy the aircraft on a well-served major trunk route instead).

“sunk cost fallacy” and ROI mean nothing to me. ROI could mean Republic of Ireland. 😁 I’ve always liked Plain English. 😉

26 minutes ago, F737MAX said:

I really hope for Concorde fans that FSL's 64-bit version makes an appearance for v5 and/or v6. Yet, that comment by Andrew at FSL is concerning without further explanation. Just have to wait until 3rd July.

Given it’s now being beta tested I think we came assume it will be available for v5. I’d be amazed if they didn’t make it v6 compatible when in all likelihood they’ll do the same for their Airbus fleet.

As for any future P3D version I suspect v6 will be the last using the ESP engine.

This thread reminds me that I need to download the latest PMDG aircraft installers and keep those safely guarded.

Never know if future updates can disable their addons from working on V6. 
 

Just thinking out loud. 

34 minutes ago, Ray Proudfoot said:

They’re still under an NDA until 2 July. They’re just covering their bottom. 😁

My source has the PMDG 737 and confirmed no issues.

I have pmdg but not using it anymore because I like ifly 737 max much better.

3 hours ago, Ray Proudfoot said:

Given it’s now being beta tested I think we came assume it will be available for v5.

I'd be amazed at this late stage for them not to complete Concorde and sell it for v5.

However, I'm not convinced any work will happen on making their products available for v6 after that FSL post. The return on investment (ROI) 😉 or, put simply, the amount of resources needed to be spent on updating doesn't (Edit: *may not* — I clearly haven't seen the numbers) justify the time and financial costs to do so.

Anyway, good to hear PMDG 737 appears to work in v6.

 

Edited June 25, 20232 yr by F737MAX
clarification

As someone who was a diehard FS9 fan...

(FSX was still "meh" to me overall - it got better just never hooked me like FS9 did)

...and a diehard fan of P3Dv4/5, who has now been converting more and more to MSFS every day since about March, this is pretty underwhelming for me.  "Whelmed" at best.  The showcase of almost all military, even trying to perhaps put a "light DCS" spin on things like weapons, underscores their commitment to Government contracts and associated compatibility (we knew this all along though).  Definitely not a day one purchase for me, if at all - not a hard "no" yet, but sure going to take a LOT of convincing to bother setting it up.