Wicked.-

Clock wise, I think it is seeing the speed of my card. It sets the resolution higher than the actual native resolution of the Pimax which to me is a head scratcher... I've boxed it back up for now and returned to the CV1. August Aurelius makes a point I had already realized but chose to ignore. No hardware on the planet right now can push enough pixels to fill the higher res HMD's. As long as DCS is limited to 1 core processing it'll be a long time before it gets much better. DCS World was released with native support for the Rift and in the last few days since the most recent update I've noticed dramatic improvement in image quality. I don't have to zoom to read gauges anymore, I can simply lean in. With my IPD of 58 and the need for readers to see clearly in the S, it looks like the CV1 is my world for now.

We both run almost identical specs so power isn't the issue. I also have a Pimax 5K+ I've been trying to get to run well but so far it's unusable. In trying to find different solutions for Pimax I changed my Nvidia driver back to 425.31 but when it didn't help I went back to the CV1. When I did, the CV1 stuttered badly with that driver. So I changed back to the newest 430.8x and it was smooth again. That was until I overclocked the graphics card and tried to run DCS. I immediately had ghosting in the Rift, both in the Oculus Home environment and DCS. If I didn't fire up DCS, the overclock didn't effect the Rift, only when I tried to start DCS did the ghosting start happening. Once it started I would have to reboot. Prior to rolling back the driver I didn't have issues overclocking the graphics card and running DCS so it could be a corrupted driver. Anyway, you may try redoing your Nvidia driver. I'm going to look for a program that completely cleans out the current driver and reinstall. Hopefully that fixes it. Otherwise as I said in a previous post, the image clarity in the 18 has been drastically improved. I need only lean forward slightly to make out letters and symbols on the MPCD and see texture detail that I would normally need to VR zoom to see.

Err, I have checked the override in SteamVR lol. By doing that, I get the impression that it ignores any changes made by the Pitools render slider. By unchecking that override I was trying to use Pitools to change the resolution size. Regardless I'm not arguing with anyhing you've said, I'm just playing catchup with all the different settings configurations that have already been tried. I just haven't gone back through them yet. So, if I understand correctly, 2560x1400 is the native per eye resolution of the Pimax 5K+. Why then does SteamVR insist on setting it to a higher resolution? It always tries to set it to at least 2800x1920 or somewhere in the range. Why doesn't it pick the standard resolution and then let me adjust my in game PD? Granted that would be just like how the Rift works but it would sure as hell simplify things. One thing is for certain, Pitools smart smoothing sucks. After the last 2 weeks I've really come to appreciate ASW.

After messing with different pitool versions, I don't think the render slider works in Pitools. At least not in versions prior to 132. I slid it all the way to 2.0 and it didn't make any changes that I could tell either for FPS or clarity. I noticed that SteamVR says it fixes your resolution based on the power of your graphics card. It sets mine at 60% which puts it at 29**x2*** something. Moving the render slider in Pitools doesn't do a thing. If you check the set custom res box in the SteamVR settings/video tab, then you can scale the res up and down and that works. The smart smoothing and FFR seem to work as well as the other sliders though. So I'm basically left with the SteamVR resolution setting and PD in DCS to try and get a good balance of clarity and FPS. If you go too low on either the image is crap. As Highway stated I realized I don't have to use Pitools at all as long as it's installed. In fact, with a couple Pitools versions it would work upon booting up the computer but disconnect as soon as I started Pitools never to turn on again until reboot lol. I wonder if those who've recently received the XR's are having the same issues.

Ran into another weird occurrence with the Pimax today. After trying different settings I decided to switch back to the CV1 and fly a while online. I turned off Pitools and fired up Oculus Tray Tool, then loaded DCS to adjust the settings. Before getting into DCS Oculus home was stuttering. That rarely happens if ever anymore and come to find out it was the older Nvidia driver I had loaded up for the Pimax yesterday. Switched it back to the current one and all was well. After a couple hours flying I decided to see if the Pimax would work with the new driver and Pitools .109. The first thing I noticed was the headset was on and projecting the Pitools home screen... but Pitools was not running. So I fired up Pitools and it wouldn't connect, but the headset was on. Then as I watched my gfx card temps where running at 71c with nothing but windows running. I then unplugged it and the temps immediately dropped to 39C. When I went back to look at the temp logs, it was obvious the Pimax was on when the Oculus was on and it was causing the temp spikes. WTF lol. I guess you can't have them both plugged in at the same time regardless of whether or not Pitools or Oculus home are running.

