1 hour ago, Tuskin38 said:

I flew about 9 hours ago and it was fine.

So I looked at their github, and it's actually a listed problem:
 

Quote

 

FCU Heading Knob

On the first load of the A32NX the heading knob push/pull may not work.

Solution:

• Restart once as for unknown reasons this event doesn't work the first time.

 

Turns out it's a problem we all have, you just happened not to use the HDG knob during your initial flight and I did. At least I now know it won't happen again.

Edited August 3, 20214 yr by WestAir

It says ‘may not” not that it happens every time. So I just happened to have it work on both my flights.

Edited August 3, 20214 yr by Tuskin38

Also flew two flights yesterday with no issues. I also used So-Fly weather addon and had no more issues with temps at 40c -30k plus

I am at risk of requiring a flak jacket. For some the Dev version of FBW A320 obviously works, for many it does not. Every time I try to load the aircraft I get to the loading page or the 'fly now' page the sim CTD! Like me I am sure 90% will have tried everything; emptying the community folder, clean installs and short of standing on my head there is nothing left to try. To find in several threads the comments, 'just do this and you will be fine' very frustrating. I am pleased for those that are having a great time but please, please have an understanding of us that are not.

Apologies for the rant but I am doing my head in over this.

 

1 minute ago, Andy675 said:

I am at risk of requiring a flak jacket. For some the Dev version of FBW A320 obviously works, for many it does not. Every time I try to load the aircraft I get to the loading page or the 'fly now' page the sim CTD! Like me I am sure 90% will have tried everything; emptying the community folder, clean installs and short of standing on my head there is nothing left to try. To find in several threads the comments, 'just do this and you will be fine' very frustrating. I am pleased for those that are having a great time but please, please have an understanding of us that are not.

Apologies for the rant but I am doing my head in over this.

 

its the same for me.  I thought I had cracked it this morning but clean install, no other mods in community folder, turned off ai traffice and still ctd.  I;m just gonna sit tight and wait for a hotfix. 

27 minutes ago, Andy675 said:

Apologies for the rant but I am doing my head in over this.

Completely understandable Andy. It's pretty infuriating to voice your issues and be met with indifference, or worse, doubt.

ASOBO devs said they are aware of the countless CTD's and are working to fix them all. While I'm skeptical that they will, I guess we can only hope that they pull through somehow.

For what it's worth, the first time I loaded the A32NX after SU5, PC CTD immediately. The first CTD in several months. Rebooted PC and tried again with another livery (the FBW generic one). Since then I have done several flights lasting up to around 2 hours each without a problem and no further CTD's.

On flightsim.to, I see several dev's have updated their liveries for A32NX to specifically state compatible with SU5. I have updated those I cared for and deleted the others to be safe. If those dev's update their liveries to specifically say SU5 compatible, something must have changed, meaning pre SU5 liveries might be bugged now. I suggest everyone with CTD issues deletes any A32NX livery that is not specifically stating SU5 compatible, even if it apparently works OK.

It no longer matters which aircraft is loaded in the hanger when selecting A32NX. It does not CTD. Biggest issue, which will no doubt be fixed on the server side is the crazy high temps at altitude. If you get plagued by those, the aircraft becomes unflyable but that is not a fault of the A32NX. IRL, an A320 would be unable to fly at 36,000 feet with ISA +80 Celcus. Pretty much the end of the world as we know it if that were to happen IRL. That's on Asobo to fix.

Only other issue is the Navigraph integration to Flypad is still a bit rough and random but the FBW team are working on it.

Those that are still having CTD's with A32NX - there must be a livery or seemingly unrelated mod that is interfering as she is looking good and behaving well.

 

Edited August 3, 20214 yr by RaptyrOne

The CTDs I had were due to third party liveries I think…

I could not load the FBW A320 in any flight without a CTD until i selected the plane first in my hangar. Seemed to work after that.

Works flawless and looks great. Great work!!!

Does anyone have -the in my mind- overdone reflections on the glass panels in the cockpit with the reflection of a GA pilot in them???

 

Regards

Nic

11 hours ago, MikeyOnTheFlightDeck said:

Ok. Forgot to turn off online traffic. It now works! Heathrow looks awful mind due to remove addons. Now to work on what addons remain compatible without CTD

And it’s CTD again. Despite having it working earlier. I’ve now decided to fly the CRJ which works well without CTD but yet with all addons now back (apart from FBW mod) .  This makes me conclude that the FBW is the CTD culprit for me  

 

 

 

 

 

 

 

 

