John Dowson

No. Keep your profile name as it is - that's not important - I just used that as I don't know what your profile name is called! What is important is to have the ShortAircraftNameOk ini parameter set to SubString, and the substring you use here: 1=PMDG 747 If you also want to use it with the PMDG 777s, then you can add 2=PMDG 777 Or, for example, if you wanted to use that profile with all PMDG aircraft, you could just use 1=PMDG Just understand what a substring match does (checks if the string you specify is a sub-string of the aircraft name) and you should be ok going forward. John

First, make sure you are using ShortAircraftNameOk=Substring in the [General] section of your FSUIPC ini file. Then, just adjust the profile to specify a substring that is in all of the aircraft names for which you want to use that profile, such as [Profile.Boeing] 1=PMDG 747 (where 'Boeing' is your profile name). This would match all aircraft hat contained the substring 'PMDG 747'. John

Note that the support for Xbox One and Xbox 360 game controllers is not 100% (others should be ok). For example, they are only affective when the FS has the focus. I can provide you with a time-limited license for FSUIPC6 if you would like to try the assignment facilities. Let me know. Sorry, didn't realise you were using FSX. Follow Pete's advise! John

Yes, that should work - two buttons, one cycling up through the values and the other down. Looks ok - did you try it? That (i.e. the offset cycle control) is new to me as well - had to look it up! Another way of achieving this would be to use a lua script, where you can maintain a local variable to hold the current state and then send the appropriate command and parameter on a button press depending upon this state.

That looks interesting, thanks. Currently you can access more of the internal variables by using the MobiFlight WASM module, with FFSUIPC event files (*.evt). Currently no way to access lvars though, I am looking into it. For FSUIPC7/MF WASM integration, see and

If its not clear, you missed the step of actually assigning an axis control to your device's axis: MISSING STEP: - check first checkbox, and select the appropriate axis that you would like your device to control, e.g. Axis Ailerons Set

Hi Dave, ok, thanks for the update. You install log now looks good.

Thanks - always nice to hear from happy customers.! John

Ok, me neither. Maybe you tried to install FSUIPC7 before installing or running MSFS? If you uninstalled MSFS, you need to install and run it at least once (to create/update the MSFS registry entries) before installing FSUIPC7. Anyway, seems to be working now.

I'm not sure why it couldn't create the link, but it looks like that prevented the documents being installed for some reason. I'll check this. Could you try the following please. First, uninstall FSUIPC7 by running the uninstaller D:\FSUIPC7\uninstallFSUIPC7.exe Then, manually remove your FSUIPC7 documents folder, if it still exists: C:\Users\dmarc\Documents\FSUIPC7. Then re-install, and show me you new InstallFSUIPC7.log file. Thanks, John

Great! So you are now using the MobiFlight WASM module with the FSUIPC event files? ...ok, I see Antonio posted the files - thanks!

Hi Max, But if you are installing SDVFR after installing FSUIPC7, you do not need to re-run the FSUIPC7 installer again after installing SDVFR, no? So how can this cause a bug in the installer? FSUIPC7 doesn't touch that file so it shouldn't make any difference to the install order. The only MSFS file that FSUIPC7 creates or modifies is the EXE.xm;, and only when selecting to install the Autostart component. Anyway, I'm glad its working even though I'm not sure what the original problem was, or if I can do anything to prevent this occurring again or for other users. Maybe its the SDVFR installer that needs updating? Cheers, John

Ok, they look better now, except for the fact that your profile ini hasn't been re-written to use the JoyLetters, which is strange. And it looks like you didn't activate logging for Buttons & Switches, but that doesn't matter now. Your log shows the Pan View controls being sent ok with the correct parameters: So your assignment is correct and the control is being sent, but I don't know why it isn't working for this aircraft. Is it working ok for other aircraft (esp. default aircraft)? If so, I think you need to ask on the SSW forums.

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.