• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

P3D v5 Moving Throttle Slider also triggers AXIS_ELEVATOR_AXIS event?

C

cptalpdeniz

Messages
31
Country
ca-britishcolumbia
I have an event handling code for AXIS_THROTTLE_SET however whenever I move the throttle slider on joystick AXIS_ELEVATOR_SET is triggered as well. I've put a trace point and the AXIS_ELEVATOR_SET is triggered with the dwData representing the throttle position? I don't understand when there is 0 input to the elevator axis (confirmed by Windows gamepad controllers too) that P3D is triggering elevator set event. What am I missing here?
 
I tested this in a different machine with a different joystick and once again moving the slider on the joystick triggered AXIS_ELEVATOR_SET. I don't understand why this would be the case?
 
The answer is probably late, but I had the same problems while programming PM777X flight control axes for SimConnect (cross coupling between axes).
For me the issue was that I did not delete all controller axes in the Prepar3D options menu, which was obviously not related to SimConnect coding issues or bugs.
It took me a while to figure out the source of this weird behaviour. Prepar3D control settings in the Options are sometimes hard to kill... :)
 
You must log in or register to reply here.
Back
Top