John Dowson

Please see Yes, Instructions on how to activate your WideFS license are included in the link above (as well as in the README.txt included in the downloadable zip file). John

The option Exit with FS (under FSUIPC7 Options menu entry) is set by default, so FSUIPC7 closes when you close MSFS. If you do not want this behaviour, uncheck that option. As for your mouse problem, I don't think this is anything to do with FSUIPC7 as FSUIPC7 no longer handles any mouse actions. Do you get the same behaviour when FSUIPC is not running?

This is a known issue - please see I will close this topic. John

It doesn't as it does not show me that you have actually assigned anything to the brake axes. As I said, you cannot calibrate if you have not yet assigned. Please post your ini and I'll take a look there to see if it is assigned. No idea what that is. Nothing to do with FSUIPC. Sorry, I do not know what this means.... John

I see the alt key is still recognised in the key assignments panel. I'll remove this to avoid confusion

Hi Chris, sorry, but the ALT key modifier is no longer supported in FSUIPC7. Note also that keyboard input is no longer masked, so any key assigned in FSUIPC will also be seen by the sim. John

Have you actually made any assignments to the left/right brake axis (LeftBrake, RightBrake, and assign 'Send direct to FSUIPC Calibration')? Your video shows no assignments. You need to assign before you can calibrate.

Sorry, yes PFC.....! As I said, I don't have any PFC devices Well, that makes sense (to me at least!), as you have to have it assigned before you can calibrate. But you also said: Which seems to contradict this. Anyway, Thomas id the PFC expert, I've never used the PFC driver with FSUIPC so best wait for his response on this. John

Hi Simone, I don't think there has been any changes in FSUIPC for those offsets either....

I'll post a question on this. Sorry, I don't understand this. If you don't select any axis, whats controlling it? Sounds like you have your axes assigned in the sim, which would certainly cause jerkiness, as it would be getting two inputs, one from FSUIPC and one from the sim. If you assign axes in FSUIPC, you neeed to check that they are also not assigned in MSFS. I think this may be related to your PFC configuration (.ini). I'll see if Thomas can help with this. John

This offset was using the toggle control - I'll switch to using the set control in the next release. I've tested here and it works ok, although there are some complications if using individual on/off controls (e.g. via the UI or an MSFS assignment). When doing this, the Avionics 1 will drive the offset and Avionics 2 will have no affect. John

There is currently no documentation for FSUIPC7, but you can download the FSUIPC6 documentation. The UI has been re-organised (as its now an exe not a dll), but the main panels are pretty much the same. You can get the documentation here: FSUIPC6_Documentation Let me know how it goes. John P.S. I see you have also posted over in the MSFS forums - but no response so far...

😂 You're certainly not a chip off the old block are you 👍 Yeah, sorry I was a bit abrupt! Just seemed a strange question.Just discussing what this involves would not only be time consuming but also a waste of time. Its not something I would even consider - maybe if I had nothing else to do and someone paid me for this....! But at the moment, with continual P3D releases and MSFS just released, there is no point even starting a discussion.

Check the documentation! See offsets 1264, 1268 and 126C, and you can also calculate from the tank level offsets (0B74, 0B7C, etc) using the capacity. Check what those offsets contain first, to see if they look reasonable. As I said, if the add-on aircraft implements its own system via lvars, you may need to use them.

Sorry, I don't know Cockpitsonic or EHID drivers (Pete may know more!), but if they register as standard windows hid devices then FSUIPC should recognise them. Have you tried?

Ok, but those offsets are 'capacity', not quantity. No - the offsets are populated from the sim (using simvars), not lvars. If the maddogX uses lvars for this (and not the simvars), then you will need to read these and write them to a free offset, and then use that offset. John

Thanks Thomas, I thought so but using the keyboard directly in MSFS is a good way to confirm.

Thanks Andrew. Good to know this!

And not in the 'details view (as a background process)? Can you please check this again. Also, could you attach your FSUIPC7.log file generated when this occurs please. I see you have several VRI devices - could you try adding this to the [General] section of your .ini file: VRIDisableCMDRST=Yes

I thought FSUIPC7 was currently only this beta stand-alone application, so I don't quite understand what you mean by that? Can I use Lua as it is now or not? Adding to what Pete has said, I meant that you can use lua plugins in fsuipc7, but if you are using a lua stand-alone application (i.e. not ran as an FSUIPC plugin) then you would have no access to the lua libraries provided by FSUIPC to talk to the sim. The specific libraries provided by fSUIPC are only available for FSUIPC plugin scripts, not lua stand-alone applications.

I have noticed this very occasionally - one or twice, and Thomas has also seen this a few times, but mainly after/during a long flight. I'll look into it, but this will take time as I find this difficult to reproduce. As a workaround for the time being, I'll look into automatically connecting after a certain (configurable) number of transmit failures, as we do for other simconnect failures. I'll post it here for you to test once done as it seems that you are getting this quite often. John

I've checked those assignments here and they seem to work fine. Could you activate Axes Controls logging, load an aircraft and move both axes full in each direction and then show me your log file. Does this button register inthe FSUIPC7 button assignment window when you press it? Yes, if you don't want multiple assignments. It has been suggested to create a 'null' profile (with no assignments) in MSFS, and use that when using FSUIPC7. Note that there are currently many more assignments available in MSFS, so you still may want to assign there for some that are either currently unavailable or not working via SimConnect (e.g. to control views).

I think most axes are working, apart from the view (PAN VIEW) and slewing axes. If not, please let me know. You can try that. My devices don't have any default assignments so I haven't investigated this yet. Otherwise, just remove any default assignments that you don't need. You may want to keep some assignments anyway, e.g. for controlling the views. You should initially try with you existing FSUIPC4/5/6 ini if you have one. Just copy it to your FSUIPC7 installation directory and rename it to FSUIPC7.ini, and copy across any auxiliary files that you may use (.lua, .mcro). Anything using lvars or mouse macros will not work, or anything using P3D specific controls, but you can remap these afterwards. Anyway, worth a try rather than starting directly from scratch.

Are you sure? Its detected here. If you are using Mixture 1, its on page 4 of the calibration screens. If its not working for you, then I think it must be due to your PFC settings. I don't have any PFC devices, sorry - maybe Thomas can help with this. It's would be more efficient to send direct to fsuipc calibration and calibrating, so yes it is correct. As for the throttle, I have also noticed that it is less respondent than the other axis. I'm not sure why this is - I'll take a look and maybe report to Asobo. I haven't checked the prop axis yet - what plane are you using?

Thanks for reporting - and yes, this is the correct place! 0x281C is the Master Battery (which you have said is working!), Avionics is 0x2E80. I'll check both of these sometime today. For the Avionics, it seems that the control Avionics Master Set works, but not Toggle Avionics Master. See I'll check what the offset is using and maybe update. John