John Dowson

I am asking you NOT to create a new log - just don't use the 'New Log' menu entry, and just one log file will be created. The 'New Log' button closes the existing log file and starts a new one. As it says in the User guide: I have just release 7.3.10 - please update., This fixes an issue where presets assigned in the general Buttons and Axes sections were lost, as the preset file was loaded after these assignments, resulting in them not being found. John

FYI, 7.3.10 has also now been released, This contains a minor update that prevents general button/axes assignments to presets being lost. John

FYI, 7.3.10 has also now been released that should resolve this issue. John

FYI, 7.3.10 has also now been released, This contains a minor update that prevents general button/axes assignments to presets being lost, which looks like the issue you were experiencing. Please update to this version. John

FYI, 7.3.10 has also now been released, This contains a minor update that prevents general button/axes assignments to presets being lost. John

7.3.10 has now been released. John

Please try the attached - I am going to release this shortly. John FSUIPC7.exe

Please try the attached - I am going to release this shortly. John FSUIPC7.exe

It looks like the assignments are now loading before the presets have been loaded, resulting in presets to the general buttons being lost. I will fix this asap.... Sorry about this - I will post an update soon... John

It looks like the assignments are now loading before the presets have been loaded, resulting in presets to the general buttons being lost. I will fix this asap.... Sorry about this - I will post an update soon... John

The log file you posted is useless to me as it is a continuation log - I always need to see a full log file, not a continuation one, so please never use the New Log function when posting logs for support issues. The latest and only supported version is 7.3.9, so please update and try again. You should always check that you are using the latest version before requesting support, as only the latest version (+ any betas) is ever supported. John

ok, thanks for the update. That is interesting, not heard of that. I have always used Everything for searching. Cheers, John

If you have set FSUIPC7 to be ran as Administrator, then MSFS must also be ran as administrator. I am not sure that setting the MSFS desktop icon to be ran as administrator will do this...if using Steam, for example, it is the Steam app that starts MSFS and the Steam app must be set to be ran as administrator. If using an MS Store install, you will need to find out how to run MSFS as admin with that installation type. If you are running both MSFS and FSUIPC7 as admin then something else must be going on. Please see the following FAQ entry for MSFS auto-start issues: You could first try running both MSFS and FSUIPC7 without admin privileges, to check that auto-start us configured correctly, If not, that post should help you correct that. Once it is working with non-admin privileges, try setting both FSUIPC7 and MSFS to both run as admin and try again. If you have an MS Store version of MSFS. if you can let me know how you start MSFS as admin then I can also add these details to that FAQ entry. John

You should not manually edit the ini and copy other peoples entries if you do nor fully understand what you are doing! First, make sure that you are using the latest release, 7.3.9, and if not please update. You can assign to the preset PMDG_B737-7_HGS_HUD_UP_DOWN_SWITCH as that exists in the events.txt file (provided by MobiFlight - see https://hubhop.mobiflight.com/presets/ for a list and search interface for presets). The other two presets that you tried to manually add, PMDG_PED_HGS_down and PMDG_PED_HGS_up, do not exist. You need to define them in a myevents.txt file before you can use them. You will need to add them to this file as: PMDG_PED_HGS_down#<x> (>K:ROTOR_BRAKE) PMDG_PED_HGS_up#<y> (>K:ROTOR_BRAKE) replacing <x> and <y> with the correct parameters for the Rotor Brake control that you see logged (one will be 97904 I guess, don't know about the other). Or ask the person that supplied them for the definitions of these presets and add them. They should really be submitted to MobiFlight for addition and be shared with the community. I suggest you read the section on presets in the Advanced User guide in the WASM section (in fact, better to read the entire WASM section!). Any further issues, please attach your FSUIPC7.log and FSUIPC7.ini files, not pictures. John

You are using an old and unsupported version of FSUIPC7 - 7.3.3. The latest and only supported version is 7.3.9 - please update. If you still have issues, repost your files but please make sure that you have quite/exited FSUIPC7 before attaching them. John

That is very strange - this would normally indicate that the presets could not be loaded, but the log you posted, truncated as it was, still showed that presets had been loaded: Do you have presets available? Can you show me a full FSUIPC7.log file please as the last one ended after 31 seconds - make sure you have exited FSUIPC7 before attachung the log file.

Yes - all your custom controls have disappeared: I don't know how that could have happened...probably FSUIPC7 was started with no access to the presets file (events.txt) and so re-wrote your ini with 0 controls. Strange - I will take a look to see if I can prevent this. Yes - just rename the FSUIPC7old.ini as FSUIPC7.ini and drop that into your installation folder. I released 7.3.9 this morning so you should also update to that. Sorry for the delay...missed this posts yesterday somehow... Regards, John

FSUIPC7 7.3.9 has now been released, so please make sure you are using this version before posting again with any issues. Note that with this version you no longer have to remove any calibration when assigning to Send to FS as normal axis as any calibration for such assignments will be ignored. John

Sounds like it - your log file shows that event being sent. Try activating logging for Events, open the logging console window and switch the pumps in the virtual cockpit and see what is logged - if any event is logged, you can use that. If nothing is logged, you could try using lvars - list them to see what is available. If any look applicable, you could try using those. Note that if you do find another method of controlling the fuel pumps, you would have to create a specific profile for this aircraft. To do this, manually remove the aircraft from the profile in the FSUIPC7.ini, then the next time you start MSFS/FSUIPC7 you can add the aircraft back to a new profile selecting 'new based on...' and then select its old profile. This will give you a new profile for that aircraft which will be a copy of the existing one, which you can then modify. Note that here are quite a few issues with 7.3.8 since the release of SU10. I will be releasing 7.3.9 later today (hopefully!), and there is a beta currently available, 7.3.9i, over in the Announcements sub-forum. John

👍

Not always....'send to FS as normal axis' and calibrating (now not possible!) can sometimes not play well with some advanced aircraft that also intercept the axes events, due to priority levels. In such cases, we used to recommend either removing the calibration or assigning direct to FSUIPC calibration. But you said that sync pos was working for you, so I wouldn't worry about it.

When using 'Send direct to FSUIPC Calibration' the axis controls are calibrated before sending to the sim. When you use 'Send to FS as normal axis' the event is sent to the FS and then is received from the FS. If calibrated, the event is masked (i.e. blocked from being applied in the sim), calibration is applied and the newly calibrated value sent back to the sim. What seems to be broken in SU10 is the masking on the event that allows this to be done, although the error reported is rather strange.... I have removed this capability in the latest beta - events received back from the sim will no longer be calibrated but allowed to pass through - but are still received for logging as well as for many other purposes. Regards, John

Ok, but you should update when released as that will be the only supported version. John

Understood. If you could provide the different files, I can add them in the next release. Otherwise I can look at this after the next release. Thanks, John

No problem, but I am surprised it works with 7.2.8 after the SU10 update! There have been quite a few issues with the SU10 update, but hopefully most are now resolved. The latest beta for SU10, 7.3.9i, is available from: I am planning on releasing this tomorrow - still a few minor non-functional updates I need to make, as well as updating the documentation, but other than that that will be the next release if you would like to try. John