Unable to use WASD keys in CTRL+F11 camera view

[tygra09]

Hi! After using the mod, some commands on the keyboard in the game are blocked. For example, if after using the mod to open the flight on the drone (Ctrl+F11), it is impossible to control it with the WASD keyboard.

[okopanja]

It's a bit more complicated but I will, try to reproduce the problem. When talking about drone I am not 100% sure what you mean, I gather this is some special view. Do I need to spaw the in-game drones for this. In general SharkPlanner has to interact with keyboard to some degree:

1. CTRL+SHIFT+SPACE is used to toggle the SharkPlanner visibility. This was carefully selected to avoid conflicts with default DCS and module keybindings.
2. Certain keys are blocked when the SharkPlanner is displayed:
   1. SPACE, ENTER, DEL, BACKSPACE are used to support faster keyboard input
   2. ARROW keys are used to navigate the list of waypoints, as well used by some options controls
3. In #111 I tried to fix issue where the SPACE/ENTER/DEL/BACKSPACE were still monitored by SharkPlanner even when hidden. Sadly I did not test, and in #113 I have fixed the issue, but #113 is not part of the last release.

At the moment I am working on 1.6.0 release: https://github.com/okopanja/SharkPlanner/milestone/12

Since it will take some time before 1.6.0 (it brings some improvements and bug fixes), I will consider the possibility of create 1.5.3 to include #113 and fix for #121.

[tygra09]

After I used the program and outlined the points, I transferred them to ABRIS. After that, I hide the scheduler and switch to drone mode (Ctrl+F11), you can control it with the W A S D keys, but they do not work.

@. @.>:

It's a bit more complicated but I will, try to reproduce the problem. When talking about drone I am not 100% sure what you mean, I gather this is some special view. Do I need to spaw the in-game drones for this. In general SharkPlanner has to interact with keyboard to some degree:

• CTRL+SHIFT+SPACE is used to toggle the SharkPlanner visibility. This was carefully selected to avoid conflicts with default DCS and module keybindings.
• Certain keys are blocked when the SharkPlanner is displayed:
• SPACE, ENTER, DEL, BACKSPACE are used to support faster keyboard input
• ARROW keys are used to navigate the list of waypoints, as well used by some options controls
• In #111 I tried to fix issue where the SPACE/ENTER/DEL/BACKSPACE were still monitored by SharkPlanner even when hidden. Sadly I did not test, and in #113 I have fixed the issue, but #113 is not part of the last release. At the moment I am working on 1.6.0 release: https://github.com/okopanja/SharkPlanner/milestone/12 Since it will take some time before 1.6.0 (it brings some improvements and bug fixes), I will consider the possibility of create 1.5.3 to include #113 and fix for #121 . — Reply to this email directly, view it on GitHub , or unsubscribe . You are receiving this because you authored the thread. Message ID: <okopanja/SharkPlanner/issues/122/1962868105 @ github . com>

[okopanja]

OK, it looks like you meant LCTRL+F11 (very cool, I did not know this), which will derive the "drone" view from what ever is visible at that moment. I could not reproduced it with my latest work.

I will have to go outside for the next 3-4 hours. Meanwhile take a look at this (still processing high res) and let me know if this is the drone view you meant:

https://youtu.be/Nh6Sra5yLgI

Also: I need to know exact version you are using, so I can reproduce it better.

[tygra09]

V1.5.2 Yes,  this drone view 

@. @.>:

OK, it looks like you meant LCTRL+F11 (very cool, I did not know this), which will derive the "drone" view from what ever is visible at that moment. I could not reproduced it with my latest work. I will have to go outside for the next 3-4 hours. Meanwhile take a look at this (still processing high res) and let me know if this is the drone view you meant: https://youtu.be/Nh6Sra5yLgI Also: I need to know exact version you are using, so I can reproduce it better. — Reply to this email directly, view it on GitHub , or unsubscribe . You are receiving this because you authored the thread. Message ID: <okopanja/SharkPlanner/issues/122/1962877748 @ github . com>

[okopanja]

I've just tried the with 1.5.2 and could not replicate the issue. The only way I found that WASD will not work is if I switch to LCTRL+F11 and do not hide the sharkplanner. E.g. if I hide it WASD starts working again.

If your issue is not what I just described:

1. attach dcs.log and SharkPlanner.log (try to start DCS fresh)
2. create small video (first send logs so you do not waste effort if it is something we can deduce from logs).

[okopanja]

@tygra09 any news on your side in respect to my last comment? :)

[okopanja]

@tygra09 within #133 I fixed an issue causing the keybindings to be stolen when user click Hide button. Hotkey was not affected by this.

Please confirm if v1.6.1 fixes your issue.

If not my questions from before still stand.

[tygra09]

Hi! in the new version, the Sharkplanner does not open at all in the game, I press CTRL+SHIFT+SPACE and nothing opens

вс, 19 мая 2024 г. в 04:37, okopanja @.***>:

@tygra09 https://github.com/tygra09 within #133 https://github.com/okopanja/SharkPlanner/issues/133 I fixed an issue causing the keybindings to be stolen when user click Hide button. Hotkey was not affected by this.

Please confirm if v1.6.1 fixes your issue.

If not my questions from before still stand.

— Reply to this email directly, view it on GitHub https://github.com/okopanja/SharkPlanner/issues/122#issuecomment-2119009327, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGNW2U2UNJB55CZSKJTUDKLZC7CZXAVCNFSM6AAAAABDYP6TYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJZGAYDSMZSG4 . You are receiving this because you were mentioned.Message ID: @.***>

--

С уважением,

Дмитрий Геннадьевич Михайлусев,

тел.моб. +7 962 084 1777, +7 913 524 6272

[okopanja]

Please add Attach the dcs.log and SharkPlanner.log. I will retest when I get home to confirm if there is issue.

[EccentricxMD]

For me, 1.6.2 ctrl-shift-space didn’t work. Works with 1.6.1