RackMonkey

I've found the fix for my problem. I don't know if it will help everybody but it might help those with the same setup I have, DCS standalone and the Reverb G2. After resetting my environment in WMR and checking the floor level in the cliff house... plus resetting the setting position in SteamVR I went back into DCS. One thing kept ringing in my head, J2 kept saying to assign the same re-center button on the HOTAS for centering NSVR and DCS. I had already cleared all the setting that made Num5 the re-center button, and since NSVR didn't have the option to use the keyboard to re-center I was confused. That is until I went into CONTROLS and the UiLayer. I found an item there titled "recenter VR Headset". BINGO. Once I assigned that item and the NSVR reset to the same obscure, out of the way button on the HOTAS I have not had any problems with it. I hit the reset once I am in the cockpit and I haven't had to touch it the rest of the flight.

The "out of focus" just means that DCS is not the active window any more. Look at your monitor and look for the dot to be in the VR mirror image and click. The massage should go away. After you get used to it you can do it without looking at your screen. There is also an option under the VR tab to lock the cursor into the VR environment but that gets to be a pain if you are also using things like Voice Attack or NSVR.

From everything I have read, DCS is not Rodin's Thinker and your not going to get it to work with a sculptors hammer. DCS is a very big freaking boulder and your going to need the biggest badest sledge hammer you can get your hands on to make it work. And until the next generation for GC's come out the 3090 is the biggest hammer in the bag. Or, DCS can start writing code that takes advantage of some of the performance built for the cards be they AMD or Nvidia. Maybe AMD's newest FSR enhancement can bridge the gap since they say it will also work on Nvidia cards.

In my opinion the G2 is a great piece of hardware. The face plate could have been better thought out (multiple size and replaceable pads) and some vent holes above the hot spot where the cable attaches. I think the real problem is the software implementation. Instead of having to run it through WMR and SteamVR it should have a single direct software package that is installed on Win 10. There is just to many moving parts when you have to go from Windows to WMR to SteamVR to whatever your game or software might require. There are just to many opportunity's for incompatibility. And every time your software has to convert you waste cycles doing so. I would also like to see the inline power pack removed ( a point of failure that would require the replacement of the whole cable) in favor of a requirement for a powered USB hub. I don't know how VR hardware will progress from here. They may require more or less power but I don't want to rely on MB manufactures to supply it.

I'd like to add my 2 cents also. 2.07 was working, then I think it was one of the DCS updates that caused it to start jumping around. I tried 2.08 and got the same results. For a while, when I brought my head forward again, I would come back centered on the left MFD. Now I go up and right, out of the cockpit. It is an interesting view but it's hard to fly from there. Num5 gets me centered again but twisting around will put me back outside the cockpit again. I hope the author can find a fix for 2.09 because other than the translations mod's for the SU33 and SU25 this is the most useful mod I have found.

I'll give it a try because I'm tired of trying to fly watching a 1930's movie.

You don't make any sense. The first line says don't run reprojection and motion smoothing together. The second line says that 2.7 is picky. Then 1) says ENABLE reprojection/motion smoothing. I think you should rethink what you said and clarify it.

I should clarify. I know the end mission mapping is a general command. My problem is that ESC works in all the other places it should but not in CA. There are some key mappings that are screwed up. I would suggest that ED QC the entire CA system for usability. It's like the title says...I can't use Tac Cmd on the server I fly on because there is no end mission key bind and no other keys work either. You come in on an isometric view and that's all you get. You can't select any other position in the unit.

Switching to Edge worked. So much for a universal browser.

I'd like to try this but every link I click on goes absolutely nowhere. Does anybody know where Kegety's shaders are currently posted.

It's been a while but I feel safe in saying that Z170 and 270 chipsets won't support VR. You can see by my sig that I have upgraded my system. I now have at least a workable VR system but the 2070 is running really hard to get any kind of decent output. The 8GB of memory is topped out along with the GPU running at 2000 OC'd and the memory at 7000. If your going VR, spend your money on a top end GPU first...if you can find one. Right now that will be all you can afford.

I'll come back and revisit this when I get my HMD back and see if it has anything to do with my problem.

I didn't really know how to define the term "blurry" so that you would understand so I Googled "vision charts". The 20/100 is the one that come closet to what I'm seeing in DCS. I should say that this blurryness is each eye. It's not a matter of adjusting something like the IPD. I think your right about DCS though. They need to stop new development and fix what they have now. I think VR is going to become more popular and more used as it matures and while most of their users will always be 2D there will be a growing VR community that they can't ignore. I remember watching a Youtube review of the G1 from a guy who said he could now read the decal on the plane just across the deck from him, I can't even read my instrument 18 inches in front of my face. This tells me that I can get a much better result than what I have know. Since HP isn't going to do any compatibility test it will be up to us to keep the rest of the VR community informed.

Unfortunately HP is letting us do the testing they should do. I think you'll agree that the rest of my components should provide enough horsepower to run the G2 without the blurryness...at least on the lowest setting. There's no way to test it though. I just have to rely on others with a 170 or 270 chipset to respond. I haven't heard from any of them though. Those are the only 2 chipsets that will run the i7-7700 and I'm not willing to fork out the money to try a Z270 only to find out it won't work either. My friend with the Z490, I5-10600 and 3080 will test the G2 on his system this week and let me know if it works. I can't be there with him to see for myself because he just got contact traced, sooo, he's in quarantine. He is running the Oculus right now so I know his system has the ability to run a lower end VR HMD. I'll post when I find out but my bet is the VR community will just have to declare that Intel's 170 and 270 chipsets won't work worth and damn with the G2.

