richboy2307

Sorry you feel this way. We continue to improve and update our products periodically, especially with performance in mind for Xbox builds. However owing to the complexity of this large airport in particular, and its vicinity to a dense populated area as well as the hardware limitations of Xbox, it is possible you will run into scenarios where you're pushing the boundaries of what it can handle (particularly when it comes to RAM) and thereby experience performance or instability issues. While we do our best to mitigate these as far as practicable, it is impossible to completely negate this whilst also offering the visual fidelity that customers have come to expect of us. Nonetheless, as on Xbox the purchases are made via in-game Marketplace, you will need to contact Microsoft/Asobo support regarding refunds. Thanks!

We'll look into publishing a list, but in the meanwhile you can do the above. Thanks!

Unfortunately not able to see your posted images. Nonetheless, we are working on longer term art fixes on windows and wings among other things. They will come in a planned update. Thanks!

Hi, are you still facing this issue as of SU 15 public release? We have not been able to successfully reproduce crash-on-load on either A310 or A300 reliably internally or through our beta testers till date so I'd recommend the following: What can you do? Troubleshooting such as : Do a flight without any other addons, or third party A310 liveries in your community folder, to see if there are other addon conflicts. (Simply rename existing 'Community' folder temporarily e.g. '_Community', sim will create a new empty one on next launch. After done testing, delete new Community folder and rename the old one back to 'Community') Delete the contents of your "work" folder after a fresh re-install to ensure no corrupted data Steam: %APPDATA%\Microsoft Flight Simulator\Packages\microsoft-aircraft-a310-300 MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\microsoft-aircraft-a310-300 Make these flights in default "White" or "Inibuilds House" liveries to eliminate any "bad" livery files causing conflict And when you do encounter the issue, report with: Screenshots/Videos of the failed systems or anomalies you notice Write-up of the things you did just prior to the crash (e.g. what you clicked, what you interacted with, what control inputs you gave etc) Route information & navdata used (E.g. Navigraph data - KLAX/24R LADYJ4 CSTRO DCT DUCKE DCT LMT DCT MOXEE TMBRS2 KPDX/28L ) Any extra things you noticed just before to the crash (e.g. momentary sim-freeze, abrupt winds change, sudden weather update etc.) All this allows us to try and recreate your flight to see if we face the same issues or find common conditions across reports to try and nail the issue. Your patience and understanding is greatly appreciated. Thanks!

It was previously only available to users who were enlisted in the SU15 beta, however it should be available to all now as of 20th May 2024 when SU15 was publicly released. Thanks!

Did you type in the Frequency in /XXX.XX format? Or were you trying to use the ILS identifier (e.g. IBSW)? However yes if you do encounter an issue, please do report back with a screenshot as well as the data entry tried. Thanks!

Thanks for the suggestion. I'll share with the team.

Thanks for the suggestion. I'll share with the team.

Hi, thanks for the suggestion. I'll share it with the team 👍

Yes currently only via those LVARs but I'll check with the team in case its possible to implement control via simconnect/default events as well. Thanks!

Hi, currently there aren't any more liveries planned for the A300 however we note your suggestions in case we do. In the meanwhile the best bet is for community to paint some, or find some painters through those sites to who may take requests/commissions for A300 repaints. Thanks!

Hi @janjoensson Usually we do not exactly when updates will go live, however EGLL update v3.1.0 (PC) on marketplace has finally gone live as of 20th May. Also for your reference, if you want you can actually request to transfer your order from Marketplace to IniManager here: https://forms.inibuilds.com/order-transfer Thanks!

Thanks but I believe this is more applicable to the A300 so moved. Thanks!

Hi, thanks for the video. I'll pass it on to the team.

Hi, thanks for your post. Apologies for the late response. Can you confirm when did you notice this? Also where? As I'm not seeing this as of the v1.1.25 on the overhead. Thanks!

Thanks for the feedback, i'll pass it on to the team! As for the Terrain Radar on ND however, that is not simulated for the time being as the default sim terrain radar has significant performance issues.

Thanks, please see this and reply there.

