Rocky49

latest update SEP 10 is for Stable version

hear you about aging eyes :smilewink: mine are 70

I run at 1.5 and 2x MSAA, everything else high, except shadows on low and default. I will try lowering to 1.2 when I get home. Perhaps there are just too many pixels at 1.5 and it defaults to ASW on?

Yes this is exactly what I have tried. I have searched Oculus site for a fix or explanation but found nothing

I'm away from home for 11 days will try again later:thumbup:

I used the tray tool to turn off ASW and to make a profile for DCS but I had the same result, locked at 40FPS

DBurne: I have nearly identical hardware and when I turn off ASW do not get higher than 40 fps. It is a very fluid experience with no stutters or other issues. It seems like I am not truly getting ASW turned off?

Left Alt and Enter should do it, brings up full screen.

I think its the Rift S that limits the frame rate to 40. My system (see below) shows 40 frames as well but I have PD set to 1.5 MSAA at 2, and rest of setting high. Even when I disable AWS it makes no deference in frame rate, however rift runs very smooth, no stuttering or other issue

I also find no issues with the FOV, it would be somewhat extreme to say" looking through a pipe" in my opinion. Much easier to read dials too

I also find no issues with the FOV, it would be somewhat extreme to say" looking through a pipe" in my opinion. Much easier to read dials too

I think the current Tpod released this week is only a stop gap until work on the new system is done, with marked improvement with IR, clarity and performance coming with new Tpod

frame rates jumping all over from 37-80 (Oculus Rift S) 37 is cockpit looking at ground near airport 80 is looking out at sky climbing out, level flight 40-55

I forgot to set PD, and that was what I missed, now works, Thanks guys.

tried both suggestions. Frame Rate locked at 40, Debugging tool says Adaptive GPU off, ASW disabled. So it seems that it doesn't matter what you change, still locked into ASW, not disabled.

I have tried using the keyboard commands, Oculus Debugging tool and OTT. Every time I reset ASW in Debugging tool, I go into DCS and run the Instant action P51 mission, the frame rate is 40. I leave DCS, reopen Debugging tool, ASW is back at Auto. Tried setting the ASW in OTT, set to Off. run DCS, frame rates 40. Leave DCS check OTT, it says ASW is Off, check Debugging Tool, ASW is set to Auto. Using keys, Ctl + 1 (KP) has no effect. All Drivers are up to date. Windows 10 Version 1903, Oculus 1.38

Actually what Wag said was not as specific as your comment alluded to, more of a general statement that they were not satisfied with that implementation

can you give a source for your comment in paragraph saying Unfortunately it turned out that the fix did not work for all systems (unknown whether it's certain HMD's that do/don't work, different GPU's, or what. I think I remember them saying the fix actually decreased frame rate for some users, which is why they have to figure it out and fix it before they can send it out to us.

I too have been waiting since Comadore 64 days for this type of flight simming. I have always been an early adapter so have gone down the wrong path a few times but this time VR is the Golden path to total immergence. I just turned 70 so hope that I will see a few new advances before my last flight :music_whistling:

Thanks, guess i'll let windows update

apparently issues with sound, mic drop outs?

Is it safe to update to Windows 10 Version 1903? Have the issues been resolved

No adverse effects from 137 for me

MY biggest concern with the Reverb is the Company HP. Not the best at keeping customers happy and their software record with respect to updates is spotty. But who knows? This headset (reverb) looks more like an Oculus Product than the Rift S does :music_whistling: Kind of wonder about that.

Spend most of the training mission trying to find the targets!!! labels need to be on. Jester assistance is very hit and miss. Visibility of Targets is ridiculous.