Away for a month so MSFS automatically updated to the latest version including removing all my settings! Reset everything and checked with a default aircraft that all was ok. Then updated FBW 320 and restarted  MSFS and then selected FBW which loaded totally corrupt:

- engines were on with Parking Brake showing on yet aircraft moved forward

- all glass instruments blank

- increasing power on joystick engines increase )sound) but vc throttles do not move

- rotary knobs turn ok but no “click” actions work

etc etc

so far I have tried everything listed in the FBW guidance including three clean reinstalls.

Before this update I have had no problems with FBW so v grateful for any suggestions a to where I might look for a solution……….

2 hours ago, FOD said:

Before this update I have had no problems with FBW so v grateful for any suggestions a to where I might look for a solution……….

Deleted by author as not usefu

-B

 

Edited January 15, 20242 yr by btacon

You said you've tried 3 clean installs. Have you tried https://docs.flybywiresim.com/fbw-a32nx/support/reported-issues/#test-with-only-the-a32nx-add-on-in-community and https://docs.flybywiresim.com/fbw-a32nx/settings/#utf-8-support?

Thanks folks. I had tried everything suggested except to delete the Community Folder - this results in MSFS doing a full 130gb reinstall!  With my internet speed this will take all night but at least tomorrow I will have a new clean MSFS to work with……….

2 hours ago, FOD said:

I had tried everything suggested except to delete the Community Folder

No need to. Just move it somewhere else where MSFS doesn't see it.

7 hours ago, FOD said:

Thanks folks. I had tried everything suggested except to delete the Community Folder - this results in MSFS doing a full 130gb reinstall!  With my internet speed this will take all night but at least tomorrow I will have a new clean MSFS to work with……….

Read the linked posting I provided. There is no need to delete the community folder. 

On 1/15/2024 at 8:14 PM, FOD said:

but at least tomorrow I will have a new clean MSFS to work with……….

Which made no difference - installed FBW in the new clean Community Folder, launched MSFS and still exactly the same problem - a totally uncontrollable cockpit.  Spent today looking other options - graphics driver etc without any success.. …….?

Did you try the utf8 thing, Donstim suggested?
https://docs.flybywiresim.com/fbw-a32nx/settings/#utf-8-support

 

4 hours ago, FOD said:

Which made no difference - installed FBW in the new clean Community Folder, launched MSFS and still exactly the same problem - a totally uncontrollable cockpit.  Spent today looking other options - graphics driver etc without any success.. …….?

That's a shame.  It makes no sense.  Keep trying, as it is a great aircraft.  I have picked up some vibes somewhere that SU14 (or a W11 update) has messed with it for some people, but I don't know the detail. 
A vast majority of people with SU14 are using it fine, so it's strange.

Maybe try the Unicode solution above supplied by Watsi.

Edited January 17, 20242 yr by bobcat999

Are you sure you haven't switched on something like skipping the WASM compilation in the Dev Mode?

Sorry for stating the obvious, I would also just check to make sure you have the Asobo A320 neo installed, you should be able to select it in-game as it would show up. The FBW A320N needs that installed to work properly as it uses parts of it. So if thats not installed then it won't work properly.

 

 

31 minutes ago, ckukmale said:

Sorry for stating the obvious, I would also just check to make sure you have the Asobo A320 neo installed, you should be able to select it in-game as it would show up. The FBW A320N needs that installed to work properly as it uses parts of it. So if thats not installed then it won't work properly.

 

 

That was my feeling when I read the OP. Sounds like a conflict rather than a system issue. I made this mistake at the beginning too and had issues with the camera views, I would spawn outside the cockpit because I had created my own views in the FBW, I realised later I was loading into the Asobo bird by mistake because my aircraft positions had changed on the list and I was on auto-pilot.

The thumb nail in the aircraft list will specifically label it with the LEAP engines, make sure that is the one selected.

Thanks for the help folks. I had tried the utf8 check and also ensured the default 320 was present. Not sure I understand the DevMode point as I have never even opened the DevMode.

of interest, I have tried several default ac plus addons from gliders to the DC Concorde along with updates to the tbm930 etc -All ok. Also tried the SuperJet but as this appears to basically the FBW 320, I wasn’t surprised when it had exactly the same failings.

After 25 years of flt sim, nothing surprises me but this is a bit frustrating………l

 

31 minutes ago, FOD said:

and also ensured the default 320 was present

Are you selecting this in the aircraft list when you begin your flight?

No - they are now two separate aircraft.  In fact the default 320 is fine.