richboy2307

Hi @LukeFF I'm afraid I'm not able to reproduce this issue on my end. Haven't seen any reports as to that from our testers either, who use it routinely on VATSIM/IVAO so it would have caused issues in those environments. Enclosed video for reference (ignore the warning in the end, I hadn't aligned the IRS yet) 2024-08-19 16-49-18(1).mp4 Could you check that your AI ATC Communications option is disabled from the Assistance Options? If not, then perhaps try without any additional 3rd Party programs, or an empty community folder to rule out any add-on conflicts. Thanks!

Hi, apologies for delayed response. I missed this report initially. Been a hectic few weeks. Yes I can confirm this bug, the drawn WXR image does not seem to be updating with selected range on ND. However, I'm not able to reproduce this issue. Can you confirm the steps taken for you to notice this? I tried changing systems (1, 2 or off, then back to either), and turning the mode select knob (TEST, WX, TURB, MAP) and was still able to have the WXR work. Just the range cannot be adjusted. Thanks!

Hey @Allard Ah yes I'm seeing this issue too in LNM and on the World Map. Thanks, I'll share your report with the team.

Hi @ThibaudBenjaminVandenhoven, I notice your engines aren't running as yet. As the hydraulics are driven by the engines, can you check if it works fine *after* you have started your engines? What I see on your screenshots seems normal for an engine-off situation as the BGY (Blue,Green,Yellow) hydraulic systems aren't pressurized as yet. However, in case you still notice an issue after starting the engines, can you please check your assistance options to ensure all the AI Assists under Piloting, as well as assists such as "autorudder" are disabled? They are known to have caused issues in the past. Also if you're on PC, you can try to clear the contents of this folder below such that the plane will recompile all files "fresh" on next launch of the A300: The location will vary depending on which version of MSFS you have: Steam Version: MS Store Version: Thanks!

Hi @Tyler Thanks for your report. I'll share with the team.

Hi @TJC This is not implemented as yet (v1.1.2). It is noted on the internal wishlist, no ETA at this time for when it will be implemented. Thanks!

Hi @nick Mathias This was an acknowledged bug in the current version. Should be fixed in the upcoming AAU3 update. For now, DIR TO next waypoint is the best way. Thanks!

Hi, thanks for your reports. Apologies, it seems it somehow slipped through the cracks when initially reported. I'll share with the team. Thanks!

Can you check if you're running the latest version of the iniManager (v2.3.8)? You can see that on the settings page. If not, grab the latest from here and simply run the installer to install the update on top of existing install. Thanks!

Hi, the use of add-on linker is currently not supported by the iniManager. We are working on this for future version so users may be able to define custom library locations. As such there may be issues. Also please try to re-scan your library in the settings (click on your name top-left corner) to ensure there is no mismatch. If the update process was not completed properly, it may continue to show you updates available. So please let it run completely then try again. Thanks!

Hi, As mentioned in the attached post, AviaWorx has reached out and we'll be working with them for a remote FMS option on the A300 MSFS. For the A320neo V2, as it is a Microsoft product, it is up to them to decide. Thanks!

Good catch. Maybe he missed his flight? 😅 Will report to team, thanks!

The sim environment is dynamic, so is the state of the product with new updates coming over time. SU15 brought with it new ground handling physics, and so did the A300 update with that which incorporated it. Thanks!

The decision regarding that is up to MS ultimately as is the case with all of their products. This is not a confirmation or a promise, merely personal opinion - it is more likely than not. Thanks!

Thanks for the report. Can you specify the full route used (along with SID/STAR/APP) as well as planned ZFW, Fuel load & Cost Index to see if we can reproduce the issue with those exact parameters. Both instances appear to be high altitude airfields, near hilly terrain, so warrants a test. However for transparency, I've tried the approaches at MGMM and LFML already twice without issues on my end personally. Thanks!

Hi, I've included a screenshot of how its looking on my end. However, I did notice a similar issue as you when trying via Xbox Cloud. MSFS on Xbox will sometimes disable certain objects and effects in order to save memory, so it may be what is happening in those instances there. Thanks!

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!

Hi @MaxiMoose Thanks, i'll share this feedback with the team. In the meanwhile, please ensure you are using the latest version of the iniManager (v2.3.8). This update added in the "Alternate downloader", which allows you to select between two different download methods if you are encountering download issues. Enabling this should result in faster downloads (however has the potential to be slightly less reliable in extreme cases). Any issues please do report them to a member of staff and we'll continue to try and resolve any bugs you are encountering! This option can be enabled in the app settings section by clicking on your name on top left corner. Please try it next time you are downloading, to see if it helps in your case. 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!