whitav8

@dburne, I don't have (nor want to buy ) the Touch controllers. Is there any hope for me to use Rift Core Beta with just a mouse - that is, could I just start applications with a mouse (even if I have to use a Windows 10 Icon outside of the Rift. Right now, I use the "classic" home but I wonder if they will take that away eventually. Thanks Dave

One thing I forgot to mention is that I use Project Lasso to make sure that OVRserver_x64.exe runs at high priority. I started that a couple months back because I was noticing that Oculus Home was "sluggish" - I don't know if that helps tracking. You could try by using Task Manager.

@SkateZilla, I flew around with heavy maneuvering and lots of head turning in Aerofly FS2 in an F15 today for a half hour and didn't see any problems with 1.11 Runtimes.

@MrReynolds, Glad you have the DK2 going - except for a little more SDE than CV1, I think you will like using the old unit - it has advantages (no god rays, stays cool, only requires 75Hz, not 90HZ which gives you 20% more chance of keeping up with Riftsync). Also, I run my CPU at 4.2Ghz and with that and an Nvidia 970, I am able to run with SuperSampling at 1.5. I do not like ASW so I turn it off with CNTL+Numpad_1. I do wish the framerate of DCS was better - more like Aerofly FS2.

@MrReynolds, Just to give you confidence, I have a DK2, and running the latest Oculus Drivers(1.10.2.322199) on Windows 10, DCS runs fine in VR.

Yep, I'm seeing a steady 25 fps taking off in formation with a couple other A-10s and it should then go to 40 or so but it doesn't. This is with ASW off - with it on, I get some really strange texture distortions and not really any faster anyway. Dave

Let's forget the missions - just an A-10C ready for takeoff as a test. I agree that the frame-rates are down - with both 1.5.5 and 2.xx. With a A-10C facing away from Las Vegas at Nellis, with 2.xx (not VR) - I see ONLY 54 fps - that won't cut it in VR and any kind of RenderScale (SuperSampling) settings. With the A-10C ready for takeoff in 1.5.5, I see about 94 fps - still not enough. We need about 150 fps or more in nonVR mode. What has happened?? Dave

IS anyone else having severe pausing (hourglass and no head tracking) just inside Oculus Home but I think OK in DCS World?

One of the best parts about War Thunder is the ability to get 90 fps without ATW/ASW interpolating frames. The fluid flying is great - but make sure you get out the old Oculus Debug Tool and set up Pixel Density Override (Render Scaling) at 1.4 or better - they don't have it incorporated yet. You also have to choose the PostFX effects in the graphics options and fiddle with that to reduce image shimmer. Try some of the User missions or Single Missions - not many available at the start - but the Chronicle of a Dive Bomber mission is quite fun at treetop level. Their VR forum is as follows: https://forum.warthunder.com/index.php?/forum/604-oculus-rift-htc-trackir-problems-and-advice/

@Derek, I really appreciate your taking time to investigate for the DK2 and ASW. I had tried it, couldn't tell if it was working, but I can't hold 45fps anyway - maybe away from cities on DCS 1.5 I am enjoying Aerofly FS2 because it has such great performance that it is providing 75 fps (a Nvidia 1070 will provide 90fps) always - smooth and fluid - even with quite complex instrument panels and beautiful photoreal terrain. They don't have a lot of FSX/P3D features(ATC,AI,FMS,...) yet but if they keep that on cores other than the main graphics one, it will be great - non combat though. I hope the DCS devs can eventually optimize the graphics loop like Aerofly has because our CPUs really aren't getting any faster soon. Thanks again - I appreciate your input on these forums! Dave

@average_pilot, I agree that 90fps is the key to the best experience - totally fluid movement without ghosting of close objects while at 400 knots or stuttering. I mention a new flight simulation that was recently released that has great VR in that it does meet the 90fps with graphically complicated cockpits and photorealistic terrain with plenty of buildings, trees and other objects such as many static aircraft at airports. This sim is Aerofly FS2 and it shows that on an i7 at 4.2 Ghz with at least an Nvidia 970, that two 100 degree field-of-view scenes for stereo and at least a SuperSampling ratio of 1.5 can be completed in an 11 millisecond frame (90fps). You can see that the Aerofly FS2 image in non-VR mode is running at 250 fps or 4 msec. - so two of those views plus another 3.5 msec for supersampling just makes the 90 fps. I mention this only to encourage the excellent developers of DCS World to strive to purify the graphic rendering loop from the complex calculations required for the aircraft systems, ATC, AI movement, weapons flight, etc and let them run on other cores. We aren't going to get much faster than 5Ghz CPUs and slightly faster Pascal video cards any time soon so I just want the graphics loop to be as fast as it can. The difference between sub 90 fps with ATW/ASW and a straight 90fps is really amazing! Thanks Dave

