TooManyTims

To try and answer both questions above (from @MAXsenna and @virgo47) I am using modifiers with toggle swithces simply becuase I want as much as practical bound to the Hotas, so I don't have to try and fumble over a keyboards while flying in VR. Ytou quickly run out of buttons on the Hotas with something liek the FA18 or BS3. I realise that using modifers on toggle swithces can create a logical disconnect between by physcial Hotas and the cockpit, but that's a pirce I'm willing to pay. By physical disconnect I mean that if a move the physical switch to say the "on" position then the cockpit switch will move "on" (as it should), but if I then move the physical swtich to the "off" position while holding the modifier, that will/should result in a different cockpit swtich (the one mapped to the modified combination) moving and the original cockpit switch remaining in the "on" position (i.e. no longer logically matched to the physical state of my Hotas) I'm not sure what you mean by "a keybind that resides in the "special for joystick" category" perhaps you coudl elaborate a little I'm am using a momentary press button as the modifier. This modifier is used in conjuction with lots of other buttons, hats etc, but I only seem to have the above issue when used in conjuction with toggle switches. Any help/ideas appreciated!

Is anyone else able to confirm they have the same behaviour? I fly largely in VR and so maximising bindings to HOTAS is key as fumbling for a keyboard mid fight is a poor option.

Fixed for me in a single test with conditions below (conditions that I first experienced the bug) 2.5.8.40170 MT OB mi26 instant action weapons range 2 screens in pirmary screen at 3840 * 2160 GUI scaling at 1.5 Many thanks

Thanks @Rikk, this is indeed the same issue. @Moderators feel free to close this issue as duplicate of below, but please bump the priority to fix too!

Summary: Video shows the problem most clearly. In the video I've demonstrated the problem in the A10 II though I believe I had exactly the same issue in other modules too. Here's my attempt at a short verbal description.... When a toggle switch on the Hotas is bound to two different switches in the cockpit (one with a modifier and one without) the cockpit switch that is not associated with the modifier can be made to move (erronously) when the only input on the Hotas is with the modifier held. Details: SW verison = 2.8.4.39259 Though this problem has been around for quite a while (only just found the time to report it) Warthog switch bindings (as shown in the video) Short video showing modifier not being obeyed for toggle switch movements.mp4

So when I set resolution inside dcs to 1920 x 1080 everything works as it should! The Pet ai traid is cented on my screen and when I command a search he searches directly where I designate. Whne I swithc back to 3840 x 2160 it breaks again. As much as this is great, I'm pretty keen to not call this fixed as it should really work at higher reses

good idea. i'll try that now I waited the 2min or so after commainding weapons arm for Pet to tell me weapons ready, but when i ask him to seach issue is still present.

Yeah, I've tried custom missions with the same problem. I suspec the track is playing back fine on your system. Perhaps take a quick look at the video excerpt in the orignal post, this shows what I see on my monitors when playing back the track.

I did a "verify integrity" in steam (took ~10 min), then retested. Still no good. How does the track file look to you @admiki ?

Yup also run on a singel monitor at 2560 * 1440 with exact same issues. What do you mean by "Slow repair"?

Thanks for the feedback. I've added a track file and a short video (excerpt from the track) incase the track does not result in the issue on other people's setups

Summary I first thought that Petrovtich was not even searching at all but then by luck discovered that he was, just with a huge offset from where I had commanded him to do so. In image belo you can see the "Designation Reticle" is way off centre and this screen shot is the instant after I've pressed the search command. The "Designation Reticle" is up in the sky and he is searching down in the bottom right (as seen through the hud). This is 100% repeatable. May be related to report below, but as I'm only running one monitor and ite not just that the reticle is off centre I've created this separate report. https://forum.dcs.world/topic/283910-designation-reticle-is-not-centered-in-the-main-screen/#comment-4793857 Details Occurs on both 2.8.4.38947 MT Preview and 2.8.4.38947 (non MT) Note: Issue also occurs identically when secondary monitor (number 1 in pic above) is unplugged from GPU Short video excerpt showing issue.mp4 Mi-24p search offset.trk I also just tried unplugging my 4k screen and running dcs on my smaller (non 4k screen with the settings below) and had exactly the same issues.

SW 2.7.18.30765 TMS right in TWS to set all track targets as system targets (as expected). Cursor then nicely snaps to the targets and moves with them. null In EXP view, moving the cursor over the same target (now at 13,000 ft and in the centre of the screenshot below) the cursor snaps to the position of the target in the NORM view (upper left quadrant as shown in pic 2). This results in the cursor not tracking the target in the EXP view like it does when snapping to a target in the NORM view. null