John Dowson

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...

Open the windows Event Viewer application, go to Windows Logs -> Application, find the crash events (Error, Application) and copy and paste the details here.

If it works, then just use that. I cannot advise if this i correct or not as I have no idea what the lvar ranges are, no idea what your full axis range is, and no idea what range of the throttle axis you are using.... It surprises me that you are still using 1 byte to hold the lvar value that you want to set. And, as I said, it is probably easier to do this using a preset.

There are plenty of other support requests on using VoiceAttack with FSUIPC which maybe helpful. I have not used VoiceAttack myself, but I understand that this will convert a voice command into a key-press combination. You can assign this key-press combination to start a lua script which would then play the required sound file using the lua sound library.

So it was working and now it is not again? What changed? Can you please post the files I need to see when you get a CTD: FSUIPC4.log FSUIPC4.ini the crash event(s) from the windows Event viewer I really need to see these files if you want assistance with this. It is no use telling me that it is crashing and providing nothing that helps me understand when, why and where this is occurring. John

If they are listed like that, then they are just individual lvars as far as FSUIPC is concerned and you can use either method. Btw, why are you using the WASMClient? You can do everything this app does directly in FSUIPC using the Add-ons->WASM menu. Cheers, John

Thats not an issue - it is just informing you that the WideServer component is running in FSUIPC and is waiting for any connections from a WideClient. However, if you are not using WideFS, you can disable WideServer in FSUIPC if you want to. John

There are a couple of things wrong with this... First, you need to determine the maximum and minimum values that the L:ENG THROTTLE 1/2 lvars take - is it really the same as your axis value range, which is usually -16384 to +16383. Secondly, you are storing the lvar value as 1 unsigned byte, which can only hold values 0 to 255. You should probably use 4 bytes, and also use the corresponding offset set function. But if your axis range is different from the lvar range, you need to calibrate the axis value first and so need to either use axis scaling or a lua script to read the axis value, calibrate it and then set the appropriate value to the lvar. I did show how to do this using axis scaling (different aircraft, in this thread: However, an easier method would be to define your own preset in a myevents.txt file and then assign your axis to use the preset. I also showed someone how to do this in this post (again, different aircraft and lvars but same principle): The preset method is probably easier, but you can use either. Any issues, let me know the lvar's range as well as your throttle axis range if you need further assistance. John

First, you posted in the Announcements sub-forum, which explicitly states NOT for support requests. I have moved your post to the FSUIPC7 support sub-forum. Please see http://fsuipc.com/ - in summary: FSUIPC7 is for MSFS2020 only. FSUIPC4 is for FSX / FSX-SE and P3D v1,4-3.4 only. FSUIPC6 is for P3D versions 4,5 & 6 only. I do not provide any software for XPlane - that is XPUIPC which is from another developer. There is no issue installing the different versions of FSUIPC on the same PC. just as there is no issue installing different flight simulators on the same PC. FSUIPC4 is always installed in a folder called Modules under the main FS folder. For FSUIPC6 and FSUIPC7, you choose the installation location yourself, and you can install anywhere you like, although it is not recommended to install under a windows-protected folder such as Program Files (or Documents). John

That is interesting - I didn't know that lvars could be indexed.... If you list the lvars (Add-ons->WASM->List Lvars) do you see them individually (as indexed) or just see B787_IRS_KNOB_STATE? In the case of the former, you can just use the ipc.writeLvar function. In the case of the latter, you can try with the ipc.execCalcCode function, e.g. ipc.execCalcCode("0 (> B787_IRS_KNOB_STATE:1)") ipc.execCalcCode("1 (> B787_IRS_KNOB_STATE:1)") ipc.execCalcCode("0 (> B787_IRS_KNOB_STATE:2)") ipc.execCalcCode("1 (> B787_IRS_KNOB_STATE:2)") John

What does this mean? What has this got to do with FSUIPC7? What have the engines got to do with the G1000? What aircraft are you using, or is this an issue with all aircraft? Do you actually want support, or is this just some sort of random observation? If the former, please explain your issue and provide more details. In the case of the latter, please refrain from posting here. John

You can try using your FSUIPC6.ini file - just copy it to your FSUIPC7 installation folder and rename it to FSUiPC7.ini. Also, delete all of the settings under the [General] section and let that get rebuilt. You may need to keep some parameters (or set them again afterwards) if you have manually changed anything (such as profiles in separate files), but best to start with a clean [General] section. If using the PMDG 737, then most, if not all, of the custom controls should be the same. However, the PMDG-specific offsets have changed so you should check those if using them. You may also want to revise the aircraft names in the profile section, if using profiles, as the aircraft names may not be the same. You can add MSFS aircraft to your profiles via the UI, but you may want to manually remove any P3D-specific aircraft. John