Well, nobody fesses up to running the G2 on a Z100 series chipset. I'm going to take my rig over to a friends Monday. He's running a i5-10600 on a Z490 chipset. I'll see if his HMD will run on my system, it's not a G2. I'll also see if the G2 will run on his system. If nothing else I'll see what VR is suppose to look like and if the G2 works on his system I'll start looking for an upgrade to my system.

I've read about that. Assuming that I have to replace my 100 series chipset MB, I'll go through the other post here in the VR section and make note of the MB's that others have listed in their sig's and make notes as to which ones are having problems and which ones are helping. I can only assume that the ones helping have working systems and would be the best choice for a new MB. I other words, I'll follow the heard and assume they know what they are doing. I just looked at the list that you linked...my MB is on it and the chipset is listed 4 times. The Z170X series. I guessing there are not more listed because it is an older board and chipset and most people wouldn't even think of trying VR on it.

The G2 is my first experience with VR so I'm learning and everything is new to me. I wasn't sure if that was normal or a symptom of a problem. Better to put everything out there and be educated.

The DCS server I fly on has a tech channel so I asked an open question there...Is there anybody here that is running the G2 on an Intel 100 series chipset that's working fine? I'll post here what I find out.

No luck with the fxo and metashaders files. There was no change. I could not find a lone metashaders folder to delete anything from. When I fly I seem to get a locked 45FPS with a low 20's frame time. And I don't see what "smoothers" have to do with this. If I'm holding my head still and looking at the instruments the image should be clear. I'm beginning to think the problem is a way the hardware and software are interacting. I've installed a couple of the free games on Steam and they work fine and are perfectly clear. X Plane is blurry but not as much as DCS. I remember reading that the 570? chipset has a problem with VR. Maybe the Intel 100 chipset does too. Notice dburne has a 300 chipset and his runs fine. That's why I was asking everybody for that info...to see if there was a correlation. If some people run DCS in VR with the same WMR and Steam software there has to be more to the problem than just raw horsepower. Let that rattle around your head for a while and let me know what you come up with.

A lot of good info Shaun. I am already looking at a MB and CPU upgrade BUT, it will probably have to wait since stock seems to be at an all time low making prices extremely high. Maybe by that time I can look at a 3000 series card also. You described what I see exactly. Ever try to land the HIND like that? It's a beast when you can see correctly, and you can forget about getting into a furball with anything in Redfor.

I'm beginning to wonder if there is an incompatibility between the the 2000 series cards and the MB chip sets and DCS. Every other title I try seem to have great clarity. I would appreciate it if anybody reading this would post these 5 things. What MB/chipset are you running? What CPU is installed and is it OC'd? What video card do you have? Is it just DCS or are other titles having problems? And lastly, are you having problems with blurry or shimmering in VR? As you can see by my sig I have a Gigabyte MB with and Intel 100 series chipset. I have an I7-7700K stock. And Gigabyte's RTX2070Sup Windforce OC 3X 8G video. By the way Vonbane, all the metacache has been cleared with no change.

I know you were asking for setting but they change every 5 minutes while I'm trying to get rid of the shimmer and blurry. That's why I said to consider everything as default and just gave the versions. I copied your setting as closely as I could given the difference in equipment. I got my frame time down into the low teens but other than that it made no difference to my "blurry" problem. If my wing man get half a mile away...I lose him in the shimmer and lose of definition of the aircraft. Thanks for trying though.

Well...Windows is 20H2, nVidia 461.14, WMR and SteamVR are the current beta's. Everything else have been changing depending on who's post I'm reading at the time. Assume that all adjustable settings are at default. One exception though, I will generally start with my texture setting on high and go down from there since that has worked for me before when using a monitor. I will now try the setting from the post that came right after your response

I did not expect this when I got my HMD. I know 2070 is not going to let me run my setting on high, but I did not expect that it would be blurry. I expected reduced frame rates and some less that optimal visuals. I did not expect it to look like I have 20/50 vision. When I start DCS and it's loading both lenses look like they are jumping between two images. It really hurts the eyes. I have checked the lenses with some free games from Steam and the are perfectly clear. I also got X-Plane 11.50 to boot up, without Vulkun, and it looks OK. So I can assume that there's nothing wrong with the HMD. I must also assume that it's the something with DCS. I'm asking you guys to looks at my hardware and if yours is the same, let me know if you had a blurry output and what you did to fix it. Assume that I have everything update with the latest firmware or drivers.

For you guy's that seem to have a "working" system...please post your spec's, and I mean everything. From you MB BIOS to the version of SteamVR you have running. Maybe we can spot a common thread of system that seem to work and other that don't or won't. Mine is blurry and stutters on loading like Plane Crazy says. I see one top level system that can't run it correctly run VR from Pickle. Mine Gigabyte G170XP-SLI latest BIOS Gigabyte RTX 2070 8GB(tried different driver sets) 32GB Intel NVME drive Reverb G2 Win 10 ver 2004 WMR and SteamVR from Steam