richboy2307

Hi @RedBenny Could you attach a screenshot or short video clip of when you notice this issue? Can't say we've seen this internally or reported by other users. Such media will better assist to find clues as to what is going on. Thanks!

Hi @diogocec, The ''Rudder Controls Tiller'' is bound to 'Rudder Axis' itself (red box), and not the yawing commands (green box) which is what is used by default sim keybinds. You could also try to assign buttons to the tiller itself, such as 'INCREASE STEERING' and 'DECREASE STEERING' keybinds if you want to control it separately to the rudder. Thanks!

Hi @falcon71 Thanks, this is a reported bug and will be addressed in next update. Thanks!

Hi @falcon71 It depends on the charts, some are pre-programmed on TRUE courses in the database, but as a general rule of thumb it is calculated with MAGNETIC courses as default. The drawing on ND is equally done on MAGNETIC course, however the AP will make corrections taking into account things like wind. However it does seem like there may be some discrepancy here based on the MAGVAR, so I've shared with the team for further investigation. Thanks!

Hmm. @Superdraco2 Can you please confirm what was your FPS at the time you noticed this LNAV tracking issue? You can check your FPS in the sim by enabling Developer Mode. Then from the Devmode Toolbar on top, select Debug > Display FPS. Please share a screenshot of the FPS window during the time you have this issue. Thanks!

Yes, the stuttering can be caused by bad/missing Bing data. MS were temporarily having a Bing Data Outage at the time, but should be resolved now. Thanks!

Hi @Postman306 Try to disable photogrammetry and then enable it again. This seems like the terrain data for this area hasn't been loaded into your sim as yet. Alternatively, you can also try to clear your Rolling Cache (if enabled) and clear your scenery indexes (see here) and try again. Thanks!

Hi @Bachal For the radio panel you should be able to swap frequencies with the default simconnect event (COM1_RADIO_SWAP). You can read more about them here. But if you wanted to do it via LVAR, then it is (L:INI_CPT_VHF_TRANSFER_SWITCH_COMMAND) and (L:INI_FO_VHF_TRANSFER_SWITCH_COMMAND) for CPT and FO side respectively. You need to toggle the bit state (between 0 and 1), rather than write a specific value to it, for example below in SPAD.next:

Can't guarantee it but we'll look into it. Thanks!

Thanks we're working on sound balancing/loudness in general but it is an intended effect of "rising" wind noises as your speed increases.

Reported, Thanks!

Hi @Timm Turner Please ensure all your AI assists are disabled (Assistance Options). The conditions that could trigger an AP disconnect include input on your stick (elevator or aileron axis) or also on the rudder (rudder axis). Please check your bindings as well for any conflicts/double binding or "noisy" axis inputs that could be causing this. Thanks!

Thanks for the feedback, noted and shared with the team.

Hi @chard757 Just to confirm, you are only noticing this issue on the ONUR AIR liveries, and not on any other liveries for the A300? Thanks!

Hi @michel racicot This is a known issue and will be addressed in the next update. For now you can clear the message by pressing the 'CLR' key on the MCDU. Thanks!

Hi @Luvbeers, In which phase of flight, and where (cockpit, cabin, external cam)? Would be ideal if you could record a quick video clip (with audio) for when you are noticing the issue. Thanks!

Hi @WallyWalt, Can you share a screenshot of your PFD + FCU when you are noticing the issue? Also is this happening regardless of which procedure (STAR/Approach) or only on a specific one? Thanks!

For testing purposes, can you also mention the data you entered for your custom PBD waypoint? As currently i'm not able to reproduce a WASM crash (MCDU module freezing) after adding a PBD, and then deleting the "wrong" waypoint which was part of the VOR Y 29 procedure. Thanks for the other detailed write-ups @Azlog. Logged for further investigation, thanks!

Hi @lfrivera Please ensure you are running the latest version of FSUIPC 7. I have been running the A320neo with FSUIPC v7.4.11 without issues for the past few months. (Specs: 5800X3D, 3090, 32GB DDR4 RAM) Thanks!

Hi @Andy J, The glass avionics are disabled by MSFS (hence black screens) on X Box whenever you are running out of memory (RAM). What that means is you have too many things loaded into your sim, perhaps too much traffic, or scenery objects (dense scenery) for example. So try to reduce traffic (Aviation/Airport Life/Land and Sea Traffic categories) to see if it helps in such situations. Thanks!

Hi @kekki Yes that is correct, the plan imported/inserted manually into the MCDU will not be read by the in-game ATC. This is because the A320neo (v2) is not using the in-game planner for LNAV. For the in-game ATC, you need to import/set your flightplan on the World Map before loading into the flight. Then you need to import/manually insert your flight plan on the MCDU/EFB seperately. Thanks!

Hi @neagabi Could you try to delete the contents of these folders? It should regenerate these files when you load into the A310. Steam: %APPDATA%\Microsoft Flight Simulator\Packages\microsoft-aircraft-a310-300 MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\microsoft-aircraft-a310-300 Thanks!

Hi @Superdraco2 Please ensure you don't have any assists enabled (Options > Assistance Options > Piloting). Even if you didn't have them enabled before, do cross-check as MSFS has a tendency to re-enable them sometimes whenever it updates. Other users who reported such issues were able to resolve it after disabling the AI assists. Thanks!

Thanks, @Mathlets, can you also post your specs? (CPU/GPU/RAM/Storage Type (ssd or hdd))

It means the bug is logged internally for the dev team, and they will address it in a future update if possible. Unfortunately that is not something that would be user configurable, and will not be implemented as an option. Thanks for the suggestion though.