John Dowson

License has been sent. LINDA is optional, but may be easier to use LINDA in top of FSUIPC rather than lua directly. Also please see Appendix 3 in the FSUIPC Advanced User guide on handling VRInsight (serial) devices in FSUIPC. Any issues, please search this forum before posting, as there have already been several support requests on using the VRInsight MCP with MSFS using FSUIPC and your questions may be answered in thee posts. John

Ah, ok.... Sorry, but what do you mean by this?

Ok, got the 737 running again. You can assign the throttle either with 'Send direct to FSUIPC calibration' using Throttle1 and Throttle2 and then calibrating in FSUIPC7 (3rd page of calibration tab) or assign using 'Send to FS as normal axis' using Axis Throttle1/2 Set and not calibrating.

I took al look at that last FSUIPC7.log file and it shows: What lua file is that? It doesn't correspond to any lua file that you shown me so far... I guess the WASMIF.log files are from you using the WASMClient, no? Why are you using that? As I said, please use the FSUIPC7 facilities (Add-ons->WASM->List Lvars) and get everything logged to the same FSUIPC7.log file....

Why are you attaching pictures instead of files? Why do you have a separate FSUIPC_WASMIF.log file, instead of using the default and having everything logged just to the FSUIPC7.log file? I am not going to look at those files. Please supply just two log files, the FSUIPC7.log file, generated containing the WAPI debug information, lua plugin logging and Button & Key logging (maybe also Event logging, but probably not necessary), and the FSUIPC_WASM.log file. Also attach your FSYUPC7.ini and the *.lua file you are using. And please check the log file before posting - it should contain both lua logging and WAPI debug logging. If it doesn't, no point posting it as I will just ask again... This really isn't that difficult - you seem to be over-complicating things...

Another post in the FAQ sub-forum, where it explicitly states NOT for support requests. If you mean the PFC Radio Panel, then there is at least one other support request in this forum on this issue - why don't you try searching for that? We updated the PFC driver a while back to add support for this in MSFS, and this is documented in that support request. Or just download the PFC driver for FSUIPC and try it... John

Btw, you posted in the FAQ sub-forum where it explicitly states NOT for support requests. Please use the sub-forum for FSUIPC7 in future for any/all questions in FSUIPC7 / MSFS. I will move this topic to that sub-forum. John

This depends on the aircraft and your throttle... Why don't you just try it? And please take note of what I previously said about calibration...make sure that you create a profile-specific calibration section and initially try without any calibration. Are you configuring with a reverse zone on the throttle, or are you using reversers or a button for reverse? There are already plenty of posts on setting up reversers in the 737, so please check some of them. I have changed the title of your post, as your original title 'FSUIPC7 FS2020 ISSUES' applies to every single post in this subforum, as it is the support forum for FSUIPC7 and MSFS2020...please take care to give an appropriate title for your posts, and also check for similar issues before posting. I do have the 737 (for support purposes only) but am now getting memory errors when I load this and MSFS CTDs. I need to look into this before I can advise on this further, but you should just try to assign as I have suggested, and check-out the many other posts on using the PMDG 737. John

Did you check the MSFS logging console? You can try zipping/compressing the files. Otherwise you can PM them to me... Your limit should increase with the number of posts.... John

Also can you try with the following version, which has extra WAPI debug logging added, so you should now see the lvar update request sent in the FSUIPC7 log file. With this and lua plugin logging enabled, you should see what is happening, e.g. here's a log extract from a simple lua script that first writes 1 to a couple of lvars, then 0, then 1 again: John FSUIPC7.exe

