John Dowson

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

Of course only C1 works, as you are testing the flag on the button that is being pressed. So, flag 11,11 is always set when button 11,11 is pressed, and it is never not set when the button is pressed, which is what you C2 assignment is checking for. For C2 to work, you would need to do it on release, i.e. 101=CU(F-11,11)11,11,C2 But then this us the same as not using a compound condition at all, as in effect you are saying that you only want the press event to be sent when the button is pressed, and only want the release event to be sent when the button is released. This makes no sense. You should only use such compound conditions on different buttons (or button flags) to the one you are assigning. So you should dedicate one button that is used to determine what the other buttons send. When it is on (or the latch flag for that button is set), your other buttons would perform one function. When it is off (or the latch flag is cleared), your buttons would perform the second other function. No, sorry. That would be pretty complicated (all your button assignments would also need to be done in lua) and I don't have time to look into such requests, sorry. John

Sorry, I don't understand. What has this got to do with, for example, Cowl flaps? Reverse zone only applies to throttle/thrust.

Please be aware of the difference between a preset and a hvar. Hvars DO NOT show in the drop down menu - you need to define a macro to set/activate the hvar, as you have found. An easier way to use hvars is to define your own preset to activate the hvar. To do this, you would create a file called myevents.txt and add lines of the form: presetName#(>H:hvarName) where presetName is the name of the preset (and will appear in the drop-down menus) and hvarName is the name of the hvar. Using this method, you also don't need to make the hvars known to FSUIPC via the *.hvar files. it is just, for example: ipc.activateHvar(“H:AS01B_MFD_1_Range_DEC”) John

For lvars, you can just use the Add-Ons->WASM->List Lvars function - that will list all available lvars for the current loaded aircraft. Interesting. As you are in the events page and you execute them, they are probably events or K vars. You could try executing them from FSUIPC using the calculator code 1 (>K:AIRLINER_LS_On) They could also be one of the new 'B' variable types, or an F type input event. See https://devsupport.flightsimulator.com/questions/1859/b-input-events-and-the-simconnect-and-gauge-apis-f.html John

Yes, I need to know what version of FSUIPC you are using. If its FSUIPC3, that is no longer supported, sorry. But, you can achieve what you want by using a lua script (including having your button assignments in lua). However, I've never used FSUIPC3 (before my time!) and have no idea if lua is even available in that version... But, why use a timer? It would be simpler to use a compound button control, where the function of a button depends upon whether another button is pressed. See the Advanced User guide for details on compound button assignments. John

Sorry for the delay in responding to this. I'll take a look tomorrow, but could you let me know: - are you using any of the FSUIPC6 mousewheel controls (Mouse look, Move or Trim)? - do you have the P3D 'Enable Advanced Mouse Controls' option checked/active or unchecked/deactivated? - is this just an issue with the CPFlight MCP? Does the view point move/operate correctly when using a default aircraft? - what do you mean by 'position goes to zero position'? Also, please attach your FSUIPC6.ini. Thanks, John

This should be corrected in the attached version. John FSUIPC7.exe