I've noticed that like my CV1, image quality in the Pimax 5K+ is greatly dependent on the PD in DCS. I haven't tried cranking up the render in Pitools while lowering the SteamVR resolution to 30. Will try it tonight. The only reason it's not on eBay is I think there's a good chance it will get better with future Pitools updates. However I still think I've got a bad cable and will try to get another new one.

What are your frame rates like? Hit right CNTRL and Pause, then if they're not at 45 FPS your ASW is off.i did a totally clean install yesterday and noticed judder which I've NEVER had in the Rift. I've had it lag but not judder. When I looked at my FPS they were spiking all over from 45-90. I immediately downloaded Oculus Tray Tool and made a profile for DCS to lock in 45 FPS for DCS and it fixed it. It's possible I set something in the nvidia card settings that caused this, or the new update is not letting ASW work. Since I did that, the cockpit in the 18 looks the best I've seen it with my normal setting of 1.8, no FSAA, shadows flat, terrain shadows flat, AF at 16X and everything but civilian traffic at high.

I'm curious which Pitool version and gfx card drivers everyone is usuing. I ask after spending several hours on Discord with a buddy who has the 8K, loves it, says it's looks better than his O+ and is smooth as silk. Hearing him talk about it made me get the 5K+. As we were going through his settings I realized he didn't have the FFR option under Smart Smoothing. He in fact is using the older .109 Pitools whereas I'm using the current .132. Seeing this I asked what nvidia driver he has and it was 425.31 whereas I'm using the current 430.86. My biggest frustration with the unit has been getting Pitools to see the unit and connect it though it's never been disconnected and then having the lighthouses track being only three feet away with a clear view. I would have to reboot, fire up Pitools and wait like 5 minutes for it to connect, then wait as much as 7 minutes for the lighthouses to track, if both did at all. After I rolled back to .109 and 425.31, the unit connected almost instantly and the lighthouses likewise. Almost as smooth as a Rift. Those two simple changes kept me from stomping the thing. It's also much sharper now in the Pitools loading screen with the planets but I still can't eliminate the judder. He said he is running SteamVR at 100% and Pitools at 1.0 and that he' has his PD in DCS as high as 1.8 with no issues. He did however have issues when he got the new pitool. Specifically judder. But with the .109, it's smooth and clearer than an O+. His current rig is an i7 8700K at stock 3.6. I can't remember the boost clock but I think it's 4.5 or 4.7. He's running an RTX2080Ti from PNY at stock 1650Mghz with 64GB memory and an M.2 drive. I on the other hand am running an i9 9900K @ 5.0Ghz on all cores with highest temp at 74c, Asus RoG Strix RTX2080Ti @ 2000Mghz with highest temp at 67c, 64GB memory and an M.2 and can't get it smooth regardless of SteamVR custom resolution under the video tab setting or pitool setting below 1. Is it possible I have a bad cable lol. This is ridiculous.

Keep at it. You should be able to hook up with the tanker while he's in the turn. VR makes it infinitely easier with realistic depth perception. As to the stick, what are your curves set to? I have a dead zone of 10 I think and set both pitch and roll curves to 30. It will keep the roll rate slow and more precise until you need it. The manual says use your trim.. right. Lastly there is a Japanese brand white grease made for plastics that is really good, I'll post the name when I find it again. I would deflect the stick over and squeeze the grease in before taking out the gimbal. The wires that go through the gimbal break easily and Thrustmaster charges $70 for a replacement ribbon cable. Splicing them back together required more delicacy than my normally dexterous digits were capable of. I just bought another stick lol.

While I don't have one, the FSSB makes the Warthog like the Real Viper stick. It's force sensing and only moves a quarter inch in the actual jet. Realsim has made them for years for the Cougar and Warthog. I have the TUSBA for my F-16 Cougar TQS.

