John Dowson

No

It should, but there seems to be an issue with the calibration using this method (as I mentioned above). You can try it to see if you get the same... Just tried this again and it seems to be ok this way as well - and better as no round-trip of the axis value to the server and back required... Not sure why this didn't work the first time I tried it this way... John

Ok, thats good to know. Thanks for the update. John

This issue should be corrected in the attached beta if you would like to try it: FSUIPC7.exe John

It should, but there seems to be an issue with the calibration using this method (as I mentioned above). You can try it to see if you get the same...

Yes, you can still calibrate if sending to the FS - FSUIPC receives the value back from the FS, masks it (so it isn;t applied), applies the calibration and then resends it. No need to show me the logs/assignments if it is working.... I'm happy we got to a solution for this one!

I should say that this is what I see with my assignments using Axis Mixture1 Set. When I move the mixture in the VC, I see Mixture 1 Set events where: - < 164 is cut-off - between 164 and 16064 is low idle - >16064 is high idle So, switching to assigning with Send to FSUIPC as normal axis, and using Mixture Set and unchecking Exclude MIXTUREn_SET and with No reverse zone checked, I can then set the minimum axis position, Setting this to just below your detent should give cut-off in the range before your detent, and then low/high idle for the rest if the axis range. This is basically what you are trying to achieve, no? John

correct. If by macro you mean preset, then also correct. John

Could you log Axes Controls and let me know the output values you see when you move the mixture lever. I have tested here and see that - any value above -16186 or so moves the mixture out of cut-off to low idle - values between -16186 and +16000 (or so) are shown when moving the lever between the low idle zone - values above +16000 are high idle So, if any small increment above -16383 moves the lever from cut-off to low idle, to allow more movement until low idle is achieved, you should be able to set the min value to just below your detent. HOWEVER, when I try this here the calibration minimum seems to be completely ignored.... not sure why this is at the moment. I will look into this (when time permits, I have a lot of things to look into at the moment...), but would like to know if you see the same. Maybe you could also attach your FSUIPC7.ini so that I can see your actual assignments. John

I will also look into this further...I think offset writes to user-defined offsets are automatically copied to the read area, which is why the 2nd condition would be true. For offsets that have lvars added to them, there should be no copy and the read offset area should only be updated when the new value is received from the FS.

What you could do is just use the offsets for reading the lvar state and change them using calculator code / presets. So, you would define a preset (in your myevents.txt file): Aux_Bus#$Param (>L:XMLVAR_AUX_Bus_ON) And then assign to that preset (with parameters 1 and 0 respectively) instead of the Offset Byte Set control. John

Button assignments are processed sequentially, in order. When assigned 11 is processed, if 10 has already been processed and the value in offset A000 changed from 0 to 1, then the condition for 11 would then be true and so processed. That case is different as it was sending a control, which requires a round trip to the server, and we also never got to the reason why it wasn't working as expected. In this case, it is obvious as the offset is directly changed by the first assignment, so the condition will be true when the 2nd assignment is processed. John

You should be able to achieve this by assigning both left and right brakes to the rudder axis and then manually edit the FSUIPC7.ini file to apply scaling to each axis assignment - see the Advanced User guide section Additional parameters to scale input axis values on page 41 on how to do this. The example given would be how to scale the right foot brake (i.e. use *0.5,+8192), and for the left one you need to scale by *-0..5,-8192. John

Well, as I am not sure what that "code" is or does, it is difficult to say, but I don't see why it wouldn't be possible in lua if its just using custom events and lvars. It may even be possible to implement directly in calculator code, in which case you could just define a preset and use that. The MobiFlight Discord channel would be the place to ask about turning that into calculator code. John

This issue also posted in this topic: I haven't had time to look at this yet...once I've got the next version of FSUIPC7 released I will take a look to see what PMDG have changed and see what I can do about it... John

👍

