John Dowson

From the provided README.txt file: John

If nothing is logged, that just means the button is not using a standard FS control. Hvar activation and lvar changes are not logged (although the latter can be). I cannot help if the provided hvars don't work as advertised - FSUIPC looks to be sending the commands as configured, so if this is not working as expected then you need to ask about this either on the Asobo forum for this aircraft. However, rather than using the hvars directly, why don't you use the MobiFlight presets for the H145? There are currently 263 presets available for this aircraft. You can install the MF events.txt file using the FSUIPC7 installer, or download the latest version from the MF HubHob site (https://hubhop.mobiflight.com/presets/ - you need to create an account). You can also copy the presets that you want to use to a myevents.txt file instead, and remove the events.txt file so as to not overpopulate the controls drop-down menu (as there are > 7000 presets available!). John

Hi Leo, There is no concept of 'profiles' for the WideClient buttons page. You could create an initial page with the aircraft selection with "Go To" buttons, and then implement the buttons for each aircraft in separate (and also possibly multiple) pages. You could then select the top-level button page for the aircraft that you have loaded when started. Cheers, John

Logging is one way to determine the parameter, otherwise you can use the SDK header file. This has not been published yet, but you can use the P3D737 header file if you have that. The SDK for the MSFS PMDG 737 should be published in the next update. There is a guide in the FAQ section on how yo calculate the Rotor Brake parameter codes: John

I don't see why not, but as you assign these with your SIOC software (and not in FSUIPC) I don't really know. If they are button-type rotary encoders, you should be able assign the buttons to send the appropriate control or preset using those offsets. Not sure how you would do this if they are axis-type encoders though... John

This functionality is available in the latest beta, v7.3.8b, if you would like to try it, available here: John

This has been released in the latest FSUIPC7 beta, v 7.3.8b, available from: John

This sounds like the joystick ids, assigned by windows, have changed. The issues that occur when this happens can be avoided by using the JoyLetters facility (see the User guide for details). Rather than deleting your assignments and starting again, it should be possible to just switch the device' ids back by editing the FSUIPC6.ini. If you would like to try this, please attach your FSUIPC6.ini and FSUIPC6.log files and I will take a look and advise. Otherwise, to delete all your assignments, you can either just delete (or better to just rename) your FSUIPC6.ini and let a new default one be created - you will lose all your assignments to all controllers if you do this, as well as any general settings you have changed. Otherwise, you could open the FSUIPC6.ini file in an editor and manually remove any assignments - they should be relatively easy to identify. John

Good to hear - thanks for the update and the configuration details. It looks like something other than the lvars need updating. I am surprised that there is not a control, standard or custom, that cannot be used for this - hopefully this will be addressed in a future aircraft update. I remember issues with the throttle un the TBM930 but I thought they had been resolved (or maybe that was with using a mod...). I'll check this one (as I have access) next week and let you know. Make sure this change is in the WASM persistent storage area, and not un the FSUIPC_WASM.ini located under the Community\fsuipc-lvar-module folder as that will get overwritten the next time you update FSUIPC7. John

The presets use calculator code, and much of the calculator code uses the custom events, as well as lvars. The custom events/controls for the PMSG 737 in MSFS use the Rotor Brake control, with the parameter indicating the actual control/event. You can see the parameters used by looking at the calculator code for the presets (in the events.txt file, or, better, on the MF HubHob site https://hubhop.mobiflight.com/presets/). PMDG have not published the SDK yet - this should come in the next update, due any day now. I don't know. You need to work out if its not configured properly (i.e. the preset calculator code is not being sent to the FS) or if it is the preset/calculator code that isn't working correctly. For the former, I need to see your FSUIPC7.ini and FSUIPC7.log files, the latter with Event and Extras logging activated, and with Debug logging enabled in the WAPI (add the line LogLevel=Debug to the [WAPI] section of your FSUIPC7.ini file). If its the latter, you need to ask about this on the MF Discord server. Note also that there is an FSUIPC7 beta out with the additional offsets for the PMDG 737 populated (for read-only). See John

If the installer cannot see that file, then this must be due to one of three reasons: 1. Your APPDATA environment variable hasn't ben set correctly. To check this, open a command prompt and enter the command: dir "%APPDATA%\Microsoft Flight Simulator\UserCfg.opt" Can you see the file listed doing this? If not, you need to ensure that your APPDATA environment variable is being set correctly. 2. Anti-virus software is preventing this file from being accessed. Check any messages/warnings in any anti-virus software that you are using and maybe disable while installing. 3. Windows access permissions are preventing the installer from accessing this file. Check the windows permissions. Can you open this file in a text editor? Failure to determine the location of this file results in the WASM module not being installed and the the auto-start component not being enabled. If you cannot determine (and correct) why the installer cannot see this file, both of these components can be installed manually. I can provide further instructions on how to do this if needed. John Later: note also thar this file is only created the first time you run MSFS, so if you tried to install FSUIPC before running MSFS, try again

What does 'No mcro file' mean? Why not? If the list lvars/hvars menu items are available, then so should the items to activate hvars and to execute calculator code. Try setting the WAPI LogLevel to Debug by adding the following (in bold) to your FSUIPC7.ini file: Then check your log file (or, better, open the logging console using Log->Open Console) and you should be able to see what is happening when you try to activate hvars or execute calculator code. John

This should certainly not happen...are you changing this while FSUIPC7 is running? Any changes to the FSUIPC7.ini file should either be made when FSUIPC7 is not running, or if it is running then you should have the axis assignment UI panel open when making these changes, and when the changes saved you should click the 'Reload all assignments' button. If that makes no difference, then you are certainly doing something wrong. Before you assign the throttle, I suggest you try logging the offset/lvar values to make sure they are as expected. You can do this using the Log->Offsets... menu option, entering the offsets A000 and A004 both as type FLT32. I also recommend that you activate logging for Axis Controls. Then move the throttle in the cockpit UI through its full range. You can do thus with the logging console open (Log->Open Console) to view the messages in real-time If you see any throttle axis events logged, you should use those rather than the lvars. If no such events are logged, check that the offset/lvar values are in the expected range. You should also make a note of the values you see for the different throttle positions. As discussed earlier in this thread, it looks as if the relationship between the lvar values and the throttle position is not linear. This implies that you cannot use just one scaling value and get your controller throttle position to match that of the aircraft. To do that, you would need a lua script to receive your axis values (via offsets), apply calibration/scaling based upon that value, and then set the lvar values to this scaled/calibrated value. If you don't want to use lua, then you need to use the axis scaling method (as previously discussed) to get a response that you can use/lice with. You can start with the values previously mentioned, If you have any further questions, please also attach your FSUIPC7.ini as well as your FSUIPC7.log file with the above offset logging enabled. John Later: if using lvars to control the throttle, you should also change the lvar update frequency in the WASM. This defaults to 6Hz, but you should change this to Frame or VisualFrame to get faster updates if using to control an axis. You should set this in a FSUIPC_WASM.ini file in the WASM persistent storage area - see the Advanced User guide for details. Note that this file will not exist in that location by default - copy the one from your Community folder to your WASM persistent storage area and then update it.

Just compress/zip it - it should be fine to attach if you do that. I need to see this file. It is normal for many aircraft in MSFS to continually send certain events, which are different for each aircraft. You can ignore these, or use the DontLogthese ini parameter so that such events are not logged (see the Advanced User guide for details). Note that in your ini you have assignments to an X52 that is no longer available: If you no longer use that controller, you should remove those assignments. John

In FSX/FSUIPC4 the mouse macro facility relies on the coding of the gauges being strictly to FS2004 C++ programming, using the tools originally provided by MS. The facility is a 'hack' into the code. Most gauges just aren't coded to suit. In P3D4 and P3D5 the mouse macro facilities depend on new facilities implemented for us by L-M, and are thereby more consistently applicable. It is therefore probable that mouse macros cannot be used with that aircraft. Try using standard controls where available. If those don't work, try listing available lvars (there is an FSUIPC-added control for this) to see if any of those look applicable for the functions that you want to implement. If you still have problems, maybe create a separate post with the aircraft name in the title and the function you are trying to assign, and other users with this aircraft may be able to assist. Unfortunately, not having this aircraft it is difficult for me to advise. John

Are you sure that it is FSUIPC7 that is crashing, and not MSFS? Was MSFS still running? If so, what happens when you restart FSUIPC7 - does it connect and function correctly? Also, check for MSFS crash reports before the FSUIPC7 one that you posted. Usually this FSUIPC7 error is reported (it is an error, not a crash!) as it is MSFS that has crashed and then this error is generated in FSUIPC due to the simconnect connection no longer being available. The log you posted indicates that FSUIPC7 exited as MSFS was no longer running: If it is MSFS that is crashing, you should check the Asobo as well as the PMDG forums, and maybe report the crash to Asobo. Note also if using the PMDG 737 for MSFS, you can try with the latest FSUIPC7 beta version with the PMDG offsets available (if you use those) - see this post: John

Hi Tom, I will check the updates on my windows 10 system the next time I fire it up, but I am pretty sure that is on the latest updates as of a few days ago, and I have not experienced any issues. And if there was an issue with the latest updates, I would have expected this to be reported by many other users... I have just checked and updated to KB5015807 and everything is still working as expected. Are you still having issues? Please update to the latest FSUIPC version, v7.3.7, and let me know if it starts or not. If not, if an FSUIPC7.log file is created, please attach that. Also check the Windows Event viewer to see if there are any errors or crash reports there, and if so please paste the details. John

This is very strange - if it is trying to update an FSUIPC4.ini file, then that implies it is for FSX, not P3D... Ok. You should change the aircraft names in your profiles to use a substring match, so that all variants are matched. To do this, change: to That will then match all aircraft whose title/name contains "Sim-Avionics". I can't help with the PilotEdge client, but to prevent problems when your joystick ids change (which can happen), you should switch to using the JoyLetters facility. See the User guide for details, but the easiest way to activate is to just change: to If you do this when FSUIPC6 is not running, and then start FSUIPC/P3d, a mapping of letters to joystick ids will be added, and your assignments will be switched to using the letters/characters rather than the using the ids directly. This will prevent issues if/when they change. John

No, but I don't use the MSFS beta's, and I don't support FSUIPC if/when using the MSFS beta updates. If anything breaks with a beta update, you should report to Asobo on the beta forum. If the problem persists once officially released, I will investigate then. John

I am not sure how the throttle works on this aircraft as I do not have it, but if there are issues when assigning direct to FSUIPC calibration, try switching to using 'Send to FS as normal axis' instead. Also check which throttle control you need to use - you can do this by activating Axis control logging and moving the throttle in the cockpit UI yo see what control is logged - maybe it is using the THROTTLE1 AXIS SET EX1 control, which I have seen with other users with this aircraft, so you could try that. There are also several presets available for the throttle on the Hawk: HT1_FWD_LEFT_ThrottleTransmit_Press HT1_FWD_LEFT_ThrottleTransmit_Release HT1_FWD_LEFT_ThrottleRelight_Press HT1_FWD_LEFT_ThrottleRelight_Release HT1_FWD_THROTTLE_Idle_Stop_Toggle I am not sure what these are supposed to do, but maybe they also need to be used? Maybe some other users of this aircraft can help? @Shorty01 has indicated that he has this aircraft configured with FSUIPC, and so may know how to assign the throttle with this aircraft... John

This indicates that, when selecting to install the "add-on.xml" component, there is an issue writing to your Documents\Prepar3D v5 Add-ons folder. The documents for FSUIPC6 should be installed under a Documents\FSUIPC6 - do you have them installed there? John

The log files you attached stop after 3 seconds... can you run MSFS with FSUIPC7, select an aircraft and get ready-to-fly, then check the WASM menu options. If they are not available, exit FSUIPC7 and then attach your FSUIPC7.log and FSUIPC7.ini files. Thanks, John

Where are you trying to install FSUIPC6? Check that you are not trying to install into a windows protected folder. Also, check your VC++ redistributables are up-to-date. If you get the same issue, try installing again without selecting the 'add-on.xml' component.

Of course - that is the whole point of this topic...and it is available/downloadable from the first post in this topic. John

These are known as Add-on Custom Events - see the Advanced User guide, page 38. To use them, create an event file in your FSUIPC7 installation folder, e.g. PilotEdge.evt, and add the following content: [Events] 0=PILOTEDGE.PTT_ON 1=PILOTEDGE.PTT_RELEASE then restart FSUIPC7, and you should see and be able to assign to those events as you would any other FS events. John