John Dowson

A link would have been useful...but I found that post... What does this mean? I don't understand what 'half a stroke' means, sorry... Are those the read-outs from the 'on' values? If so, that seems reasonable to me...generally axis ranges go from -16383 to +16383, so you are missing a bit at the extremes but otherwise it looks ok. Have you calibrated your axis in the windows game controller app - you could try this to get the full range. The 'out' value will depend on the axis control you have assigned to, if you have defined a reverse zone or not, and any calibration that is applied. Also, the issue you described over on FlightSim.com is different: This sounds like its going from -16256 to +16256 for the first half of your axis, then jumping from +16256 to -16256 half way through the momvement and starting again....that does sound very strange and I really can't see how that can be happening... Maybe you can attach your ini and log files. For the log, activate axis logging and move your throttle, prop and mixture axis each through its full range and back again. This should show what values are being sent to the FS. John

This is usually due to the fact that the installer detects a steam installation when you are in fact using a MS Store installation, or the MSFS UserCfg.opt file cannot be located. Can you attach your InstallFSUIPC7.log file please and I can take a look. Also, please update to the latest version, v7.3.1. Only the latest version of FSUIPC7 is supported. John

Hi Andrew, No, I'm afraid not. Allowing additional simvars to be added once the simconnect connection has been opened and simvars already requested poses many issues that I am not willing to look into at the moment. It will have to be up to the user and the software developers to handle this correctly. I could allocate a specific offset area (i.e. not in the 'free for general use' offsets) for use by LINDA to prevent the same offsets being used by other utilities, if that helps. If you let me know the size required, I can take a look and see if I can find an area to allocate for this. Cheers, John

Could you also attach your FSUIPC7.log file as well as your complete FSUIPC7.ini file (not just an extract), with logging for buttons and events activated, and showing an assigned button press. If you aren't loading the aircraft 'CRJ700ER Horizon Air N613QX' then that profile won't be loaded. You should use a substring in your profile to catch all versions, i.e. [Profile.CRJ] 1=CRJ700 John

To receive button presses and release, the format is: event.button ("H" , 2 , 3, "my function") The downup is a parameter and should be one of the following values (as described in the documentation): John

It is always better to install in a different location, especially when using OneDrive. So first, try re-installing in a different location.

@Tim M I have had a look and it doesn't seem possible at the moment without using WideClient/WideFS. I will look into this this week (i.e. key handling in FSUIPC7 on a client PC). I will let you know if possible (without using WideFS/WideClient) later. John

I think you are confusing things a bit.... a key press to change an offset is straight forward. The difficult part is connecting the offset to the PTT toggle. But what is handling the PTT? Surely not ProSim - that is an aircraft, not an ATC program... And, as I said, I don't know what 'Skalarki ACP' is - is that is what you use to activate PTT, then maybe ask them to help you to configure? Or are you using P2ATC and want to configure with that?

It is certainly there - "Joystick Calibration", to the right of "Axis Assignment". Please see the documentation - start with the User Guide. John

If the assignments tab is missing, then the version you are using isn't registered or the registration has expired. Did you see your registration details in the dialog at the end of the installation process? If it was previously working, did you change the installation location? If so, copy across your FSUIPC7.key file (as well as FSUIPC7.ini and other files you may use). Alternatively, re-install again back to your original installation folder. John

