Chaos_Out

Without any explanation as to why people need to activate the "hand controllers" setting and what relevance it has, you might as well add "trust me bro" to the end of your post.

My issue is that I don't have any single binding that would work across ALL aircraft. Perhaps the devs forgot we don't have full access to a keyboard since we have our headsets on. Due to what some aircraft require, even my modifier is different across some aircraft, which can be a pain to recall sometimes (like coming back from my break), but luckily I've flown my preferred aircraft enough to where I can remember pretty quickly.

This actually has changed. There used to be an option for this in each aircraft, which IS missing. I just came back after a break and noticed none were working, and that the aircraft specific binding option was removed. @BIGNEWY Why were the individual bindings removed? There are some aircraft that I can't have the same zoom keybind for, so having an option for each aircraft worked great. This is now an all or nothing for me. EDIT: referring to both VR Spyglass Zoom and VR Zoom

I thought I saw on here that someone found a slightly modified version of reshade that actually worked with OpenXR. They had a link to the d/l. I didn't test it myself or save it (both file and post), but it might come up if you search the forums a bit.

This is something I've always thought could be happening, as I also have a terrible time with OpenXR in MSFS 2020. Every setting and resolution lowest possible and still stuttering. From you or ED? Care to be more specific?

I wouldn't call it placebo, when most of those user reports are simply "I use steamVR, no stutter, when I use OpenXR, massive stutter." I'm one of those that thought using SteamVR with a G2 made one use the SteamVR motion reprojection. I can say for 100% fact that going from SteamVR to openXR, while mimicking the SteamVR settings and optimization mods as best as possible, the motion reprojection and performance IS worse, in both clarity and stuttering, for me and others on here (yes, used openxr toolkit). I have better performance in single thread DCS using SteamVR than I do in multi-thread openxr dcs. I have a 5900X and 3090.

OpenXR has been nothing but a pain for me. I gave up on MSFS 2020 because i couldn't get it to not stutter in the cockpit, even with EVERYTHING set to low (including res). I tested it a little bit in DCS when it went native but instantly noped out of it since it was stuttering vs my buttery smooth and clear OpenVR experience. I can't for the life of me understand why so much focus is being put on it when the entire community is dependent on one person and their 3rd party app (XR toolkit) for OpenXR to really shine. Especially now, when if I recall correctly, the dev has stated they need to take a break due to personal issues or something. The vast majority of the community needs motion reprojection for VR to function and/or be clear enough to be enjoyable, and it's been stated that the MR of OpenXR tools and OpenXR toolkit (great naming btw) is very subpar compared to what the steam client offers. I've been using Skate Zilla's DCS Updater/Launcher to launch the DCS standalone version with Steam VR, but if that ever breaks I'll simply move back to the Steam version of DCS. Until I can use that utility to launch the MT DCS into Steam VR, or any method I suppose, while being able to use OpenVR, I won't touch it. Can you tell I'm frustrated?

Yea, this happened to me too. I forgot about this part, when I had mentioned no matter what I do, this was one of those things I tried. It always got stuck. There's some imaginary resistance/hump that it has to be forcefully dragged over to be able to move freely. For example, like the guy above said I bound my TMWH side slider to the wing sweep handle, and found that if I use it right when I land and forcefully move it over that "hump", the voice attack "macro" will be able to finish with the wing sweep and put it into EWS. The other thing I tried was using wing sweep aft (the one that is grouped with Auto/Manual/Bomb mode) to 68 degrees, and that was how the handle ended up stuck at 68 degrees. If there is no manual action to break that resistance, no keybind will work. With this post, I was hoping someone could explain why that resistance hump exists or maybe point it out to someone at Heatblur that this could be a bug. Does anyone know how well they monitor these posts, like say how Nineline or Bignewy does?

