Allow trigger (or non-keyboard) to advance in Missions rather than just space bar especially for VR

[imacken]

It is so annoying that there is a constant need 'Press Space Bar to continue' in missions. I mean 'space bar' only. In Training Missions, this can be every few seconds, and fumbling around in VR trying to find the space bar so often drives me crazy and is really clunky!

It always seems strange to me that the trigger - normally bound to space bar - doesn't work to advance in these circumstances.

Would it not be possible to allow us to bind this action to something on our HOTAS?

[cfrag]

Any mission designer can do that already. All they need to do is use  X:Start Listen Command instead of X:Start Wait User Response. The issue here is that it may cause the aircraft to actually cause the weapon to fire (or whatever space is bound to), while WaitUserResponse seemingly catches the space bar trigger and prevents the fire weapon (or whatever is bound to it) to be executed. WaitUserResponse is also directly bound to space bar, with StartListenCommand you have to check the modules to look up which command space is bound to.

 

 

Edited March 23, 2021 by cfrag

[imacken]

I take your point about the trigger, so make it definable. In the UI menu?

[cfrag]

7 minutes ago, imacken said:

I take your point about the trigger, so make it definable. In the UI menu?

 

Agreed. IMHO, an optimal solution would be an 'UI Continue' command that is automatically bound to space, and can be intercepted as a separate command

Edited March 23, 2021 by cfrag

[Fri13]

12 minutes ago, cfrag said:

Agreed. IMHO, an optimal solution would be an 'UI Continue' command that is automatically bound to space, and can be intercepted as a separate command

 

That is how it should have been done. But there is a workaround to use some other method to input "Spacebar" like using joystick or voice control software.

I don't have a keyboard anywhere near me while flying, so it is of course a problematic. I would see a binding like trigger or release button to be great correspondance to it, but so that what ever is binded to it, will not work in its default state when tutorial is in waiting of "User Action". So trigger wouldn't fire anything at the moment. 

 

 

 

[Lace]

Agreed, I raised this exact topic a while back, but it’s well worth reiterating. 

[jib]

You could use an external program to bind the trigger to the space bar command but we shouldn't have to.