IniSteve

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!

We're aware of the move but appreciate the heads up. Once the facility is fully completed, we'll see if it's something we can add in a future update.

There is a manual the aircraft folder located here - ....[YOUR COMMUNITY PATH]\kwikflight-aircraft-hunter\Resources\Documentation We also released a feature showcase the day prior to release -

Yes. Despite the guidnace from FSDT we have found that GSX is not always respecting the filter for 2020 vs 2024 in cfg files. Until it's fixed on their end, you'll need to switch profiles per sim if using the same airport. Nothing to fix on our end as explained above.

Hi. Are you using the correct winglet option for the aircraft?

Hi. I will move this to the proper thread. with respect to your issue, did you update the aircraft in the manager or install fresh?

HI. I need to confirm winwing has actually reached out to us but in the interim we'll take a look and see what we can uncover regarding compatibility.

Not needed, this is enough. We'll take a look and see what's uncovered. Thanks!

logged. thanks!

Hi. GUI issue logged. Time compression has been extensively tested in 2020 so something else may be causing your sim to reset the clock. Are you using any 3rd party ACARS or tracking apps in concert with the 350?

Hi. It seems the timing of inputs was changed inadvertently and should be resolved in today's update. Procedurally, take a beat (half second or so) between clicks to make sure the sim doesn't fail to register the 2nd one as a unique event.

Hi. We'll look into this and report back.

Route info please.

Hi. Thanks for your report and the feedback. We are investigating these issues. With respect to AP disconnect the resolution rn is to deliberately press the AP disconnect button twice. If you go too fast, it won't always register the second click (we believe something in the core logic has changed and are trying to determine what that is)