I fly VR and don't like using a mouse or keyboard if I don't have to so I use Voice Attack. I don't even have a keyboard by me when flying it's that good now. I'm trying to automate some things with Voice Attack, and sweeping the wings back to emergency wing sweep after a carrier landing is currently on my to do list. The issue I've found is that, no matter what I do, the keybind "Emergency Wing Sweep Handle move Aft" just shakes in the 68 degree position (Yes, I waited for the bags to deflate, tail auth warning to go out, flaps up, cover open, handle up, etc etc.). Even using the mouse wheel takes a couple of spins before it finally pushes over. Clicking it with the mouse and using a "forceful" drag has been the main way to get it over into emergency wing sweep. Is there a reason it functions this way? Is there any way to get a keybind to work and not have to manually mouse it into emergency wing sweep every time? Thanks for the help.

As others have said, use Chucks guide as a baseline and then modify to your needs. I try to make my control mappings across the various aircraft as similar as possible to avoid having to re-learn each time i switch aircraft, i.e. flare is always forward, chaff always back, etc. Since the harrier and F/A-18 have similar style controls (even same stick?), use that for reference as well when mapping the misc stuff on the HOTAS.

So, technically, no, you couldn't do that as I mentioned, because I specifically said "without messing with any radio settings or F menus." This is a simulation with built in shortcuts for people who don't want to deal with every little tidbit of a real aircraft. I have that shortcut activated with easy comms. Not a single other aircraft has this issue with this setting, and as the person above you mentioned That's been my whole point this entire time. I think most dismissed the easy comms part, since, by the book, a radio switch does need to be toggled. I'm not trying to argue how real life policy and procedure is executed. Now that I have a better understanding of what the problem is, I could probably just say that easy comms is partially broken in the Ka-50 III. Partially, because you can still talk to ground crew in the F menu without having to toggle the radio switch. Keybind toggling rearm/refuel is broken.

Are you saying you actually get the ground crew to acknowledge your request to rearm/refuel just using the basic/default rearm/refuel keybind without messing with any radio settings or F menus? You can go Ka-50 III -> Instant Action -> Runway Takeoff (Caucasus) -> (when loaded) LAlt + ' -> pick any loadout -> and then the ground crew acknowledges and completes your request? Yes, I got it to work using the F menu, not with the default keybind. I'm not referring to bringing up the menu. To be more specific, I haven't rebound anything, I've been using the default keybind of LAlt + ' and then use Voice Attack to bring it up. Even manually pressing LAlt + ' doesn't change the outcome. This is the default keybind used in all of my aircraft and they all work except for the Ka-50 III. I rebound it to a random MFD button to test that, and it still didn't work. I refuse to believe that this is the only aircraft that requires a button to be switched for the ground crew to hear you. It especially doesn't make sense when I can get them to rearm and refuel using the \ menu -> F8 Ground Crew ->F1 rearm/refuel, without touching a single switch in the cockpit. Edit/Update: When I set the switch to GRND, using the default keybind for rearm/refuel did work, however, since I use the easy radio mode, and have never had to adjust anything in any other aircraft, I still feel like this is a bug.

I have a keybind that directly brings up the Rearm/Refuel menu when I need to use it. This has worked for every single module I've used (a lot of them). However, when I use it for the BS3, the ground crew never replies and I never get any weapons or fuel. To successfully get the BS3 to rearm/refuel, I HAVE to use the F1-10 menu options "Ground Crew -> Re-arm & Refuel" for it to work. The ground crew will then reply and proceed to arm and fuel. Is this a bug or done on purpose? Tested in both SP and MP, easy radio mode (or whatever it's called). Again, only module where I am required to go through the radio menu to rearm/refuel. Thanks

