FBW A32N unknown simbrief user id error

The first time I got a QR code in the flypad and the aircraft connected fine to Simbrief. Now, I get unknown user id on the flypad and I can’t connect my A320 at all to Simbrief anymore. I have logged in/out, even changed from experimental model to stable model; same error. Any help would be much obliged, thank you.

Same problem here since today.

Same problem since today

hi all

I am using the A320nx by FBW version 0.12.3 stable version and latest version of FS2020. I have added my simbreif id in the tab. When I set up my flight plan in simbreif It loads on the flypad. However, I am not able to select it from the init button - nothing happens it just says INTERNAL ERROR. I have never seen this before. Any ideas whats happening here? I have also tried to uninstall and reinstall the FBW a320 , restartred sim, restarted pc etc.

In fact even if I load it without the simbreif username - its still not letting me manually add to and from on the init page. and hence doesnot allow me to add my F-plan.


flypad does work

FBW plane is not V2 plane. V2 plane is the IniBuild’s plane. Trying an FBW A320 trend may help better.

I have the same problem on A380 & A320 FBW planes. All other planes unaffected

Do you or does anyone know a fox for this ? It was working perfectly fine before. :frowning:

I pref the fbw compared to the inibuilds one. Also the inibuilds one is giving me some rendering issues too of a purple colour block where the pannel is meant to be so something odd is certiably happening!

Sorry what do you mean ? I am selecting the fbw plane on simbreif and on the sim

Initially my msg was in the thread " Simbrief + a320-v2 not working (anymore)". 6 posts from that thread were merged into an existing topic: FBW A32N unknown simbrief user id error. That is why you see your post in the thread about the FBW plane now.

Thanks - any ideas whats causing the issue on the fbw aircraft and the error I raised ?

I had this INTERNAL ERROR as well when the development version was the same as 0.12.3 stable. This disappeared on my side when the Dev version progressed. This is what I have now (the procedure changed a bit):