IniSteve

Thaks for the feedback. I'll pass it on to the sound team.

Hi Thomas. Understand the frustration but this doesn't seem to be a widespread issue. Can you share your autosave and OFP/Flightplan details so we can try and reproduce the crash internally? The changes made to the model to reduce node and bone counts were really necessary, and not just for those on low-end hardware but even for those on higher end hardware, especially Intel and non-x3d chips. As mentioned in our post these changes significantly reduced stutters when looking around the aircraft or changing views, which of course benefits all of us even on the highest end chips and also helps with stability as these stutters can affect that as well. Regarding the cabin packs, unfortunately these changes broke them completely, and they were already very difficult for us to maintain as any minor changes to the interior 3d models had to be repeated manually for every cabin pack across every variant. With this change, it was a bit of a final straw, and we've decided that the time and resources needed to maintain them is simply not sustainable for us as these efforts are better focused on the core aircraft as well as our other upcoming projects. Hope that helps clear up the factors that led to our decision and helps everyone understand it wasn't taken lightly. (for others following along, I deleted the other posts that were not relevant to OP's issue so we can all focus on helping him)

logged. I will pass this on.

Hi Daniel. We are aware of the zoom limits on the 350 and are investigating the issue as it works correctly on our other aircraft which have the same boundary limits. Thanks for your patience while we figure it out.

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.

The Navigation Display (ND) on the iniBuilds A350 Airliner can display terrain and obstacles information when the TERR ON ND pushbutton is pressed. This function relies on a Terrain Database which is downloadable via the OIS - 3RD PARTY OPTIONS page. (Click to enlarge image) Why is this required? This process helps ensure terrain data integrity by minimizing risk of corruption whilst streaming the package. This process reduces overall bandwidth usage whilst streaming the package. When is this required? This process only needs to be done once when you first launch the A350 Airliner after your purchase. The process does not need to be repeated when updating the aircraft - unless stated specifically in the changelog. The process is only required again IF you manually delete your Terrain database (.bin) file which is located within the WASM/Work folder. How to download terrain data? Navigate to the Options > 3rd Party > Download Terrain Data section on the EFB Press the START DOWNLOAD button and wait for the download to complete. Once completed, you will see a notification at the top of the EFB Display. Press ESC to return to main menu and restart your flight for the changes to take effect properly. (Click to enlarge image)

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.