Having owned both now I would take the S all day over Pimax. The Pimax has the potential to be great and the 170 FOV is awesome but that's about it. You have to give up so much both in image quality and frame rate I end up with graphics worse than the CV1. Way worse. I've barely flown in the week I've had the Pimax. Instead I've spent my flying hours dicking with Pitools, Steam and SteamVR trying to get an acceptable experience.

I'm flying on a brand new system tonight. Specs in my sig. I guess my concern is that while the Rift is a lower res and narrow field of view, even at high settings of 1.8PD/Shadows Low/Terrain shadows flat/No MSAA/No SSAA (I saw zero effect from this) and most everything cranked up except grass, chimney smoke and pedestrian traffic it is silky smooth. With the PIMAX I can never get rid of the judder without making the image look like ass. I'm still trying all your suggestions but I'm assuming Pitools is going to need a few more updates before it gets worked out.

Today I got a chance to mess with some of the options on the 5K+. My system specs are below but today I was using a new Asus RTX2080Ti instead of the 1080ti. I have a few questions. The first is IPD and fitment of the unit. My IPD I believe is about 58 and I can just use the unit without using IPD offset but the image is never really sharp regardless of where I set it. I don't wear prescription glasses but I do wear 1.75 readers to read but I've never needed them in the Rift CV1. Does anyone else need readers but not need them with the 5K? Second question. Is judder always present? No matter how low I go on settings it's always somewhat present even though I'm getting a solid 45FPS with the DCS frame counter. Judder, I'm assuming, is when static objects seem to vibrate for lack of a better word, when rolling the jet or flying by. I've followed and tried most of the recommended settings listed in this thread but haven't been able to get rid of it. Thanks for all the previous work and suggestions in this thread. Otherwise I'd have tossed it by now lol.

Welcome to VR!

Awesome! We had Cubpilot's hall sensor upgrades for years. Glad to see someone's working on it. I already have the Realsim TUSBA which cleans up the old pots but the Hall sensor rocked. At one time I had six Cougars, I would wear out the gimbals on the stick in a year and a half or two so when they were selling for $150 new at Fry's I bought a few more. For anyone looking to by one beware. They are made from Zinc and fall apart within 3 years at most. You can litterally squeeze the throttle too hard while it's off the arm and shatter it. (I've done it!) Foxy software doesn't work for shit on Windows 10 so you'll be using the in game setup for programming which will leave you wanting for switches and rotaries especially in VR. For the stick, get the Warthog. It the same thing but has an extra button on the CMS which is great for the slap switch. I currently use the Warthog throttle as well even though I have two Cougar throttles. This will change when they release the Viper as that's all I'll fly and won't have a need to change out throttles. As to how the HOTAS works compared to the A-10 or 18, it's much more simple to me. First, the cockpit avionics setup is Master Mode dependent. You have AA, AG and Nav. On the throttle you have a 3 position dogfight switch with MRM mode (A2A past 10 miles AMRAAM's), Nav/AG and Dogfight or ACM mode. Depending on which position the switch is in, all avionics will be configured for those modes. MRM and Dogfight positions will always pull up settings for those modes. The Nav/AG mode is changed by pressing the AG master mode button on the ICP (UFC for those new to the Viper). Each of these modes can then be configured more specifiacally like RWS/TWS/VS/LRS in the MRM mode by the MFD and the TMS switch. Or slew, 10/60 and bore in Dogfight mode by using either MFD's or the Cursor Zero button or TMS switch. Basically, you set up the different pages of the MFD's for what you'll want in the data tape cartridge. You can have three pages per MFD per mode. You can call up more but you'll need to use the MFD to do it. Otherwise you DMS right to cycle right MFD pages and left for left MFD. This covers only some of the HOTAS functions and none of the ICP functions. I will say after using this setup for 20 years going to the A-10 setup felt arcane. It's like it's over complicated. As compared to the 18, you can do a whole lot more on the HOTAS in the 16 which means less hands off the stick and throttle.

There's a mountain of F-16 stick and throttle how to' s for the uninitiated for almost every joystick or HOTAS that is halfway good. It would be epic if TM released a new modernized TQS. I would pay a heavy penny for it.

Well shit! I've been at it for four days now, probably 40-50 traps. Now that I know it's possible this is all I'll do in DCS until I get a 75. My issue is always bank angle. Nice job.

