John Dowson

As Al has stated, this is already documented as not working. This is because that offset was populated from an lvar (was Ok-Lvar in previous versions of the offset status document), and lvars are currently not supported by FSUIPC7. I am currently looking in to providing lvar access in FSUIPC7. John

For the Xbox 360, the device will only be take affect when FSX has the focus, and the left and right trigger buttons act as a single button.

I think that those are the buttons outside of the 32 button limit (0-31). To access those, you currently need to use a Lua sctipt. See John

Nothing changed on your system. I changed the position and font size in a recent release as it didn't show completely on one of my screens, so it probably changed for you then. I'll remove the 'We Are' in the next release.

Yes, probably a better solution!

Current time-limited license attached, although its only valid until 01/02/2021. Drop it into your installation folder - no need to re-install or register. John FSUIPC7.key

What size/type of screen are you using? Its nothing to worry about - I adjusted text size and position so that its all visible on the displays I have. And the text looked a bit strange when centred as it hides the a/c. I'll reduce the font size slightly in the next release so it should fit. John

I'm not sure which version you are using, but if you have the 'MSFSwithFSUIPC' icon, then starting MSFS via the standard icon will not start FSUIPC7, and FSUIPC7 does not alter anything in MSFS at all, and installs no mods. It is a stand-alone application. The latest install does have an option to have MSFS auto-start FSUIPC7, but more on that later. It is not a 'mod' as such, so you don't need to uninstall it, just don't run it. Also, running FSUIPC7 will have no affect on the sim until it has a simconnect connection, i.e. when 'connected'. Yes, with the proviso of the EXE.xml file in the latest installer (see below) which is optionally created and/or modified. No. Yes, you can rule it out. I'm not sure what version of FSUIPC7 you are using, but the latest is v7.0.4. And the latest installer has the option of having MSFS auto-start FSUIPC7 when it is ready, which is better. This creates (or modifies if it already exists) a file in your MSFS AppData folder (EXE.xml) to give details to MSFS to start FSUIPC7. You can disable this if you like but this is now the recommended way to start FSUIPC7. The desktop link (and batch file) is still also optionally available, but now no longer starts FSUIPC7. Once you have sorted out your MSFS issue, that I can't help with I'm afraid, I suggest that you download the latest version and installer. John

@Djeez Could you try the following version please, v7.0.5d. In this, I have added a 1 byte offset at 0x029E. This is a bit oriented flag, so a value of 0x1 will indicate Avionics master 1 is on, 0x2 that master avionics 2 is on, and 0x3 indicates both avionics are on. Similarly, writing 0x1 will turn avionics 1 on and avionics 2 off (if on), 0x2 will turn avionics 2 on (and 1 off, if on), 0x3 will turn both avionics on, and 0x0 will turn both off. As there is no sim variable for this, the initial state cannot be determined, so its probably best to sync this by sending each control (avionic 1 & 2 set off - maybe) on start-up. Anyway, please try this and let me know how it works for you. I've tested via direct assignments but not using lua. John FSUIPC7.exe

Presume you mean that there is no control you can map to your button, no? Have you tried the Toggle Flight Director control? There is also the Autopilot Flight Director Active offset at 0x2EE0 that you can use. John

Sorry, but where does it say that? You ARE using profiles. What it says is that if you are using EXTENSIVE use of profiles, then it MAY be easier to use profiles in separate files by setting UseProfiles to Files (rather than Yes). You don't need to do this. No, it isn't. A profile name is just the name. The strings that match the profile are specifid in that section, as n=.... (where n is 1,2,3,...etc, and the ... is the substring to match). Here: [Profile.Boeing]1=PMDG 747 i.e. under your Boeing profile. Or, if you also want to use that profile for the 777, use [Profile.Boeing]1=PMDG 747 2=PMDG 777 Then, the Boeing profile would be used for all aircraft whose name contained the substring PMDG 747 or PMDG 777.

No! Please read my comments. Its ShortAircraftNameOk=Substring This is all explained un the User Guide, section User profiles for all control settings. Please read this. We provide this documentation so that we don't have to continually respond to questions like this.... Not sure what this means. What has this got to do with profiles? You assignments are to specific devices, so they work independently.

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.