New System w/x56 Rhino HOTAS problem..

[Malakie]

Hi,

 

Just built a new system:

 

i9-9900k w/liquid cooling - set at base 3600mhz, autoclock to 5.0 mhz per Intel Spec

ASRock Gaming 9 mainboard

48 gb 3000mhz ram

RTX 2070 Video w/liquid cooling

2 x Crucial 2 tb SSD

2 x Samsung 970 EVO 500 gb m.2 SSD

1 x Intel Optane 32 gb m.2 Cache

Logitech G-19 Keyboard

Logitech G502 Mouse

Logitech x56 Rhino HOTAS (no pedals at this time)

Tobii 4c Eye and Head tracker

Asus Strix RAID DLX 7.1 Surround

Onkyo 7.1 Surround Amp/Speakers

Window 10 Home

 

 

I just today installed the full DCS clean with all the modules.. Pain in the butt with all the license keys from older modules! LOL

 

Anyhow, game runs fine but I am having two problems:

 

1) My x56 Rhino HOTAS will not map correctly. Basically the game is recognizing it, separated columns for stick and throttle.. but when i try to map the throttle to Z of the throttle, it makes it stick X instead. In fact when I try to map anything to the throttle, the output is is a stick map instead.

 

For example, I push throttle forward, the things maps to the X axis of the joystick. pull throttle back, the roll axis of the joystick.. Something really messed up here.

 

And how do I turn on the Tobii 4c in game? I see the stuff for Track IR and the Tobii does support DCS but I see no place to actually turn it on in game.

 

Suggestions?

[Sandman1330]

One thing I have noticed is that stick is not necessarily the first column in the DCS control setup. In fact, the order of mine from left to right is throttle, pedals then stick.

 

As the column titles usually cut off the full name of the controller, mouse over the heading to get the full name and verify that you are trying to bind the correct controller. Remember to click the cell in the correct column when you are binding the axis. It sounds to me like the columns are reversed.

[Malakie]

One thing I have noticed is that stick is not necessarily the first column in the DCS control setup. In fact, the order of mine from left to right is throttle, pedals then stick.

 

As the column titles usually cut off the full name of the controller, mouse over the heading to get the full name and verify that you are trying to bind the correct controller. Remember to click the cell in the correct column when you are binding the axis. It sounds to me like the columns are reversed.

 

Nope not reversed and not the issue.. Something definitely messed up though.. The game is reading my hotas throttle like it is a stick.

[Sandman1330]

Super weird. Sorry, got nothing to suggest :dunno:

[crab]

Sounds like drivers may be a factor. If you've already been there remember you need to remove all the default axes in DCS and put them back in manually because they're sure to be screwed up at default.

[72westy]

Just had a the same issue when setting up in P3Dv3.

 

 

I had to be sure and remove the setting/s (default) for axis within the sims control settings. Once done, I had to be sure to bind throttle settings to the throttle and not the stick. There is a tab above to choose stick vs throttle.

Edited January 10, 2019 by 72westy

[Malakie]

Well tried again today to resolve this.. no go.. The game sees the throttle but maps it at primary joystick X instead of the throttle.. Thus in game, using the throttle sends the plane into a spin.

 

If I manually map it or let the game map it, it does not matter.. I cannot get the x56 Rhino to map the throttle... My x52Pro does not have this issue.

 

I thought maybe the Tobii 4c was somehow interfering.. nope not the problem.

 

Just don't get what the issue is and why the game is not seeing the stick separate from the throttle.. especially since every single other game I have maps just fine.

[Sandman1330]

Have you tried only plugging one in at a time and trying to map it? Unplug the stick and try mapping the throttle?

[72westy]

Be certain to clear the entire row/s under 'throttle & stick' in the input settings with DCS for both the stick and throttle. Then set them accordingly.

[Malakie]

Have you tried only plugging one in at a time and trying to map it? Unplug the stick and try mapping the throttle?

 

Will try that next

[Malakie]

Be certain to clear the entire row/s under 'throttle & stick' in the input settings with DCS for both the stick and throttle. Then set them accordingly.

 

Done did that.. no change.. the game sees the throttle as the joystick for some reason.. or at least that is what it is acting like.

 

BTW, this is a clean new install on a brand new system, i9-9900k, GTX1080ti Poseidon, 48 gb ram, 4 SSD's, Windows 10 Home

[crab]

Don't let the game map any of the axes. In DCS make sure that you are on sim and not game. Delete all the axes, there should not be a single DCS assigned axis remaining. Now light up a free flight mission, at this point your stick and throttle axes should do nothing. Start mapping your axes one at a time and verifying each one before moving on to the next. Make sure you're setting left and right thrust, thrust should not be used.

[LOGIRich]

Crab's beat me to pretty much exactly what I was going to say. The key point to remember is that the throttles on the X56 ARE the X and Y axes. That doesn't matter though. Provided you've correctly assigned the axes then you should be fine - follow Crab's picture as the comparison.

[Malakie]

OK will be trying these other suggestions later today...

[Doomal_dolgo]

19.02.2019 в 20:17, crab сказал:

Не позволяйте игре отображать какие-либо оси. В DCS убедитесь, что вы находитесь в симуляторе, а не в игре. Удалите все оси, не должно оставаться ни одной назначенной оси DCS. Теперь зажгите миссию свободного полета, в этот момент ваша ручка и оси газа не должны ничего делать. Начните наносить на карту свои оси по очереди и проверять каждую, прежде чем переходить к следующей. Убедитесь, что вы устанавливаете левую и правую тягу, тягу использовать нельзя.

Faced the same problem. Can you please tell me how to bind thrust for single-engine aircraft such as F-16, M2000C, etc.

Edited October 2, 2021 by Doomal_dolgo