KDog88 Posted September 6, 2022 Report Share Posted September 6, 2022 Hello, I'm not very knowledgeable about this stuff, but I've been trying to get either FSFO copilot or Multi Crew Experience to work on my MSFS PMDG 737. Neither is working correctly and after doing a lot of reading, it seems maybe this has to do with FSUIPC7 WASM lvar / hvar's not being enabled (always greyed out) or not working correctly on my PC? I've been using it for my smartCARS (virtual airline) in MSFS for quite a while with no problems, but I uninstalled and reinstalled FSUIPC7 to 7.3.8 w/ WASM yesterday to make sure I had the latest version but that did not help. I tried to attach my log, but it's 30 KB so it won't let me, but I could attache the prev.log if that is any help. Thanks, Ken FSUIPC7_prev.log Link to comment Share on other sites More sharing options...
John Dowson Posted September 6, 2022 Report Share Posted September 6, 2022 5 hours ago, KDog88 said: I tried to attach my log, but it's 30 KB so it won't let me, but I could attache the prev.log if that is any help. You can always compress/zip a log file if too large to attach... From the log you attached, it looks like either the WASM hasn't been installed or the WAPI has not been enabled. Please check both, and attach your InstallFSUIPC7.log and FSUIPC7.ini files (as well as your latest FSUIPC7.log file) if you still have issues. John Link to comment Share on other sites More sharing options...
KDog88 Posted September 6, 2022 Author Report Share Posted September 6, 2022 Thanks. Here are the log and ini files. I thought the WASM file was part of the install (at least I recall it asking me to check the box if I wanted WASM). I don't even know what WAPI is or how to enable it. Hopefully the attachments help. This morning I also got an error message "connection failed. FSUIPC Error #12" but I think that may have been because I started FSFO before I loaded into MSFS. Ken FSUIPC7.zip FSUIPC7.ini Link to comment Share on other sites More sharing options...
kingm56 Posted September 6, 2022 Report Share Posted September 6, 2022 Ken, Do not start FSFO before you're in the cockpit and have hit ready to fly; otherwise, your copilot will act very strangely. Error 12 exist for two reasons: 1. FSFO cannot connect to FSUIPC7; if you started before FSFO before MSFS loaded, it's possible FSUIPC7 was not running yet 2. FSFO and FSUIPC are running at different permission levels. If FSFO is running as admin, so must FSUIPC. I'll await John's answer regarding your logs; I'm always interested to learn more about the WASM module. Link to comment Share on other sites More sharing options...
KDog88 Posted September 6, 2022 Author Report Share Posted September 6, 2022 Yes, I normally always wait until I'm loaded into MSFS before starting FSFO. It was just that one time, but I though I would mention the error just in case. I don't think that is related to my problem. Ken Link to comment Share on other sites More sharing options...
John Dowson Posted September 7, 2022 Report Share Posted September 7, 2022 16 hours ago, KDog88 said: It was just that one time, but I though I would mention the error just in case. So this just happened the once? Your log shows that the WAPI interface was not started. I'm not sure why this happened - the next version will have additional messages relating to the WASM/WAPI - you could try this (attached) and show me your FSUIPC7.log file if this happens again. 21 hours ago, KDog88 said: I thought the WASM file was part of the install (at least I recall it asking me to check the box if I wanted WASM). I don't even know what WAPI is or how to enable it. The WASM is the module in your Community folder that runs with MSFS, and the WAPI is the interface in FSUIPC7 that communicates with the WASM. The WAPI is now enabled by default if the WASM is installed, and your ini file shows this is enabled anyway: [WAPI] EnableWAPI=Yes So I'm not sure why it didn't start... John FSUIPC7.exe Link to comment Share on other sites More sharing options...
kingm56 Posted September 7, 2022 Report Share Posted September 7, 2022 I thought you were on holiday, John? I have an interesting FSUIPC question that I was hoping to get your council; attached is the log. In short, my application shows the users LVARs are available via WAPI; however, his FSUIPC7 LVAR/HVAR menus are not accessible ('greyed-out'). I'd be grateful for any insight, when time allows...enjoy your holiday first. Also, what version of FSUIPC7 is the .exe? THANK YOU. Matt FSUIPC7 (1).log Link to comment Share on other sites More sharing options...
John Dowson Posted September 7, 2022 Report Share Posted September 7, 2022 4 minutes ago, kingm56 said: I thought you were on holiday, John? From Saturday for 9/10 days... 6 minutes ago, kingm56 said: In short, my application shows the users LVARs are available via WAPI; however, his FSUIPC7 LVAR/HVAR menus are not accessible ('greyed-out'). I'd be grateful for any insight, when time allows... The log you attached shows the lvar names were received - when this happens, a message should be logged in the FSUIPC7 main window with the number of lvars/hvars/presets loaded, and the WASM menu items should be enabled. I can't see how the menu items cannot be enabled once the lvar names have been received... Make sure the user is checking after this message is logged... 10 minutes ago, kingm56 said: Also, what version of FSUIPC7 is the .exe? 7.3.9b. John Link to comment Share on other sites More sharing options...
John Dowson Posted September 8, 2022 Report Share Posted September 8, 2022 Some issues with that version, try this one, 7.3.9c: FSUIPC7.exe Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now