I have 2 trim issues.

First, no matter what I do, the control interface in the game will not recognize my joystick when I try to use the game to recognize the roll command axis of X. I have to manually add it to the axis. The pitch works fine.

Second, while the pitch on the plane is fine, the roll is all screwed up. It starts off with the plane just rolling and rolling and I have to pull the joystick way over to keep it straight.

You neglected to mention your flight stick type?

Regards your roll problem. Could it be that you need to go into "axis tune" and invert the axis?

Also in the "config" folder there is a file called "producer.cfg" open it with Notepad++ and set-

ForceFeedbackEnabled = false;

Have you checked your flightstick is recognised and calibrated in the Windows>controlpanel>gamecontrollers?

1. I have all CH equipment including the joystick.

2. I will check your two suggestions tonight.

3. I believe forcefeed is already false but will check tonight.

4 I have no problems with the joystick in any other game and all calibration of CH Products is supposed to be done only with the CH manager but I will check the windows applet to make sure the joystick at least appears there.

5. Strange that the pitch axis is recognized but not the roll axis.

Is the CH Products stick, by chance, mapped to a different DirectX device? For example I have the CH Products MFD and I mapped half the buttons to DirectX device 1 and the other half to DirectX device 2. Is it possible that pitch is mapped to DirectX device 1 X axis and roll is mapped to DirecvtX device 2 Y axis? That would be the most obvious way for the in-game axis mapper to not identify the roll axis when you moved it.

Another question, how many columns do you see in the in-game axis mapper? What are they called? This may help point out the problem.

Fridge

I will get back to you on your questions tonight. I am using a profile that Rugbutt made and posted on the CH forum site so I will have to see what he did. I have a second profile that I will try tonight and see if the same thing happens to the roll axis.

SOB. It appears the problem was the forcefeed command. I cannot believe it was that simple to fix.
thanks to everyone for the help.