Twwhitey

Sure thing - it's by no means super elegant by coding standards but here you go. Note you'll need this custom rotary encoder library (ErriezRotaryEncoderHalfStep) which is brilliant as it allows for the capture of more than just CW/CCW rotation but also 3 levels of speed so you can adjust output speed (in this case button press duration) based on how quickly you spin the dials... helps with traversing the big dials like the HSI Course & Heading dials with bigger jumps quickly while still allowing for very fine tuning when turning at slow speed. You obviously need to customize the pin assignments and may need to adjust the sensitivity variables, button press durations or even use his FullStep library based on type/model of your encoders and/or what flight systems you're most interested in controls but it's all easy to adjust & test if need be... DIY_Knobster_V3.ino

In need for an extra few dials to augment my VR setup for things like the F/A-18 Radar Alt setting or the A-10 & F-16C HSI CRS and HDG dials the internet seemingly pointed me to the perfect solution - a thing called the Knobster… looked perfect but wait… 95€??? And it only works with a 30€ plug-in that may or may not work with DCS?… so $130+ plus shipping from Europe? Good lord cut me a break.. No thanks… having dabbled in Arduino boards for a previous button box and finding the dual encoders necessary online with a slick mini-board w headers I figured I’d just make my own (as I’m sure many people have done as well). (2) $13 encoders from Propwashsim.com (1) $24 arduino micro w headers $10 in short header wires $10 in small plastic project box (Pack of 5 mind you) $6 6ft USB - micro USB cable from Amazon and (with a leftover L bracket I had in the garage) voila a DIY version for < $60… and a deluxe edition with 2 dials instead of 1 LOL the soldering of the encoders to the mini-circuit board was a bit fiddily (Pretty small pins to deal with) but otherwise it was pretty simple to assemble and fits pretty perfectly into the small project boxes I found on Amazon. Shows up as a 10 button joystick in windows easily mapped in DCS so no 30€ plug-in required I’ve got the simple arduino code and 4 project boxes left over happy to throw a box in the mail (USPS) for karma sake if anyone with basic soldering skills is interested in doing the same just DM me… cheers

just curious regarding this weeks patch (2.8.2.35632 1.26.2023) is there anything that I need to do to refresh/reset related to Buttkicker +SSA + SSM post-Open Beta update? Everything still works but man the sound levels and everything related to my Buttkicker DCS confit seems all out of whack… sound levels are super loud and wonky all of a sudden and it was all super stable prior to updating this past week - something doesn’t seem quite like it was before. Is there like a .lua reset/refresh that I can or should do related to SSA & SSM and my Buttkicker profiles after a patch update?

ahh got it thanks @edmuss I actually found an older thread posting where it was explained better (to me) and I completely spaced on that so sorry about that. That said I saw the recent post-OB patch (before the hotfix) posts where it was recommended to set Disabled or Auto (i.e NOT to set "Always On" because of the crashing) which is confusing because it sounds like Auto doesn't do anything for DCS... LOL That said, based on what I read... is it correct to state that "Always On" doesn't necessarily mean that Motion Reprojection is "Always On"... it's only "On" if you can't maintain 90fps (@ 90Hz)... is that correct?

So I really want to give OpenXR a go vs. SteamVR for my Reverb G2 but I can't for the life of me get OpenXR Motion Reprojection "Automatic" mode in to engage. My system (13900K + 4090) and DCS settings (pretty spartan by most standards) can generally support 90fps in most of the single player persistent missions I churn through by myself. When using SteamVR (with Motion Smoothing set to "Auto" in SteamVR) say I get into a busy area (like overflying Damascus) I can watch the Framerate indicator drop from 90fps to 45fps which I believe indicates that Motion Smoothing has "kicked in" and is now engaged... when I leave the area or things get generally get less busy (i.e. look to the sky) the framerate jumps back up to 90fps. "Auto" appears to be working as expected... When using OpenXR with Motion Reprojection set to "Automatic" in the above scenario the "Automatic" engagement doesn't seem to happen... same scenario as above but instead of 90fps <> 45fps I'll see framerates bounce around from the 60's and up (with obvious stuttering) until things lighten up and I'm back at the 90fps threshold. nullLike I said I like the idea of ditching SteamVR but the fact that I can fly *most* of the time at 90fps but have Motion Smoothing/Reprojection kick in temporarily and automatically when need be is really nice.. not having the feature work is literally game changing... Anyone have any theories why this wouldn't work in OpenXR? Is there another setting somewhere I need to check that might be overriding that Automatic setting?

