John Dowson
-
Posts
13,265 -
Joined
-
Last visited
-
Days Won
271
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by John Dowson
-
-
Hi Keith,
21 minutes ago, Stinger2k3 said:The button is numbered M7 in FSUIPC7 but I cannot find which switch this relates to on my cockpit
Check your FSUIPC7.ini file. The [JoyNames] section should contain a list of your devices with both the JoyID number and letter assigned ('M' will be the letter assigned to the device).
17 minutes ago, Stinger2k3 said:I did a buttons and keys console log but it does not show M7 operating in there ?
Then it wasn't pressed or MSFS wasn't running (or FSUIPC7 not connected). However, if you have button logging active when in the buttons & switches assignment panel, you should see a log message like this:
Quote221000 9220 FirstButtonChange res=00000108 (0.1, 8 )
In that line, the 1 indicates the joystick id, and the 8 the button number.
-
1 minute ago, nantelp said:
If it is well simulated I should see a impact on the power with 100%, according to the manual I should loss about 10% . I will test this on my next flight.
But also test with 50% or 75%. If this is graphics only and not affecting the model, then you should either see no change (i.e. <100% = 0) as we suspect, or (maybe) still see the same as if it was 100%.
-
1 minute ago, nantelp said:
Something I do not understand is, I can use the mouse to pull and push the cab heat. The mouse doesn't use an axis?
That's just the graphics/visuals, not the model. I suspect that the model value would still be 0 (as Thomas says) when the graphics show < 100%.
Do you notice any affect when you have, say, 50% carb heat? And if so, is this any different from 100%? -
It may be possible in an actual Cessna, but as Thomas has stated: MSFS doesn't support for CarbHeat any other than ON or OFF (1 or 0).
To support a carb heat axis or values other than on/off, MSFS need to implement this. You therefore need to raise a new feature request with Asobo/MSFS.
-
Maybe you could also show me your add-on.cfg file, located under <your account>\AppData\Roaming\Lockheed Martin\Prepar3D v5. The P3D auto-discovery should pick-up the FSUIPC add-on.xml file and update this file accordingly.
-
Hi Mario,
ok, glad its working via the dll.xml install method.
Do you have any other add-ons installed? I can only think that there must be some sort of ordering issue during the loading of the dlls.
You could try (temporarily) switching back top the add-on.xml install method (just re-run the installer). If you could activate SimConnect logging, as shown in this post:Then start P3D, and show me the SimConnect log file produced.
Thanks,
John
P.S. Also, when you re-install via add-on.xml method, please choose an installation folder outside of both your Documents folder (especially if using OneDrive) ) and your P3Dv5 installation.
-
Can you also check if you have any ant-virus software running that is maybe preventing the dll from being loaded?
Let me know how it goes when you install using the other (i.e. dll.xml) install method.I don't think activating SimConnect logging would help at the moment.
-
10 hours ago, mario.rosati@mclink.it said:
How can I install not as add-on ?
Its always installed as an add-on. However, there are two install methods - add-on.xml (the default) and via the dll.xml. To use the second method, just re-run the installer and de-select the 'add-on.xml' checkbox when choosing the items to install.
10 hours ago, mario.rosati@mclink.it said:where can I find my P3Dv5 loading logs to show you ?
I'll let you know shortly...
-
2 hours ago, mario.rosati@mclink.it said:
no file with this name is in Prepar3D v5 Add-on/FSUIPC6 folde
Ok, then FSUIPC isn't even starting.
2 hours ago, mario.rosati@mclink.it said:Could it be better to install not as add-on ?
You could try this. But I would like to know why its not loading it via the add-on.xml method. I''ll need to see your P3Dv5 loading logs...I'll get back to you on this.
-
1 hour ago, mario.rosati@mclink.it said:
P3D v5 doesn't work, it freezes immediately (before asking me to accept the add-on)
Do you have an FSUIPC6.log file (in your installation folder: C:\Users\Admin\Documents\Prepar3D v5 Add-ons\FSUIPC6)? If so, can you please show me that.
1 hour ago, mario.rosati@mclink.it said:Do I need to buy a new complete version?
No. Its the same version, you just get a discount as you have already purchased a license for FSUIPC5.
1 hour ago, mario.rosati@mclink.it said:In attache my .log file
That's your installation log which just shows a successful install.
You could also try re-installing the P3Dv5 client - no need to uninstall or re-install FSUIPC6.
John
-
There are no standard offsets for COM3 active/standby, but check the PMDG 777 SDK documentation to see if they hold the information there.
-
Hi David,
5 hours ago, dwbarnett said:I created a Mouse Macro for one of my buttons. It works great, for the initial start. However, it will continue
to press the start button indefinitely. IE the starter won't cutout at 60% engine RPM. I don't have a button off macro, as I believe
the starter button is coded in the sim. Is there a way, that I can still set this up, as a starter button, and still allow the code to cutout the starter at 60%?
I'm not sure about cutout at 60%, but there are a few things you could try before resorting to lua.
Your mouse macro is I guess something like this:
<n>=<name>=RX<id>, 3Where '3' is a mouse left click. You can try duplicating this macro, giving it a unique number and name, the same <id> but using '13' for a mouse left release. You can then assign this new macro to the button release on the same button as the press for the original macro.
This would then send the mouse click release when you release the button. Worth a try. You could also try a both actions (i.e. press and release) in the same macro, but there may be an issue with the timing if this is done, but also worth a try. ,If the 'cutout' is automatic in the sim when you give a single mouse button press/release, then it should work if you do the same via a mouse macro (so maybe just try this first!).There's no point in looking at lua if you don't actually know what to send to tell it to 'cutout'.
Also, check that you haven't set repeat on for the button.
By the way, have you tried logging events to see if any known events (or controls) are used when you start? If so, it may be better to use these instead. Otherwise, maybe the aircraft provides some lvars for this - there is a control (or lua script) you can use to log these.
John
-
13 hours ago, NZFF said:
For FS2020 in particular, does it matter what the joystick sensitivities are set to inside the sim, or will FSUIPC override whatever is in there anyway?
It shouldn't matter what the sim is set to, the values sent by FSUIPC should be used directly.
Some folks have achieved better sensitivity by manually editing the ini to extend the value range of the axis. However, this does mean that the axis can no longer send the full value range, but would also give you more control. To do this, you need to manually edit the ini and change the high/low value. So, for example, this is my elevator calibration setting:
Elevator=-16384,-400,400,16383
So changing to something like
Elevator=-20384,-400,400,20383
Would increase the 'expected' range, and so reduce the sensitivity, especially when using slopes. You could try this technique (with different values) to see if this improves things. -
2 hours ago, SWhite said:
Right now I am parked at OMAN but the log shows OI02 as being nearest but that is 493 km away.
Yes, it seems to return all airports except those that are closest to you!
2 hours ago, SWhite said:I swear though that yesterday, every time I chose a new airfield from the nearest page on the TBM the API returned that airport. I switched it like 5 times by doing that.
It seems Asobo have a bug or two. Who'd have though!
Yes, it seems that the latest release introduced this bug - but the release note stated that this functionality had been fixed! I'll report to Asobo.
-
This functionality is still in FSUIPC7. However, its currently not working now FSUIPC7 is an exe (rather than an embedded DLL). The problem is that FSUIPC7 does not receive a QUIT message, so is not notified when MSFS exits and so cannot initiate a save. I think the lack of a QUIT message has already been reported to Asobo, but I'll check. However, I doubt this will be possible now FSUIPC7 is an exe, as it would mean that MSFS would have to wait for all external clients to exit correctly before closing down.
-
Just checked the list received from MSFS and it seems to contain each airport around 30 times! This is why its finding the same airport 6 times as the closest 6.
Could you try adding the logging I mentioned in the previous post to see if you also get the same airport 6 times - if so, I'll report to Asobo and see if I can add a temporary fix to ignore the duplicates. -
Sounds like an issue with MSFS not updating the GENERAL ENG COMBUSTION variable when the engine is shut down. I'll check this (tomorrow) and raise a zendesk ticket with Asobo if this is the case. I'll let you know.
-
FSUIPC receives a list of all airports in the aircrafts "reality bubble" from MSFS, then calculates the distance of each from the aircraft, and then populates 0x0658 with the nearest 6 airports.
FSUIPC uses the SimConnect function Simconnect_RequestFacilitiesList to get the list of airports. This has recently been stated as being "fixed" in the latest MSFS release (1.9.5.0), however the SDK documentation for this function still lists this as 'bad response' and 'all facilities lists are empty', so I'm still not 100% sure this is fully working yet.
I've just taken a quick look and there seems to be various issues. I am getting plenty of airports through from SimConnect (36974 in total!), but many don't seem quite right (e.g. invalid ICAOs). Also, it seems that FSUIPC7 is only determining the closest one, and then repeating this 6 times in offset 0x0658. To check the full list in that offset, you can go to Log->Custom, and enter x20. You should then see the complete list of the 6 nearest airports (in your log).
Not sure what's going on yet, I'll look into this more tomorrow. But, the offset should contain the 6 closest airfield (as determined by FSUIPC) from the list of airports in the aircrafts reality bubble as received from MSFS.
John
-
Yes, this was added in the September 14th release. However, there are still various issues:
- not all keys are recognised. See the SDK documentation (SimConnect -> Status of Input Events) to see which keys are currently supported
- FSUIPC only receives the numpad keys when numlock is off, rather than when numlock is on. This has been reported to Asobo.
I have also added a new ini parameter UseAlternativeNumpadKeyMapping :
Quote... you can add the following ini parameter to the [General] section of your FSUIPC7.ini:
UseAlternativeNumpadKeyMapping=YesOnce this is added, FSUIPC7 will receive the numpad keys (but only with numlock off due to MSFS bug) via SimConnect, but then send them to itself as the un-numlocked keypad keys.
So, as discussed, using this you would assign to the non-numlocked numpad keys, and when using MSFS you need numlockk off for FSUIPC to react to these keys. They will also work when FSUIPC7 has the focus (with numlock off).
(from
) Of course, you can always activate logging for 'keys & buttons' to see which keys are recognized from MSFS/SimConnect.
-
Hi @pilotjohn
Those last logs are pretty interesting, thanks. Getting closer to the issue...
On 10/11/2020 at 11:19 PM, pilotjohn said:I will now turn on UseAIClient=No.
I wouldn't bother with this now - remove if you have added (although it won't make much difference). Please try the following build, and keep logging of extras active:
Let me know how it goes with that version, and post your FSUIPC7.log again if you get a crash. No need for the SimConnect logs for now.
Thanks,
John
-
5 hours ago, NZFF said:
I have not been able to find a user manual
Yes, I'm currently updatimg the User manuals and they should be ready shortly. For the time being, most of the information in the FSUIPC5/6 manuals is still relevant, so if you are new to FSUIPC you can use these - see
I will be releasing an installer for FSUIPC7 shortly (i.e. next 3-4 days) that will include the documentation (although not all updated).
5 hours ago, NZFF said:so trialed and errored a few different varies to try and increase the flat dead area in the center of the curve. Is this the correct methodology? If not, could someone please point me in the correct direction?
Its best to just try them and see what works for you. Flattening in the centre is usually the way most people prefer.
5 hours ago, NZFF said:Also wondering if I need to start FSUPIC7 every time I use the sim, or if its a set once and forget type software?
Depends on the settings. By default, FSUIPC7 exits with the sim, so you have to restart when you start the sim. To change this, you can turn off the option Exit with FS, and then FSUIPC7 will just sit in the system tray rather than exiting. Of course, the ideal solution is for FSUIPC7 to start automatically with the sim, but this is currently not possible with MSFS.
John
-
@bertranda ok, thanks for the update.
-
No, there are many buttons on the G1000 that are not working and/or currently unassignable. This has already been reported to Asobo.
-
1 hour ago, MartyReynolds said:
The log file has no errors in the values you see. The issue is when the output values go to zero, this means that I have stopped using that yoke and it is now resting in the neutral position within the null zone. Then you start seeing values again, it means that the other yoke has now finally started working and once it does, it works without error. You really can't see anything in this log file unless you could time stamp each value and I moved the yoke not randomly but for a fixed period of time ... then at the moment stopped and switched to the other yoke ... But I think this would only show what I am observing and not be helpful.
But the largest gap in the logged elevator axis values only seems to be around 9 seconds, with most of them being a lot smaller (2-5s):
QuoteModule base=7FFF55B30000
146156 LogOptions changed, now 10000000 00000001
146671 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET
146671 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET
...
146671 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
146687 *** AXIS: Cntrl= 65764 (0x000100e4), Param= -1280 (0xfffffb00) AXIS_RUDDER_SET
155515 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 27 (0x0000001b) AXIS_ELEVATOR_SET
155593 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 773 (0x00000305) AXIS_ELEVATOR_SET
155625 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 1468 (0x000005bc) AXIS_ELEVATOR_SET
...
158781 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
162718 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 1641 (0x00000669) AXIS_ELEVATOR_SET
...
163687 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 667 (0x0000029b) AXIS_ELEVATOR_SET
163734 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
163781 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -1202 (0xfffffb4e) AXIS_ELEVATOR_SET
163843 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -2801 (0xfffff50f) AXIS_ELEVATOR_SET
...
164781 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -766 (0xfffffd02) AXIS_ELEVATOR_SET
164828 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
164875 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 844 (0x0000034c) AXIS_ELEVATOR_SET
164937 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 2351 (0x0000092f) AXIS_ELEVATOR_SET
...
165640 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 358 (0x00000166) AXIS_ELEVATOR_SET
165687 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
165828 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -475 (0xfffffe25) AXIS_ELEVATOR_SET
165875 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -863 (0xfffffca1) AXIS_ELEVATOR_SET
165937 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -1202 (0xfffffb4e) AXIS_ELEVATOR_SET
166093 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -717 (0xfffffd33) AXIS_ELEVATOR_SET
166156 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
169484 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 425 (0x000001a9) AXIS_ELEVATOR_SET
...
170640 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 524 (0x0000020c) AXIS_ELEVATOR_SET
170687 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
170734 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -426 (0xfffffe56) AXIS_ELEVATOR_SET
...
171937 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
171984 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 77 (0x0000004d) AXIS_ELEVATOR_SET
...
173296 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 326 (0x00000146) AXIS_ELEVATOR_SET
173328 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
173484 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -380 (0xfffffe84) AXIS_ELEVATOR_SET
173609 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -754 (0xfffffd0e) AXIS_ELEVATOR_SET
173781 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -192 (0xffffff40) AXIS_ELEVATOR_SET
173875 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
175390 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -912 (0xfffffc70) AXIS_ELEVATOR_SET
...
176421 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -1299 (0xfffffaed) AXIS_ELEVATOR_SET
176484 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
...
177437 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 1774 (0x000006ee) AXIS_ELEVATOR_SET
177500 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
177546 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -717 (0xfffffd33) AXIS_ELEVATOR_SET
...
178734 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -39 (0xffffffd9) AXIS_ELEVATOR_SET
178781 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
180078 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 623 (0x0000026f) AXIS_ELEVATOR_SET
...
181250 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 1766 (0x000006e6) AXIS_ELEVATOR_SET
181296 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
181343 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -754 (0xfffffd0e) AXIS_ELEVATOR_SET
...
182234 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -426 (0xfffffe56) AXIS_ELEVATOR_SET
182281 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 276 (0x00000114) AXIS_ELEVATOR_SET
...
183234 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 823 (0x00000337) AXIS_ELEVATOR_SET
183281 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
183437 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -4 (0xfffffffc) AXIS_ELEVATOR_SET
183625 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
188203 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 358 (0x00000166) AXIS_ELEVATOR_SET
188234 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 1332 (0x00000534) AXIS_ELEVATOR_SET
...
189343 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 181 (0x000000b5) AXIS_ELEVATOR_SET
189406 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
189437 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -1299 (0xfffffaed) AXIS_ELEVATOR_SET
...
190625 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -669 (0xfffffd63) AXIS_ELEVATOR_SET
190687 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
198015 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -239 (0xffffff11) AXIS_ELEVATOR_SET
198031 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -1317 (0xfffffadb) AXIS_ELEVATOR_SET
...
199343 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -4 (0xfffffffc) AXIS_ELEVATOR_SET
199390 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 77 (0x0000004d) AXIS_ELEVATOR_SET
...
200437 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 1815 (0x00000717) AXIS_ELEVATOR_SET
200484 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
200562 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -567 (0xfffffdc9) AXIS_ELEVATOR_SET
200609 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -2675 (0xfffff58d) AXIS_ELEVATOR_SET
...
201843 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -1129 (0xfffffb97) AXIS_ELEVATOR_SET
201890 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
202000 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 971 (0x000003cb) AXIS_ELEVATOR_SET
202046 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 1666 (0x00000682) AXIS_ELEVATOR_SET
202250 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 1170 (0x00000492) AXIS_ELEVATOR_SET
202296 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 722 (0x000002d2) AXIS_ELEVATOR_SET
202343 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 227 (0x000000e3) AXIS_ELEVATOR_SET
202390 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
207484 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -379 (0xfffffe85) AXIS_ELEVATOR_SET
207531 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -1736 (0xfffff938) AXIS_ELEVATOR_SET
...
208750 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -2074 (0xfffff7e6) AXIS_ELEVATOR_SET
208796 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
208843 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 1021 (0x000003fd) AXIS_ELEVATOR_SET
208890 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 2926 (0x00000b6e) AXIS_ELEVATOR_SET
...
210078 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 933 (0x000003a5) AXIS_ELEVATOR_SET
210125 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
210187 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -669 (0xfffffd63) AXIS_ELEVATOR_SET
210234 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -1977 (0xfffff847) AXIS_ELEVATOR_SET
210281 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -2947 (0xfffff47d) AXIS_ELEVATOR_SET
210328 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3383 (0xfffff2c9) AXIS_ELEVATOR_SET
210375 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -2850 (0xfffff4de) AXIS_ELEVATOR_SET
210437 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -1347 (0xfffffabd) AXIS_ELEVATOR_SET
210484 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
210531 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 136 (0x00000088) AXIS_ELEVATOR_SET
210578 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 1110 (0x00000456) AXIS_ELEVATOR_SET
210687 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 712 (0x000002c8) AXIS_ELEVATOR_SET
210734 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
210828 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -379 (0xfffffe85) AXIS_ELEVATOR_SET
210875 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -766 (0xfffffd02) AXIS_ELEVATOR_SET
210968 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -184 (0xffffff48) AXIS_ELEVATOR_SET
211015 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
Mystery button press
in FSUIPC7 MSFS
Posted
Note also that you can use the IgnoreThese ini parameter (in the [Buttons] section) if its causing issues: