Wow - that must have been an amazing experience for the young you! Definite second from me on getting the VC-10 in the sim!!!

Push/Pull for ALT and SPEED definitly don't work with LOCK INTERACTION. Would be great if you guys could fix this.

disregard - I guess I should have used the ADV button :p A power reset still did not allow to get rid of the message though !

@Zajcek100 To keep this from getting too long, I've picked out a few relevant FMS or EICAS messages that may appear regarding degraded navigation modes. The POSITION UNCERTAIN alert is an action‑required message that appears when the radio signals received by the system typically from VOR/DME or VLF/OMEGA stations don't match the position computed by the Flight Management Computer, indicating an inconsistency that requires the pilot to manually update the aircraft's position in the system. The FMS/VLF POS DISAGREE alert is a more specific message related to very low‑frequency radio navigation. It illuminates when the difference between the FMS‑calculated position and the position determined by the VLF/OMEGA sensor exceeds a threshold of 2.3 nautical miles. It remains active until that discrepancy is reduced below that value, signaling that the long‑range radio system is providing a fix that doesn't converge with the rest of the navigation solution. Finally, the FMS IN DR MODE message (as I explained above) is a status message indicating the worst‑case scenario for navigation. It means the FMS is not receiving adequate radio signals from any source whether VOR/DME or VLF/OMEGA forcing the system into Dead Reckoning mode, where it relies solely on the last known position, combined with magnetic heading and true airspeed, to project the current location. This degrades accuracy and causes the computed wind vector to freeze on the display until radio signals are restored and the system automatically reverts to primary mode. The first two messages are alerts that call for corrective action by the pilot (updating the position in the system), while the third is a confirmation that the system has lost all external references and is operating only on internal dead‑reckoning data.

@Kestrel21 That's my understanding too. My intention is to offer the enhanced volume and clarity of the interaction sounds while using headphone simulation as a replacement for the haptic feedback that you would receive in the real aircraft.

Sometimes doesn't engage PROF yes, it gives me this error sometimes when I change the original CRZ altitude. Imagine it came from Simbrief FL350, and I see OPT altitude is FL340 so I change it to FL330, on the CDU Screen I see "wrong cruise altitude", some warning like that, not sure the sentence now, I know from there that I can't engage PROF, all flight, even in flight cruise. Think could be something with the Simbrief initial import... don't know. PS: Doens't know it it is an "error", it just doesn't engage.

I’m completely at a loss here. I’ve removed every single addon and even reinstalled the bundle from scratch, yet the radar altimeter still doesn’t work at all — neither on the passenger nor the cargo variant. Is there anything else I could be missing? I’d really appreciate if someone could shed some light on what might be causing this radar altimeter issue on the Caravan.

Would it be worth it to update to the hotfix or just take it out of ATS and manually apply thrust? I’ve noticed this on approach into RWY18 @ YPXM with flaps 42° and did troubleshooting with flaps 25° and noticed a slight improvement but after a multiple attempts I ended up just taking the plane out of ATS altogether and at MDA, I then took out the AP as well and got the results I wanted.

Hi there, Do you already have found a solution for this issue? I have bought, two weeks ago, the PA-28R Arrow III and PA-28R Turbo Arrow III/IV and I am facing the same issue or worst because after remove the *.PNG file from .../charter folder and remove the three lines of code from *.INI file the MSFS2024 (Steam) continue to freezing or close during the fly loading with the Arrow III/IV. To solve the issue was necessary remove and reinstall the plane. Adding documentation, it's a functionality that I would like to use and for my surprise I have founded this post already posted December 2025 but the issue remains. I´ll appreciate any help or recommendation to put the documentation adding work In advance many thanks Note: I haven´t tested add documentation with the PA-28R Arrow III to avoid more issues with MSFS2024 while I haven't a solution. I have already created a post in the Just Flight Support and I’m waiting for an answer.

Perfect moment to get it for a small GA that is often owner-operated, makes sense for everything to be as you left it

Thanks for confirming. I'd suggest sending support a ticket on this one as I've not been able to replicate the problem here. It should just be a case of clicking the door in this area. [image: 2779f32f-3443-4d40-96fe-b5e011b69670.png]

I don't see an issue with the placement of the LIM waypoint here, as @JabbyJabara says those are all 6000+ restrictions so you wouldn't expect to be at 6000ft until WW974. What was your cruise altitude for the flight? As for whether the LIM point would reflect an earlier speed restriction, we had quite a bit of debate over this internally but found evidence amongst the documentation that it always will display the standard 250/10,000ft but the aircraft will stick to the procedure speed restriction.

@Cptrossco Unfortunately, it's not feasible to convert the FSX/P3D version of the 748 for use in MSFS. The aircraft would need to be built from the ground up, as per the F28 and F70/100. Based on the sales of the 748 in earlier sims, I am not sure the commercials would stack up on this one.

Thank you! It worked!

It’s a wonderful aircraft, but I’m unable to fly it in VR because of the cockpit proportions. I hope Just Flight may fix this in the future. None of their previous aircraft had issue like that.

I also noticed that changing the viewpoint helps in VR, but unfortunately it doesn’t change the fact that the cockpit proportions are incorrect.

@Rich That didn't happen when I updated to v1.2. In the original release it did allow me to install it elsewhere, but when I updated to v1.2, it didn't give me the option, only removed the old installation from the custom directory, and installed it into Community directly...?

Thanks all. We'll investigate.