Airbus sharing.

[sequal32]

Airbus sharing.

[Sequal32]

Hi! I believe this issue was caused by the latest MSFS update. I recommend you delete the YourControls folder from the community package location, and reinstall using the installer. Make sure you install YourControls after you install the A32NX.

[rafistolique]

Hello, as expected here is my test return. Indeed the solution was there, it was enough to reinstall "your controls". I'm ashamed that I didn't think about it. It finally works. Thank you for your time and apologize for the inconvenience.

THANK YOU

[rafistolique]

Thank you very much for taking the time to answer me. When I get home from work tonight, I'll test this out without waiting any longer. Again last night we flew a Cessna (g1000) for more than two hours, without ANY problem. And I must admit that I am really delighted with the current result. I will come and post the verdict and thank you again for this wonderful work.

[larsf96]

Hello,
I'm experiencing the same problem as @rafistolique. I've also reinstalled YourControl, but the issue still exists. Everything worked fine before the latest MSFS update, so maybe that update broke something.
Any idea how to debug the problem?

[rafistolique]

Hi to you,

For our part, my brother and I deleted the "your controls" directory from the "community" folder. We also, my brother and I, erased the contents of the "AppData" directory. We no longer wanted a trace of "your controls".
Then we reinstalled the DEV version of "A32NX Fly By Wire", (The folder already existed in community, but we just clicked on "install the" dev "mode).
During our last tests, we stopped at a stable version.

Once done, we launched the "installer" file of "Your controls", chosen the "DEV" version. And this app again placed the "Your controls" folder in community.

Once "your controls" started, we had to retype the name, the host IP, the choice of the plane (here Airbus in DEV mode). The proof that there was no longer any trace of the old installation.

At this point we had a problem, the host had a "script has stopped" message and the client had their program exiting. But the client (my brother) had chosen the wrong plane. Once the host and the client chose the same plane, there were no more scripting problems, and we were able to play together without "problems".

(My brother had a "community" folder super loaded with mods of all kinds. I only had two scenes. He moved all his addons except the two scenes we had in common. I don't think that has changed. many things).

Unlike the other planes, here we see that if the autopilot is engaged for a long time, the client obtains a bad frame rate (it suffices to temporarily cut off the autopilot and the frame rate improves), but this is another topic.

I hope I have been as detailed as possible.

Good luck to you.

[rafistolique]

I think the problem has been solved. Thanks again for the help provided.