John Dowson

😂 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

You posted your key!!!!!!!!!! I said, DO NOT POST YOUR KEY!!! If you do that again. your key will be blocked as posting a key publicly is a violation of the license conditions. I have deleted your message. I've sent you a PM showing that your registration is valid. I really don't understand what your problem is as you are providing no information except that 'my key is not valid', which it obviously is.

Did you do as I said? What happens after you click the 'Register' button? You should get a pop-up either saying that your registration is valid or not - what did it say? If it said it was invalid, then you entered your details incorrectly. I have validated them here and they are fine.

Your registration details work just fine here. Please double check that you are entering them correctly - as I said, best to copy/paste, and make sure you click the 'Register' button.

Sorry, what does this mean - v4 or v5? what is '14'? An FSUIPC6 key is valid for FSUIPC6, not FSUIPC5. You must use the details EXACTLY as specified in your SimMarket account/purchase email. Try copying and pasting the details from there. If you still have issues, let me know your order number and purchase date and I will check it here. DO NOT POST YOUR key!!! John

It seems that the events MSFS uses to control the avionics individually have not been exposed through SimConnect. Activating them via the UI (or via an assignment in MSFS) shows no associated event/control. I can ask if its possible to add these to the SDK. For now, you would have to use the Avionics Master Set.

Hi Rod, the individual controls are no longer present in MSFS - well, in the SDK documentation. I'll activate them here locally to see if they work, and if so I'll report back and add them back in for the next release. I've just taken a look at the C172 and it looks like the Toggle Avionics Master has no affect. However, the Avionics Master Set control works. You can use this with a parameter of 1 to turn both avionic systems on, and 0 to turn them off. John

If you want to assign an action to a button, you would use the drop-down 'control' menu to assign the action there. Whether this action is then implemented via an event/control or via updating a simvar is not particularly important. Usually there are various methods of implementing a function. If you had the choice of using an offset or sending a control, then the control method would be preferred - the offset method may use the same control/event in the background, so using the control directly would be (slightly) more efficient. Note I will be removing those 'Ok-SimC', etc status from the document at some point as I think they are confusing and unnecessary for most users. It would be better to just say if read/write wee working or not (or unknown).

The distinction is technical and is related to the SimConnect API - and not really relevant to users of FSUIPC, so I wouldn't worry about this too much. SimConnect provides both simulator variables that you can read and sometimes write to (not all variables are writable), as well as 'events' (or controls) that perform specific actions. FSUIPC uses both methods.

PMDG usually implement their own controls for these type of things. Are you sure this was working for your PMDG aircraft in FSX? For many PMDG controls, you have to use their custom controls. This is explained somewhere in their SDK. This also may be helpful: https://myhomecockpit.de/index.php/en/?view=article&id=56 John

What aircraft are you using? Just tried it in the Maule and it seems to work ok there. If its an add-on aircraft, standard controls may not work. You could try try AP_MASTER to see if that works, but that will toggle on/off. However, if that works, you can probably add an offset-check condition to only turn it off via the button (if you do not want the toggle functionality). Otherwise, turn on FSUIPC event logging, switch the autopilot on and then off in the UI and see what events are logged. Cheers, John

First, you posted in the main FSUIPC support forum. As it says in the release note and in the README.txt provided with FSUIPC7-Beta, there is a dedicated sub-forum for FSUIPC7-beta/MSFS. I have moved your post for you. And if you had checked this sub-forum, you would have seen that this problem has been reported many times. It is an issue with SimConnect that is known and will be addressed in the next patch release of MSFS. Please see John

Both FSUIPC4 and WideFS7 require a new license, available from SimMarket. John