John Dowson

I don't need the dll - I've removed that. Looks like you didn't activate the logging that I asked for. Could you add that and re-generate your FSUIPC6.log file please. Did you assign the pan view control to your VKBsim Gladiator? If not, it could be that your joystick ids have changed. Before you generate the new log, change To AutoAssignLetters=Yes In your FSUIPC6.ini (before you start P3D). This will re-write your inis to use "JoyLetters" (see the FSUIPC user manuals for details on this). Then start P3D, load your aircraft, activate the required logging (Axis controls and Buttons & Switches), and then show me the 3 files again - your FSUIPC6.ini, FSUIPC6.log and SSW F-104G.ini John

Ok Ed, thanks for the update. Glad its all now working, John

Then you installed into a location where an existing FSUIPC6.ini file was not found, and so a new one will be created. That is probably why the version still said 6008 in the ini you posted - thats not where you installed. And you are using separate files for profiles. As I said, please read the provided Installation and Registration guide. John

If you checked both boxes, it will install one copy of FSUIPC6 for use by both P3Dv4 and P3Dv5. It will update the add-on.xml (or dll.xml file, whichever method you choose) for both. If you want a separate installation for each P3D version, then you need to run the installer twice, and install once in P3Dv4 and a second time for P3Dv5. Note that it is also HIGHLY RECOMMENDED to NOT install FSUIPC into the (default) add-ons folder. Please choose another location (e.g. C:\FSUIPC6 or C:\P3Dv5 Add-ons\FSUIPC6) to keep your FSUIPC installation folder separate from your xml add-ons folder. All this is explained in the included Installation and Registration guide.

But your ini file shows that you have no assignments at all!: Both your Axes and Buttons sections are empty! Did you select an appropriate control from the drop-down menu? I think not. Please see the User Guide.

That ini file still shows version 6008. Do you not have an updated version? As you are using files for profiles, I need to see your SSW F-104G ini. Could you also activate axis controls and button logging in FSUIPC, then start P3D, load your aircraft and try the hat switch. Then close down, and show me all three files (your log and the two inis).

1. Please upgrade to the latest version, v6.0.12 as only the latest version is supported. 2. Please attach you full FSUIPC6.ini file (not just an extract) and also your FSUIPC6.log file and I will take a look (after you have updated). John

Ok. But how is it currently working? With admin privileges or without? If running everything without, you should be able to use the EXE.xml auto-start method. You really need to just play around with the various options and see what works for you. It would be better to run all without privileges, unless needed.

But you can still try with this. If, when you install FSUIPC7, do not check the component 'Auto-start with MSFS', so the EXE.xml is not updated to start FSUIPC7. Then, if you go to your installation folder and open the MSFS.bat, you can uncomment these lines (i.e. removed the colons marked in red/bold): Then, change INSTDIR to your FSUIPC7 installation folder.

I see you posted in the other thread: Good to know, thanks!

Yes. You don't need MF installed to use the WASM module. You just need to download MF to get the WASM module.

The difference is, of course, that FSUIPC5/6 runs in a dll inside the P3D process, and so shares the same privilege level. FSUIPC7 is an executable, and so behaves differently in this respect. And it probably depends on hoe FSUIPC7 is started, either manually or via MSFSs EXE.xml.

If they are new, I would think that there would be an updated WASM module release. Have you (or anyone) checked? As I said, those new events may not yet be released, according to the spreadsheet. Maybe you will find more information on this on the MobiFlight forums? John

But are you using the MSFS EXE.xml to start FSUIPC7 (latest method), or the older batch script that starts MSFS and then starts FSUIPC7? Yes - select the FSUIPC7.exe file, right-click and select Properties..., go to the Compatibility tab and check Run this program as administrator. I thought you had done this already... I'm not sure, but if MSFS is starting FSUIPC7 with admin privileges, then I think MSFS must also be ran with the same. You can either try this (i.e. all started as administrator), or also try removing the autostart of FSUIPC7 with MSFS via the EXE.xml, and either start manually or go back to the old method using the *.bat file.

Please note that many of the new events you initially listed are not yet released, according to the spreadsheet available here: https://docs.google.com/spreadsheets/d/1jTXlcHaJWx0B7TB63Pmma7bKwpxsxXJO6EJ3ECt7zpc/edit#gid=172455454

Ah, ok - got it, thanks. Not unless FSUIPC knows about these, e.g. via an event file. No. The WASM module is needed as that handles the events. Is it the same WASM module, or do MobiFlight provided different WASM modules for different aircraft/mods? Hopefully the former... I would initially try adding these to an event file, as I said. I can try this at some point, but it may take me a day or two to get around to this. Note that some new MobiFlight events (for the A320) have also been reported here:

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.