Put some tape over the G2 sensor between the eyes (I used masking tape/painters tape, I don't know if clear scotch would work). It detects when you're wearing the headset. I could look through the lens and see the mouse move, but when I put the headset on the mouse stopped working. The tape makes it think from the start you're wearing the headset. I don't recall why this fixes it, but it does.

I'd say there was probably a little ignorance on your part as to how the DCS VR experience would go, so you came into this with the wrong mindset. If you look up anything about DCS VR settings, you'd find pages upon pages and loaded guides full of an abysmal amount of "tweaking" needed for things to be "right." Was your research before or after you pulled the trigger on getting into DCS VR or was it, I have a headset now how do I set things up? I knew this coming into it and expected the long period of trial and error to get the results I wanted. I really wouldn't recommend DCS VR to anyone who wasn't tech savy enough or who just wanted a plug and play experience. Since you're here though, let's get you where you need to be. For starters, pick a goal that you'd like achieve and then find the route that gets you there. Are you a constant 90 fps required no matter what settings kind of person, do you want more clarity and smoothness over fps, etc. etc. Once you have a goal, it should help you feel a little more in control and on a path with a set mission instead of being lost in the sandbox now knowing where to go next. For me, especially as I get older, I wanted 1. clarity and 2. smoothness aka stutter free when looking around. This meant 90fps was out, but who cares if you can't even realize it when flying. Installing openvr_fsr 2.0 and reshade 4.9.1 (I didn't like 5.1) was the game changer that finally allowed me to get what I wanted. A higher Super-sampling (I started at 150% SS but think I settled on 120% but with MSAAx2 as I found they looked almost identical but with less dropped frames) and everything looks amazing. Reprojection I think is on auto but I'm almost always locked around the 45 fps. Only on busy airport SP mission starts can it get a little wonky. I used the most demanding aircraft cockpits to tweak my settings (at the time the A-10C II, so when the AH-64D came out things were already dialed in). Shader mods, as of late, haven't had that great of an impact on fps, so unless you need a couple ms of render time or whatever (haven't used fpsVR in forever so I don't remember the measurement names), then you could probably skip it for now. I have a 5900x and 3090 and DCS VR still isn't perfect, but it's in a good spot for ME that I can really enjoy it for the things that I personally do. Also, walking away from the game and taking a break can be a really good thing, sometimes even necessary. I haven't played in a month or so but I'm getting the itch again to fly. Only do it when you want to. This is a game, and you're supposed to be having fun. VR made things easier to do in-game for me (AA refuel and carrier landings) and the feeling of actually being in the cockpit vs looking on the screen is way too different now. I personally don't even touch my trackIR/screen dcs gaming anymore because I only want to do it in VR. TL:DR - take your time to get things dialed in, expect a lot of trial and error. Once you get things in a good spot, you'll absolutely love it. Best of luck. Don't give up.

Yes, bug still exists apparently. Just use Overcast and Rain 2.

I know what you're talking about now, but we're talking about two different things. I added a custom Norm/Else Off switch for the NVS Mode that I have to transfer over every time they update the controls in the default.lua. You're talking about going inside the game and saving the bindings for each hardware piece (throttle, joystick, etc.). I just tried what you were doing and it does create a double .diff.lua because that how it's listed in the filename. The only way for it to actually overwrite the old file is to take out .diff.lua in the filename box when saving. Then you'll get the prompt of "this will overwrite the file are you sure?" Is this a bug or not, I don't know.

I just updated my input .lua for the new trim reset and used OvGME to overwrite the default .lua and it worked fine, didn't generate a duplicate. Does your version of the input profile have the .diff.lua accidently added in twice for it? Edit: Looking at the screenshot again I realize you might be talking about the in-game controls profile that's saved in the saved games area, not the main one in the main game files. Moar coffee plez

This. But only thing that sucks is if they update some functionality/controls, then you have to manually add it back in to the new controls file, i.e. when the F16 got the ECM switches added in. Doesn't take long, but just something to keep in mind seeing how this module was just released, it's likely to receive new binding updates in the future.

I tend to agree with the above post that MSAA is a form of super sampling, and possibly a more workload efficient one. I found that going from just 150% SS to 120% SS with MSAA x2 to have practically the same visual quality/clarity but was significantly less stressful on the system and allowed me to have a smoother experience without having to sacrifice clarity. Yes, I keep forgetting to update my sig but maybe after writing this I will (I won't).

Just did a little flying around and was very smooth. For those that say they're getting low fps or stutters, if you've only tuned your VR for aircrafts like the f-16/18 types, you're gonna have to dial your settings down a bit. I noticed when I was tuning mine, that the 16/18 were great, but the A-10C2 cockpit was stuttering a lot, so I dialed everything down until the A-10C2 was also smooth, hence why my VR transition to the Apache was probably smooth. Now if I can overcome being overwhelmed with trying to map the controls of this thing I might be able to have some more fun!

@speed-of-heatAny chance you can update this for the recent patch? Things work pretty well without shader mods these days but I found this one to make things a tad bit smoother without having to wait 15+ minutes for the shaders to compile, and the IC Pass is a must for me. Also, where can I find info on what exactly it is people are doing with these shader mods and the files. I don't like always being heavily dependent on others with stuff like this because I know people eventually lose interest and move on, so I'd like to try and teach myself what exactly is being done so i can take a stab at it.

https://wiki.hoggitworld.com/view/Threat_Database The bottom part of the page that has clickable SAMs, the "Overall" section, links to pages that give tactics on encountering them. Some might be missing some info, but it's a start. Simple trial and error is how I learned. "What's that annoying thing shooting down all of my missiles?" Ok, now I know, need to overwhelm that one first and destroy it before I can attack the rest...etc.

The lazy way to create a DCS server with the same build is to simply create a new DCS shortcut (or copy paste a new one) -->right click on shortcut --> properties -->shortcut tab --> put "--server --norender -w DCS.server1" at the end of the "Target:" box, so it would look like this: "E:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe" --server --norender -w DCS.server1 This creates a new folder in the windows saved games folder called DCS.server1. To open the server GUI, browse to E:\Program Files\Eagle Dynamics\DCS World OpenBeta\WebGUI and open the index.html file. Making a shortcut for the index.html GUI file makes it simpler to access, or use something like a Stream Deck like what I use. You can get fancy and change the shortcut icon to distinguish it from the regular DCS build too. I think the first time you try to run it, it might say can't run the same build or something, but once it creates that folder it should work the second time.

In the 20+ years of computer gaming, I've never heard of anyone using L3 cache as a serious metric for whether it will do well or game well. From what little research I've done, it doesn't appear to be that big of a deal on newer games, maybe it is for cpu rendering (referring to VFX movie stuff) where that extra memory could be useful, but I honestly don't know. Where DCS fits in that new vs old with all of the updates done + upcoming major ones (multi-core + vulcan), I'll let you decide. From what little research I've done on the 5800x3d, I personally would not want it at all. It's been "down clocked" to 4.5ghz and new reports are suggesting it can't be overclocked. There is also still the possible temperature issue and if they fixed that as well. Look at any benchmark testing done and you'll see almost always the biggest metrics for performance are speed and temps, in this case core speed. It's why Intel was the gaming champ for so long, since they had cpus that could hit 5ghz+ while AMD was sitting mid to low 4ghz AND games couldn't take advantage of multiple cores. Down clocked and LOCKED at 4.5ghz is a major downgrade from getting an unlocked cpu and getting it to 5ghz ballpark. Make no mistake, 4.5ghz to 5.0ghz, even the stock 4.8ghz (5900x), is huge, nothing slight about it. I got my 5900x to boost to around 5-5.1ghz without having to do anything crazy, and coming from my 2700x, which could only really do low 4s overclocked, it was a huge performance difference. DCS VR needs every little bit of performance possible, as only a couple of frames could be the difference between smooth clear gameplay and stuttery blurry gameplay. Bigger memory is only better if it's either faster or was even a bottleneck to begin with. For example, what good is a 3090 with 24GB of VRAM if you only 2D game and max out at 8-12GB (FYI DCS VR does in fact use up all 24GB). My 5900x and 3090 offer good clear performance, but it took a ton of trial and error tweaking to get there, and I have to lock it at 45 fps, and even then it's not always perfect and has moments of stutters when a lot of stuff is loaded (mainly at airports). I personally refuse to sacrifice clarity though, so I accept those small moments of performance hits. This also brings up another point, we don't know what OP has for a GPU. It could be that their money could be better spent trying to upgrade that instead of getting something that will offer either breakeven or marginal gains. Just my 2 cents. EDIT: And until the 5800x3d is released and benched, everything is just speculation.