John Dowson

Yes, this is an issue and why I recommend that you don't use the events.txts file for now, but only the myevents.txt file, where you have control over the order and number of each preset. You can copy any of the presets you use from the FBW events.txt file to the myevents.txt file, and also add comments to keep track of the preset numbers. It should be pretty east to implement - I just need to find an offset area of a minimum of 60 bytes in length, which is the tricky bit! I'll take a look in the next few days and maybe get this into the official release. I don't know - take a look at the [EventFiles] section of your FSUIPC7.ini and that should tell you what it was. I don't think that should be an issue. You would just have the same custom event registered twice under two different numbers, if this was allowed, or maybe an error would be logged when registering the same custom control the second time. I'm not sure really, but either way it shouldn't cause any problems. Yes, that would be great - thanks! Cheers, John

The only ones that I can think of that may work would be the windshield ones: Windshield Deice Off / On / Set / Toggle Did you try them? You can also check the controls list document document (Controls List for MSFS Build 999.txt) in your FSUIPC7 documents folder for a full list ov available controls. Note that not all internal controls have been exposed by SimConnect and so may not be available. To see what control is being used for a specific function, you can turn on logging for events, open the FSUIPC logging console and see what events, if any, you see when you manipulate that function in the aircraft. If any events are logged, you can assign to those. If you don't see anything logged, you can also try listing the available lvars (from the Add-ons->WASM->List Lvars menu item) to see if any of them look relevant. If you see one that looks related to the function you want to assign, you can try changing its value to see if it has any affect, and if so you can use that. Alternatively, if its only available in MSFS, then you can always assign there. John

To reverse an axis that does not go through FSUIPC calibration, you can use the Additional parameters to scale input axis values functionality (see page 40 of the Advanced User guide). Basically you need to add a scale number of -1 to the axis assignment, e.g. add ',*-1' to the end of the axis assignment line in your FSUIPC7.ini file. John

Great! Ag, then that must be in event file 1. Note that the event file number you should use to determine the control number for custom controls should be taken from the [EventFiles] section of your FSUIPC7.ini, and not by counting the number of *.evt files in your installation folder. This is probably not clear in the documentation - I will check and update. I'm glad you are making such good progress. Maybe you could consider writing a FAQ entry on how to configure FSUIPC7 for use with the A320/FBW A320 to help others with this aircraft. Regards, John

Not exactly - it is read the first time a simconnect connection is established. No, that is not going to happen - lots of complications to do that, just not worth it as it only takes a few seconds to restart FSUIPC7 (you don't need to restart MSFS). John

It is because they are custom controls, not hvars. *.evt files make custom controls known to FSUIPC for assignment. Yes, that should be correct. Are they being sent and not having the desired affect, or are they not being sent? Activate logging for events and see what you see in the log. If they are being sent but have no affect, I cannot help really. I presume those custom controls just trigger the associated hvars, as do the MobiFlight presets. If the hvars aren't working, then the custom event and the MF preset won't work. Which FBW version are you using? The MF documentation states this was tested and working in the stable FBW v0.7.0. If you look at the presets for the A320 dev version, these don't appear so I suspect they may only work in the stable. I cannot really help if the hvar is not working. FSUIPC is just the conduit to send these controls to the FS. It is up to you to determine what controls to use. John

Hi Mike, thanks for reporting back. Is the button assigned in MSFS then? To what? Doesn't the same assignment work in FSUIPC7? John

Just disable controllers using that checkbox. John

How can I if its an MSFS issue? Have you monitored your CPU/GPU usage? it could be that you are overloading your system. Try monitoring your system resources. If you see that your CPU (or one of your cores) or GPU is overloaded then you need to turn down some of your settings in MSFS. John

Yes - you do that in FSUIPC7, and that is also how you do it. John

I find this strange...if its acting weird in the key assignments tab, it will be acting weird for the actual assignments. However I have no idea what is happening as I still haven't seen a log file produced when you press your "key" buttons. Please show me that log. If I were you, I would try the HidDemo.lua to see if that recognises those buttons and can convert them to virtual button presses. Also, can you please explain exactly what you are trying to achieve using your yoke buttons and other devices "key" buttons - just the functionality you are aiming for when you use these (without mentioning virtual buttons or flags!). I don't understand this: what do you mean by '2,4/2,5/2,6/2,7'? I uderstand you want to change the control sent when using the soft buttons, but not sure how/what ither buttins you want to use to do this.

Sorry, no idea - sounds very strange...I have certainly not noticed this. Are your axis assigned in MSFS or FSUIPC7? FSUIPC7 will (probably) be very slightly slower than assignments in MSFS as it is an external program and has to send the inputs to MSFS for action. That is even stranger...no idea what could be causing that, sorry. John

👍

Seems to be working fine as far as I can tell. I tested with the following lua script: When it is running and I press my joystick#1 button 6, I see 822891 LUA.6: Hot button changed: 3 I suggest you check how you are using this offset. John

You are not upsetting me....don't worry about that. I am just not understanding you... You can, but only virtual button presses, via offset 0x3340. You cannot use a key assignment to trigger a button press from your yoke. But, there should be no need to. Just assign to the button press. Are the keypresses sent by your hardware seen by FSUIPC? This may be the issue. I know this is a problem in FSUIPC7, as this is an external program, and key presses sent by non-keyboard devices are not seen by FSUIPC7. So, the first thing to clear-up is if the keypresses sent by your hardware are seen and can be assigned in FSUIPC. Can they? And again, I'm not upset! If your device is a hid type device, you could try using lua to control it. There is a lua script available, called 'HidDemo.lua'. This will convert non-joystick hid device type button presses to virtual joystick button presses to which you can then assign. The lua should be available in the zip file Example LUA plugins.zip. If you don't have it (don't know if that was available in FSUIPC3) let me know and I can attach it. John

