John Dowson

This has been implemented in the attached version. Also, if there is no currently assigned preset, the parent node of the previous node selected will be selected. John FSUIPC7.exe

Sure - sent! John

Of course....the main function of the installer is to install the FSUIPC4.dll file. And it has been installed but here: C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL No - the only file "generated" in the installation process is the FSUIPC4.key file, generated when you enter and validate your registration details. Yes, i know, but that is NOT where FSUIPC4 is being installed, due to your registry issues which I have mentioned... For the THIRD time, when you run the installer FSUIPC4 is being installed here: C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules. It MUST be there as this is from your installation log: Did You look at that folder? Try looking at the installation log yourself adter you run the installer - this will tell you where things have been installed. It is clear to me what has happened and I have explained this several times now, as well as what you need to do to rectify this. If its working, fine - just leave it But just remember that your documents will now be installed in C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC Documents. This is why I suggest that you move the contents of that Modules folder across to the correct Modules folder for FSX.

Maybe, but that is not the one where FSUIPC4 was installed - from your installation log (first one): FSUIPC4 was installed there, due to the registry entry. Because it is not running - if it was, it would be under the FSX Add-ons menu. What was that second installation log you posted/attached - that was for an old beta version of FSUIPC4 (4.955c) and showed a failed install. If course not...and that cannot be the only FSX files on C:\ - as your installation log shows, FSYUPC4 was installed here: Why do you have the FSYUPC4 installer and related files in your Modules folder? Most of those files should NOT be there... So basically you manually installed it. That is Ok, but you will be missing the documentation. I suggest that you look into the Modules folder where FSUIPC4 was actually installed (C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules) and move the files from there to the correct location (D:\SteamLibrary\steamapps\common\FSX\Modules)

No, sorry, as it is coming from the kACARS program, and not FSUIPC. I have heard of this (it is not malware) but have not used it. Seems to be just a standard acars client that supports various virtual airlines. If you don't use it, then just uninstall it, or just prevent it from running. Otherwise, you need to contact the providers of that software about that error - I cannot help with that. Cheers, John

No, sorry - for FSUIPC4, you can just delete the Modules folder. Yes - the installer just installs FSUIPC4 under your FSX main folder. Your issue is that the installer thinks that your FSX installation is under C:\Program Files (x86)\Steam\steamapps\common\FSX rather than D:\SteamLibrary\steamapps\common\FSX due to the registry entry.: However, rather than deleting the registry entry. as I suggested in my previous comment, you could just try moving the Modules folder C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules to D:\SteamLibrary\steamapps\common\FSX\Modules You need FSUPIC4 running first, and then you access the assignments panel in the FSUIPC4 main window, opened from the FSX Add-ins menu. They may have been automatically re-assigned - best to disable your controllers in FSX if assigning in FSUIPC4. John

Are you running FSX under steam or from Microsoft? The installer detects both in your registry bur with different paths: Which of these is correct? FSUIPC is being installed under C:\Program Files (x86)\Steam\steamapps\common\FSX, whereas it probably should go under D:\SteamLibrary\steamapps\common\FSX, no? So it seems that your FSX-SE installation is confused,,, You could try uninstalling FSUIPC4, removing that first registry entry for FSX [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0] (take a back-up first) and then installing FSUIPC4 afresh. Let me know if you need further help with this. John

License sent. John

Which bit/bits? Or do you mean all 16 bits? Can you try logging that offset using FSUIPC's offset logging facilities (as UB16 in hex). What values do you see? I can see 0 when cold and dark, and this changes to 0x101 (which is DC HOT BATT and AC TRANSFER 2 only powered) when started. I can't seem to get this value to change once started, but I am not that familiar with the 737 (especially the electrical system). Could you explain what you are doing and what you are expecting to see? And if this was previously working, do you know what version of the PMDG 737 you were previously using? The current/latest version is 3.0.72. Note also that FSUIPC just receives this data from the PMDG SDK. I have checked the previous offsets (0x64BC and 0x64C9) and these seem to be ok. So if this is an issue, I can only report to PMDG. You can also ask about this in the PMSG forums - it is the ELEC_BusPowered variable of the PMDG_NG3_Data structure provided by the PMDG SDK that provides this data. John

This file is found by the installer: However, this is nor modified by the installer, but an entry is added under the [Trusted] section when FSUIPC is ran for the first time and you allow the program to be ran with FSX. The entry that starts FSUIPC4 is added to the DLL.xml file: C:\Users\epp\AppData\Roaming\Microsoft\FSX\dll.xml and your log shows that this has been updated correctly: Your install log looks ok, so not sure why you can't see FSYUPC in the add-ons menu at the moment, Do you have an FSUIPC4.log file in your Modules folder? if so, can you show me that please. Otherwise I will get back to you, but probably tomorrow as I am busy today... John

Once I have figured out how to show the current selection, I can show (and open) the previous parent node when there i no current selection. I am having difficulties with this at the moment but will persevere... John

Sure - license sent. John

