John Dowson

They are in your FSUIPC7 installation folder. If you don't know where that is, you can open it in Windows Explorer using the File -> Open Installation Folder... menu option in FSUIPC7. If you cannot see the files, you probably have Explorer configured to hide extensions of known file types. If this is the case, see the Addendum at the end of the Installing and Registering FSUIPC7.pdf. Please be aware that support is also closed now until 3rd January, that is, I am on holiday. I may cover a few outstanding requests, but most will now have to wait. Please check the provided documentation, and there is also a lot of information in these support forums. However, for specific information on add-ons you may need to try the add-on developer' support.

Save the following text as RemoveMyX52.reg: Disconnect your controllers, back-up your registry, then double-click the .reg file you created to remove the registry entries, then reboot and re-connect your controllers. No need. Just remove/uninstall them using the windows device manager. The default windows ones will be re-installed. John

You uninstalled the software, but did you uninstall the drivers? if not, you need to do that, ot just do that anyway. Reboot and then reconnect and then you should see windows install the default drivers. If you have already done this, then as both the throttle and stick are giving the same joy id numbers, you may need to clean your registry. First, you could try to see if FSUIPC can do this by changing this part of your FSUIPC7.ini: to Try that to see if it recognises your throttle and stick as separate controllers. If not, unplug your controllers and clean/remove the registry entries for the throttle and stick (I can help with this if needed), then reboot and after reconnect your controllers. You also have controllers active in P3d. If assigning in FSUIPC, we recommend disabling controllers completely in P3D as it has a tendency yo re-assign when it afain detects your controllers as 'new' controllers. John

FYI, the latest release of FSUIPC7 v7.2.14 by default will only request these 2 variables for 6 pumps/indices. There is a new ini parameter: NumberOfPumps=6 which you can add (and change - 6 is the default value) to the [General] section of the FSUIPC7.ini if you want the offsets for additional pumps to be populated. John

It always helps if you can attach your FSUIPC7.ini and FSUIPC7.log files, to see what you have currently assigned. For the saitek X52, make sure that you have not installed any saitek software or drivers. If do, unplug your devices, uninstall any saitek software or drivers, and then reboot. Re-connect your X52 and then let windows install default drivers. I have the X52 and use this without issues on my development machine so there really shouldn't be any issues using these controllers with FSUIPC. As for your issue with the SWS Kodiak 100, I cannot help with this as this is an add-on aircraft that I do not own. I think you first need to understand how reverse thrust is controlled in that aircraft - does it use the reverse thrust toggle control? Is it using the *_EX1 controls for thrust? How do you control reverse thrust if assigning in MSFS? These are questions for the Kodak support forum (flightsim.com) - I cannot answer these, not having the aircraft. Regards, John

What changed between the different sessions? FSUIPC gets device information from yoit windows registry, so something must have changed... Are you using any saitek software or drivers? If so, please uninstall and let windows install default drivers. Then try again. If you still have issues, please show me (i.e. attach) your complete FSUIPC6.ini, FSUIPC6.log and FSUIPC6.JoyScan.csv files. There is no point pasting extracts. John

Doesn't matter - that was an example (it is a plug-in for the Bravo lights). That may have the same issue (i.e. corrupts the EXE.xml) - there is also a logitech plufin that does this, but cannot remember the name at the moment... As with all windows applications, you double-click the executable, in this case the FSUIPC7.exe. If you don't know where that is, plerase don't ask me - read the documentation.... Have you tried as suggested? Have you looked at the documentation or searched for previous support requests? Have you looked at the MSFS documentation on the format of the EXE.xml file? It really isn't that difficult... But if you post yout current EXE.xml file here, then rename it to EXE.xml.notused (for example), then re-run the FSUIPC7 installer it will create a new valid EXE.xml. Then show me that file, together with the old/renamed EXE.xml.notUsed, and I can add that back in for you. BUT, it really isn't that difficult. You should try and do this yourself and I can assist if you have difficulties. John P.S. I am closing support in 2 hours or so. You can continue posting but I will not answer until the 3rd Jan.

So, FSUIPC7 is not auto-starting with MSFS? The usual problem is a corrupt EXE.xml file caused by another add-on (AFC_Bridge can cause this). This is mentioned in the provided README.txt file: John

For the FBW A320, there is a custom event for this: A32NX.FCU_EXPED_PUSH There is an FBW custom event file provided in the EventFiles sub-folder of your FSUIPC installation folder, called flybywire-aircraft-a320-neo.evt. To use this file, move it up one folder to your main FSUIPC7 installation folder. You can then assign a button or key press directly to that control. You could also test that this works first by using the Add-ons->WASM->Execute Calculator code... menu entry and enter the following: (>K:A32NX.FCU_EXPED_PUSH) In general, for the FBW aircraft (and many others), you can use the MobiFlight hubhop preset list resource to see what lvars/hvars/custom events the presets are using: https://hubhop.mobiflight.com/#/. Not 100% sure what this means. If you are referring to the keypresses in your image, then this shows you pressing some keys, none of which have assignments: U, t, [, You only have the following keys assigned: The log you attached shows nothing.

What is the 'expediate' button? What aircraft are you using? What us that image supposed to show? Please describe your issue fully and attach the appropriate files, namely your FSUIPC7.log and FSUIPC7.ini files. John

Change this: to this: And this: to this: If you do that, any aircraft containing the string 'FWB A320neo' will match the A320 profile, and aircraft names containing the substring 'CRJ700ER' will match your CRJ profile. It is that simple. I don't understand why I have to explain this so often.... But what is your actual issue? If you think that your profile assignments are not being loaded, I need to see a log file with appropriate logging added that demonstrates your issue. So, if you thing a button assignment isn't being loaded, activate logging for Buttons and Key presses + Events, and generate a short log file where you press the button, then exit.

