I was using the A320 Fly by Wire mod with no problems prior to the update. After the update, I was able to load the plane, but the cockpit screens were blank. I researched and found out that this was an issue for all the FBW users. FBW said to download a specific hotfix development version that corrected this issue. I did, and then the sim CTD every single time I tried to load it. The crash always occurs during the C172 screen display. I can select the A320 and I see the new liveries. I then deleted the latest FBW mod from my Community folder. The same CTD still occurs at the same place in the loading sequence. So far all other aircraft load with no issues.
Did you install a hotfix or just switch to the dev build of FBW? I just switched from the stable to dev build with the installer, and the panels work fine now. No CTD (knock on wood) that was last night anyway, who knows what tonight will bring.
Question: I’m having issues with the mod not wanting to follow the FP on autopilot. When I engage the AP, it just flies a heading of 360 degrees straight north and completely ignores the route I created. I’ve been testing it all day with no different results. Both the dev. and custom versions.
Used the development version with hotfix as specified on the FBW website.
Did you do any Livery modifications especially something to do with Generic AI traffic?
@FearlessTiara18 Were you able to fix this issue? I also just head north, and it ignores my flight plan. I can set heading but AP won’t follow the plan.
I’m not sure if this is related or if it helps your case, but I think most people don’t realise that the Sim update doesn’t automatically update the A320. You have to do this manually through the content manager.
So remove the A32NX mod from your community folder. Start the sim, go to your Profile → Content Manager, and update the Asobo A320neo and any other updates that is available for download. Then you can close the sim, and reinstall a fresh copy of the A32NX Dev or Custom version.
Nope… I’m still trying to figure it out.
I reported the issue on the Github page and someone said a workaround is to make sure during takeoff the throttle is set to MAN FLEX/TOGA and then reduce to climb after takeoff. Somehow the PERF menu on the MCDU gets stuck in the CLB setting. However, is that really how the A320 flies IRL, or is that just a temporary workaround? I’ve still not found anything on this forum or the Github issue page…
I did try manually installing the latest dev. version instead of using the installer, so I’ll see if that works later and report back.
1 Like
Thank you!
But isn’t that how the actual procedure is? For me I always do this way. Take off with MAN FLX, then after takeoff, when I see the THR LVR blinking, I bring it back to CL, and it switches to CLB mode.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.