@Derek, I am still using a DK2 and I'm not sure but it sounds like ASW is not supported on it. Not sure if you could easily try yours or not. Perhaps you have read about this issue. I am already on Win10. Thanks Dave

@KCBallin, I would guess that unless you overclock your CPU (you said "Specs: i5 4590 @ 3.3 ghz"), you will have slower FPS. Most of us are running at 4.2 or higher and that might provide another 10+ fps. Also, make sure you are running with "prefer maximum performance" on your Nvidia settings for Power Management mode

One option you can try with regard to Win 7 and Win10 is to have a dual boot system which is the way I operate. It allows me to make sure I can test out Win10 for all my desired applications before I finally turn Win7 off. It did require that I use my older/smaller SSD (just 128gb) for win10. Someone around you probably has the Win10 install on a flash drive.

While I really enjoy flying the A-10 and Huey in DCS World, and I never feel nausea as long as I am inside the cockpit (looking toward the rear and being outside the cockpit is another story), I don't like being at 45 or even 27.5 FPS (on the ground at Nellis at dawn with lots of AI) even with ATW helping - I have to shut my eyes when I turn my head too fast and I don't like the ghosting (double images) when I look sideways at the ground objects. What I do enjoy is flying and maneuvering in War Thunder with the same PC and video card which will in fact provide a 90fps experience - no ATW needed (no ghosting). I suggest you try it to see how it feels for you. Maybe not the arcade battles with lots of tight turning but just the Preview flights without the need to dogfight. At least you can see if it helps to have 90 fps. Make sure you use the Oculus Debug Tool to set Pixel Density at 1.4 or so and occasionally - for testing purposes - turn on the Performance HUD overlay to make sure you are getting the app framerate at 90fps.

When you manually start Oculus Home and have the 2D window with the large icons of the different apps that you could purchase, the top title bar has the gear-shaped settings icon, select that (Settings), then General and the version will be printed out at the very bottom in gray font.

OK - I stand corrected regarding the automatic update of Oculus Rift runtimes. I guess I just happened to be near the last to get the update and by chance, just after I re-enabled the Auto Update switch on the Settings page, I then got the update to 1.8. It certainly would be nice to ask to be near the end of the updates or maybe have that switch actually include the re-enabling of the runtimes update since I like to wait and see what troubles are being seen.

One thing I recommend is to disable the Automatic App Updates on the Settings->General page and then wait until you see on various forums (this one especially) that somebody is having success. I did that for 1.8 and then rebooted with it enabled and it came in a few hours. I still had to hope I would be OK since it seems it is different for each system config.

@funkyfranky You might want to check the Oculus Support forums - for example: https://forums.oculus.com/community/discussion/42771/whos-still-having-constant-headset-disconnect-errors#latest I also just moved to 1.8 runtimes on Win7 and after rebooting, I seemed to be OK - I've never had any disconnect problems. I use the Inatec USB3 card Oculus recommends - some people even have problems with that though - maybe a motherboard issue?? I will check on my Windows 10 PC and report back if any difference

On Oculus and Reddit forums, there is a lengthy discussion about the fact that the Oculus Runtimes have not been using the IPD settings and therefore world scale is incorrect. Oculus is supposedly fixing it possibly in 1.8 but there is also a request for being able to set it manually with a tool or in Oculus Home. Being able to directly set World Scale in the application (DCS in this case) is also desired - it is available in FlyInside for FSX/P3D.

It's clear that DCS is not seeing your rift - your attached screen capture shows that it is not creating a stereo distorted image as in the following image. I don't understand the need for Windows install as long as you have the latest 1.8 Oculus Runtimes. BTW, how does War Thunder look? Is it OK? (Starts up and looks fine in the Rift?) (Note: you need to use the Oculus Debug tool from the older SDK to set Pixel Density for WT

You probably have already done this but you could try this: 1) Turn OFF the Rift and start DCS so that it comes up on your monitor. Select the Settings Icon (the gear at the top middle) and go to the VR tab and set it up (enable VR headset and start pixel density at 1.4 or so) then EXIT. 2) Turn Rift ON and then restart DCS - which version(s) are trying to use - there is a 2.0.3.56 and a 1.5.4.56 - try them both

WOW - Excellent work - a big help for VR. Like what was said above, if there is any way to increase the font size of the DSMS of the CDU display - that would be a huge help!

As far as star size, you can edit the variable starSize in \Bazar\shaders\star.fx to maybe 250.0(my setting) or somewhat larger. I haven't found any way to make the terrain darker - and water is a weird color as well.

Just edit them out entirely with the Labels.lua in the Config\View directory.I think you could start with them off by setting things like AirOn = false