August 20, 20214 yr Commercial Member 2 minutes ago, fijisimpilot said: last update was done yesterday Okay, I'll send you an email. There's built in test function in FS2Crew FBW so that allows us track down stuff like this. I'll have you run it. Check your email. Edited August 20, 20214 yr by byork B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
August 20, 20214 yr Commercial Member We found the problem. The user had a stable version of the FBW A32NX and a development version of the FBW A32NX installed at the same time in the Community folder under manually created different folder names. No worries, these things happen to the best of us. So if anyone has the problem, ensure you only have one FBW A32NX (the Dev version) installed on your computer. Cheers, Edited August 20, 20214 yr by byork B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
September 10, 20214 yr Author On 8/19/2021 at 10:55 PM, byork said: Thanks, let us know how it goes 😉 No one else is reporting this, so it should work. Cheers, Hello mr. byork, my problems solved and its only my own error, which is I never read the read me file such as "FS2CREW QUICK TROUBLESHOOTING GUIDE". (shame to me). The program worked perfectly when I switch to A320NX - Development version (" REQUIREMENTS: -Latest "DEVELOPMENT VERSION" of the FLY BY WIRE A32NX PROJECT FOR MSFS"). Thank you very much for your kind assistance and now I only fully recognize that important to read the READ ME file. :)
September 10, 20214 yr Commercial Member Glad it's sorted... yes, "Deployment" version is required Best, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
Archived
This topic is now archived and is closed to further replies.