This is too addicting.. I'm going to forget how to blow shit up! Highest grade I've gotten is 69 so far. Outstanding trainer! Thanks for the contribution.

That's good to know about SteamVR even though as an Oculus user I already hated it lol. Nothing beats the smoothness of Oculus' native integration to DCS, or the software in general. That's another reason I didn't keep the Odyssey. Steam, steam vr, WMR and Bluetooth just to get the graphics to the HMD is a lot of failure points. With the Rift, I fired up DCS and there it was! Well, except turning off the damn controllers. Sadly though, I can't use the S as much as I'd like to. At 48 I wear readers to read but otherwise my vision is excellent from just past the reach of my arms outward lol. Without the readers in the S I can't get a clear picture. When using readers I can't get the headset to line up and stay that way. It was making me slightly nauseous. I put the CV1 back on and even though the picture isn't anywhere near as good its better than the S all around for me. I only hope I don't experience the same thing in all of the new HMD's.

Ok, after some further testing I found out I need to where my readers when using the S. I'm not sure why that is as I don't need them with the CV1. After figuring this out I flew for several hours online and it is an overall much cleaner image. I only need to lean slightly in to see the color map in the Hornet on the MPCD and make out the symbology and markings. That's a huge improvement as before I would need to zoom in to see and read it. So as far as image goes it's definitely an upgrade. However, as far as replacing the CV1 as the unit I'll use for the next 2 years hopefully, this won't cut it. If I didn't have to shell out another $400 it'd be great lol. But since I do, I'll probably return it and spend a bit more for the Index. I do not dig the halo head mount at all. It simply isn't as secure as the catchers mask style mount. Also the speakers are lacking which I already knew. Even though I can wear my headset fairly comfortably it's a pain in the ass when I need to alt tab. Lastly, the FOV seems smaller than the CV1. That more than anything is a deal breaker. I wish I'd had this in the beginning though as it has a much better image.

After more testing it's not just the IPD. I can see that the clarity is better than the Rift in certain respects but I can't get a stable position and constantly have to adjust. I don't think it's going to work for me which means another two months until the Index is available.

It was IPD. It seems 63 is my number. I could push it all the way in on the CV1 without effecting it much. As to the aliasing, I used PD in DCS to get rid of it instead of MSA as it worked better. I think it will be the opposite with the S.

I picked up the S today and have noticed a few things compared to my CV1. 1st. Big time aliasing compared to CV1. 2. Clarity outside the pit is horrible. That being said I wonder if it's the IPD setting that's causing the blurriness. That's kinda what it looks like. When you adjust IPD in Oculus home for CV1 you adjust the tab under the headset in and out so the vertical lines of the cross aren't blurry. When I use the software adjustment in the Oculus setup for the S I'm not seeing a difference visually that corresponds with the IPD number. Is that normal?

I agree bumping up to an i9 9900k would make a noticeable difference. I don't however think the 2080ti would make enough of a difference even then to justify the cost. But you've helped me make up my mind which is the best upgrade for the cash and that's a new CPU and mobo. My Zotac is clocked at 1900 something stock, whereas the EVGA is 1600 something. So, other than new technology for Vulcan (which I won't use) there's no benefit that I can see. I just thought that at $1250 for a new video card I would see a considerable amount of improvement in settings. Thank god for the 14 day return policy..

Since PG theatre came out I started noticing a line that went from one side of the screen in my Rift CV1 to the other, halfway down from the top. I wasn't sure what was causing it but it wasn't enough of an issue to make me take time away from flying to fix it. With the near release date of several new HMD's I decided I was going to upgrade my Rift and most likely get the Index. Knowing this, I bought the EVGA RTX2080Ti XC Gamer to replace what I thought might be a faulty Zotac Amp Extreme GTX1080Ti. After installing the RTX I immediately fired up DCS for some online testing. The first thing I looked for was the line.... it was still there. The next thing I tried was upping the graphics a bit, mainly raising the IPD to 2.0 from 1.8. Everything else I left the same. There was zero performance increase. Meaning the GTX had the same performance as the RTX. So, my question is: is there ANY reason to upgrade to the RTX from my GTX knowing that there isn't anything wrong with the GTX and, I only use this rig for DCS? I have no need at the moment or near future for ray tracing unless it's in the next DCS update. Thanks,