One more thing - on your timer... You could assign your key press or button (the one that controls what actions the other keys/buttons perform) to toggle/set a virtual flag, and also start a lua script (in separate assignments, of course). The lua script can start a timer, and in the timer handling function, clear/toggle the virtual flag. This should be straight forward to implement. Alternatively, and maybe better to get a fixed timer period, you could just have your key/button set the virtual flag, and have an already tunning lua (i.e. auto-started) also waiting for the same keypress, and starting the timer when received, and again in the timer function you can reset/clear the virtual flag (or set/clear any others). John

That is because you have IPC read logging activated. Your log files show nothing useful. For any future logs you attach, [lease just activate logging for buttons & keys and events - turn other logging off. And show the full log - you can zip it if its large. And I am still at a loss as to what you are actually trying to achieve. You say it works 100% for joystick buttons, by then also that your hardware is not a joystick and can only be programmed using key mapping. Before I look into this further, could you please try to explain what you are actually trying to achieve. Your previous descriptions don't make much sense to me I'm afraid. And you keep talking about a timer - as I said, this is not possible without resorting to lua, so please forget that for the time being. Can you please explain what you want to achieve with your key assignments, and in a way that does not refer to buttons or virtual buttons. We can see what virtual buttons/flags you need when I see the requirements for your assignments. It seems to me that you are making things overly complicated It seems you just want to change the assignments to certain keypresses based upon whether another key (or joystick button) has been pressed, no? A key or button press cannot call any procedure- it can only perform what has been assigned. And do not confuse button flags with buttons. If you set or change a button flag, this does not mean that the button is triggered and the assignment on that button is fired. And there is also no need to do this - the action should be triggered by the key press itself. You have multiple assignments on the key press to achieve this, one to set/clear/toggle a flag (or multiple assignments if you want to do this for more than one flag), and then additional assignments, with your compound statements, to send the actual control which would be dependent on what flags are set. In summary, key presses can set/clear/toggle button flags, they cannot trigger button presses (and there is no need!). Your key assignments can check the state of the button flags to determine what action to perform. Note also offset 0x3340 can be used to trigger virtual button presses, if needed. However, it does say 'externally signalled' - not sure why, but this may/probably means that they can't be used for 'internal' assignments, although I'm not sure why... John Later: I'm sure that offset can be used, just not sure why the documentation says 'externally'....

So the issue is with Chase Plane, or with P3D, or the interaction between the two, and nothing to do with FSUIPC. As I said, it doesn't work for me, either with or without FSUIPC running. As this seems not related to FSUIPC at all, I don't think I can help you with this. I think I remember there was some sort of issue previously when using chase plane + fsuipc, but i thought that this was no longer applicable. Maybe it has returned, I don't know, but I believe this issue was solved by changing the order that these programs are started, so you could try that. John

You can zip your log before attaching. The log you attached shows nothing except that your assignment #82 on button 157 (57) is working. Are you saying that nothing at all is logged when you activate button 164 (for example), even though you can see the assignment (to AP_SPD_VAR_INC) to this button in the button assignment panel? If this is the case, I cannot see how it can be recognised when the assignment panel is open but not when closed.... Please zip and attach a full log.

Ok. I will check this when I get a chance and report back. John

There is no such thing as the 'module' folder in FSUIPC7. There is only the FSUIPC7 installation folder (although you may still label that as 'Modules', but not necessary. It is greyed out as the lvars/hvars are not available yet. You need to have an aircraft loaded and ready-to-fly. There is no access to the WASM facilities when in the MSFS main menu. Sis you have an aircraft ready-to-fly? John

It is the size if the simvar as held in the offset table, the second number, that you need to change, i.e. // offsets, size, simvar, type, units [, w] 0x66C0, 2, EXTERNAL POWER AVAILABLE, I32, Bool 0x66C2, 1, EXTERNAL POWER ON, I32, Bool I32 is the type of the simvar as received from simconnect and maps to the simconnect datatype SIMCONNECT_DATATYPE_INT32, so is actually 4 bytes. It is up to you to determine what values the simvar holds, and size the offset accordingly. John

Yes, should be simpler. I'm not going to write it for you, but if you try I will help. The control number for the STEERING SET control is 66818 - use that control number. You just need one event.offset call, e.g. event.offset(tillerAxisOffset, "SD", "tillerAxisChange") and your handling function (defined before the event.offset):: function tillerAxisChange(offset, value) // calibrate your value here tillerValueCalibrated = ... ipc.control(66818 , tillerValueCalibrated ) end But, before you try that, you could try just reducing the axis range by adding null sections to the left and right. Doing this, the axis would send the full range in the centre section (between the null zones), and so a shorter axis section sends the full range, and thus the axis is more sensitive (and the extremes of your axis, the null zines, would have no affect). To do this, use the calibration page and the 'Set' buttons on the tiller axis with your axis control in the left and right positions where you want to set the max/min movement. If you combine this with a slope, you may achieve a sensitivity that works for you without lua. John

Hi Andrew, I have just released a beta version of FSUIPC7 that allows you to add any simvar to an FSUIPC offset for reading and writing (if the simvar is writeable). I will release this officially sometime next week, but if you would like to try this, please see the following post: John

That is outstanding sir! Look forward to it. This is now implemented in the attached beta version if you would like to try. No documentation yet - I'll add that and release officially sometime next week. To add a simvar to a free offset, create a file called myOffsets.txt in your FSUIPC7 installation folder. The format of each entry is: offset, size, simvar, type, units [, w] (where w signifies it is also writeable and is optional). For the units, check the MSFS documentation (use what the documentation states for that simvar, or any compatible unit if you want it converted). The type should be one of the following: I32 - 32-bit integer I64 - 64-bit integer F32 - 32-bit floating point number F64 - 64-bit floating point number S8,S32,S64,S128,S256,S260 - strings with the number indicating length LLA - 3* 32-bit floats (Latitude/Longitude/Altitude) XYZ - 3 * 64-bit doubles (values representing x,y,z positions) (NB. I could extend these if needed). The size should match the type/units, and will be the size used by the offsets. This can be smaller than the type, e.g. an I32/Bool ot I32/Enum can fit in 1 byte - you don't need 4 bytes (32 bits). Note also that the offset needs to be bound to the size. This means that if the size is 8, the last offset digit needs to be 0 or 8, if the size is 4, the last offset digit needs to be 0, 4, 8 or C, etc (but not for string types). Lines starting '//' are ignored. Here is an example myOffsets.txt file: Check your FSUIPC7.log file when using this, it should report any errors. John FSUIPC7.exe