Yes, but you cannot use that if not using WideFS/WideClient. There is no Modules folder in either FSUIPC6 or FSUIPC7. If you see a reference to this folder, just use your FSUIPC7 installation folder (if you don't know where that is, you can use the File -> Open Installation Folder... menu option). No, you just need a lua script on the client computer. The lua should be auto-started from the [Auto] section of the FSUIPC7.ini on the client computer. In the script, you can start P2ATC using the ext.run library function. Then have an event waiting for a key (ir keys) press/release using event.key function. In the handling function, you can then send the key press/release to the P2A application using the ext.sendkeys function. However, there is no way to send a separate press and release using ext.sendkeys. If P2A uses press for PTT on and release for PTT off, this won't work as this would turn PTT on momentarily and then off, but try this first. If a separate press and release is needed, then you would need to use the ext.postmessage function, which is more complicated. If PTT is just toggled by a key press/release combination (or you can assign PTT on with one key press and off with another), you should be fine. I can look into this in more detail if you have issues, maybe later today or most probably tomorrow. John

@ON4KN I understand that setting up lvars to access via offsets can be quite confusing, especially for non-native English speakers. The latest version of FSUIPC (v7.3.1) supports the use of MobiFlight presets which should be easier to use. Check the MobiFlight hub-hob resource (https://hubhop.mobiflight.com/) for the aircraft you are using and search for a preset for the function you want to implement. So, for example, for the A320 BAT1 I see this preset: A32NX_OH_ELEC_BAT1_TOG. That will be listed under the controls menu as 'Preset: A32NX Oh Elec Ba1 Tog' (providing you have the WASM installed and enabled, and have also installed the MF preset file, called events.txt). You can assign your button directly to that preset. John

Yes, in the calibration tab. If you assign an axis with 'Send direct to FSUIPC Calibration' then you must also calibrate the axis. Here you set the axis min/max ranges, any null zones (if applicable) and can also reverse. John

Ok. I suspect that its too much logging not giving other threads time to react, or maybe a threading issue when multiple threads are logging and one (the lua thread) is hogging the log - I have noticed strange behavior on other occasions when logging is being thrashed. I'll take a look when I get time (as I've been meaning to try the RAAS script anyway), but I'm not sure if I can do anything, except maybe throttle the logging.... I can also add a note to the documentation to the effect that if you are logging lua plugins and this logs fast and/or produces a large log, then you should also enable Log Lua Separately. John

Ok. I will check this at some point, but it will be low priority. Maybe check, otherwise the user's issue is somewhere else....

But I thought it was working for you, but wasn't working for another user who didn't have Lua Plugins log option activated, so how can this be the issue? Maybe something is overflowing, I don't know. Maybe continual logging is having an affect - I have noticed this in MSFS with other logging on occasion. I can take a look at some point but not for the next few days (re-organising my office at the moment...). But how can it be if the user had an issue before he activated lua plugin logging? Or are you saying that he already had Lua Plugin logging activated, and it works for him when this is disabled? if thats the case, then there probably isn't an issue - just get him to disable the lua plugun logging!

No idea, sorry. That error is from P2A and looks like it cannot detect FSUIPC. I suggest you try P2A support for this. John

Then how is this working - how have you configured this? Are you using an offset or an (axis) event/control? You say this worked fine with a different TQ. Was the offset changing with that throttle? I think you need help with this from either ProSim or MobiFlight. As I don't use either, I cannot advise on how to set this up. John

To send the key press to P2ATC, you would have to use the lua function ext.sendkeys, and either start P2ATC via the lua EXT library ot use ext.gethandle to get the P2ATC window handle. John

Yes, FSUIPC7 on the client machine receives the key presses from the FS machine. However, P2ATC will not see that key press, only FSUIPC.

You cannot use KeySend - that is for WideFS. What makes you think that would work? Using FSUIPC7 on a client PC is not the same as using WideClient/WideFS. So 'shift + A' works from the client PC. Does this also now work from the MSFS PC? FSUIPC7 on the client PC should receive the key presses from the FS machine via SimConnect, although I haven't verified this (I can check later). John

The easiest way is to assign one event to button press and the other to button release. However, the general mechanism to assign multiple actions to a button press is by editing the DSUIPC7.ini file. You do this as follows: - assign your button to the first control and press 'OK' to save the assignment. Then, open the button assignment panel again. - open your FSUIPC7.ini file in an editor (e.g. Notepad++). Find the assignment line you just added and comment it out. You do this by inserting a ';' after the '=' sign for that assignment. Save the file. - in the button assignment dialog, reload your button assignments. After doing this, you can then assign the second action to your button. - You can repeat this a smany times as you like, to add multiple assignments to the same button - Once you have all your assignments, open the button assignment panel again, go back to the editor and remove the ';' you previously added to re-activate these assignments and save. - Finally, reload your assignments from the button assignment panel. You will now have multiple assignments to that button. Note that you will only see one assignment in the UI panel, and this will be grayed-out and not modifiable. You hanve to edit the ini manually if you want to change or remove these assignments. Yes, many times, e,g, Also explained in the Advanced User guide, although it is not that clear from the description there. I will add a new section with clear instructions for this in the next update (not that many people actually consult the documentation....!) John

Why are you cross-posting in a different topic when you raised your issues in this new topic: ? The letter should be the same, as this is what the assignments use. The ids that map to the letter may have changed - this is the whole point of using JoyLetters, so the letter maps to the correct joy id number. If the GUIDs have changed, you need to update your original letter mapping to use the new GUIDs. However, if that was the log/ini files you posted (in the other topic) from both PCs, it looks like the GUIDs haven't changed. This surprises me, as they should change on a new PC. Naybe you didm'y show me the correct files in that topic? I am closing this topic now. Please use the other topic, and do not post in multiple topics for the same issue. John

Sorry, I have no idea - I do not use ProSim or Arduino. What happens when you manually activate the spoilers - does this work? If so, how is that assigned? And does that change the values in offset 0x0BD0?

So you are using ProSim....you could have mentioned this earlier, and it is always a good idea to include ProSim in the title as this may attract other ProSim users that can help. To me it looks like FSUIPC is working as expected, although I cannot confirm as you have still not activated button and event logging, which would tell you if FSUIPC is sending the assigned events. So I suspect your issue is with your ProSim configuration. As you are using both an unsupported version of FSUIPC and ProSim, I really can't help you with this any further, sorry. John