Wicked.-

Really? When I unplugged my touchscreen things seemed to get worse. I have a Samsung 49" monitor running at 3840x1080 so not quite 4K and until recently a Dell 21.5" touchscreen. It seemed to run better that way lol. At this point who the hell knows. Nothing is consistent and basically I've learned to live with it. Glad you got a performance boost though.

DCS is CPU clockspeed/GHz dependent. You really want to be at or above 5.0Ghz. AMD's aren't going to do that.

Good deal! Glad it's working for you! If you're not going to use an AIO water cooled solution, buy a tube of Thermal Grizzly Conductanaut thermal liquid metal/paste. It will also lower temps by least 5c and probably more. It's the best thing I've tried and I've been building computers and overclocking since the mid 90's.

Awesome, get the 8700 lol. Had I known then what I know now I would have done the same thing. Correct me if I'm wrong but doesn't the 8700K lack hyperthreading? If so that's one less thing to have to mess with.

I feel your pain lol. Though I'm not having any major issues ATM, it seems for no reason it will work perfectly one day and the next it takes a huge shit. Having made no additional changes I'm beginning to wonder if every time I fire up Steam or DCS there are changes being made while loading. There's no other reason I can think of that would make the game crater after flying perfectly. I don't think it's only the Index as I have friends with the S, CV1 and other units saying the same thing. I will say the Index is more effected by packet loss when online than other units including my CV1. As I fly exclusively online unless testing I see stutters in the frame rate and frame tears before other guys flying with me see them. What's really weird is when these things happen my frame counter is usually locked at 45FPS running 90Hz. In other words there shouldn't be any frame drops or tears according to the frame rate. We are currently flying a mission called Skyfox on our server and it has a lot of triggers and a lot of activity. But the frame tears don't really happen when there's a ton of things going on, rather there's usually nothing going on when it happens. Also, things get progressively worse the longer I'm on the server. Like a cache is filling up and not purging but I've not found where this is happening. My current settings have been working well the last two nights flying minimum of 4 hours straight. SteamVR Video Custom Resolution 148% and DCS Application SS 138%. No MSAA. These are the only settings I mess with as all of the other settings I use are good to go.

Nice setup with the G13. I've never been able to find a good position for mine.

Do not get the 3900X unless it for something other than DCS. The extra cores will not help. I had the 6700K and could run it at 4.8Ghz if I remember correctly. Your first and best option is to OC the current 6700 as high as you can stable. Disable Hyperthreading in bios to bring your temps way down. DCS doesn't use it and the temperature drop could be as high as 10C. If you can't get it to 5.0Ghz or better, buy a new processor and board. I think the 9900K is cheaper than the 8700K at the moment but most of us that compare settings with the Index have 9900's I believe. Do that first. It's pointless to get a 2080Ti without having a CPU that can send it data quickly enough. 9900K's clock to 5ghz basically out of the box. The 6700 doesn't have the clock speed to push the 2080Ti. That's what you need for frame rates. We are able to do the process lasso stuff, and SS experiments because we have the horsepower to begin with. The Index needs all it can get because of the lower native resolution which forces us to use supersampling.

Imacken, I received the Vive controller today but found out quickly that Lighthouse 1.0 controllers do not work with Lighthouse 2.0 lol. Back to ebay they go!

I just rolled back to 436.02 and tested again. It definitely has less frame rate drops than .30. I also noticed that when I use 138% for DCS App and 148% for Custom resolution there is a greater frame hit with 436.30 than there is using 204% and the other SS settings at 100%. There is no difference in frame rates between the two settings with 436.02. I tested these settings in Instant Action Free Flight for the F/A-18.

I just flew about 20 minutes on our squad server and it seemed to be a little less solid than the 436.02. Granted I flew several hours last night with 436.02 and only a very short time today. I did see a couple more frame drops in the instant action I test with than usual though.

I went back to the Nvidia site and looked for 436.30 but again, on the main DL site for GeForce drivers, it wasn't there. But when I searched for ALL drivers it showed up.. Odd.

Very nice! I've though about it but like Dburne, I doubt I'll drop that much cash on top of the at least $5K I've already spent on DCS lol. Still, looking forward to the unboxing. Congrats!

I upgraded from a Zotac Amp 1080Ti Extreme which ran @ 1.9Ghz to the Asus RTX 2080Ti OC 1.9Ghz. I saw an increase of 8FPS in minimum FPS benchmarks which is what matters. That's $162.50 per frame which is pretty pathetic when going to a whole new generation of GPU. I don't give two shits about ray tracing because it doesn't do anything to increase performance in DCS. Also, I don't use a monitor other than to start SteamVR, DCS, Discord and SRS, so the ability of the RTX to push more pixels in 4KUHD games is wasted on me. All that being said, I don't see the point in OC'ing the GPU because the return isn't worth the risk. I use motion smoothing and can't stand the up and down spikes in FPS without it. Therefore, if overclocking both the CPU and GPU do not get me to the next level of locked FPS (45-60) what's the point? On the other hand, overclocking the CPU is TOTALLY worth it because you actually see the results in FPS. Unfortunately I've hit my stable limit at 5.1Ghz with HT off at BIOS.

