John Dowson

I don't know why you say this... I have a long list of user requests and I process and implement them as time permits...unfortunately, most of my time is taken up by support requests, which take priority. I also have an issue with my eyes - I have a genetic degenerative eye disease (Retinitis pigmentosa -RP) so I am certainly willing to improve the visual aspects of the software I provide, but there are only so many hours in a day and I have to prioritise, which doesn't leave me much time. If I could only spend less time on support questions, especially those that could be answered if people actually consulted the documentation I provide and used the resources available before posting questions.... this would save me a lot of time and I would have more time available to implement such features... That is, of course, up to you. SPAD.next is also a great tool - I also use this occasionally. But it doesn't provide the power and control that you can get with FSUIPC, but is generally easier to use for novice users. I don't mark threads as solved - they need to be open if someone has a similar issue that they need to discuss. Regards, John

But why? Yes, that is where they are installed.... unzip/decompress that file, and copy or move the lua file you want to use to your FSUIPC7 installation folder, which is: C:\FSUIPC6 it will then be available in the assignment menus to be started on a key or button press. Or you can start it automatically using the [Auto] or [Auto.xxx] (where xxx is a profile name) in your FSUIPC7.ini file - see the Advanced User guide for details. John PS. Please see the provided FSUIPC Lua Plug-Ins document...

Your log file does not show anything untoward. I have also just checked here using the FBWA320 (stable version) and do not see any noticeable drop in FPS. If you start MSFS without FSUIPC7 (with the FPS counter window open), load the FBWA320 and wait a few minutes, what does your FPS settle to? If you then start FSUIPC7, again wait a minute or two for everything to load, what does your FPS then settle to with FSUIPC7 running? You can also take a video of this test and show me so that I can see any performance degradation. Can you also try without the FSUIPC7 WASM module running - just (temporarily) move the fsuipc-lvar-module folder out of your MSFS Community folder before you start MSFS. Do you still get the same performance issues without this running? John

To get hvars recognised by the WASM and FSUIPC7, you need to use *,hvar files and place them in a specific location. Some *.hvar files are installed by default (for A320, DA40 TDI, DA40-NG, DA62, Skyhawk, TBM) and others are provided in a sub-folder of your FSUIPC7 installation folder called HvarFiles. To use these you must copy/move them to one of the folders where they are recognised, and also make sure that the name if the file is a sub-string of the aircraft name/title. Please see the section Using Hvars in page 47 if the Advanced User guide for details. However, it is far easier to use hvars via calculator code or presets, and they do not need to be made known to FSUIPC with these methods. John

Licenses have been sent via PM. John

Lua scripts, by default, just go in your FSUIPC6 installation folder. Note that you seem to have installed FSUIPC6 under your windows Documents folder: C:\Users\adm_local\Documents\Prepar3D v4 Add-ons\FSUIPC6 This is not a good location, as that is the location of your add-on.xml file that is used by P3D to auto-start FSUIPC6 with P3D. Better to re-install into a non-windows protected folder really - but this is not related to your issue. If you can't see the script in the drop-down (prefixed by Lua, LuaDebug, etc) then it is not in your FSUIPC6 installation folder with a *.lua extension. Check the extension - sometimes people find that a .txt extension has been added... You can do this either using the ipcinit.lua or ipcready.lua files (see the FSUIPC Lua Plug-Ins document for details), or, better, use the [Auto] or profile-specific [Autp.xxx] section in your FSUIPC6.ini file - see the section Automatic running of Macros and Lua plugins on page 41 of the Advanced User guide for details. John

However you trigger the lua, you just need to pass in the parameter of the selector button number (0 - 7) that triggers the lua and then read that using the ipcPARAM variable so that the script knows what the current position is - the c variable in my previous post.

Ok, so writing a certain value to an offset can trigger the sound? If so, then you can assign the key press (which will sent from Voice Attack) to write a value to an offset to trigger this using one of the Offset * controls (e.g. Offset Byte Set). It is up to you to determine what value needs to be set to which offset to trigger this - I cannot help with this. Just try this. You will need to know the location of the sound file (*.wav), and then just use the sound,play function to play the file - see the Lua library documentation. Your key press can then just start the lua script that then plays the sound.

Why? Each position would just call the lua script with a parameter (0-7) indicating the button number (that called the script). No need for virtual buttons as far as I can tell...

I am not sure what you want from me...I have already advised on what you should do: Why can you not just do that? And I would like you to answer my questions if you need help. I do not understand ProSim's response as I have no idea what you asked them... ? Approach what? What is wring with my initial suggestion?