In my defence, FSUIPC has this labelled as "Toggle Reverse Thrust" for some reason on their mappings (lol), so I assumed it would be the same name on MSFS. But you're right the "Hold Throttle Reverse Thrust" binding needs to be used in MSFS instead. (See screenshot for MSFS controls setup) In either way it is setup, to achieve IDLE REV with reverser doors deployed, I have to move the throttles forward after lifting the reverse lever button (circled), but only ever so slightly. This is seen in the Spad.next screenshot - the bar fills up fully red at 100%/full fwd position. If you move the throttle lever axis back to 0%, then reversers will stow themselves so it does need some input above 0% for reversers to deploy. I've also enclosed a screenshot of the plane's throttle quadrant and you can see its basically just below 0, yet the reversers are deployed. You don't have to be significantly in the yellow range for it to work. Right, I don't use that bottom button zone for reversers. On my setup I use those instead for toggling fuel cutoff switches, so I can shutdown/startup engines using the Bravo TQ. While that would be ideal, unfortunately as far as we know there aren't currently any LVARs that can be written to externally for throttle control. ``XMLVAR_Throttle1Position`` (2 for Eng 2) is what controls the levers currently, with 1.0 being IDLE, 0.0 being MAX REV, so ~0.95 being IDLE REV. But I've tried via SPAD.next atleast and its unable to write to this LVAR reliably. It may set the value for a second or so but it will then revert back to original value. Do let me know if you have any success though. Thanks!

Hi all, Could you please record a video like this where you notice the issue? While this is PC, i've tried a few times and not able to reproduce these issues. In order to go back to managed mode there needs to be a valid flightplan in the MCDU as well as the INIT/PERF pages filled in. 2024-05-28 22-43-29(1).mp4

What do you mean the button is not recognized? With AP1 on, if you mouse over to the red button and click it, you will hear the alert for 1 second once but no master warning and or AP OFF ECAM warning. With AP1 on, if you disconnect via the AP1 FCU button, you will hear the alert continuously and get a Master Warning flashing red, along with AP OFF ECAM warning. Then if you click the red button on the stick, both will be silenced. (see video) Are you using any AI assists for rudder? Also the tiller axis is disabled above a certain speed (~80 KIAS if I remember correctly), but the rudder should still be effective. Thanks! 2024-05-28 22-12-59(1).mp4

On the A320Neo you need to set fuel and payload via the EFB. It will not work if you try to do it via the toolbar payload menu. After you select the desired value, you need to hit apply and select a loading option (Instant, Fast or Realistic). Not a video but try this: Thanks!

Hi @Marcel Booij On LOCKED interaction mode, when you left click on any of those knobs, it will show you a drop-down with the possible interactions in order to interreact with the switch. For example here in order to set Managed mode you need to Right click, or in order to set selected you need to middle click. In order to see this guidance you need to enable 'INSTRUMENT DESCRIPTION TOOLTIPS' from the accessibility menu (either Delayed or Instant per your preference) Thanks!

Hi @Frafty, the MCDU autofills the frequency as set by the airport scenery itself. However if there is some discrepancy between the airport data vs the actually ILS LOC/GS set-up per the dev or navdata then the end result is what you see. So its best to cross-check what is auto-filled and make the appropriate corrections where necessary as this is always a possibility with faulty/outdated scenery data. Thanks!

Hi @AFR7545 Could you please share the route you were trying? Also are you using Navigraph navdata? I've just tried on this route (VHHH DCT CH DCT MAGOG A470 SWA V37 JCS V36 TEBON ZSAM) and do not experience such issues (see video below) Yes this is the only one. If there are any changes, that package itself will be updated. 2024-05-28 20-52-35(1).mp4

Hi @Lewis Hughes This is the correct behaviour per Airbus logic as they want you to disconnect AP using the red disconnect button on the control stick. This should be mapped to the 'Autopilot OFF' command in the control options, so you could assign a key/button to it or simply click it twice with your mouse in the cockpit to both disable the AP and silence the aural and ECAM alert. Thanks!