richboy2307

Then it would be due to the Xbox's aggressive memory management. While on PC, this issue manifests itself with blurry/lower LOD models at certain distances; on Xbox this leads to unloading of the entire object as part of the platform's aggressive memory management code. We are aware of this issue and working on it with Asobo to find a long-term solution. The LOD issue will be most prominent on terminals like OMDB owing to their odd long & wide shaped-design as described above, but the LOD ranges being spherical. You may read more about it here: No ETA I'm afraid. Especially when it comes to Marketplace releases as the ingestion/testing process is beyond our control. Thanks!

Hi @UA124567, Hmm, no that is not normal. That is not something I have noticed personally when flying the plane, nor observed from other users during testing either. Would help if you could upload a short video clip of your landing to youtube and share the link here. This will help to visualize and investigate what is happening. Just based on the limited information above, it could be related to flight controls/bindings. Such as a stuck brake (left or right), or uneven reverser deployment so make sure any of the controls assigned to that aren't misbehaving. Also check your Assistance Options to ensure none of the AI Assists (like AutoRudder) are enabled which could cause control issues. Thanks!

Hi @bicn787 Thanks for your report. May need an update of the scenery files. Will report to the team, thanks!

Could you please share a screenshot of the issue you are noticing? Both these items are already acknowledged feedback and have been improved upon in the upcoming update as part of Aircraft & Avionics Update 3 (AAU3). Thanks!

Hi, Please ensure you are running the latest version of OMDB (1.0.3) as it has included a slew of performance fixes and optimizations already, with more to come in a future update. Through our testing, we have seen great improvements, especially when it comes to VRAM usage and overall FPS across the board. Personally on my rig the current iteration runs smoother than KJFK. So, please share a screenshot of your in-game FPS counter so I can get a better idea for your performance limitations. Please also share your PC specs (CPU, GPU, RAM & Resolution used). Please also try to adjust settings such as Terrain LOD and Objects LOD to appropriate levels for your hardware in order to enjoy better performance. Thanks!

Thanks, I've noted your bug report internally. This is likely due to the XML rewrite, where the entire interaction system for the plane was re-written from the ground up using Asobo's recommended templates for improved performance. The downside of that template is that it causes issues with 3-way switches in "Legacy" interaction mode such as mouse wheel not working for all positions, or the interaction being reversed (scroll up moves switch down etc). We've notified Asobo of these shortcomings and can hopefully improve upon it in the future with their help to implement fixes to the sim's code. However until that time, this is an unfortunate limitation of the new interaction system. Thanks!

Those were instances of WASM crashes, where in the system "freeze" or fail in-place and are no longer responsive/usable. This doesn't appear to be the same thing as what we see is the fuel running out, and the systems shutting down, presumable due to a fuel exhaustion and loss of power event. As mentioned in the previous post - There was a bug with one of the previous versions related to a null value in the fuel system that was already resolved. The Null value caused the fuel system to output bogus numbers, which the sim read as having no fuel onboard. In any case, that was resolved already, and hopefully you will not experience similar issues after having deleted the generated files, freshly compiled/generated by the latest code only. Thanks!

Hi @Patrick C. The latest update to the A300 already has our new TERR RADAR incorporated into it. Read more here: It will also be making its way into the A320Neo with the upcoming Aircraft & Avionics Update 3 (AAU3) by Microsoft soon as showcased in the dev livestream yesterday: https://www.twitch.tv/videos/2224195807?t=0h19m8s Thanks!

Hi @PotatoSalad Perhaps try to clear all the contents of the folder listed below, as that will help reset the maintenance status of your A300. This should resolve any conflict caused by some status mismatch during an update. *Do note it may reset some options on the EFB, including your throttle calibration so you will need to set those again. MSFS Steam Edition: MSFS MS Store Version: Thanks!

