PA-28R Arrow III

@Bert-Pieke said in We need a NAV/GPS switch for the Arrow: @vcapra1 Just rethinking the whole thing... for the GNS and GTN panels, no switch (or clickspot) required, check. You can switch on the GPS unit, using the CDI button. For the G100 panel, fix the connection to NAV mode and leave it there, no switch (or clickspot) required either. Problem solved. No, that is not a satisfactory solution at all. See my answer to your comments in this post: https://community.justflight.com/topic/2062/real-life-nav-gps-mode-switch-and-annunciators/12

@Martyn thanks. Ticket created.

See - https://community.justflight.com/topic/2012/no-more-gns430-gps-option-on-0-4/4

Unfortunately we could find no way to include the options for having the GNS 430 as both COM1/NAV1 (as the primary GPS) and COM2/NAV2 (when selected alongside the GNS 530), as you have to define in the panel.xml file which COM/NAV radio each GPS controls and that is only checked when the aircraft is first loaded. We'll continue to investigate and restore the GNS 430 option if we find a solution.

This will be fixed in the next update.

Thanks for reporting this. It will be fixed in the next update.

This will be fixed in the next update.

We're using the logic/model behaviour supplied to us by the GTN 750 developer. Can you confirm if you see different behaviour in other aircraft using the GTN 750?

@Martyn said in ON/OFF Control Assignments Issues: The beacon light control code is identical to all the others so we're investigating if the issue is caused by MSFS/SimConnect. There is also no way to intercept the fuel pump on/off events using SimConnect in a WASM gauge at the moment. This might be an MFS-wide issue, where the button functions are not hooked up correctly in the code.

Tnx! That was it. Just did an ILS now with CB on short final. Really cool;) Tnx a lot!

@RetiredMan93231 That works for me Thanks to all for the input on this thread. For further information, this is the load_safety_factor line from the Bonanza flight_model.cfg file: load_safety_factor = 1.5 ; Flap negative load limit when down. Same dimension as gravity vector FEET/SECONDS^2 If this is correct it appears from this that the load_safety_factor line only applies when the flaps are down, which further justifies changing the negative G limits in the Piper Arrow file rather than change the load_safety_factor.

@weptburrito Yes This is the breaker I used. When that didn't work, I pulled them all. The gear will still extend and retract. Created a ticket and got acknowledged that the ticket was placed. Waiting on further advice from Just Flight. Thanks, everyone.

Ok I’ll try that. Thanks for the advice guys.

Just checked with new update and now works correctly. Garry

Ooh, ok, thanks

@vcapra1 thanks!

@Cristi-Neagu , Yes... I am only using the native MSFS commands.

I have this problem too. Tried flying in the French Alps. But every time I go above ~9000ft (in clear air) the airplane catches ice in a matter of seconds. The windscreen gets completely covered in ice and it looses lift to the point it stalls. Again this happens in a matter of seconds. I have pitot heat on, full hot air blower on the windscreen and alt air enabled. What else can I do? I have flown the exact same route in the same conditions in the default C172 and it did ice up a little but but kept flying without issues.