I use the drop down boxes for the desktop 2080Ti to search. Weird. I'll look again tomorrow.

Did any of you notice that Nvidia has take down some of it's recent drivers and the most recent one available is 436.02? I noticed the other day the link they had to the most recent at the time was a broken link but I didn't think it important enough to comment. Today, working from home, I hopped on DCS and the damn frame tearing is back. I've made no changes to anything and this is beginning to piss me off. I don't think it's DCS though but instead either Nvidia or SteamVR. I am seeing the frame tearing in the DCS UI, while looking at the online server list. Meaning it could have something to do with network bandwidth. I checked that and am getting a smooth 200MBs DL and 11MBs upload so that's not the issue. I then decided to update the Nvidia driver again after seeing Supmua's previous post. When I pulled up the latest driver it was 436.02. The problem with that is, I had 436.15 installed which is no longer in the list. So, I guess they found an issue but didn't bother telling anyone that I've seen. Regrdless, I'll now be testing 436.02 again with the most recent SteamVR stable release. Just when everything was perfect yesterday......

Roger that.

I decided to set MSAA to 2x and it ran really well in single player. At least back to normal. However I've gotten used to no MSAA and at distance objects are slightly blurred. But, without it, on my squad server, I was spotting bombers without zoom at 18NM. I guess there's no pollution in the Persian Gulf lol.

Supmua, definitely dont OC your video card. The risk is not worth the return ever. Not only that, it can only process what it's sent by the CPU. From what I've seen, just the amount that is sent to the GPU works the hell out of it but my Asus 2080Ti OC never peaks higher than 80% usage so there's room if the CPU can send more.

I just finished a 5 hour long marathon of flying the Snowfox mission on our squad server. ROCK FREAKING SOLID! lol I have no idea why other than the new SteamVR. I'm using 204% everything else 100% and no MSAA. I didn't notice a single stutter even at Kasab which is normally a hit

It could be part of the optimizations. I was one of the ones that saw a noticeable increase in performance with my CV1. That increase drained away after subsequent updates though. I agree the other cores are working on DCS and probably doing a better job now. To my knowledge though, DCS data still comes through a total of 1 core using 2 threads. 1 thread is for nothing but sound (seems wasteful) and the rest comes through the other. I originally tried setting affinity the way you are but ended up going with the REALTIME priority approach in the end. It will give you warnings that Windows my have a reason for lowering the priorities to High for security reasons. However, I built this computer for 1 thing and 1 thing only: Flying DCS in VR. That's it. There is no other priority as far as I'm concerned lol. I'll do a complete dance and wipe this sucker in a heartbeat without a second thought. Windows can kiss my ass. :D

I'm pretty I use the same PL settings as Nagilem but set DCS and VR compositor to RealTime. I don't bother with assigning cores, telling PL those programs get realtime priority is enough. Nagilem, while it's true that DCS lights up all cores with activity, the data being sent to those cores is supplied from a single thread from a single core. Once the other cores receive the data from the single thread they make light work of it. Regardless, it's still bottle necked to 1 core, 1 thread. Like sucking through a straw instead of a firehose. I can have an assembly line with hundreds of workers but if I only have one truck supplying the parts for assembly, the assembly workers are limited to the speed of parts deliveries.

I installed Elite Damgerous as a test and it was microstuttering a bit as well. In fact, just turning my head back and forth in the loading screen of SteamVR would cause it. Even when I turned the settings down to recommended custom resolution at 150% and everything else at 100% it would do it. Once again I switched SteamVR to stable instead of beta and set it to 204% custom resolution, everything else 100%. No MSAA. This time I set Steamvr compositor in Process Lasso to real time priority, and another SteamVR process that was using a lot of resources to real time. DCS is always set to real time and it seemed to improve it quite a bit. I won't say it's fixed because I ran out time but I'll test it tomorrow. The only major change to the computer in that time was removing my touch screen. I can't see any way that would mess up the Index.

I do not believe the Nvidia settings I changed have anything to do with my Index' current shitty performance. I was flying with a squad mate tonight who has the Rift S, he said his performance went in the toilet the night before last. About the same time mine did. He made no changes prior to the performance tank which was so bad he's now using his Track IR. Neither of us received Windows updates either. Pretty sure it's something to do with DCS but I haven't made any other DCS changes. I actually removed a touch screen monitor I used for the other Viper sim which if anything should have put less load on the gfx card. One other thing. The microstutters and screen tearing has happened before from lag spikes. After checking my internet speed it seemed a bit low so I installed a brand new NIC and my speed jumped up 40MBs. It had zero effect on Index performance online.

My Index hasn't been the same since I adjusted the settings in NVCP. Even single player it has micro stutters and so far, changing drivers, SteamVR beta to Stable and back, changing DP ports nada. I have noticed that when I turn on AA in NVCP, the base stations while in the SteamVR loading screen are ghosting. Whereas, normally they look crisp. Micro stutters are killing me. May have to go back to the CV1.