For the still totally frustrated at getting the FWB320 to load, you can try this.  It's what worked (finally) for me.  Got it from the developer's GitHub forum.  As always with these kind of things, no guarantees.  YMMV

1.  First, if you followed the instructions for a "clean install", you may have unknowingly deleted an ENTIRE FOLDER you shouldn't have.  It's the one in the Packages folder called "flybywire-aircraft-a320-neo".  It has a subfolder called "Work" in it with a couple "necessary files" according to the developers.  The recommendation was to NOT delete that work folder, but only the files starting with the letter "m" in the main "flybywire-aircraft-a320-neo" folder above it.  But it ALSO said it was "up to you" if you wanted to delete the whole main folder, so that's what I did.  Problem seems to be if you do that, a new installation (even using the Installer) will NOT recreate the original "flybywire-aircraft-a320-neo" folder.  So, first thing is to check if you STILL have that folder.  The location of it can be found in the picture of the folder structure at the GitHub site: Installation - FlyByWire Simulations Guides (you may have to scroll down to see it under the "Clean Install Steps" section).  If that folder is no longer on your computer, CREATE it again, WITH the WORK folder in it.  Now when you finally get the aircraft to load again, it will repopulate those folders with the files needed in them.  Another possibility (but I can't guarantee this) is if you still have that folder, just delete the files starting with the letter "m" but KEEP the "WORK" folder and the files already in it.

2.  OK, once you know you still have that folder, this is how you *should* be able to get it all working again:  

   a.  Make sure you have followed all the REST of the "Clean Install" instructions (primarily, that you have deleted ALL INSTANCES of previous FBW installations).

   b.  Start MSFS.  Load a DEFAULT airplane.  I used the Cessna 150 at a RUNWAY.  (I don't know if it works starting at a gate, but you can try it if you want to find out.)  After the Cessna has finished loading and you have selected "Fly Now"....

   c.  Go back to the sim's main Options menu, start the Developer Mode (don't be afraid...it won't kill you, your simulator, or your computer), and in the top left Menu Bar, select "Windows", then in the drop down list "Aircraft Selector", then scroll through the list until you find the CORRECT FBW aircraft to load.  There may be TWO of them you will see.  The one you want is "Airbus A320 Neo FlyByWire" (note the spaces in it's name).  You do not want the one that is named "Airbus A320neo FlyByWire".  After you have highlighted the correct one, click on the bottom left "Load" button.  If everything works right, the FBW A320 will load where the Cessna used to be.  DO NOT HIT "FLY NOW" UNTIL YOU GET THE FIRST VIDEO VIEW OF THE EXTERIOR OF THE AIRPLANE (not just the overhead view of the airport). 

HOWEVER.....(this is what happened to me then....)

   d.  Once you finally get into the cockpit it might have loaded with all the displays as black screens, even though you can hear the engines running, etc.  BUT, I couldn't get any of the "knobs" in the cockpit to turn them on.  But when I turned the Parking Brake OFF, they all popped on and everything worked fine after that.  Go figure.  In any case, using the Developer Mode to "force load" the FBW a320 after loading a default Cessna seems to work for (almost?) everybody now.

3.  Finally, it appears you STILL NEED TO KEEP the FBW a320 as the "default loading" airplane in the airplane selection screen in the simulator.  If I do that, it loads every time in the sim after that.  If I forget to make it the default airplane before closing the simulator, it will CTD the first time I try to load it again.

There is something not playing nice with BOTH the MSFS sim and the FBW a320.  It's not as simple as only being a "bad livery" or something similar.  The developers are looking for permanent fixes yet.  For now, the above recommendation is the only thing that worked for me.  Hope it may help others here still having the CTD loading issues.

Edited August 3, 20214 yr by FalconAF

17 minutes ago, FalconAF said:

For the still totally frustrated at getting the FWB320 to load, you can try this.  It's what worked (finally) for me.  Got it from the developer's GitHub forum.  As always with these kind of things, no guarantees.  YMMV

1.  First, if you followed the instructions for a "clean install", you may have unknowingly deleted an ENTIRE FOLDER you shouldn't have.  It's the one in the Packages folder called "flybywire-aircraft-a320-neo". 

Wow this just goes to show what a mess Asobo has created - think stock A320 is in my future for quite a while - sim crashes just looking at it now 

12 hours ago, MikeyOnTheFlightDeck said:

Forgot to turn off online traffic

Sorry.. online traffic not allowed?