[No Bug] Cockpit interaction with mouse not possible when Jester Wheel is open

[RafaPolit]

After a few hours just "battling" with the Jester UI in VR and the new paradigm model, I'm warming up to the process.  It's a learning curve.

Still, there are things that are done in "sequence", that are useful:

- Connect Air to Engine
- Move the switch to ON
- Start air flow

The problem, to me, resides in the fact that interacting with the cockpit is not possible while the wheel is open.  So you have to close it, reopen it (luckily it stays within the context of what you were doing), but if you have a "clear" area not selecting anything with the mouse, why is interacting with the cockpit not an option when the wheel is open?  I understand not allowing the mouse to click something in the same spot as a wheel item, but maybe there is a middle ground here?

(This is happening in VR, not sure it's affecting the non-vr gameplay)

Edited May 31, 2024 by HB_Painter
Classification of Bugs and User reports

[trev5150]

Concur. Constant opening and closing of the Jester wheel during preflight is a workflow killer.

[Japo32]

this could be sorted if after the implementation of the action the wheel auto hides.

[Keith Briscoe]

Pretty sure you can start air, then click switch to on. Did that today in VR.

But, I too noticed the no cockpit interaction with jester wheel up, and felt that is not ideal.

[RafaPolit]

Yeah, for that VERY particular example, it works if you do it reversed, but since it's not the "right" way to do it, the notion makes sense (and is probably true for other scenarios, not that just one in particular)

[Czar66]

I binded almost all crew chief and jester actions on the keyboard (the ones that are most used). Recommend.

Connect air on right engine, left engine.
Start airflow.
Disconnect air supply.
Connect and disconnect ground power.
Add and remove chocks.
Radar management actions.
IFF.
...

Edited May 24, 2024 by Czar66

[mytai01]

True, but you just have to close it and interact...

[Nealius]

4 hours ago, Japo32 said:

this could be sorted if after the implementation of the action the wheel auto hides.

This. With some selections it auto-hides, with others it does not. If all selections auto-hid the menu it would be easier to use.

[Kreutzberg]

This may require something to change more fundamentally in DCS, but I agree it would be very useful to be able to click both the Heatblur interfaces (Jester, Bombing Computer, Manual) and the cockpit itself.

[Zabuzard]

This may require something to change more fundamentally in DCS, but I agree it would be very useful to be able to click both the Heatblur interfaces (Jester, Bombing Computer, Manual) and the cockpit itself.

For now, it is the only way for us to enable people to for example use their keyboard to type in something into a search bar without at the same time having DCS deploy your gear, flaps, nosewheel steering, deploy the chute,... all the things you have bound to these keys.

This only applies to UI elements claiming keyboard focus though, such as the manual.

UI like the JesterWheel still allow you to fully click around in the cockpit while it is open. At least, if you don't click on the JesterWheel or the rectangle it's contained in.
Sadly, DCS right now lacks the ability to forward the events if one clicks on a transparent area of the JesterWheel or similiar. I. e. you can't click through it.

[riojax]

2 minutes ago, Zabuzard said:

Sadly, DCS right now lacks the ability to forward the events if one clicks on a transparent area of the JesterWheel or similiar. I. e. you can't click through it.

Is it possible to add an option to use a small and compact squared text only interface with a big offset to right/left ?

[Raven (Elysian Angel)]

2 hours ago, Zabuzard said:

For now, it is the only way for us to enable people to for example use their keyboard to type in something into a search bar

I don't know if it is possible, but a solution might be a tickbox in the Special Options to disable keyboard interaction for those who don't plan on using it (for me for example, head movement just like the old Jester is good enough) just like you can for mouse interaction?
Or is the functionality as it is programmed too intertwined for that?

[MAXsenna]

I don't know if it is possible, but a solution might be a tickbox in the Special Options to disable keyboard interaction for those who don't plan on using it (for me for example, head movement just like the old Jester is good enough) just like you can for mouse interaction?
Or is the functionality as it is programmed too intertwined for that?

Excellent idea!

Sent from my SM-A536B using Tapatalk

[Zabuzard]

I don't know if it is possible, but a solution might be a tickbox in the Special Options to disable keyboard interaction for those who don't plan on using it (for me for example, head movement just like the old Jester is good enough) just like you can for mouse interaction?
Or is the functionality as it is programmed too intertwined for that?

Its not about that. Its when you want to enter a laser code into the menu, enter a name for your waypoint, enter something into the manuals search bar, enter numbers into the bomb calculator, enter "youtube" into the google search on the virtual browser.

you know, normally, when you press 2, you would jump into the wso pit. when you type "how to fly the phantom" you would lower the flaps, engage autopilot, deploy the drag chute and more.

in order to allow you to enter stuff, we have to block any command send to dcs ahen we think its time for keyboard focus on the ui.

keyboard focus is only requested when you have the manual, the bomb calc or the virtual browser open. and in the future it will be refined to only trigger when an input field is in active use.

i wouldnt worry too much about it