Does this also happen if you use FSUIPC but no FSUIPC clients such as GSX? I think there was another report of GSX causing stutters with some aircraft, so worth checking. If it is another add-on that is using FSUIPC that is causing then then you need to raise with the add-on developer. You need to activate Dev mode first (Options -> General Options -> Developers), then just open the console (Debug -> Console) and see if you can see any excessive message logging, and if so what is causing it. You will see many messages (Errors, Warnings and Messages) - you are looking for anything that is continually logging the same message. You can also show me/attach your FSUIPC7.log file (located in your FSUIPC7 installation folder), but that probably won't show much...please make sure that you exit FSUIPC7 before you attach this. Ah, so you have the MSFS logging console window open. Looks like there are a lot of errors - are they mainly 'Could not find components..' ones? Where are they coming from? It is difficult to see images properly, but your stutters are obviously being caused by the CPU being overloaded (most probably CPU 1). I am pretty this one be caused by FSUIPC, but it could be due to GSX as you are at an airport, so please try without that. John

You are using version 7.2.14 which is over 1.5 years old. I did say: Please update. Please also exit FSUIPC7 before attaching any files.

You can get the mixture lever position (as a double with 0.0=cutOff, 1.0=full rich) in offsets: 0x3AF0 - engine 1 0x3970 - engine 2 0x3A30 - engine 3 0x38B0 - engine 4 It should be straightforward to add code to read the value from these offsets and display these as well.

And does the selector that you are using for inc/dec freely rotate? i.e. can you continually rotate it in one direction? Rather than using an offset for each position of the selector, why don't you just use one offset that holds the number of the last position the selector held. You can then read this in the lua script , compare that to the current position (which you can pass in as a parameter), and then decide what to do based upon the difference between these values. So, in the script, you would have the current position c (0-7), and read the previous position p (also 0-7) from an offset, and if (p == (c +1) mod 8 ) or (p ==(c+2) mod 8 ) or (p ==(c+3) mod 8 ) or (p == (c +4) mod 8 ) then decrease else increase then write the current position to the previous position offset, where the positions are 0..7 (for the 8 distinct positions) Doing it this way, you would only need one lua script for each inc/dec function (rather than one per selector position), and it would still work if a position (or two) is jumped.

I can look into the possibility of allowing the font size to be uncreased, and allow light text on a dark background. I will add this to my to-investigate list, although I have no idea when I will have time to look into this at the moment. Unfortunately all my time is taken up by support these days and I have little time for adding new features. I will not be adding a search function for lvars - you can just list the lvars, open the FSUIPC7.log file in an editor and use the editors search facilities. Not also that the logging console window is light text on a dark background, and lvars are also listed there (it it just a window onto the FSUIPC7.log file), so you can try opening that (Log->Open Console) and using that. John

Or you can use macros.... John

Yes - just comment out the first assignment in your ini (i.e. insert a semi-colon after the = sign on the assignment line in your FSUIPC7.ini) when you have the the button assignments panel open, then press the Reload all buttons button once you have saved the changes. Next, assign the second keypress to the button then click Ok. Then, open the button assignments panel again, remove the semi-colon you inserted to comment-out the first assignment in your FSUIPC7.ini and save the file, then click the Reload all buttons button again. Or you can just duplicate the assignment line in your ini, update the assignment line number to make it unique, and then change the key code (the number after the K) to the key code of the key you want to send - no point changing the comment as this will get rewritten based upon the actual assignment. John

First, you posted in the User Contributions sub-forum where it explicitly states NOT for support requests. I have moved your post to the main support forum. I am having trouble understanding what you are trying to do and what your issue actually is... Normally you would have one mode selector switch/rotary that has multiple positions (e.g. ALT, VS, HDG, etc) and another rotary used to increment and decrement the value determined by the mode selector switch. The second rotary would have either one or two (possibly virtual) buttons in each direction, and you would assign the appropriate inc/dec controls on these buttons and use compound button conditions on the position of the mode selector rotary. Not sure what this means.... Could you attach your FSUIPC .ini file so that I can see your assignments please, together with your lua scripts. Does the rotary have two buttons (fast and slow) in each direction or just the one? You can try activating logging for Buttons & Keys as well as Events, and if you test with the logging console window open then you should be able to see what is being detected and what is being sent in real-time. You can also attach your FSUIPC log file here and I can take a look. But I am a bit confused as to what you are trying to do and would like to see your ini file and lua scripts before anything else.

There is only a windows version... license has been sent. John

Is this regardless of the aircraft being used or only with certain aircraft? That is not necessary. Can you please check that you are using the latest version of FSUIPC7, 7.3.21. Also, please check the MSFS log console (you need to switch to dev mode) and see if there are any messages being continually logged there. Also try with FSUIPC's logging console window open (Log->Open Console) and see if any messages are logged when you get the stutters.

This is because you have assigned to send the key press (@key) on button release - you are not sending any keys on button press: If you want to send the key repeatedly while the button is being held, you need to assign on the button press not release.

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