John Dowson

You need to know the custom event number. Then use the <custom Control> entry in the assignments control drop-down when assigning. Oooh, that looks nice! Presumably its just another 'button box' though, so your problem is finding a working control for the functions needed. I didn't see the events you posted (such as WT_CJ4_AP_NAV_PRESSED) in that link....? But if they are Mobiflight events and are handled by the MobiFlight WASM module, you could try adding them to an event file, prefixed by 'MobiFlight.', and try them to see if they have any affect.

Sorry, I don't know what problem you are referring to or what the 'panel of FlightsimPM' is. Thats interesting. Is there a WASM module that handles those events (with custom event names containing a period)? If so, an FSUIPC event file (*.evt) can be used to add those events to fsuipc (as with the MobiFlight events/WASM module). Alternatively, if you know the custom event numbers used, you could try assigning to those as <custom> events.

I can't see how this can be possible - something else must be going on.... Can you please show me the corrupted ini file.

Yes, 740 indicates there is a permissions mismatch somewhere. Check that both FSUIPC7 an Prosim are running with admin privileges. Are you using MSFS to start FSUIPC7? If so, you may have to run MSFS with admin privileges (I'm not sure). What happens if you start FSUIPC7 manually before you start MSFS?

@Cjones63223 Please try the steps outlined in the README.txt: John

Similar to what? Is the joy# and Btn# recognized? Note that if the button numbers are outside the 0-31 (32) button range, you will need a lua script to assign the extra buttons. You don't say which throttle quadrant you are using, but if its the new Honeycomb Bravo then there is a lua script available for this here: Otherwise, if the joystick and button numbers are displayed and an assignment shown, it could be that there are already multiple assignments to that button, in which case you need to edit your ini. John

Ok, I will add and post again here for you to test. Quite busy at the moment (well, always!), so it may take me a few days to get around to this. Also, this offset would come with some warnings, as I don't think the initial state of the individual avionics can be determined (but I will check). If this is the case, the offsets could show the incorrect values on occasion (e.g. starting FSUIPC when MSFS already running and, say, master avionics 1 set on and 2 off) but should revert to the correct state once used. I'll know more and let you know the details once implemented. John

Yes, I think we need to wait for Asobo to fix this issue. For reference, here's the original report on this: John

It can be used directly if it is seen by windows as a HID joystick type device. If its any other type of HID device, it should be possible via Lua. Quite a few folks are using Arduino's with FSUIPC, so I guess it will be ok, but I'm not familiar with the various Arduino models.

@cchiozza Your install log looks fine. Did you not get a pop-up box when you start P3Dv5 asking if you want the FSUIPC6 add-on to be enabled? If you go to Options -> Add-ons, do you see FSUIPC6 listed there? If so, and it isn't checked/active, try activating there. I see you also installed in P3Dv4 - is it working/active in that version?

Maybe also try sending direct to FSUIPC calibration and calibrating in the calibration tab (p6 of the calibration screens).

What control are you assigning to? Which aircraft are you using? Could you activate logging for Axis controls and events, and generate a short log file (just load a plane and turn the trim wheel through its full range, then exit). Then attach your FSUIPC7.log and FSUIPC7.ini files and I'll take a look.

Just use the attached license. Save it to your FSUIPC7 installation folder. It should be valid until (and including) 01/02/2021. John FSUIPC7.key

Hi Emile, Ok, that's good to know. I'll verify this when I get a chance and update the FAQ entry accordingly. John

There are no sim variables (exposed via simconnect or otherwise) for those. I suspect there may be available via lvars (or some other type of variable, maybe k vars), but as Al has commented, there is currently no way to access lvars using FSUIPC7. I am looking in to providing such access in a future release, but no timescales yet. John

I could add to a new offset if you like. I can't really update the functionality of existing offset 0x3103, but I could add a new offset that would be read/write and accept flags 0x1 for avionics master 1 and 0x2 for avionics master 2 (and so a value of 0x3 would indicate/set both master avionics). Let me know if this is useful and I can add for you to test. John

You need to assign to the control Throttle Revers Thrust Toggle. However, this control/event seems to be broken since the last MSFS update. I have reported this to Asobo. John

As I have said, your logs show that it is MSFS that is crashing, not FSUIPC7. You are experiencing the issue previously mentioned with the MSFS SDK. You should raise a support request with Asobo, and include the event log information and the crash dump file. John

Could you attach your InstallFSUIPC6.log file please and I'll take a look. John

I don't know - it should be recognised directly if its a hid joystick type device, and programmable via lua if its any other type of hid device. I can provide you with a time-limited license to try the registered facilities if you like - let me know. John

Controls Avionics Master 1/2 Set were added for this back in October 2020 - see

Yes, thanks for the input. John

As the author says. this is calling other lua scripts and those functions are defined in Linda. Maybe the author should make it clear that those functions are used. I'm not sure if you could extract those functions and use them without Linda, as they probably reference other Linda functions. Maybe the author, @joeherwig, could either let you know if this script - only works with Linda installed, or - can be used by extracting a self-contained set of lua functions? If so, maybe this can also be added to github? John

If its now working, its not necessary to send me any more files.

It connected initially after 18 seconds: Note that WideServer is only started/enabled by FSUIPC once you have an aircraftin a ready-to-fly state. You can manually enable it earlier if you wish. WideClient cannot connect before WideServer is started. But this is a separate issue and cannot be related to your wideclient connection issue, which seems to be solved. There are currently known issues with MSFS crashing due to issues with simconnect, and so provoked by simconnect clients. Asobo are aware of the problem and are looking into it (there are various threads on this in this forum). All MSFS CTDs should really be reported to Asobo via zendesk, with relevant details (event log details + crash dump) if available.