IniSteve

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 all. Very much appreciate everyone who has taken the time to share their feedback. I’d like to provide some context on our perspective so that we can come to a shared understanding. As with any product release, sometimes things may not come out exactly as expected. While we are overall happy with the way this product has been received by the userbase we could tell within a short time that certain things needed a second look and took matters to ensure updates would be frequent and robust. We have stayed committed to addressing issues promptly and have consistently released updates to resolve major concerns, while also introducing new features based on our planned roadmap as well as user requests. Initially, we released updates on a weekly basis as well felt it was important to stay ahead of items we identified as pressing and with each of these updates, we addressed a variety of issues that have been reported by users. It’s not uncommon for feedback to include, “Stop releasing new features when existing issues persist.” While this critique is understandable, it overlooks the fact that we are continuously releasing fixes for issues alongside new features. From day one, our commitment has been to deliver both updates that resolve problems and those that introduce new things for you to enjoy. Now that we feel the aircraft has reached a more mature state our primary focus shifts to resolving key reported issues. When it comes to performance improvements, these are included with each update as well. Some updates may emphasize optimization more heavily, while others focus on general improvements. While it may be difficult to believe, we do see positive results for many users with each update. Despite that, we want to make it clear that we don't dismiss your concerns about performance on your machines. We understand how frustrating it can be, and we are continuously exploring additional optimization methods to improve the experience for everyone. However, it’s important to recognize that perfection across all machines may not be fully achievable, but we endeavour to get as close as possible. Lastly when one of us replies with “it's been forwarded this to the team,” that means your feedback has been received and passed directly to the relevant team. Typically, the titles of threads, whether on this forum or Discord, will reflect the change-log entries. For example, if you report that “the chair is 3 degrees off,” we try to make sure the change-log entry reflects that title. We aim to keep it simple and transparent so users can see if their specific issue has been addressed. However, if you would like more detailed updates or outreach, please let us know and we'll do our best to provide that. While we can’t directly follow-up on every individual change-log entry, we will do what's possible to keep the process transparent and open. Thank you.

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!