Ahhh...sorry, I was missing the point here....thought you were talking about the throttle axis for some reason, not the mixture.... For the mixture, can you not just calibrate this on the 4th page of the calibration screen (and assign to mixture1, not mixture). With a reverse zone, you can set the range for the idle zone - it defaults to 8192 but you should be able to set/change this to whatever values you need....so the default would be: and you can calibrate/change to something like (for around 256): ? This is only available on the individual mixture controls - you can map the mixture control to the 4 mixture controls and calibrate there. John

But this is not the case...if you are sending an axis value to an FSUIPC offset, then there is no calibration in FSUIPC. That is up to you. You also need to determine the max/min values od the axis that you use in the lua script, as the values you read will be raw input values, that completely depend on the hardware and drivers used (e.g. for certain older devices/hardware it could be a range of -128 to +128!). The midpoint of an axis that goes from 0 to 16384 is 8192... what you seem to be asking is to calibrate your axis from 0-8192 to send 0-5000 (for example), and then the values from 8192-16384 to send 5000 - 16384. This is, in effect, two distinct calibration settings for different axes ranges If you want to do such things, then this is easily achievable using lua, but you also need to know (i.e. hard-code) the minimum/maximum axis values, as well as the midpoint. I am not going to look into adding such facilities into the UI - it is already over-complicated for most users. Not sure what 'a monitoring Lua' means ... a lua file/plugin is a lua file, and they can be ran (auto-started) as profile specific or not.

That is the same one as referenced in the following User Contributions topic: John

Also see John

Rather than using the ;vars/hvars directly, why don't you ise a preset? There are currently 83 presets available for the HJet - see https://hubhop.mobiflight.com/presets/. You can assign to presets directly in FSUIPC7 by checking the Select for preset checkbox. If there is no preset available for the function that you would like to implement, and you know the lvar/hvar/avar/whatever that can do this, then you can define your own preset to do this using the myevents.txt file (MobiFlight presets are stored in the events.txt file). Please see the Advanced User guide for details on preset use. Otherwise, if you want to use an lvar directly, you can do this either via a macro file or add the lvar to a free FSUIPC7 offset. Both mechanisms are described in the User guide and the Advanced User guide. Just try and report if you have issues. Hvars are more complicated, but I suggest that you only use presets for hvar activation these days. John

Yes, the profile specific button section is always loaded. It is just that they are only recognised in the button assignment window if you manually check the profile specific checkbox, which is different from how axes assignments work. It was implemented this way (many years ago) to allow you to add general button assignments even if you are using a profile, as these are also inherited by the profile, unless overridden. However, I think it should be possible, and also preferential, to show any current profile button assignment when a profile specific assigned button is pressed. This would prevent you adding a general assignment to the same button, but I don't see that as an issue. This has actually been something I have been meaning to look into for quite a while now.... Once the support requests drop off (I am spending ALL my time on support these days ... please note @pilotjohn! 😉) and I have more free time, there are many small things like this that I would like to look into and improve.... John

This question doesn't make sense... If you are reading the joystick axis value from an offset, this is just a raw value which you will calibrate and adjust yourself. It will not go through DSUIPC calibration. That is the whole point of doing it this way - you get the raw axis value, adjust/calibrate to your needs, and then send it the the FS. You will just get the axis value. It is up to you to know what that value is and what to do with it....you can kif the value received, to see what that is when the position is at (or around) the detent position. Certainly not! It is not just a midpoint - what you are asking is for is in effect two distinct calibration settings for different ranges on one axis. The facilities provided should be fine for most aircraft and hardware. We provide the additional functionality that allows you to do almost anything, but it up to you to implement this.

No idea.... Can you actually tun FSUIPC7? Try running FSUIPC7 on its own, without MSFS. If it runs ok, it is nothing to do with FSUIPC7. If you get any errors, it will be because your Microsoft VC++ redistributables need updating - download and run the latest VC++ redistibutable package from Microsoft, available from here: https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170 If you have any of the 2015, 2017, 2019 or 2022 redistubutables already installed, maybe a good idea to uninstall them first, using the Windows App management panel (although the installer may do that for you, not sure...). John

The license has been updated, valid until 1st Feb 2023. John