Correct way to assign AXES in MFS2020?

[ricky74]

Hi to all,

I'm having a bit of trouble assigning the AXES to the simulator.

Let me explain: I assign them as I always did in FS9/FSX/P3D:

1) in FSUIPC scan one by one and assign the correct AXIS: Aileron, Elevator, Rudder and Throttle and the Send direct to FSUIPC calibration

2) Calibrate all axes in Joystick calibration

2) delete in MFS--> Control Options --> all 4 axes

But I notice that once I pause MFS2020 with the ESC key or when I press the Windows Key to pick up another app and then return into the cockpit, the plane no longer responds to commands axes. In this specific case I'm using Fenix A320 but think that the situation doesn't change with other aircraft.

Seem like FSUIPC loses focus, so I have to go into FSUIPC, do a RESCAN (FSUIPC recognize the previusly assigned AXES), and then everything starts working again.

Am I doing something wrong?

[John Dowson]

1 hour ago, ricky74 said:

But I notice that once I pause MFS2020 with the ESC key or when I press the Windows Key to pick up another app and then return into the cockpit, the plane no longer responds to commands axes. In this specific case I'm using Fenix A320 but think that the situation doesn't change with other aircraft.

Seem like FSUIPC loses focus, so I have to go into FSUIPC, do a RESCAN (FSUIPC recognize the previusly assigned AXES), and then everything starts working again.

This certainly shouldn't happen and haven't seen this ... but I will check this here. Can you please check with another aircraft to see if this is specific to the Fenix. I don't have this aircraft so cannot test with that here.

John

[ricky74]

Yes, John, I'll try and report back.

[John Dowson]

I have checked this in several default aircraft and also the PMDG 737 & 777, and the FBW A320 and cannot reproduce. It therefore looks to be either specific to the Fenix or your system.
Let me know if this applies to any other aircraft or is specific to the Fenix.

[ricky74]

Hi John, yesterday I reconfigured all axes from scratch (and deleted those in MFS2020 control option) and try serveral times ESC button and now seems to works perfectly. Maybe was my mistake.

Just to know: when I launch MFS2020 have I to start every time from "FSUIPC icon" if I want that FSUIPC module is loaded or can I start from the usual icon? In the previuos version of FSX/P3D there wasn't this difference, FSUIPC module was loaded directly.

Many thanks again

[John Dowson]

1 hour ago, ricky74 said:

yesterday I reconfigured all axes from scratch (and deleted those in MFS2020 control option) and try serveral times ESC button and now seems to works perfectly. Maybe was my mistake.

Ok, but strange - I don't know what could have caused this.

1 hour ago, ricky74 said:

Just to know: when I launch MFS2020 have I to start every time from "FSUIPC icon" if I want that FSUIPC module is loaded or can I start from the usual icon? In the previuos version of FSX/P3D there wasn't this difference, FSUIPC module was loaded directly.

There are two auto-start components included in the installer, via the EXE.xml file (the default) and via using the MSFS.bat file. You should first try with the default method. When using this, FSUIPC7 should be auto-started however you start MSFS. If you use the MSFs.bat method of auto-start, you must use the MSFS desktop icon installed by the FSUIPC7 installer to start both MSFS and FSUIPC7.

Please see the following FAQ entry for all auto-start issues. Usually, if the EXE.xml auto-start method isn't working, its because another add-on has corrupted the EXE.xml file.

John