Ah...in that case I am not sure which lvar was updated - especially as the lua wasn't logged... The WAPI should log the lvar update requests in the FSUIPC7.log file, but it looks like this may only happen at the TRACE logging level. I will change this. Yes please... Could you also make sure that you have exited FSUIPC7 before attaching log files. And check them yourself before posting - no point attaching if the lua script isn't being logged. Basically any call to ipc.writeLvar should have a corresponding message in the WASM log, and also in the WAPI log, or an error. Also, are you sure the lvars you are using actually exist? Initially, you get 430 lvars: You set one, byt then 431 are detected: and then when you set lvars using calculator code (which will create them if they don't exist) another 4 more are found: Next time you test, can you list the lvars (Add-ons->WASM->List Lvars) both before and after you press the button that starts the lua script, so I can see the lvars available. Thanks, John

Not sure why the lua isn't being logged - do you have logging for Lua Plugins activated? The only lua logging I see is this (and why FlightLog.lua and not FlightLogJohn.lua? Please keep file names as they are) : However, your WASM log file does show that the lvar was updated: Presumably the lvar with id 95 is L:XMLVAR_BATTERY_SWITCH_STATE (please check this by listing the lvars), and this is from this call: So the ipc.writeLvar call is working as expected....unless its getting the wrong id got some reason,.. John

Done

Trial license sent via PM. John

Please see the Installation and Registration guide (included in the zip file you downloaded and also installed in your FSUIPC5 documents folder), section Invalid Key Problems. John

That is the default and is no longer required. Please check that you are using the latest version of FSUIPC7, which is 7.3.21. Do the stutters occur all the time or occasionally? If occasionally, it could be due to FSUIPC's AutoSave feature, so try disabling that if it is enabled. If its happening all the time, try opening the MSFS logging console (you need to be in dev mode) and see if there is anything throttling the log, as this can cause stutters. If you see anything suspicious there, please report what messages you see here. Also, please attach your FSUIPC7.log and FSUIPC7.ini files. John

Before anything else, can you please update top the latest FSUIPC7 version, 7.3.21. Only the latest version is ever supported, and you are still using 7.3.15. Next, please revise your profiles to use substrings. Got example, for your 737 profile, change to and your F18 profile from to It is always better to use substrings so that your profile will match the aircraft regardless of the variant or livery being used. You should also revise your other profile sections accordingly. For the F18, this is your axis assignment (if it matched your profile): i.e. you only have throttle2 assigned.... And for the 737 profile, you have: which also doesn't make sense - why different throttle controls for throttle1 and throttle2? Your 737 and F18 profiles also have no profile-specific calibration sections, which means the default calibration section will apply. You should create a profile-specifoc ca;ibration section for these profiles, and clear/reset the throttle calibration for these profiles, at least initially. You can calibrate later, if required. Can you please check your assignments in MSFS. If assigning in FSUIPC7, you should use (or at least start with) an empty profile in MSFS. Once you have corrected for the above, if you still get issues please re-attach your FSUIPC7.ini together with your FSUIPC7.log file and I can take another look. John

Unfortunately your log files aren't showing me much. Looks like you didn't activate WAPI debug logging until after you activated your lua script. Can you provide me with a fresh set of files please, this time with the lua logged in the FSUIPC7.log file and not in a separate file. Also, could you set Debug level logging in the WASM and show me your WASM log file as well - see the Advanced User guide (WASM section) on how to do this and where the WASM .log and .ini files are located. If you have Lua Plugin logging enabled, you can start the script with just Lua and not LuaDebug. Also, if your issue is just with the ipc.writeLvar function, it would be easier to see what is happening if you just has a simple lua script with these calls for test purposes, which can be started on a button or key press.

Why did you log lua files separately? I specifically asked you for no other logging options other than the ones I specified as I did not want to see a separate log file for your lua script. It is far easier for me to tell what is happening if I can see just the one log file... I will take a look at these tomorrow now... John

When you press Alt+F, do you see FSUIPC7 in your task bar? If so, it could be that it is opening and positioning itself outside your screen coordinates. To correct for this, delete the ini parameter Window from the [General] section of your FSUI{C7.ini file (when FSUIPC7 is not running) - this is the ini parameter that holds the size and position of the FSUIPC7 main window. If that is not the issue, check your FSUIPC7.log file - near the top, do you see a message indicating that the Hot Key (Alt+F) has been registered? This is from my log file: John

License sent via PM. John

Can what be send to ProSim? Do you mean the key press? If so, what would ProSim do with a key press? You did say that you wanted to "trigger an audio sound with prosim" - how do you do this? i.e. what do you need to send to ProSim to trigger the sound? Can you not trigger/play the sound file in FSUIPC using a lua script, which you can assign to the key press sent from VoiceAttack?

It is just ipc.writeLvar("B787_IRS_KNOB_STATE:1", 0) ipc.writeLvar("B787_IRS_KNOB_STATE:1", 1) ipc.writeLvar("B787_IRS_KNOB_STATE:2", 0) ipc.writeLvar("B787_IRS_KNOB_STATE:2", 1) That should work. Note that you need to wait for a short period after the aircraft is loaded for lvars to be available. If it is not working, set WAPI Debug level logging (Log->WAPI->Debug) as well as lua plugin logging (Log->Lua Plugins) and Log->Buttons & Keys - no other logging please - and generate a log file showing your issue, and then attach your FSUIPC7.log file together with your FSUIPC7.ini file and lua script and I can take a look.

Of course you can - as I said:

Of course...there is no difference between the trial and a full license, except that the trial license will expire... Not sure if that was a question or a statement...