Hi, Thanks for your report. It is very odd, I'm using the marketplace version of the EGLL in testing regularly on my rig (5800x3D, 3090, 32GB RAM @ 4K res) with our A320Neo and A300 recently and haven't experienced any consistent stuttering caused by the scenery. I have experienced instances of regular interval stuttering happening when the simconnect connection is being overloaded/stuck open (for example by Navigraph's Simlink, LittleNavMap or Volanta) wherein it is solved by restarting the relevant 3rd party app. Also occasionally stuttering caused by autosave functions in certain trackers or FSUIPC7. Perhaps worth looking into? Things to try: Clear your scenery index: Run with an Empty Community Folder temporarily to eliminate any conflicts: 1. Rename your existing community folder to ``_Community`` 2. Create a new ``Community`` folder in its place. 3. Run the sim and see if same problem persists. After finished testing, you can close the sim, and restore your original folder as follows: 1. Delete the new ``Community`` folder you made 2. Rename the ``_Community`` folder to ``Community`` Try without any of the 3rd party apps (Simlink, Volanta, LittleNavMap etc) listed above to see if they may be causing an issue. Yes you may request an order transfer from: http://inib.uk/order-transfer It is free of charge, simply fill the form with required info and you should receive a response via email usually within ~7 working days. Feel free to reach out if you have any more questions. Thanks!

Thanks for sharing! I haven't experienced this issue on any of the more latest builds in testing, so its possibly addressed already but your bug report is noted, and we'll look into it if we can reproduce it. Thanks!

Correct. It is not separable per variant/livery at the moment. This feature request is already noted on the internal Wishlist. No, its not purely cosmetic. It can have an effect on the ground handling of the aircraft, particularly to do with drag. However it won't disable the aircraft completely, nor "burst". Thanks!

Thanks, I am able to reproduce this. Will share with the team.

Maybe I'm missing some context here, but not sure what you're replying to here. None of the posts above are referring to speed, nor calling out your piloting ability, especially any posts by an iniBuilds staff/representative. In any case, can you please confirm you have followed the above suggestions? I have read your post and relayed to you that such oscillations have not been observed by us internally throughout testing, nor reported by our wider testing group of users. As such it is possible the issue is localized based on certain setting or configuration on your sim or control setup. All of the above suggestions are based on previous user reports / identified conflicts. They are mentioned for you to try and help eliminate possible factors. There is nothing here about being defensive, but rather relaying to you what our experience has been, and how we're not able to reproduce the issues you're facing on our end, so trying things to get to the bottom of it. Thanks!

The team is aware of this issue of WASM crash when making changes to the ALTN airport/procedures and working on it. For the time being we recommend using the SEC F-PLN instead, and not using the ALTN feature. Thanks!

Thanks, I'll pass on the suggestion.

Yes, as mentioned above, it takes additional time for updates to be available via the Marketplace. If you're on PC, you may request an Order Transfer to move your purchase from the Marketplace to the iniManager: http://inib.uk/order-transfer Thanks!

There is no update at this time, other than that Time Acceleration / Pause at TOD and other such QoL features are planned for a future update. As discussed on the Discord and other forum posts:

Hi @rlaycock This is because the scenery predates the New Zealand world update (WU12), which incorporated significant changes to the photogrammetry and other elevation data for the area. A patch was released to work around this, however as suggested in other posts, photogrammetry needs to be enabled. If you do not, then there will be issue with default buildings, as already noted by you. Any purchases made via the in-game Marketplace are handled by Microsoft directly. They are subject to the their store's policies, so you'll have to reach out to them directly for any such requests: https://flightsimulator.zendesk.com/hc/en-us/articles/360015885580-How-to-request-a-refund Thanks!

Hi @MarcusVT How are you toggling the FD/FPV switch? A keybind or LVARs? Or through mouse interaction? The switch is momentary and should return to the center (ON) position after you move it up. The mode switch between the BARs or FPV happens when the switch returns to the center position. In your screenshot I see it stuck in the top position, which is why the mode may not have changed. 2024-08-14 00-25-14(1).mp4 Thanks!

Hi @Jorrallcorrall There is already an update for xbox in testing with some more LOD improvements. We hope to have this out to users soon. However this issue is most prevalent at OMDB owing to the shape of the terminal being long and wide, whereas LOD zones are spherical. In any case, do let us know after the new update. Also please ensure that you have disabled the Asobo OMDB from the content manager (if using Premium Deluxe edition of MSFS) Thanks!

@Azlog Thanks, all of the issues listed above are known and being worked on. For this one specifically, it is loading in with incorrectly pre-filled values, and easiest way to clear is to toggle the units (Metric/imperial) in the EFB options. This will clear all weight values read by the FMC. Alternatively, you can simple overwrite the values with your own correct ones. Thanks!

Hi @LukeFF The GSX profile was updated for EGSS. Should also be updated via the iniManager already. Please check your GSX folder to ensure there's no left-over or conflicting EGSS profiles. For your convenience, updated GSX profile attached below: Official GSX Profile.zip Thanks!

As advised, we're aware of the issue and are working on it. The fix will be included in the next update whenever its ready, no ETAs. Thanks!

You can upload to Youtube and share the link that way. We'll look into it. Thanks!