I looked at KBFI and what I see is the Cirrus Jet being placed, as the sim tries to find a “jet” for “General Aviation” that is no larger than class C. I did not see props being placed in jet-only spots; if you see this, please file a bug report with pics.

I agree the upgrade logic could be less stupid.

In terms of your own airports, once WED 1.5 comes out, you can then specify the correct ramp starts. There’s no harm in starting the task of replacing statics with ramp starts in WED 1.4.1 but you might find it faster to do all of the ramp starts in 1.5, since you can pre-configure the ramp start tool with the new operations-type data.

It now seems to work in beta 2 an many airports.
But the way the new ramp start data (1301 code) is derived seems to create suprising results. It would be nice to have a bit more info on how the old & new ramp start entries work.

E.g. in case of ramp start “Boeing Ramp 3” at KBFI (Start Type “Tie-down” and Equipment Type “Jets” (only)).
The new 1301 data entry derived for this ramp is size C, “general aviation”, which apparently results in props to be placed. Which looks non-plausible.

Another start “Boeing Ramp Heavy 1” , also of type “Tie-Down”, but allowing equipment “Heavy” and “Jets” gets converted to size E and “airline” and it seems to never get populated with props. Thats what I wanted.

Next, should we manually update gateway airports by removing static aircraft and put ramp-starts instead ? So to free these positions for users/auto placed & AI plus allow more variety ?

I know, the new data fields can only be edited once WED 1.5 is out, but I wonder if I even properly use the old data fields …

Exactly right. The “this isn’t guaranteed” label on the private datarefs tends to get lost among end users who just don’t understand why their add-on broke.

There are plenty of ways to determine if a dataref exists in the sim, so such issues are specific to FWL and layers on top of it.

It’s clear that fiddling with these DRs is at own risk. But plugins like RTH do a huge improvement, so for me it’s worth it.

It’s also clear that it’s kind of annoying for you developers, that some/many users – as they may not really understand what happend – misinterpret this as a bug by LR.
What, again, definetly is not true, as you can of course change undocumented and “/private/” features as much as you like.
(BTW, I’ve stated that a few times in the forums about RTH the last days.)

Unfortunately, when using FlyWithLua, there seems to be no way right now, to check if a DataRef exist, without somehow spoiling FWL. If there was a way, we plugin developers could do the scripts more reliable.
I’ve already started a thread in the FWL support forum about that, hoping for a response of the FWL developer. (Who might be a little annoyed too, as many users said “FWL does not work with 10.50b”, just because RTH crashed it.)

However, X-Plane is great, lot of fun flying and a lot of fun creating content and extensions! So I hope, it will stay as open for the latter as it is now, which is awesome and extraordinary. : )

Read the name of the dataref out loud. Now which part of “private” did the developers of that plugin not understand?

Would be great if you find the time. RTH is quite popular, but of course that’s not a major issue on early betas.
Thx!

I don’t know what happened to it. I can investigate it. But there’s absolutely no guarantee that it remains.

Oops, i saw your answer below.

Sorry. I mean
appearance library airplanes on parking. I`m install 10.50 today and don`t see it. But I`m asking like developer.

Real Terra Haze plugin does not work with b1 for that reason, what is an issue for many users with the beta.

No complaining, just a question, as we’re told all the time that undocumented DRs can change with every update… : )