John Dowson

Just run it as administrator - from the MakeRwys readme document: John

You can use the Flaps Set control. To calculate the parameter, see the description for offset 0x0BDC: Alternatively you can read/log offset 0x3BFA which will give you the flaps detent increment (i.e. the value between each flaps detent/position) and then use this to calculate the parameter needed for each position. John

What axis? You are defining a preset, not an axis or an lvar. You can see presets in the axis assignment panel once you have selected 'Send Preset to FS'. You should then see the presets you have defined in the axis assignment drop-down. When you list the lvars, you can see the lvars that the presets you have defined are using: INPUT_AILERON & INPUT_RUDDER_S. Note I have just released a new version which, amongst other things, reduces the presets in the axis assignment dialog drop-down menu to contain only those presets which accept a parameter, which drastically reduces the number of presets available and makes them far easier to find and assign. So please update at your earliest opportunity. John

Which version of FSUIPC and what FS are you using? If its FSUIPC7 / MSFS, please use the specific sub-forum for this product. No A-type variables (also known as simvars) can be read via lua. The only A-type variables can be read are those that are held in FSUIPC offsets. Of course, as these facilities are for L-type variables, or lvars, only. You cannot use them for any other variable type. So, A-type variables (simvars) can only be accessed (read/write) via FSUIPC offsets. Facilities are provided to add any simvar to a free/spare FSUIPC offset (see the Advanced User guide) using a file called myOffsets.txt. So you can add them to a spare/free FSUIPC offset, and then use the appropriate lua offset function to read the value.

Yes. just delete it. John

License sent. You can assign to the presets Longitude Eng R Fuel Run Stop Button Press and Longitude Eng L Fuel Run Stop Button Press. There are also presets available for the engine left/right starter - see https://hubhop.mobiflight.com/presets/. Note that tomorrow I will be releasing a new version that contains a UI update that makes finding presets a lot easier, so I suggest you update to this version once released. John

This has now been implemented in the attached version. 7.3.23. This completes the implementation of this item for the time being. The attached version will also be the next release, and also contains a version check at start-up and will notify (display a message) if a newer version of FSUIPC7 is available. John EDIT: the attached file/version has been removed as this version has now been released

What do you mean by this? Lvars are independent from the PMDG offsets. Even if you uninstalled the FSUIPC WASM module (to disable access to lvars) the PMDG offsets would still be available and populated (once activated)..

Please try the attached version: FSUIPC7.exe This should automatically select and show any current preset that is assigned, and also select the parent of the previous selection made if no current selection/assignment available. Note however that it does not remember the previous state if no selection is/was made. John

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