John Dowson

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

Hi @Djeez / Emile, I have now added the functionality to allow the user to add any simvar to a free user offset. I will release this at the weekend, but I have attached a beta below if you would like to test. To use this, create a file called myOffsets.txt and add the following content: This will add the simvar ELECTRICAL MASTER BATTERY:2 to offset 0x66C0 as 1 byte, for both reading and writing. Please change the offset to a free user offset if already using that one. Cheers, John FSUIPC7.exe

You would write the axis value to an FSUIPC offset (send to FSUIPC offset) and use event.offset to get the axis value each time it changed, apply whatever calibration you require to that value, and then send it to the sim. I recently provided a similar lua script to handle the throttle for a specific use case which you could look at and adapt if you want to go down this route. See . John

Btw, what aircraft are you using? It could be that the aircraft is not using the standard controls. To work out what to use, activate the required function in the aircraft IO and see what is logged. Many aircraft in MSFS, especially more complex aircraft, use lvars, hvars or complex calculator code. You could try searching for a MobiFlight preset that activates the required function in the MobiFlight HubHop preset list. If one is available, you can try assigning to that (MF presets were added in v7.2.16, the latest version). John

Not sure why you would want to do this, but what do you see in the log when you press the 'o' key? I always need to see your log (or a log extract) - just saying nothing happens or it doesn't work is not enough. Show me the assignments (your FSUIPC3.ini) and the log produced when you press the button. You mean for a key or button to trigger a virtual button> It should be possible. I really need to see your FSUIPC3.ini to see what is happening rather than you keep pasting these individual lines. Give me a concrete example and I will take a look. However, I am extremely busy at the moment, so I won't have time to look at this until Sunday or Monday at the earliest. John

This is normal. and is for historic reasons. FSUIPC only used to recognise up to 32 buttons (0-31) and a POV switch (buttons 32-39). Buttons 40 onwards are offset by 100, so button 50 would be 140, etc. What is CW/CCW? If by 1 you mean a press and 0 a release, then that is usual for rotary buttons. Could you show me your FSUIPC7.ini file, and an FSUIPC7.log file showing your issue (i.e. with button and event logging enabled, first turn the encoder that works in both directions, then one that doesn't). Show me the full log - do not start a new log file. You can zip it if its too large to attach as-is. John

For more sensitivity (around the centre) you need a negative slope, not a positive one. Or do yo mean that you would like it to be less sensitive, i.e. the same axis movement to move the tiller less? Only the slope functionality is available to adjust the sensitivity of an axis. If you require more extreme calibration, you would have to write a lua script to control your axis where you can calibrate as you wish. John

Strange...have the documentation been installed? I ask as this can occur if the unstaller cannot determine the location of your Documents folder from the registry. John

I also experience a lot of crashes when the FBW and even when it isn't being used - just being installed in the Community folder can cause issues. I do use the dev version though (and don't update that often), maybe the stable is better. This is the MobiFlight request that you should vote for: https://forums.flightsimulator.com/t/enhanced-api-to-access-all-aircraft-state-and-trigger-all-cockpit-functions/454608 John

it is untested but should be working. If you want to use it, go ahead. Report back if you have any issues and I will look into it. In fact, report back if it works as well and I will update the documentation to state it us working. Most, if not all, of the offsets marked as untested should work ok. John

If course - if the program is an FSUIPC client program. Thats the purpose of WideFS/WideClient. John

I wouldn't do it that way - see my example. Toggle the flag in a separate assignment, before the assignments that check the flag. And the button flag for the button you are pressing is automatically toggled - no need to explicitly toggle (or set) the flag again. No - they need to be known by FSUIPC (and be available via SimConnect). Og FSUIPC doesn't know about them, they are either not available via SimConnect or were missed/not known at the time. John

No point in doing that really - I can't read anything in that image due to the resolution. Then it sounds like its one of the new B type variables. Did you read the link I posted about these (https://devsupport.flightsimulator.com/questions/1859/b-input-events-and-the-simconnect-and-gauge-apis-f.html)? You can try to see if that works as calculator code, i.e. (>B:AIRLINER_LS_Toggle) but I don't think it will work. That is what the post I referenced was talking about - no access to these new B-type variables at the moment either using SimConnect or WASM. I will have to wait for further functionality (and, hopefully, some documentation) from Asobo before these can be used. John

I'm not sure why it says that, but then again I have never used FSUIPC3 - or even seen the documentation. That is why FSUIPC3 is not supported. My advice relates to FSUIPC4,5,6,7, and may apply to FSUIPC3, but I cannot be certain, sorry. Was thinking a bit more about your issue with the button flags. It should work - I tested something similar in FSUIPC6. Maybe its an issue in FSUIPC3, but I cannot test or do anything about this. However, why don't you just use an unused joystick button flag? For example, instead of: Change this to use, for example, the flag on joystick 15 button 2 (update to any joystick/button not in use), use: 100=P11,11,C1005,3842 101=CP(F+15,2)11,11,C1 102=CP(F-15,2)11,11,C2 The first assignment says execute Control 1005 whenever your button is pressed. Control 1005 is "Button Flag Toggle". The parameter '3842' identifies the Flag: 256 x joystick 15 + button 2. So, this flag will now alternate between being set and clear each time you press the button. John

Each button has a flag, so how can that be independent of the button being pressed? But yes, sorry, for the "latch flags", on one press the flag is set, on the next, the flag is cleared. However, I think the issue is that compound button conditions are meant to allow 'you to specify actions for one button which are dependent on the state of another button'. I just don't think this will work correctly if using for the state of the same button. But is doing this of any use, even if it did work? The result would be that C1 and C2 would be triggered on alternate button presses, so you would get C1 on the first press, C2 on the second, C1 on the third, C2 on the fourth, etc I guess there is no reason why it shouldn't work (in theory), but i would have to look at the code and test in FSUIPC6 or 7 to see why, and only those versions would be updated. FSUIPC will re-write the ini (or certain sections of it) at different times. If you are manually changing the ini buttons sections, the best way to do this is to - open the FSUIPC button assignments tab - load or reload the ini in your editor, make your manual changes and save - click the 'Reload' button in the button assignments tab to load your changes John

Just took a look and I couldn't get the default space key assignment ('Mouse - control view direction (on/off)') to do anything, either with FSUIPC6 running or not. When pressing the space bar, the mouse cursor changes to cross-hairs but I cannot change the view direction. Same when using shift+O. It also seems that the FSUIPC 'mouse look' function is difficult to control when using the thiss on its own - not sure why. I find the best setting for me is to have the P3D Advanced mouse controls active, as well as the FSUIPC Mousewheel 'Move' and 'Mouse look' options checked. The space bar still sort-of resets the view (not sure why!) and ctrl+space does a proper reset. John

Only events available via SimConnect will be logged. No, not as far as I know, which is next to nothing about these new event types. John

It scans for all lvars by id and stops when a null lvart name is received, so if an lvar is not listed it is not available. You must have missed it - if you have added it successfully, it must be known to FSUIPC otherwise you would get an error. I meant also with Mobiflight of course. Does that use the Mobiflight presets? They are the ones available in the events.txt file. You could copy the ones that you want to use from that to your myevents.txt file if you want to use them, and be certain of the control number to use for them in offset 0x3110. John