No problem. There i no check on duplicate preset names, so they will be added. The problem is that only the preset name is stored in your FSUIPC7.ini, so when this is reloaded this will match the first preset it finds that matches the name and use the preset code for that, which may be different than the one initially selected. You may want to check-out the latest beta version I have posted in this thread: This contains a Find Preset.. button, currently only for button assignments, that displays a tree-view of the presets available. The tree is constructed using the comments, so you may also want to add comments to your myevents.txt in the same way as they are used in the events.txt file. John

@joeherwig I have added a Find Preset... button to the button assignments dialog in the attached version, 7.3.23a, in the attached version. This is shown when the Select for Preset button is checked. The implementation is not yet complete - still to do: Add a Find Preset... button to the key assignments dialog. This should be straightforward. Automatically select the preset in the preset tree if a preset is already assigned when the Find Preset... button is pressed. I am having some difficulties with this but will continue to look unto this. This version also contains a change to the axis assignment dialog when the Send Preset to FS option is checked - now only presets that accept a parameter will be listed, as there is no point assigning an axis to a preset if a parameter is not accepted. You can still assign an axis to any preset when the axis enters a specific range, in the right-hand side of the axis assignment dialog. Let me know if there are any issues. Cheers, John FSUIPC7.exe P.S. You can add comments that won't be processed as tree nodes by using '///' to start the comment

Shouldn't matter as it should be using the AXIS_THROTTLEn_SET controls, but if you are using the THROTTLEn_SET controls and you don't see the calibration values change, then uncheck it. No...they look pretty standard,,,, You have to clear the Throttle calibration to see this - click the Reset button for the Throttle. Also better to set a larger idle range for the individual throttle calibration rather than just 0...

Did you try this, as specified on page 44 of the FSUIPC6 User guide: Don't forget to uncheck the NRZ (No Reverse Zone) checkbox on page 3 of the calibration screens when you calibrate. Otherwise, if you don't want to map to 4 throttles, you can assign to throttle 1 (and maybe also throttle 2) instead of just throttle, and then calibrate them on page 3 of the calibration screens, making sure NRZ is unchecked. John

Ok, great - thanks for the update, saves me some time! John

No. The installer is needed as, it also needs to update the MSFS EXE.xml file to add the auto-start of FSUIPC7 with MSFS. The installer also updates the windows registry (with the installed location paths) and generates the uninstaller. However, you can install manually if required. I can, as a one off, provide you with 3 zip files - one for FSUIPC7, one for the FSUIPC7 WASM module and one for the FSUIPC7 documentation. It would be up to you to manually modify the MSFS EXE.xml to enable auto-start. However, this would be a one off- I will not be making such zip files available on each release of FSUIPC7. Let me know if you want to provide you with the 3 zip files, but it may take me a few days to put these together. John

The file is provided as-is from MobFlght. Comparing the new one to the old one,. it looks like many of the KA_* events (as well as others) have been renamed rather than removed. Not sure why MF did this as it is bound to create issues with folks using the older preset names. I will ask about this on the MF discord channel. I have attached the previous events.txt file used for reference - you can diff this with the current one to see the changes (various free tools available for this): events.txt Probably better to update to use the new names, if available... Yes, many of them are generic - not sure why they are listed under the King Air rather than as generic Asobo events. John

License sent. John

Line 10 is not pressed.... when you press button 6 on joystick 0 then the assignments on that button, which are stored/saved in your ini file, are triggered, The assignment stored in line 10 is only activated when button 0 on joystick 0 is also pressed, and the assignment stored on line 20 is only activated when button 0 on joystick 0 is not also pressed. Pressing button 6 (on joystick 0) will trigger the assignment stored in line 10 if button 0 is also pressed, and the assignment stored in line 20 if not. By also pressing button (joystick 0) at the same time, This will then trigger the assignment at line 10 and not the one on line 20. But all this should be obvious, so I don't understand what/why you are asking this... please use FSUIPC's logging facilities to see what is happening - activate logging for Buttons & Keys and open the logging console and this will show you what is happening in real-time. Any further issues or questions, please raise a separate relevantly titled topic - but only after checking the documentation and also this forum for similar issues first. And any problem with assignments, please attach your FSUIPC7.ini and FSUIPC7.log files (with relevant logging activated). I am closing/locking this topic now. John

🖕

But its not 2022 x86 and x64 combined, it is 2015, 2017, 2019 & 2022 combined, with separate packages for x86 (32-bit) and x64 (64-bit). Not sure what your initial issue was, but glad its now working... But, this is not the place for such issues anyway, which have also been reported many many times before and always with the same resolution. This topic is for requesting a trial license only.... John

No - the combined package also installs the latest VC++ redistributables for 2015, 2017 and 2019. The registration checker is an older utility, used by the installer, which requires the 2019 (or maybe 2017) redistributables, which is why you need to install the latest combined package.

It may have the latest VC++ libraries installed, but it won't have the latest combined package which is the one needed....this is always the issue that people have with new PCs/laptops... John