MSFS Products

@Black-Square that is totally understandable that in a product this complex there will be some bugs on release. It's an amazing piece of work you've done there. Please don't feel pressured by all the bug reports, take your time. And I personally really appreciate you sharing the hotfixes with us when possible.

I am having major issues with the Arrow AP. I don't want its altitude hold feature active, I want to control the trim myself. I don't know if it's my logitech AP unit or what but the plane never seems to want to stop holding altitude. Because there is no switch just a clickspot, I can't tell whether altitude hold is supposed to be on or off, and my bindings for altitude and heading hold seem to do nothing in this plane. I'd like an option in the ipad to disable the clickspot and all the altitude features of the Arrows so they NEVER take control of trim, and the AP works as it would in real life, please. And ideally I'd like the "Heading Hold On" and "Heading Hold Off" bindings to work so I can use my switches instead of the mouse.

I think it might be my logitech AP unit interfering, so I will test with it unplugged, but it seems pot luck whether I can get the AP in the Arrow to release control of trim.

I accomplished this by purchasing the FIPs MP, RPM and engine gauges from FSX Times. Using SPAD.neXt (a FIPS subscription is required), I detached the gauges to a separate screen so that I can see the gauges.

I bought this screen from Amazon https://www.amazon.com/dp/B0C746JHJJ?psc=1&ref=ppx_yo2ov_dt_b_product_details

@trevor250

See this page - there is an email link to submit queries if you have bought products from elsewhere:

https://www.justflight.com/support

Did look but didn't find an earlier post from last year which I have now found through google and can see that this issue related to mixture = 0 setting on controller. Now tested by having Mixture 1 fully rich on my bravo and no engine shut down after pressing the ESC key. Alternative being to set up a separate Bravo profile for the Hawk and delete the mixture axis.

Thanks for confirming. That's the 'Classic' UNS-1 FMS so the LVars you listed above are correct.

In theory, all you should need to do to trigger a key press is to set the values of "PED_FWD_L_FMS_A" to "1". That will register as a press on the FMS and our code will then reset the LVar back to "0". Note that you likely will not see any animation on the buttons with this method, and we're not too sure there is a method that will allow for the animation to properly trigger with the press detection.

The above example is for the "A" key on the left FMS, but you can use similar LVars for the other keys "PED_FWD_L_FMS_Lsk_1L", "PED_FWD_L_FMS_1", etc

Hope that helps.

Mark - Just Flight

There are many factors that could prevent traffic from generating in the simulator, but a quick one to try is to open the Traffic Control Centre and then go to the 'Options' tab. In the wingspan options box, select "Compatibility Mode (High)", then "Confirm Change" and then restart the simulator.

This option controls the wingspan values set in the config files for each of the FS Traffic aircraft. Every gate and parking space in the simulator has parameters set up that determine the maximum size of aircraft that it can accommodate. Sometimes this value might not be set to the correct value by the scenery developer and therefore can prevent any aircraft larger than the size defined by the gate/parking space from generating at that position.

Reducing the wingspan of the Ai traffic fleet ensures that FS Traffic aircraft can fit in more gates/parking spaces.

Mark - Just Flight

I believe you would need to restart the flight in order for the lock wiring to reappear. You may also need to disable state saving (if enabled) to prevent the aircraft from loading in with the valve already open.

Mark - Just Flight

@NickW61 I'm having this issue. When I open the aircraft, EFD is unclickable. When I start the VR, this show that "pink texture" and work even worst, which made me think about some Texture conflict with the B78XH, cause when I removed it, the problem was gone.

Thanks Mark - for excellent reply!