MSFS Products

UPDATE: I've just had it happen while taxing at KSMF, an airport I use all of the time and have never had problems with, anywhere, I'm nearly 100% certain it's not the airport.

I have tried the Turbine Duke, it works 90% but the altitude indicators and baro numbers are wrong. That makes it unplayable for the moment. Also something fishy seems to happen with the amperometers fluctuating more than usual and the cabin thermometer is showing wrong temperature in comparison with the tablet which seems to be the correct one.

Thanks so much for getting back to me. I know JF is very busy with the new RJ, so I appreciate it. I'll try what you mentioned, not just for the Tomahawk, but for the BkSq mods as well.

The TFR does not have a coupled autopilot mode in the Vulcan. Once an altitude is set on the TFR height selector, the pitch attitude required to maintain that height above the terrain will be displayed by the flight director. This is how is works in the real aircraft too.

Mark - Just Flight

Thank you for reporting this. This is something we have logged on our internal bug tracker and is something we plan to investigate ahead of the F28 V2 update. I suspect it's caused by a limitation of having a single GPS unit in the aircraft, but we will investigate that further.

Mark - Just Flight

From my experience, go into SYNC mode, follow the FD and trim out the plane. Once you are at a point where you only need minimal control inputs, the AP should be stable enough again once you disable SYNC.

It seems to be a runaway condition somewhere in the AP code that sometimes starts to overcorrect deviations and can't get back to stable without manual intervention, but once you've intervened it tends to remain stable for a long enough time again. Usually that happens on slowdown for descent/arrival/approach (somewhere below 220kt) and is easily corrected.

FS Traffic is not officially compatible with FS Hud so this isn't something we would be confident in answering. We do, however, have FS Hud compatibility logged as a feature request on our internal trackers.

Mark - Just Flight

The flaps in the Hawk are controlled by the standard flaps control assignments within the simulator. The most likely cause of the flaps remaining in the down position will be a control on your external hardware extending them. An easy way to test this is to unplug any external hardware (joystick, throttle quadrant, etc) and then restart a flight. If that fixes the issues, then that confirms the issue will be linked to the external hardware.

If the flap standby lowering system is triggered, the flaps will be locked in the fully extended position and will require a restart of the flight to reset.

Finally, if state saving is enabled on the EFB, the aircraft will load in the state it was previously left in. So if flaps were fully extended at the end of the previous flight, they will be fully extended at the start of the next flight.

Hope that helps.

Mark - Just Flight

@Mark : Ok, thanks !

Thank you for the feedback. I have added this to our internal feature request tracker as something to consider adding in a future update.

Mark - Just Flight