Comments on: Gentlemen, Start Your Engines (We Hope)

By: Francois Ruel

Francois Ruel — Sat, 11 Mar 2017 10:58:10 +0000

In reply to Francois Ruel. Problem solved with pb14. Thank you.

By: Ben Supnik

Ben Supnik — Thu, 09 Mar 2017 23:33:15 +0000

In reply to John. Hi John, Probably not. There are mandatory engine model updates for v10->v11. If the author doesn't update the plane and the plugin code in the plane is picky about engine behavior, it's unlikely the plane will "just work close enough".

By: John

John — Thu, 09 Mar 2017 22:18:23 +0000

Beta is beta guys. Thats it. For now what it could be later…very good so far.
For stable IFR long flights better choice is at the moment XP10.
We must wait…for the big suprise. 😉

Wishes for me are:
Stable planes. Stable sytem.
Correct NAV implementaion
Old plane integration 10 to 11
Trip planning tool

Question:
Will the Carenado planes (PC12/TBM750/SenecaV) work stable after final release without an carenado update ?

Greetings
John

By: Ben Supnik

Ben Supnik — Thu, 09 Mar 2017 16:52:53 +0000

In reply to Alexander.

We have three choices.

1. Make the change at 11.0, albeit late in the beta. This makes people who think the beta should be final really nervous. It makes developers who have shipped their add-on despite it being a beta unhappy. It reveals the mismatch in expectations between LR and third parties. It shows the danger of having a reasonably stable EARLY beta when all feature work is not done.

2. Make the changes in a point release. Our goal is to maintain add-on compatibility during the binary release, so this makes the change a LOT more expensive – the change has to be wrapped in a big pile of compatibility code. This is not impossible..but it takes developer time. That developer time means something else cool for x-plane doesn’t happen until later.

3. NOT make the change at all, and continue with the old code. Based on what Austin has learned about engines, he considers the old code to simply be _wrong_. Wait another few years.

Given these three choices, I thought option 1 was the least bad option.

We are trying to get to ‘final release’ as fast as we can. But the fact that we still call it a beta, and not even an RC, should give you some indication of where we are at with that process.

By: Alexander

Alexander — Thu, 09 Mar 2017 16:04:06 +0000

When I purchased the X-Plane 11 Beta in early January I thought I’d have a new fine, stable Sim by March or April.
Why does LR fundmentally change things so late in a Beta program?
Your customers are waiting for a final product, the addon developers are waiting for release and the new SDK.
Customers want to enhance XP11 with addons, but developers cant progress.
The current turns in the Beta are bad for your Business and reputation, I think.

By: Ben Supnik

Ben Supnik — Wed, 08 Mar 2017 21:01:10 +0000

In reply to Günther Wittwar. I think it's luck that the artifact is more objectionable on certain visual settings.

By: Federico Villa

Federico Villa — Wed, 08 Mar 2017 20:56:09 +0000

In reply to Ben Supnik. Sent a bug report. X-Plane crashes if I install latest FAACIFP18

By: Ben Supnik

Ben Supnik — Wed, 08 Mar 2017 20:49:33 +0000

In reply to Federico Villa. PLease contact tech support.

By: Federico Villa

Federico Villa — Wed, 08 Mar 2017 20:47:44 +0000

With this latest update I cannot run my Full X-Plane 11 installation…it simply crashes while loading. My X-Plane 11 installation is a plain vanilla..no addon or plugin.

By: Günther Wittwar

Günther Wittwar — Wed, 08 Mar 2017 20:28:37 +0000

In reply to Ben Supnik.

This I understand, Ben, seems also depend on the level of Visual Effects.

I just wonder why is it working with the Visual Effekts set to High?
Is at that level another kind of guessing at work?