IniSteve

OK, barring a line-item response to everything reported in OP's post I can say we take each and every one of these reports seriously and track and log them on our issue tracker. We know it can be frustrating when certain bugs linger or when smaller QOL items take longer than expected to resolve. Behind the scenes, our workflow is to prioritize fixes based on impact, reproducibility, and the resources we have available. Showstoppers and issues that impact use naturally rise to the top, but we also need to ensure those fixes don't cause follow-on issues, so the overall experience keeps moving forward. It’s a constant balancing act, especially when the same team is also maintaining existing products and supporting new development. Items like the HUD however are already set to receive a deeper update in the future. (Our intention is to completely rework the HUD but as you can expect these updates take significant time and resources, so they are planned out in stages) That said, we genuinely appreciate the patience and constructive feedback from the community. Your reports help us reproduce problems faster and understand which issues affect the widest group of users. of course we can’t fix everything at once, but we remain committed to steady progress and to delivering updates that meaningfully improve the experience for everyone.

Hi, We used high resolution mesh for the area but we're happy to take a look at further references if you have them and they are authorized for free commercial use.

Hi all, We are tracking this issue. We're not entirely sure what happened as it was working as expected in the RC so we're investigating. We have earmarked a hotfix for the known issues for this coming week and will try to rectify this and get it in as well, but we appreciate your patience in the meantime. Thanks!

Thanks for this feedback. I've passed this post on to the art team.

Thanks. I will forward this to the sound designer.

Not really no. We have found the sim itself exhibits poor stability above 4x so trying to combat that is a challenge.

Hi, Try refreshing your Navigraph token. This should resolve the issue with both terrain data and ANF functionality.

This should be resolved in the forthcoming 1.0.4 update but as we mentioned when WW first brought the MDCU feature in 340 online, we never promised full compatibility as it was as much a surprise to us as to the user. Despite that, we have had several rounds of conversations and development calls to ensure it's fully featured once the update rolls out. The last flight I did was 10.5 hours long and I didn't lose sync so its feeling promising.

Hi. Launch the manager and let me know if you have an update for this livery and if it resolves the issue. Regarding the winglet config, not every livery has automatic configuration so you can just set the correct type in the EFBN.

Yep, understood. We'll take a look and see if it's something conclusive or if it's a "quirk" of the WASM process. Thanks again.

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 😉