Pilot Joystick vs RIO Radar stick. (Can they be one and the same)?

A question for anyone at Heatblur, really appreciate it if you could answer this one! (I know you guys are in crunch time now, so I won't hold it against you if you don't)

When changing between seats (in multicrew or even singleplayer) will we be able to use the same controller to control the flight stick, as well as the RIO stick, or will they have to be two seperate

independent controllers?

I.E. Can we double bind our joystick and it's buttons for use in the front as well as in the back seat?

You can always program your X-52 outside the game in the tool that comes with your flightstick. There are 3 different modes on it that allow you to program each button with 3 different commands. So you can program it with the commands you need for the pilot in mode 1 and for the RIO in mode 2 l. Then you can just switch between them when you need.

@Timberwolf The answer to the question should come from the developer ;)

If not I marry with Saitek and everything is fine :smilewink:

@Timberwolf The answer to the question should come from the developer ;)

If not I marry with Saitek and everything is fine :smilewink:

Just thought i give him a workaround if Heatblure does not have time to answer or if the answer isn’t what he hopes :)

The pilot and the RIO have separate input entries, so it is possible (and default BTW) to have your X and Y axes assigned to the RIO's Hand Control Unit (HCU).

The same applies to any key, button or axis - you can assign a function for the pilot and another function for the RIO.

The pilot and the RIO have separate input entries, so it is possible (and default BTW) to have your X and Y axes assigned to the RIO's Hand Control Unit (HCU).

 

The same applies to any key, button or axis - you can assign a function for the pilot and another function for the RIO.

Awesome. Thanks for the reply! :thumbup:

The pilot and the RIO have separate input entries, so it is possible (and default BTW) to have your X and Y axes assigned to the RIO's Hand Control Unit (HCU).

 

The same applies to any key, button or axis - you can assign a function for the pilot and another function for the RIO.

I presume the potential input axis and commands are finalized by now. Any chance of releasing these mappings before the module itself?

I'm sorry, but it's the opposite: they are still being tuned and added, and probably they will be tuned until the very last minute.

I'm sorry, but it's the opposite: they are still being tuned and added, and probably they will be tuned until the very last minute.

Just to be clear, I didn't mean the actual keyboard assignments, but the list of all available commands and axis mappings (i.e. the first row on the left side in the controls screen).

What I wrote applies to both the commands and the mapping - they are still being adjusted, and we won't be able to publish that before the release.

The pilot and the RIO have separate input entries, so it is possible (and default BTW) to have your X and Y axes assigned to the RIO's Hand Control Unit (HCU).

 

The same applies to any key, button or axis - you can assign a function for the pilot and another function for the RIO.

So, pilot's stick won't be available when switching to RIO position or they will be synchronized with RIO stick?

So, pilot's stick won't be available when switching to RIO position or they will be synchronized with RIO stick?

I don't think it'll be available - you can't fly from the back seat, they've said a rudimentary AI will take over when you jump in the back seat if you're in SP.

I don't think it'll be available - you can't fly from the back seat, they've said a rudimentary AI will take over when you jump in the back seat if you're in SP.

Oh, completely forgot that, thank you.