So after 3 years of using the TPRs this past weekend I implemented the TPR damper mod which is awesome and highly recommended. Next up is trying to find a way to simplify the removal / readdition of the centering springs. As I’ve been switching back & forth between the AH-64 and F/A-18 and removing the centering springs for the AH-64 does wonders for reducing rudder fatigue… I find the removal & addition of the springs on the TPRs to be at best fiddily & inconvenient to do quickly (them being mounted under a desk with the fiddily screw/spring combo and all) Wondering if anyone out there found a slick way to mod the spring(s) attachment mechanism to allow for a 10 second job to remove or add the springs back?

Interesting - did this "on-demand" capability of OXR/WMR motion reprojection change at some point? I seem to recall months and months back (I took an extended break from DCS a while back) that I couldn't get MR in WMR to do this - it was always on (even in bland scenarios where I could easily maintain 90FPS). Just curious but either way I see that it does indeed do this now so that's awesome thanks for the explanation!

Eureka! this worked... I was completely unaware of the "Unlocked" option in the OXR toolkit. I've been looking for the ability to have MR "on-demand" i.e. only come on when I dip below 90fps and basically be off otherwise. I've got a beefy machine and play with very starkly configured visual settings in the hopes of maintaining 90FPS as much as possible as I just can't look past the artifacts that MR creates (especially the rotors in the AH-64D)... so having MR on only when it absolutely has to is great. Thanks for posting this!

I think what he’s asking is does or can OpenXR MR actively engage when the frame rate momentarily drops below the threshold (say in an area where there’s a lot of objects or activity) but then DISENGAGE when the system is able to maintain the threshold again? SteamVR motion smoothing does this - I can fly around at 90 fps most of the time but say I fly though smoke or a busy area it’ll turn on smooth things out then disengage when things calm down (ie Auto). My understanding was the OpenXR MR can’t or doesn’t do this… it’s either always on or always off. There is an “Auto” setting but it supposedly doesn’t do anything. Is that right?

Oh awesome thanks @Surrexen I’ll give it a go. I was poking around the generals.lua earlier today and had suspicions the initiator might be in there somewhere… appreciate the input - like I was saying and what you’ve probably heard over and over the options, variety, replayability and simplicity of these mission sets are a god send, weeks and weeks worth of game play in these… cheers mate

Somewhat random question for you @Surrexen - is there a way (either through a variable setting or commenting out select functions, etc.) to disable the base capture / "escalation" functionality in this mission? The reason I ask is that Syria has always been a resource intensive map and as a single & VR player I'm interested in replicating the simpler Surrexen old-school Operation Clear Field/Snowfox functionality w/o the additional mission complexity/logic/resources that might come with the added base capture/helo/escalation functionality. I've dabbled in slightly modifying some of your mission scripts in the past (for example reducing the number and cycle times of red air CAPs) to make it a tad easier on single player scenarios so I'm reasonably comfortable finding/commenting out portions of scripting if necessary... not sure if there's spot in the scripts somewhere I might be able to comment out the initiation or triggers around all that. Not sure if that's at all possible or if the logic is too embedded but figured I'd ask.. these missions (including the old school ones) have so much replayability they're absolutely great...

