Wicked.-

I tried this tonight. First I had to manually put in the line “render camera mode raw”. Once done I didn’t notice any improvement but it did make my spyglass zoom cross eyed. So unless your index is cross eyed, adding this line doesn’t have any other benefit.

VR has killed any possibility of flying in 2D for me. I honestly wish I didn’t try it as early as I did. However, it’s totally flyable for me. I typically have 45 FPS even on heavier maps with the common frame dips around airbases. Is there ghosting? Yes but it is not enough of a distraction to take away from the immersion I get from VR. Then again I flew the other Viper sim for 20 years and was already accustomed to shit graphics outside the pit. Being able to do overhead breaks, air refuel and fly formation with the precision of being in a real aircraft with realistic visual cues is truly outstanding. What I don’t get, what I struggle to wrap my head around is how 10 people can have practically identical top end computers and get totally different results using the exact same settings and exact same HMD. It makes no sense. It reminds me of having to do “The Dance” before connecting online with others to fly the other Viper sim. I’m talking circa 2001-2002 lol. The difference being, after doing “the dance”, you were pretty sure to get at least an hour of online flying. Granted, ensuring everyone’s config settings were the same for network syncing is different from hardware/driver settings but the same principles apply. Anyway, in the end this is what we do for enjoyment. If you’re not enjoying it, do what you gotta do. For me though, if I quit VR, I quit DCS and all other flying sims as well.

I have openVR debug tool installed currently. I would think it will fix what little cross eyed effect I get. I’ll let you know which settings work when the Reverb comes in. So what you’re saying is you have NO PROBLEMS with the Reverb? Thank you sir.

So no cross eyed vision? Even though the minimum IPD setting is 59? I already told the wife I was ordering another lol.

If you’ve saved some settings using the tool it should go away. In order to bring it back you’d need to delete the file in the saved games folder. If you’ve saved a setting and it comes back anyway I would think it isn’t really saving. If it is saving and still coming up every time I’m not sure what’s going on.

It seems we're all trending that way now. Correct me if I'm wrong, you have an IPD of 58? If so I'll buy a Reverb tonight. It would be different if I played other games with the Index but the only game/sim I play is DCS.

You need to see a white dot in both red contacts. That lets you know your radar sees the target. If they’ve split and bracketed vertically, or one has notched, the radar has lost sight of the contact. There’s nothing you can do but monitor the radar and see if the second target pops back up with the white dot. There’s a lot going on visually on the radar with L16 active. With the current behavior of the radar I begin trying to get contacts twizzed up around 40 miles. Keep in mind you’re also limited in azimuth in TWS. If they’re pop up contacts inside of 20 miles don’t bother with TWS. If you have two close contacts that have the white dot, TMS up ONCE on each which should make them solid red. Once that is done TMS right to bug one and then TMS again to swap the bugged contact.

I kind of agree with this statement. In hindsight, DCS has not been worth the investment.

The index is the only option for those of us with IPD’s outside 59 or 71mm. Yes it’s expensive in comparison to the rest but the build quality and features are exponentially better than anything else on the market. It has both mechanical IPD and eye relief adjustment, extremely comfortable catchers mask style mount like the CV1 but easier to adjust, excellent quality headphones that sit off the ear, built in mic and la cable that is no heavier than the CV1. You’ll need base stations, some people could get away with one however I could not. No need for controllers with DCS so with headset and 2 new base stations you’re looking at $800. However, you can pick up some used 1.0 base stations for cheaper and they work. You WILL want to have the fastest computer money can buy though. The pixel count is lower than the Reverb and takes a lot of SS.

From my short usage of the Reverb I can confirm that is is clearer. The image just looks tighter is the best way to describe it. More pixels and less gaps or the need to fill those gaps with SS. If I could actually use the Reverb using the OpenVR tool to fix the slight cross eyed image I get from an IPD of 58 I would consider getting one. I have 3 squad mates that have the Reverb and they’re all happy with it. They still run into issues caused from updates to SteamVR, DCS and WMR but they usually get fixed quickly. Also, every tweak I’ve come across lately has had a direct effect for the better on the Reverb. I’m assuming because they were all Windows based tweaks and directly effect WMR. Nothing I’ve tried lately has made an improvement to the Index though. Lol that more than anything makes me want to try it. That said, my only complaint with the Index is frame rates but even they have gotten much better. Flying single player on the Round Table Mission Caucasus, my Video memory is around 15Gb but for the most most part I’m at 45 FPS even on the ground. Image quality in the Viper has gotten very good even though I don’t use MSAA. The one thing I’d notice going to the Reverb is the reduction in FOV. Regardless how clear it is, it looks like a periscope compared to the Index.

