John Dowson

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

Ah, ok. I can add them - there are already those hvars but with '_1' and '_2' appended.

Note that 7.3.9i has now been released, hopefully fixing the axis calibration issues. No change in the WAPI/WAPID though, so PilotsDeck 0.7.3 should still be fine, but I recommend updating to this latest release. I will publish this as the official 7.3.9 tomorrow (probably....!). John

Yes - they added to the Nosewheel steering event internally and have not exposed this via SimConnect yet as far as I know, but I will check this. The Steering Set was working for some aircraft (the last time I checked), but not all - probably not for the ones that have switched to the new nosewheel event. Anyway, I will check this but probably not until I have released 7.3.9 as I need to get that out asap really. Do you have reversers working? Later: it may be possible to use a preset for the Nosewheel steering axis and assign to that, if I know what the event is actually called...I may look into this in the next few days...

Yep. there is not really much use of the *.hvar files any more unless you want to use them in macros. They are helpful to see what hvars are available though - but then you need this file provided so someone has to create this file in the first place. Note also that you can call presets from lua using ipc.writeSTR to offset 0x7C50. I am planning to add an ipc.preset or ipc.executePreset lua function to make this easier. Cheers, John

Two things: 1. Lvar and hvar handling is broken in the current released version 7.3.8 since SU10. You need to update to the latest beta release 7.3.9i, available from 2. Hvars are only known to FSUIPC if you have provided them in a *.hvar file, named accordingly so loaded with the aircraft. This is described in the WASM section of the Advanced User guide. Please review section. Only a few such files are provided by FSUIPC out-of-the-box, and I generate these quite some time ago and so are probably not up to date (i.e. may not contain all known hvars). However, there is no problem activating hvars or setting lvars using calculator code, and doing so by-passes the need for FSUIPC7 to know about them. If you want to use a *.hvar file though, if you create a new one or update any existing one, if you could share that with me I can add it to the installer so that it can be used by others. Regards, John

There have been a lot of posts on this subject...with the 7.3.9i release I hope most of these issues are fixed. As far as I am aware, I still need to check the following: - reversers in the PMDG 737 - Steering Set and Nosewheel Steering If I have missed anything that needs to be checked, please let me know - but AFTER you have tested with 7.3.9i please, and, as always, please specify aircraft being used and attach your FSUIPC7.ini and FSUIPC7.log files. Thank you all for your patience with this matter, John

I have re-checked this and get the same: I therefore don't see how these events can be used except through MSFS assignments at the moment. I will report this to Asobo. John

Could you all try the attached version please, 7.3.9i. In this version, I have prevented any axis assigned to 'send to FS as normal axis' being diverted to FSUIPC's calibration facilities. Any issues, please supply a brief description of the issue,, specify the aircraft or aircrafts that you are using that give the issue, and attach both your FSUIPC7.ini and FSUIPC7.log files. I would like to release an official version today, although I doubt I will have time to completely update the documentation... John FSUIPC7.exe NB. Full installer from the Announcements page also updated, but the only change is the FSUIPC7.exe posted here.

Yes, of course it is....that is what this whole thread is about!

Sorry, but what does this mean? If you mean that assigning using 'send to FS as normal axis' without calibrating is working, but when you calibrate it isn't, then that is the known issue - you cannot currently calibrate any axis if NOT assigned using 'send direct to FSUIPC calibration. Otherwise, can you please supply more details and also attach your FSUIPC7.ini and FSUIPC7.log files. John

Toe brakes are working here with AXIS_LEFT_BRAKE_SET and for other people: AXIS_LEFT_BRAKE_LINEAR_SET is not available via simconnect (and so FSUIPC) as far as I am aware - I tried adding this but get a NAME URECOGNIZED response with this, so it was removed. How are you assigning to that event?

I know that I should have tested FSUIPC during the beta period, but unfortunately it was/is just not possible at the moment. I have to support the current released version of MSFS, that is the priority. I also support FSUIPC for FSX, P3Dv4 & P3Dv5 (as well as any P3Dv5 betas available, although I cannot obviously discuss this or even confirm if there is one or not). And I also support the various other free utilities and drivers that I provide. Support, especially for MSFS. is taking up 90% of my time and is leaving little time for development, let alone anything else I have just not had the time to set-up a dual system where I can investigate the beta as well as provide support for the released version, as there are various tricks/hacks you have to perform to be able to run both systems on the same PC. And I currently just don't have the disk space to run multiple copies of MSFS. This is certainly something that I am planning to do, but I just need the time to look into this and re-organise my hard disks or purchase new ones. I will certainly be doing this once the SU10 issues have been resolved. John

@Cloud8.5 You have you mixture1 axis assigned to 'send to FS as normal control' but have calibrated: Mixture1=-10130,8192,8192,16247/32 Remove that line. I don't know why the throttle assignment is giving errors - can you try in another/default aircraft. No! That has fixed some issues, but not all - I am still working on it. However, I don't think I can do much at the moment except report these issues to Asobo and remove al calibration except when sending direct to FSUIPC calbration. Anyway, I will update and release a new beta at some point.... @Chad P You were sort-of using profiles but not correctly, which is responsible for some of your issues (i.e. axes disappearing). If you need a lua script started just for one aircraft, then you need a profile for that aircraft. I will check this. No. This was due to your dodgy ini. Please post your latest ini and I will correct it for you. @tango3000Did you remove any calibration for axes assigned with 'send to FS as normal axis'? If not, do that and try again, otherwise please show me/attach your FSUIPC7.ini and FSUIPC7.log files. @Agniparvata But you said these are now working... This is related to how FSUIPC can calibrate events received from the sim using event masking which seems to have broken in the SU10 update. I guess the other 3-rf party add-ins don't do this, and calibrate before sending to the sim, as FSUIPC does using the 'send direct to FSUIPC calibration', which IS still working. I will reply to your other points in a separate comment.... John