After trying many times as the faq mentions, removing app, liveries, admin rights the error message keeps popping up. I'm getting rather tired of redoing this for the 20th time, not to mention the registration menu that pops-up 1/4 of the time but the registry entry is present.

One other problem is: That the installer doesn't include the Command Center info in the exe.xml if there is already a exe.xml present.

I have both FBW A32NX Project with only default livery and Pushback express (latest versions) installed and the Wasm module is 1.0.

 

 

Edited September 6, 20214 yr by Cygnific

1 hour ago, Cygnific said:

After trying many times as the faq mentions, removing app, liveries, admin rights the error message keeps popping up. I'm getting rather tired of redoing this for the 20th time, not to mention the registration menu that pops-up 1/4 of the time but the registry entry is present.

One other problem is: That the installer doesn't include the Command Center info in the exe.xml if there is already a exe.xml present.

I have both FBW A32NX Project with only default livery and Pushback express (latest versions) installed and the Wasm module is 1.0.

 

 

If the EXE.xml is already present, the installer will add the Command Center info to the EXE.xml.  You shouldn't need to do it manually.

Ensure your MSFS is run with Admin rights to avoid write permission issues.

If the registration screen pops up after you're already registered, ensure you're not blocking the FS2Crew FBW or PBE exe with your firewall.  

Firewall blocking is the source of that issue.

If you still need help, send me a support ticket via: www.fs2crew.com

I'll help you via a Remote Desktop.

Cheers,

 

 

Thanks, tried everything and still doesn't work, will send a ticket. Hopefully you can find the source of the problem.

 

Edit: removed everything from community folder and now it works. No A32NX liveries in folder, so it's something else causing the problem. Will update the post when i've found the problematic file(s)

Edited September 6, 20214 yr by Cygnific

Ticket received.  I'll help you via a remote desktop.

Cheers,

 

Edited the post, something in my community folder (not a livery) is causing it.

8 minutes ago, Cygnific said:

Edited the post, something in my community folder (not a livery) is causing it.

Cool, glad you isolated it. 

Let us know what it was.

Cheers,

Finaly found the culprit. It was a mod that added a co-pilot (on the seat) but was named A32nx and overlooked it when searching in my (many) folders for a320. Sorry for wasting your time. 😬

No worries, but I'm not sure how such a mod could have such an effect.

But as long as it works for you, I'm happy 😉

 

No idea what causes those problems, since nothing is done with wasm or other data being send. Dont want to blame the creator because it probably isn't even his fault, but if you want to check it out yourself it's this one: https://flightsim.to/file/8352/pilot-copilot-mod-for-fbw-a32nx-dev

7 hours ago, Cygnific said:

No idea what causes those problems, since nothing is done with wasm or other data being send. Dont want to blame the creator because it probably isn't even his fault, but if you want to check it out yourself it's this one: https://flightsim.to/file/8352/pilot-copilot-mod-for-fbw-a32nx-dev

That addon may have corrupted the FBW A320NX.

I've heard reports of certain 3rd party liveries for the FBW corrupting the FBW if they contain mistakes.