Hi, we've vastly improved how the plugin manages the windows (see the linked post to the .org forum for details). However, it seems this particular aircraft is still causing issues for some, and this really is a problem in the way the aircraft is coded (from the feedback gathered so far).

It must be something solvable somehow, but this is a cross-plugin problem which gets longer to correct, if ever possible.

On 1/6/2018 at 1:41 PM, Rnon said:

Hi, Same problem.. any news? 

Believe the issue hase been found and will be repaired in the next B200 update by Carenado. NoJoe good guy!

https://forums.x-plane.org/index.php?/forums/topic/138236-b200-reality-xp-gtn-750-sasl-bug/

2 hours ago, Adrian123 said:

Believe the issue hase been found and will be repaired in the next B200 update by Carenado. NoJoe good guy!

This sounds good, I'm glad they've found out the root cause in the SASL code!

They sent a test/hot fix file for the B200 but I'm waiting on a reactivation for the B200. Will keep informed. edit: appears the problem has been resolved.

19 hours ago, Adrian123 said:

Believe the issue hase been found and will be repaired in the next B200 update by Carenado. NoJoe good guy!

https://forums.x-plane.org/index.php?/forums/topic/138236-b200-reality-xp-gtn-750-sasl-bug/

What makes me unhappy is that the bug was reported months ago and only now somebody took a look at it and a fix was provided within a few hours. However it works now finally. Unfortunately I'm not using the RXP anymore, because of the lack of a possibility to update the navdatabase.

I won't disagree. It depends on who's ears it falls on I reckon.

2 hours ago, Adrian123 said:

 

I won't disagree. It depends on who's ears it falls on I reckon.

 

Hi, once a bug found, it is always the same: how couldn't it be found sooner, it seemed right in plain sight:

Nonetheless, both Carenado and RXP are small teams and it sometimes takes longer. The most important thing in the end is the bug found and fixed!