IniSteve

Hi Willy, Thanks for the report. We'll take a look and see if we can reproduce. Have you tried to fly the same scenario again since posting?

Hi. the small variance between planned and live is by design, to factor in real world style manifests.

Thanks!

Aircraft specific event variables list. Pocket Rocket Hardware Key Bindings.pdf

Pocket Rocket Operation Manual.pdf

Hi. This is in fact the case with our reference aircraft as well as many in-use examples still flying where the MCDU has been replaced despite the avionic suite being older. In any event. We will log the feedback and discuss it as a possibility for the future. Thanks!

Hi all. While we understand the frustration, reverting back to single displays is neither easy or efficient. Despite that, we will take a look to see if it's possible to implement an alternate solution. Thanks.

Hi Marco. Your brightness is too low. When its at its lowest position, the RDY light comes on as its basically in STBY mode

Hi. We're investigating this and hope to have a solution soon. Thanks for the report.

This is logging and has been sent to the cabin team. Thanks.

Hi. We no control over regional pricing.

Hi all. We have confirmed this is a side effect of the SU4 beat update. We've communicated it up the chain and are waiting on a fix.

Hi, this is by design and a quirk of the Airbus system. The TO/LANDING INHIBIT messages are designed to prevent non-critical messages during the most important phases of the flight. Unless it's a warning, all ECAM advisories are suppressed until in climb or taxi phase.

Yes, the betas always bring some quirks that require workarounds on the user side. Glad to hear it's working well despite that

Hi all. I have some positive news. Just loaded into the SU4beta update and it seems whatever change they made affecting SU3's LOD boundary in the VR sphere is fixed or reverted. The 350's cockpit is correct and fully interactable. I will continue to test this during the life cycle of the SU4 beta but this is a positive start. Perf is also screaming in VR but that's a topic for another thread 😉

Hi all. We are not seeing this on our end in either pax/cargo variants. In fact we find the engines are powerful enough to accelerate to takeoff speed with mid-range torque values. Pax- 2025-07-21 06-57-25.mp4 Cargo 2025-07-21 07-02-00.mp4 Can you all confirm props are set to full RPM and the parking brake is indeed off prior to setting full power?

Hi. Back into the swing of things and we have an MCDU on hand. Hope to have an update soon.

Ah, yes. I'll pass this on to the team and see what they say.

Hi. To clarify, the position isn't it won't be implemented, but that it ships with a simplified FM that binds trim to power and the simulation of the stability system. Despite that, the kwikflight team is working on an advance FM update that will ship in a future update. You'll be able to toggle it on and off prior to sim load should you desire.

HI Rudilo! Thanks for the comments and so happy to hear you're enjoying the Hunter. To address your comments, the wire cutter is present on the cannon as well as the struts (see attached images) The Kwikflight team is working on improving the payload/visual options and these should launch in a future update. The strut height has been compared against some other avail sim options as well as real-world reference and it matches up pretty well. Despite that, I will send your feedback on to see if it requires another look. Thanks again!

Hi, this is due to an issue in how the sim interprets layers with VR. It's not a quick or simple method but the QF folks are looking at how to make it work while not sacrificing performance.

Nothing yet but should have more to share after FS Expo at the end of the month.

Possibly, but I'm going to work one problem at a time 🙂

Something appears to be corrupted in your plan/autosave. I was able to reproduce the issue when loading your save but when I replanned the routing fresh from C&D there was no turn to the right or stall condition induced. Of note was the 430' alt constraint did not auto sequence to the next WP so we'll look into why that happens on certain procedures.

Hi. This is known and logged. Thanks!