So I just gave 471.41 a try within the last hour and had some peculiar issues post installation. I took a full C:\ backup, did a full DDU / Safe Mode uninstall of my current 465.89 drivers, rebooted Windows and installed the non-DCH version (ala Standard) 471.41 drivers. Seems like those drivers don’t like something in my system likely the HP Reverb G2... if I had to describe the symptoms WMR seems to start & restart over and over manifesting itself like the system hangs... comes to life, hangs, comes to life... black screen flashes, etc etc. really weird. I admittedly didn’t try all that hard to get them to work - tried a couple of reboots to ensure the drivers installed correctly and pulled up nVidia Control Panel and my system was acting all wonky. Very happy I took a full backup beforehand and just restored, I’ll stick with 465.89 for now as I really don’t want to spend all weekend fiddling with nVidia drivers... not saying you’ll have the same issues but if things are running well for you at least take a backup beforehand

So I've been dabbling in DCS Liberation, specifically establishing a dedicated server (on the same machine) to host the Liberation mission while I join from DCS client. (As I've read that hosting a dedicated server with appropriate DCS CPU affinity settings can net out some additional performance given how busy those missions can be...). Anyhow - when joining these "hosted" missions (I'm the only client/participant mind you) I'm finding that Vaicom pro (I have the paid-for PRO version with Realistic ATC comms, and Kneeboard plug-in etc.) isn't working. I'm able to use VA for non-DCS integrated stuff (I've got commands for full screen toggles, etc.) and I see that VA is recognizing my speech/commands however none of the DCS comms/integration is working. ATC commands, wingman commands, ground crew commands, etc. and also the new VCP Kneeboard aren't registering/working. The kicker is running the same exact missions locally (I have a few missions I've tried, one Liberation... others non-liberation related) - i.e. NOT hosted on a dedicated server - all the same attempts to work perfectly fine in VA/VCP so it appears to be something related to joining/running on a pseudo-multiplayer server. Now I HAVE confirmed I have the "Use with Multiplayer" option selected (see preference screenshots). Is there something I'm missing? or anything I need to do on the server? or in my DCS configuration or VCP preferences so enable this? Anyone have any thoughts?

edit: confirmed - removed the DCS World entry and I no longer get the orphaned folders upon VA launch... thanks for the info again guys... Awesome Got it - thank you so much for digging up the details... will dig through the registry and sort out this evening... much appreciated guys

Trying to clean up a trivial but somewhat irritating item on my gaming (aka DCS) computer. I'm currently running ONLY DCS.OpenBeta but whenever I launch VoiceAttack w/ VCP it automatically creates a Saved Games/DCS (stable) folder (with Mods & Scripts sub-folders) under Saved Games and a root directly "DCS World" folder (also with Mods & Scripts sub-folders). At one point I did have both Stable and OpenBeta installed on this machine but ultimately uninstalled Stable... the problem appears to be that VCP still thinks I have Stable installed so every time I launch VoiceAttack it goes ahead and creates these unused/orphaned "stable" folders. It's not hurting anything per se but does vex my OCD tendencies. Anyone know if there's a registry setting or some configuration file I can edit somewhere where I can tell VCP that I only have OpenBeta installed but not the Stable version? I've been through the LCTL+LALT+C configuration GUI but can't seem to find anything that would sort this out... Any help would be greatly appreciated!

easy overlooked button you need to click to see the “unknown” profiles, did you click that button? Click "Show unknown settings from NVIDIA Predefined Profiles" - second button from right on the toolstrip. Note the 3 entries which list 17 profiles. On the first 2, click on them and amend 0x00000000 to 0x00000001 On the 3rd, click on its dropdown and select the only item. You should now see this..

I subsequently figured out why I was getting the “Selected Unit is not a SuperCarrier” message. This weeks DCS update must have reset ‘Easy Communications” to ON which royally screws up how VCP works when your not expecting it. Turning off easy Comms fixed my issue. Great way to spend hours...

Ok last update... I'm convinced something wonky is going on with DCS and/or the default set of missions in DCS or ship units associated within a Supercarrier group. Pulling up the ATC "menu" it appears that all of the ships units associated with the SuperCarrier in the default F/A-18 Supercarrier Case 1 (standard) missions all apparently show up as ATC options for channel 127.5 (see screenshot). As these missions were my "test" missions this is why I'm getting the "Selected recipient is not a supercarrier". Great way to spend hours and hours the past 2 days...... Creating a custom mission with only a lone supercarrier (and no affiliated units) VA/VCP command messages work fine. Good lord...

Ok update - a clean out of the C:\Program Files (x86)\VoiceAttack\Apps\VAICOMPRO folder cleared up the mess of all the never seen before "building" & "reset" messages noted above upon starting VA. Those folders get recreated by the .dll when you run VA with VAICOMPRO.dll in the proper place so that cleared up the mess I noted above. I've also renamed and moved the C:\Users\<username>\Saved Games\DCS.openbeta\Scripts\export.lua file (which also gets recreated) so good there... I've then done a complete Repair of DCS (including scan and removal of all added files) and I'm still getting "Selected recipient is not a Supercarrier unit" in both standard F/A-18 SUPERCARRIER-HORNET-CASE I RECOVERY missions (both Caucasus and Persian Gulf). What's interesting is that upon entering the mission, VoiceAttack is noting that the "Nearest ATC: DDG Arleigh Burke IIa" (see screenshot) - that doesn't seem right at all. I have to think this has something to do with the recent update to 2.7.0.5518... AM I really the only person seeing this? @Hollywood_315 What am I doing wrong here? I've literally had zero issues with VA/VCP for 2 years and this is the first time I've seen anything like this. (Minor rant: between the week+ of near constant DCS and OS re-tweaking & testing in an effort to reclaim lost performance in VR and now this 2.7 has been a complete nightmare.. zero fun so far)

Anyone have any recommendations on how to reset VA/VCP and DCS? Upon starting up VA for some reason this week (after the recent DCS update) I see all sorts of messages that were never there before (see screenshot) so me thinks something got corrupted somewhere with this new update this week. The end result of which none of the ATC commands are working with the Supercarrier (I get message "Selected Unit is not a Supercarrier") Will a complete uninstall & reinstall of VA clean this up? (noting I have to backup and reapply the C:\Users\<user>\AppData\Roaming\VoiceAttack\VoiceAttack.dat file). One of the ancillary issues is that VA still thinks I have a Stable install of DCS on my system, when in fact I don't anymore. I'd like to clean this up and sort out the issue. Any recommendations?

So I fixed it but potentially unhelpful update here as it’s not clear exactly what did the trick. I uninstalled and reinstalled WMR. (No immediate fix) I DDU’d & reinstalled nVidia driver 465.89 (No immediate fix) i DDU’d and installed nVidia driver 457.30 (no immediate fix) as a last resort I went into updates and applied all outstanding updates there were only 4-5 if I recall. The odd thing is it looked like the recently publicized KB5001330 update which I uninstalled earlier this week re-applied (and took forever to do so) and once completed the pre-allocated setting once again seemed to suppress the extra monitors. Note I’m on Win10 Pro 20H2 service pack. Doesn’t make a ton of sense but I guess I was successful... good luck

Interesting I'm seeing this behavior as well. Registry entry is in there unchanged and toggling back & forth and/or deleting and re-creating doesn't seem to make a difference... those extra monitors keep reappearing. I guess I'll give the WMR uninstall/reinstall a try <eek>

Huh interesting thanks - never seen this issue before and VCP/VA appears to working fine otherwise... restart/reinstall/repair might be the ticket I suppose

Instead of starting a new thread I figured I’d resurrect this one. Updated DCS 2.7 to the new OB patch that came out today and now I’m getting the “Selected Recipient is not a Supercarrier” message in VA and none of the VCP carrier comms are transmitting to the supercarrier. Did something break VCP with today’s update? I’ve tried various pre-built and custom SC missions and just about all of the commands (‘marking moms”, ‘hornet ball”, “commencing”, etc)... using the onscreen menus work so they’re definitely SC’s Im licensed for the Realistic ATC Comms plugin and it was working fine yesterday pre-update... anyone else having issues using VCP and SC today?

You nailed it @Maksim Savelev... thank you for the info, that was definitely the issue! Switched it back to Best Visual Quality and the issue is resolved... hope this thread helps others in the future... and thanks again!