Wicked.-

The Pimax 5K+ I had was a nightmare. If there's an HMD on the market that's not ready for prime time that's it. I had the Reverb for a couple days when I sent in my Index and I can attest to its clarity and also it's narrower FOV. I believe the FOV is smaller than the CV1. Looking through it with one eye closed was beautiful though lol. My IPD is 58 and if you read what HP says it should adjust +-8mm from its stock 63.5mm. Not true unfortunately. The slider in WMR only goes to 59 and left me a little cross eyed. Too much so to fly with it comfortably otherwise I'd still have it. The only thing I use the Index for is DCS. I'm still happy with the Index itself and of all the HMDs I've tried it's the highest quality rig there is. In truth, every module I have looks and performs great, except one. The Viper. Which happens to be the only module I fly now that it's out. The only difference between mine or Supmua's rig and yours MPK is your GPU. That said, you should still be able to get good ( no judder) clarity and FPS of 45 with it. At least in the other modules. When I tried 1.4 PD again tonight, I had worse results than using my regular settings of 148%/138%. Each computer is different and subjective but once tweaked the Index will look and perform well. Except with the Viper.

I feel your pain with regards to DCS and VR. For me though, I'm in it for the online co-op and combat flying and am able to overlook a lot regarding visuals. That said I've a couple questions for you. 1. What are your specs? They are not in your sig. 2. Are you dead set on the Index? 3. What's your IPD? Being completely honest, I would brave a narrower FOV and WMR if my IPD was in the range of the Reverb. Several of my squad mates have it and love it. There is one simple reason for this. The Reverb has a much higher native resolution than any other HMD on the market. Having a higher native resolution means you really do not need any SS to clean up the gaps in pixels other headsets like the Index have. This leads to another clear advantage of the Reverb over the rest; it takes MUCH less computing power to use it. Super Sampling is what KILLS our frame rates. Period. Yet we have to use it to get a good image, eliminate aliasing and so on. Unfortunately even the fastest system available for purchase isn't able to keep up because DCS can only utilize 1 core and 2 threads. Oh, and one of those threads is for audio only. My advice is if you can use it, send the Index back or sell it on Ebay and buy the Reverb... If I could, I would in a heartbeat.

I'm wondering the same. I thought there was a firmware update along with 1.8.20 but my devices all say up to date.

Call it a placebo effect but I almost always end up switching back from 204% to using 148% CR, 138% DCS Application and Pixel Density of 1.0. That said 204% is what I consider my default fallback/safe setting when testing. Using DCS App at 138% seems to add saturation making the image richer in color. Again, it could simply be a placebo effect.

So your Video Tab Custom Resolution is at 120% with motion smoothing unchecked? DCS Application is set to 100% and your in game Pixel Density is 1.4? I'll test tomorrow. As to the question about motion smoothing on, there are at least 2 areas to turn it on. I keep the one in video tab on, otherwise it's a mess visually. There is another one in the Application Tab DCS with 4 options I believe. Global, Always Enable, Always Disable and Force on which cuts frames to half. This one I leave at the global setting. If you check force on, you can watch the monitor go from green to yellow instantly. If you turn both off, I believe it defaults to reprojection.

Update on my performance issues, my 5 month old Asus board was bad. My frames in the Viper are back to 45 running 148/138 and 2x MSAA. MFDs still look like ass though lol.

:thumbup:

Awesome! I'm not delusional after all lol. I reformatted my computer today but based on what you're seeing it probably won't help. Do you have a link for the blank lens inserts? I think I'll try them.

I'll let Supmua confirm but I believe you will only get 64 buttons in combination with the FSSB3 Lighting.

I reformatted my computer and after installing VC++ 2017 RS Tools will not install and says I need to install VC++ 2017... Which I've done. lol I ran into this problem several years ago when I bought the TUSBA. Does anyone remember how to get this to work? Thanks *edit* Fixed. Uninstalled the 2015-2019 and manually put them in.

I only fly open beta so I get what you're saying and mostly agree. I guess I'll shelve it like I did the Hornet on release. My complaint is in comparing two vastly different rigs and determining there is no issue because the slower rig is running fine. Every game these days have minimum specs and recommended specs. The OP and myself are well above recommended specs and yet we are still having performance issues. My fault for buying it.

It may be possible. I know you can change resolution options when changing viewports for exporting MFD's though that's probably not the same thing. I don't know how to do it and haven't messed with exporting MFD's since I got VR.

Looking at the specs in your sig I'm not sure you could notice. Your running a Dell Visor, DDR3, a 1080Ti and 4.4Ghz. What are your settings in DCS? I say this because you've probably gotten used to your settings which are MUCH lower than what others with newer maxed out systems are using. If DCS is basing performance on your hardware it would have been nice to know that up front. The difference in performance with the Viper is a fact. My other modules are not effected. They look and perform as they have for a while now. The Viper was better on release, much better actually as I was able to up my normal settings for the Hornet with virtually no frame hit. After 10/31 performance is below all other modules and almost un-flyable. I'm not being a dick but I am frustrated at the lack of give a shit shown to reported problems. At the end of the day, your customers haven't only invested $60-$70 on buying a module but in most cases thousands of dollars building systems to run your software. What EXACTLY do you need from me to examine what's going on? Where should I send it? Thanks,

LOL, you've just described the last hour of my life. I tried updating the headset but it said it was up to date as well as the base stations. I'll update NV drivers next. *edit* I'm all up to date. My issue now is still performance in the Viper since the Oct. 31st update. It's seriously pissing me off that they won't acknowledge it. I guess it hasn't crossed their mind that we customers might fly on this software exponentially more than the 120 employees they say work at ED. I realize not everyone is seeing it but my question is: would everyone notice a difference? Or is it only higher end system owners that are seeing it because of the high settings we are usually capable of? Sorry, venting lol.

I'm seeing exactly the same thing. MP menu is not that bad for me but overall performance of the Viper has taken a massive hit. I have no mods installed at all. Where would I get the log file to send in? Ive had to dial my settings down to where MSAA @ 2x doesn't do anything. It was the Oct. 31st update when my performance crashed.

Reboot fixed the Stable version but haven't gone back to the beta yet.

Update. SteamVR will no longer start. Beta or Stable. Rebooting.

I just got the new SteamVR beta and now SteamVR keeps failing to load. Switching to stable.

Here's a good pic of the HUD.

Me too, ain't she pretty?! lol

You should be seeing a blue Bullseye in the bottom left corner of at least the left MFD and blue range rings on the HSD. They're there but almost impossible to see without zoom.

Yes it is getting hard to justify. After more research on switches I've found replacements for the Otto's. The problem is they're still expensive as hell. I'm looking at $450 before I even think about the grip, base, arm and tensioner.

I'll turn on shadows and see if it helps. If it does, i can hopefully turn off MSAA.

It was introduced before the 50 as the Block 40's have it as well I believe.

I wish that was the problem. I do not use shadows at all. No texture shadows and no terrain shadows. Both are off. Never liked them. The amount of aliasing seems directly related to the position of the sun. It's different for each theater, in PG it's not as bad in the evening and morning which is the DCS sweet spot for all modules. Those pics I posted are from Caucasus though just after dawn and that SS looks exactly like that in the Index. No other module looks that way. They are crystal clear. I don't get it...