Hi,

I'm pleased to announce v2.4.10 RC2 is now available!

Please make sure to post your feedback for this version in this thread only. Once we get enough feedback, this will become an official release through "Check Updates..."

This update includes:

• IDENT mode: it overrides the NAV1/2 audio panel while active, while still permitting to change NAV1/2 audio selection in the GTN. It also work with GTN+GNS V2 on the same panel!
• Fixes Avionics bus / battery bus problem introduced in the last update.
• Fixes Transponder switching to 1200 during takeoff.
• Further fixes the GTN trainer process stuck in boot, aka 'black screen'.
• Further Stability and Performance enhancements.

Fixes since RC1:

• Added Piper PA-28 Arrow III Checklists in the sample pack (credit Bourrinopathe).
• Fixes Flight Plan import.
• Fixes Database Selection not working in RC1 (Americas/Worldwide).
• Fixes RealityXP.GTN.ini file creation on new aircraft.
• Further fixes the GTN trainer process stuck during boot, aka 'black screen'.

Download link for both e-commerce installers

Edited November 28, 20178 yr by RXP
missing items in the list.

I have a quick question, if I have both the 750 and the 650, do I have to run both installs in the zip file or do I just need to run one of them.

I have always ran both of them previously.

Quote

Fixes Avionics bus / battery bus problem introduced in the last update

 

Looks like this isn't fixed. The GTN's are powered on if i start the aircraft cold and dark with "Avionics bus" selected on power source. If I change it to "Main battery" they start powered off.

 

@asandor you are right, only one suffice to install, as there is a single plugin handling both GTNs. There are 2 different e-commerce installers for license authentication only.

@Alvega this is a typo, this was meant for the GNS. Now, the Avionics Bus on/off detection is just based on reading the corresponding datarefs. You might want to cross check with dataref editor what the values are when the aircraft is cold&dark, and compare what the power status of the GTN is accordingly. The datarefs used are:

"sim/cockpit/electrical/avionics_on"
"sim/cockpit/electrical/battery_on"

It is possible this aircraft doesn't have its electrical circuits configured to power these on/off and this fails the 'power source' setting logic?

1 hour ago, RXP said:

@asandor you are right, only one suffice to install, as there is a single plugin handling both GTNs. There are 2 different e-commerce installers for license authentication only.

@Alvega this is a typo, this was meant for the GNS. Now, the Avionics Bus on/off detection is just based on reading the corresponding datarefs. You might want to cross check with dataref editor what the values are when the aircraft is cold&dark, and compare what the power status of the GTN is accordingly. The datarefs used are:

"sim/cockpit/electrical/avionics_on"
"sim/cockpit/electrical/battery_on"

It is possible this aircraft doesn't have its electrical circuits configured to power these on/off and this fails the 'power source' setting logic?

Jean-Luc, you are right. The plane is the default Cirrus. It doesn't have an avionics master switch and it starts with avionics on even in cold and dark. Is there a way to make it start with avionics off?

Thanks.

As far as I know, all this is configured with Plane Maker (the electric circuit), but this probably won't add a switch on the panel though. Maybe someone else might shed some light?

5 minutes ago, RXP said:

As far as I know, all this is configured with Plane Maker (the electric circuit), but this probably won't add a switch on the panel though. Maybe someone else might shed some light?

Ok, thanks. Sorry for the off-topic.

Just now, Alvega said:

Sorry for the off-topic.

On the contrary, it might help many!

Two birds one stone. Thanks to your report, Alvega, I think I figured out something.

That avionics bus is powered by default to avoid getting an instrument off on cold start with no way to switch it on if there's no avionics toggle switch. The Cirrus jet is a good example.
So, my guess is that LR kept that logic to prevent possible problems when using the Plane Maker.
I know at least one developer who had the avionics 3D toggle switch ON on cold start for one of his aircraft and it seemed stuck that way.
The solution is to modify the 3D panel and add a generic avionics switch - then the simulation will consider that there's a proper control available in the cockpit and the avionics will be switched off on cold start.

Adding a generic avionics switch in a panel using the Plane Maker would require to add a bound switch in the virtual cockpit too. Otherwise there will be no access to the avionics bus power.

So for the GTN, that's a normal behaviour.

Thanks Jean-Luc!!