MSFS Products

@Bananza I'm sorry to say, I hadn't flown the F70/F100 in a little bit, but this wasn't an issue I recalled having. So I loaded into the F100 to check it out for you, and found that my tiller steering works perfectly, using Axis and Ohs and the AXIS_STEERING_SET event. I have seen other reports (don't remember if they were here or the MSFS forums) of issues with nose wheel steering, but they were reports of it working and then suddenly cutting out for a little bit, not of it not working at all. That particular issue I've had myself in a few aircraft, and it's always been a result of having the steering bound both in Axis and Ohs and in a MSFS control profile that the sim erroneously loaded. Your issue doesn't sound like this, but it might be worth checking, if you haven't already?

We do have this logged on our internal trackers, and we'll be further investigating it ahead of the next RJ update. From our previous investigations, it appears to be a core MSFS 2024 bug, and fixing it on our side will require a rewrite of that autopilot mode's code, which is a significant time investment and needs to be scheduled into our workflow at an appropriate time. Therefore, we can't provide a specific time frame for when the next RJ update will be at this time. From my experience, the aforementioned LVL CHG behaviour may only exist on the first LVL CHG engagement of a flight and only if a specific simconnect call is being made by another program to generate AI traffic. If you experience this behaviour in the sim under those conditions, my recommendation is to toggle LVL CHG ON > OFF > ON, and LVL CHG will then behave as expected for the remainder of the flight. Mark - Just Flight

I'm pretty sure it worked for me before. Are you sure the Visual Approach you selected has a GP? When loading the Visual you'll get a pop up saying something like "Visual Approach for referency only, no obstacle clearance assured" and "TCH:XX" as well as "Glidepath:XX". Normally you have a 3° GP but on some approaches it will just say "-" meaning there's no vertical guidance available for the visual.

If Working Title puts the Aspen avionics natively into MSFS, that might be an option too. I thought I saw that somewhere as being on their to-do list but I could have been dreaming. It would be inserted into the panel much like the 430/530 units are now...those are Working Title's 430/530's.

It looks like the correct TACAN frequency for the LKH TACAN is 39X. Mark - Just Flight

Sorry - been travelling (for real as opposed to in sim) and just saw this. Appreciated ... I wondered if it was something like this I was missing :). I will check it out soon now that I am finally back in town for a good while.

Could I kindly ask you to raise a support ticket for this with Just Flight Support at the following link: https://www.justflight.com/support Our support team is best positioned to provide assistance and troubleshooting. Mark - Just Flight

@badgersausages This sounds like something Just Flight or Just Trains support could help with. There are links on their websites www.justflight.com and www.justtrains.net See: https://www.justflight.com/support https://www.justtrains.net/support

@Mark Hi, I’ve shelved the Hotas 4 and reset alot of my settings, including the DualSense bindings, and everything is working great now. Spotting the trim sensitivity setting was a game-changer too. Thanks for the help

Yes, that is intentional. We removed the tutorial flight files from our aircraft packages in order to comply with some MSFS Marketplace requirements. The manuals likely do still refer to the tutorial flight files, and it is something we have logged to get corrected the next time the manuals get updated. The old tutorial flight files simply loaded the aircraft at the location stated in the tutorial flight; they didn't affect the aircraft systems in any way. So as long as a flight is loaded at the departure airport stated in the manual, it'll still be possible to complete the tutorial flight in full. Mark - Just Flight