TAW_Impalor

Hello. Dug up this old thread because in 2021 Low middle radar is still -16 degrees. Did I miss some setting or something? How do you guys use Jester for finer radar angles?

Good job! I tried, but was still getting a conflict for RCtrl-K in most modules. I just cleared it everywhere since never use. For my Harrier the "[" and "]" were also messed up because for some reason they were explicitly added in Saved Games\DCS.openbeta\Config\Input\AV8BNA\keyboard\Keyboard.diff.lua. Clearing and then assigning defaults fixed that too. So, it is not just the two files you mentioned can conflict with each other, but each aircraft's .diff.lua may have an error inside! I attached an OvGME-friendly zip if anyone wants to try your fix. Kneeboard Fix.zip

@LeCuvierWell, sadly, the problem is not limited to M-2000C with non-default kneeboard assignments! Once I started going through all my modules, I now see these red marks in many of them! ((((( And it is the same in VR and non-VR modes...

@LeCuvierThanks. I can try your suggestion as an OvGME mod. Better still, I will change my TARGET profile and all modules to default [ ] keys for kneeboard navigation. This should fix the bug for good.

Short answer: because I am lazy! I like to program a sequence of keystrokes into single button press or flip of a switch. I think it started with Mig21 and its incomplete autostart routine. A screenshot below explains what I mean. Then I adopted the same keystrokes to make F18, F16 etc battle ready. Or be able to turn the radar on and lock a bandit in JHMCS/boresight with one button, on any airframe. In my squad we may fly different planes in the same mission, so I must rely on muscle memory. I like the flexibility of TARGET for that. Some of my physical buttons generate both virtual keyboard keystrokes and virtual joystick button presses. I have VAICOM Pro as well, but only use it to talk to AI "people": Jester, Chief, Flight, Tanker, ATC...

@LeCuvier 1. Sorry for the confusion. I was meant to say my assignments were not the default ones. I only learned about the 'bindings' while reading these replies, and this is all confusing to me. 2. OB latest as well. 3. The red conflict symbols only appear when DCS "reverts" the Kneeboard bindings back to default ones. This happens randomly - only in Mirage and only in Kneeboard section - with no action on my part. I used the quotation marks because such reversal is not functional: I cannot use [ and ] to flip pages. My own assignments do not work either when this happens. I just launched DCS and see the same exact screen as in my first post. I don't have "[", "]" and "RCtrl-K" assigned to anything else in M-2000C, General or UI Layer. When I press either of those combinations while on Options-Controls screen nothing happens. I don't jump to corresponding lines even when on the page which shows these shortcuts. Hovering mouse over red circles shows the binding itself (RCtrl-K etc) with no information on the conflict. I do NOT see the exact line you mentioned in "common_joystick_binding.lua". I attached my files from "...\DCS World OpenBeta\Config\Input\Aircrafts". I removed all mods and repaired the game to be sure. Now, I just closed DCS and launched it again. The yellow lines disappeared and the Kneeboard section shows my correct assignments. This randomness is driving me nuts! common_joystick_binding.lua common_keyboard_binding.lua

I don't touch any .lua. I assign key combinations in DCS Options - Controls menu. All my keystrokes are generated by Warthog TARGET, with single profile for all modules. To fit more commands I have two modifier buttons on my HOTAS. This all is beyond the point. I should be able to define my own keyboard bindings and they should work reliably.

For me the issue is that SOMETIMES my custom blinds for kneeboard next and previous page get replaced by default [ and ], creating conflict with other binds. Restarting DCS usually fixes that. Only in Mirage module. Deleting the folder and assigning the buttons again did not help.

Thanks for the link, it does describe the long-standing bug I encountered. No, I don't edit lua myself, but DCS creates .diff.lua when I assign custom bindings.

Hello. Any progress on identifying the cause of this bug? I am having the exact issue as in the previous post: my custom keyboard binding to operate kneeboard in Mirage sometimes stop working and duplicate orange lines appear instead. Restart DCS and the issue MAY go away. Super annoying as it prevents me flying Mirage on MP servers that require full alignment.

Yeah, I typed a long text along with the screenshot, but then I clicked 'post' all text was lost and only the screenshot posted! I noticed that too late...

You all are showing how it works with DEFAULT bindings. This is not what I am after.

I don't want the default binds! I already tried deleting the folder and assigning anew.

@Rudel_chwYes, I do have custom bindings for all my modules. And no, they do not conflict. In fact, there are no default bindings with LWin. All my modules work stable except Mirage (((

Hello. Well, I went through that trouble: deleted the folder and assigned all the bindings again (looking at Kneeboard.html that I saved beforehand). It appeared working fine after the first restart. But once I went online in VR the kneeboard stopped working again and orange duplicate lines appeared as before (I did not take a screenshot, but it was exactly like the first post, just in VR). Restarted again in flat screen to do a screenshot, all looks fine: Tried in VR. All fine. Went back online, all fine! It was like that before I tried to remap everything - M2000 kneeboard worked sometimes but failed me suddenly when most needed. My other squad mates also experience this and revert to using mouse. I don't know how to reproduce it right now, but there is definitely a bug and RAZBAM should look into it. For me this is only happening with Mirage and only within Kneeboard section. I attached my Keyboard.html for devs to analyze. Keyboard.html

My CUSTOM bindings for Kneeboard Next and Previous Page SOMETIMES fail to work. When I look at control options, I see duplicate lines in orange. Restarting DCS may or may not fix that. Deleting the Keyboard folder and assigning same custom bindings again did not help. Only happens with Mirage! Sorry for edit, the original detailed text describing the problem was lost upon posting.

yep, that was it, thanks! need to read up on that AIRIO plugin...

Hi all, I am new to F14. I see no Jester menu in VR and non-VR, but I hear the sound and can choose the invisible commands by turning my head. Any ideas?

Wrong! I am loving W11 on my low PC.

Hello! Is there a version of Necksafer for Windows 11? The one I have jumps high over the cockpit every time I turn head...

I just tried DCS with Reverb G2 in Windows 11 Pro and I do see better performance. WMR seems to be more advanced. I did not have to register as insider. I built my own ISO using this guide to bypass TPM check for my low-end CPU: https://www.reddit.com/r/Windows11/comments/oat2qp/isoguide_how_to_install_the_windows_11_insider/

TAW_Impalor, blue, F18, SC yes

I still have a question to devs. @BIGNEWY Why can some bindings be orange and come in duplicates? Right now for my Mirage module:

I just tried disabling Tacview in Options-Special. It is unchecked, but still saves acmi files, and they work! Rebooted DCS and PC, double checked everything. Wtf? 1.8.6 Starter and latest OB...

Hello. I had this problem for a while, where I could not rearm/refuel sometimes in MP because F menu would not come up and Vaicom would not respond. I had to either reboot PC and DCS, so they would work again, or wait 10-15 minutes for the rearm screen to finally come up (Viacom would finally trigger it). Happened on several occasions in different missions, but always in MP. Running the same mission in SP or self hosting it did not manifest the problem. Finally, I narrowed it down to Viacom and disabled it two months ago. Never had a problem with comms menu ever since. Latest versions of VA and Vaicom Pro. Conf screens below. I did reset lua code after each DCS update and tried clean install to no avail. Vaicom is unusable for me. Can I get a refund?