This I did not know... I could have sworn I've used it like that in the past, both with the other Viper sim and DCS. No worries. If it's correct, then it's correct.

Im seeing exactly the opposite firing 120’s in the Viper. Regardless of whether I’m in STT, TWS or DGFT, when the missile is halfway to the target it will not only stop tracking, it makes a right angle turn away from the target. Basically it’s happening when it should go pit bull.

What I was referring to when using the cursor to scale out the radar range was simply that. Using the cursor to increase my scanning distance instead of the MFD OSB’s. I did not have any targets locked at the time. Am I not able to do this? Even when in NAV mode with the FCR page up?

From your descriptions it’s sounds like an issue with ASW of some sort. When I used my CV1 there were a couple times that it made me sick. In one case it was because I wasn’t wearing the headset right (not low enough) and the other time was a mismatch in drivers after an Oculus update. Turns out I needed the latest Nvidia driver as well. I know you’ve tried these suggestions however I didn’t see which specific Oculus your using or if you’re using Oculus Tray Tool. If you’re not using it you should give it a try. While it doesn’t make a lot of sense to me, myself and two other buddies would create a profile for DCS, set ASW forced to 45 FPS, set super sampling to 1.6 and turn Pixel Density to .5. Yes, .5 lol. It ran smooth as silk and looked great. Basically anything over 1.8 PD has diminishing returns. We were using the CV1 at the time. Good luck!

It's called OpenVR debug tool. It's for use with DCS. I just spent the last ten minutes looking for a link. BigNewey posted about it but I can't find it. It's basically to help eliminate being cross eyed. My Index is fine but I would have liked to try it on the Reverb.

If it works for you I very well may get one too. My IPD is 58 as well. There is an app now that allows you to further adjust the lens spacing inside DCS. That wasn’t available when I tried the Reverb and it was slightly cross eyed. That said I’ve been pretty happy with the Index in the Viper lately. I’m going back and forth between 184% and 194% CR only and the pit is looking VERY good with mostly 45 FPS locked on even heavy online missions.

CPU and M.2 SSD. With that GFX card it’s begging for an upgrade. I was able to get my 6700k to 4.7 with an AIO cooler without issue. I don’t see the point in overclocking the GPU until you at least do so on the CPU. An M.2 Nvme drive will make a HUGE difference, both in game performance and Windows performance in general. However if it were me, I would buy a new board and CPU. Pick up an MSI or Asus board and an 8700 or 9700K. Either will hit 5.0Ghz and they’re a better bargain than the 9900k which I have. The big difference between the 8700 and 9700 is Hyperthreading. Unless you’re doing encoding or processing video you don’t need it. It also makes the CPU run hotter and has 0 effect on DCS and in some cases can cause issues like stuttering. The 8700 has HT while the 9700 does not. Lastly, if you do OC the 6700, disable HT in BIOS and it will lower temps around 8c allowing for a higher overclock. Good luck!

I noticed I can turn down brightness now with the rocker on the MFD. It does not however brighten the MFD’s without the mod though, then again with the mod they’re almost perfect :D

I guess I didn't look hard enough! Roger that!

Track file from tonight. https://www.dropbox.com/s/npwdynlc6lr94bo/Wing%20MISSION%20v1-20191207-204649.trk?dl=0

I couldn't get it to work without controllers.

I had multiple 120’s veer off sharply when about 3/4 the distance to target. The targets were hot and I had a solid lock in dogfight mode within about 7 miles. The track file is about 3 hours long so I’ll try and get a shorter one tomorrow.

My 2 reverb buddies are very happy with setting the refresh to 60Hz. Another tweak that worked as well is hitting ALT ENTER once in DCS. This tweak was posted on another thread but they report even less frame drops when using it combined with 60Hz. Thumbs Up!

Yes, I’ve been using the registry edit for a couple days but haven’t noticed much improvement. I started changing my mirroring to full screen tonight but I was flying online and couldn’t get a good idea as I didn’t have a baseline for the missions we flew. I will get a better test but both Reverb using friends reported much better results by hitting ALT ENTER once in DCS changing the monitor mirror to full screen. I believe I had less dips in frame rates as well but will test again tomorrow.

While in RWS and TWS I was unable to scale out the radar range by moving the cursor up. Neither myself nor a friend I was flying with were able to do it.