TAW_Impalor

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.

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.

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?

What do you mean? For Mirage they are in this file: Saved Games\DCS.openbeta\Config\Input\M-2000C\keyboard\Keyboard.diff.lua, for example. If I delete the file I would have to assign all bindings from scratch. I attached the file, in case someone can spot a problem there. Can it have a limit how many changes are allowed? Keyboard.diff.lua

I have custom bindings in DCS to show kneeboard and flip pages, the same ones for each aircraft (but different from default [ ]). Recently, i.e. after 2.7, I started receiving this annoying bug where I bring up the kneeboard but can't flip the pages. I look at Control Options and see all lines related to Kneeboard in duplicate and colored orange (play in VR, so the screenshot is bad). Exit, restart DCS, all binding are white and normal again, but my Next/Previous page bindings are replaced with default [ ] or erased altogether (see screen 2, in flat mode)! I already reassigned them twice to what I want, but after some time I get the same problem again (orange duplicates and all is gone). Happened with M2000 and F18 so far, so not limited to one module. I have too many custom assignments to just erase my Saved Games folder and start over. I use a single TARGET profile to control all my modules. What is causing this bug?

Mine was always forced so that cockpit size feels right, but the clouds are jumping after 2.7

"options" also did not work. now trying to not use Vaicom for some time, to see if it helps

Yes, 3Dmigoto VR mod, because without it spotting is very hard in VR. It's a shader mod, I doubt it affects comms menu but I can try without it. More suspect is Vaicom, because it directly integrates with comms. But it is an official mod?

Another and more often occuring problem in MP is that I lose only comms menu functionality. Yesterday after 30 minutes into the mission I could no longer rearm etc. F menu would not come up at all, and using Vaicom took 10-15 minutes of waiting (twice on different airfields), but worked eventually. Some people in my squad confirmed they also lose comms menu sometimes on servers. I'd really really like to understand what is causing this! @BIGNEWY

Check out your log files guys. There are 100 lines of clouds-related errors and warnings produced at each game launch. Could explain increased load time of 2.7? That's in addition to other errors and warnings on missing sounds and objects that been there for ages. Noice showcase of ED's programming skills!

I am not losing keyboard bindings or having problems with every mission. Only TWO particular MP missions WITH LUA SCRIPTS consistently make my DCS unresponsive to keyboards (virtual or physical). I have only one TARGET profile and I modify key bindings in DCS for each module to work with it. For many many years this worked very well, and I am not sure it is TARGET's fault. I the last such case, after full PC reboot and joining the troubled MP mission, all it took is to autostart an F18 and the keyboard was gone! I doubt the buffer was overflown by that single keystroke.

Well, today it happened three times in a row on the same mission as a month ago (in my TAW squad 'mandatory'). I can send that mission file to @BIGNEWY in PM and I attached fresh logs. The mission used Moose scripts. The only other server I remember having this problem does not use Moose, but still uses some custom LUA scripts. Just an idea about possible cause: I generate lots of keystrokes with Thrustmaster TARGET, with modifiers including RWIN. Maybe it gets 'stuck' logically in DCS? I do not have RWIN on my physical keyboard, so I cannot 'unstuck' it. Other people at TAW are not having my problem. I can fly all other servers and SP missions. I will keep bumping this thread until Devs look into it. My goal is to fly competitively and this bug is thwarting this. (( Logs.rar

Other games work fine? Remove all mods and repair DCS did not help?

If it were for fame or money, maybe. Many just join once in a while to have fun. And when there is a choice on other servers I always join to balance sides.

Can't say, really. I used 3Dmigoto VR mod to fix gamma in/out of cockpit, saturation and sharpness. After 2.7 this mod no longer works, so my VR looks bleak and soft. I had to boost SS and tried VR Reshade mod, but it is not flexible enough. Waiting for 3Dmigoto update, hopefully this weekend.

@xcomHi! Why lock a pilot to a side for the duration of campaign? This makes side balancing harder and prevents me from flying with friends on different airframes. Locking until mission restart would be better, especially if done automatically (joined red first, stay on red until restart).