Profile settings are automatically loaded, you don't need to do anything. Make sure that you are using substrings for the aircraft name in your profile section (needs manual editing of your FSUIPC7.ini file) so that it catches all different versions/liveries of the aircraft. See Appendix 2 (About the Aircraft Specific option and “ShortAircraftNameOK” ) in the Advanced User guide for details. If you think that a profile is not being automatically loaded for a particular aircraft, activate logging for Buttons and Keypresses + Events, load the aircraft, press a button that you think should be assigned, exit and show me your FSUIPC7.ini and FSUIPC7.log files. John

The log you posted looks reasonable with the N1 values starting at 4401 and then reducing to 0. Did SLC show the same? As I have said, the FSUIPC offsets are just holding the values as received from the FS. If they are different in SLC, then it is an issue with SLC. If the N1 values reported in those offsets are not correct, then it is a an issue with the aircraft. John

The spoiler controls are being logged ok. I don't know why those controls aren't having any affect. You have assigned to 'Direct to FSUIPC Calibration'. You could try switching to using the FS control instead, and remove the spoiler calibration line under [JoystickCalibration.787]: Spoilers=-11903,-7168,-512,12223/24 The calibration looks a but strange in any case - you have a very large null zone set.

No. The scan returns all available lvars at the time of the scan. The issue is that some lvars, especially in complex aircraft such as the FBW A32NX, are created quite a while after the initial scan is performed. You can delay the time the scan starts in the WASM module, by setting the WASM ini parameter LvarScanDelay. From the Advanced User guide P45: I would suggest a value of around 45seconds, but try varying it until you get all the variables you need. Note that you can also issue a WASMPtr->reload() call at any time which will re-scan for available lvars (as well as reloading hvar files). John

If you activate event logging and move the switches in the UI, do you see any events logged (in your FSUIPC4.log file)? If so, try assigning to them. You could also try looking to see if there are any lvars that look applicable - try listing the available using the List Local Panel Vars control. Do you mean the box where you enter the macro name (see P37 of the User Guide)? If so, you need to give the macro a name, and once you have finished creating macros, end the macro session. Please see the User guide for details. Mouse macros should work, if there are no standard controls. I don't have the Aerosoft A321 for FSX, but I do for P3Dv5. I can take a look at that to see what that uses, but I can't be sure it will be the same for the FSX version.

Yes, you just need the one section: Delete the other.

I think there are issues using the TCA Quadrant with FSUIPC. See this thread: The last posts from @Jetdriver50are interesting but we never got a response from the OP: John

You still have not changed your ini as recommended...never mind, but there is no point sending me the same ini each time if you are not going to change it. I only want to see it if you have changed anything. And you will have issues with the profile not being loaded for some aircraft - any not currently specified in your profile section. I don't understand why you do not change this. Your log shows the assigned control being sent each time you press a button. However, there are lots of other events that are being seen not related to button presses. This may be normal for the QW, I don't know - some add-ons do seem to continuously emit certain events, but they do look strange (especially so many PAN_* events...). As for the spoilers, there are quite a few spoiler controls being sent upon start-up: I don't know where these are coming from, but its not FSUIPC. Ok, lets see what they have to say. It does look like something the aircraft is doing. The aircraft also seems to take a long time to load. You should give it more time before you try to do anything. And as your spoilers are on an axis, you need to activate logging for Axes controls, not buttons, sorry. Could you try that - produce a short log file where you load the aircraft (wait until fully loaded...), operate your spoiler axis, then exit and show me the log file.

To run FSUIPC6, you have to run P3D, as its an embedded dll, so I don't see how this can help...you will also get the weather/radar.bin from P3D... John

This is no longer possible, as ActiveSky is NOT compatible with FSUIPC7. FSUIPC6 (and earlier) use a dll provided by ActiveSky to achieve this - either the as_connect_v5.dll or the as_connect_64.dll (depending upon AS and FSUIPC version). But these dlls are no longer loaded by the FS, and if they were FSUIPC7 would still have no access to these as FSUIPC7 is a separate executable and is no longer embedded into the sim. It is therefore no longer possible for such images to be created in FSUIPC7, sorry. John

No, but you are logging the values incorrectly. You are logging them as U8, an unsigned byte, whereas they are in fact two byte unsigned shorts, so should be logged as U16. This is why you are only seeing values in the 0-255 range (the range for a U8). So, change your logging to U16 and repeat your tests - and you do not need IPC read logging activated. You can also see the log in real-time if you open the logging console. Look at the logged values and compare to what you see in SLC. If they are different, then report this to SLC, You could also log the N1 %age values, held as 8-byte floating point values in offsets 0x2000 and 0x2100. john

Your image shows the values logged as 107. on a scale of 0-16384, this is .007%, which is basically zero.....I don't know where SLC is getting those numbers from...

Please stop with pasting images. I need to see your files - I will not look at images.... If the logged values are different than those shown in SLC, you need to contact SLC to find out why... If the logged values are not correct, then ask on the PMDG support forums. FSUIPC just requests these values and stores them in offsets for access by 3rd party programs, such as SLC. John

You could try reading the documentation on logging.... You need to select where to log the information. Check 'Normal log file' and the values will be written to your FSUIPC6.log file. You can attach that here so that I can see the values. I am only suggesting you check this for the values you need....maybe PMDG implement their own systems for this. However, if it was previoulsy working ok, O suspect that something else must have changed.... This is why I have suggested logging those offsets, so we can see what FSUIPC is holding for those values. Nor am I! How can SLC be displaying such values if its an unsigned int...only SLC can answer this question... But it will help if you can log those offset so we can actually see what the source of those values actually is... John