[REPORTED] latest update - Oculus Rift Issues

[yeager]

It depends on what "playable" mean. VR experience is affected by a large extent.

[D4n]

Well I have RX 580 8GB and Dell Visor, ofc. i play on "VR preset" (DCS graphics settings) and once in the air, on full server, also have over 45 fps continuously, mostly around 60 even. flawless experience for me, even when looking around to left and right quickly, no black loading spots or so.

Edited September 2, 2018 by DanielNL

[yeager]

Well I have RX 580 8GB and Dell Visor, ofc. i play on "VR preset" (DCS graphics settings) and once in the air, on full server, also have over 45 fps continuously, mostly around 60 even. flawless experience for me, even when looking around to left and right quickly, now black loading spots or so.

 

yep exactly, kind of rift not catching up fast enough for rendering the image. Never experienced before on DCS.

 

(I5 6600, 16GB RAM, 1080TI)

[D4n]

"no" instead of "now", typo. I have no issues at all (SteamVR, WMR).

[EDT]

"no" instead of "now", typo. I have no issues at all (SteamVR, WMR).

 

The issue is only for oculus rift users. Thats why.

[Ala12Rv-Tundra]

Why, the game is NOT crashing, so it IS "playable", right?

check thread´s title again :smilewink:

[JumpinK]

So only oculus-pilots are grounded by the last update?

[E61-v1T1]

So only oculus-pilots are grounded by the last update?

 

 

I think yes...

Performance is still terrible, even with the new "Shaders Performance Mod" installed..., something has changed in that OpenBeta that affects only the Rift users, a shame..., instead of moving forward,we go back ...

 

 

 

So, waiting for a fix .. :doh:

[dburne]

So only oculus-pilots are grounded by the last update?

 

Apparently so, but not all Oculus users which is strange.

[imacken]

Apparently so, but not all Oculus users which is strange.

 

Don, are you not suffering the menu bug? What desktop res are you running on?

[dburne]

Don, are you not suffering the menu bug? What desktop res are you running on?

 

Not suffering any bugs currently I am aware of - well except apparently ASW is not working even though it does lock my fps to 45 fps or 90 fps which is strange if it is not working, but still very smooth. I say ASW must not be working as I don't get the squiggly gun-sight reticle and blurring/ghosting of the planes as they fly past that I would expect to see with ASW on. I fly with ASW off though and my VR is very smooth.

 

Spent about half the day today flying the Spit over Normandy off and on in my Rift. Also about the same yesterday.

 

My desktop res is set at my monitor's native resolution - 1920x1080.

[HawkeyeHHDF]

The majority of guys in our wing who have the rift cannot fly because it is so bad, mine works personally , but I hope it gets fixed soon.

[Talonx1]

Mine works well enough in most situations but the black box borders are pretty annoying and I’ve had to turn down a lot of options to make up for worse frame rates.

[imacken]

Not suffering any bugs currently I am aware of - well except apparently ASW is not working even though it does lock my fps to 45 fps or 90 fps which is strange if it is not working, but still very smooth. I say ASW must not be working as I don't get the squiggly gun-sight reticle and blurring/ghosting of the planes as they fly past that I would expect to see with ASW on. I fly with ASW off though and my VR is very smooth.

 

Spent about half the day today flying the Spit over Normandy off and on in my Rift. Also about the same yesterday.

 

My desktop res is set at my monitor's native resolution - 1920x1080.

 

1080? That’s why you’re not suffering from the menu bug. It doesn’t appear at that res. Anything above that and it is impossible to select menu items like ‘Fly’ and ‘Quit’! I’m at 4K, and back on 2.5.2.

And yes, the Spit is beautiful in Normandy at dawn!

[Guest arc_tander]

Just tried hotfix 2. Had 45 fps locked (ASW on?) at 20ft skimming over the sea in a Huey. Seems better to me.

[Laserxray]

Hi

Since the last update the performance is bad in vr, black borders when turning to look around, building going by are blurry,everything was smooth just before. Im using the rift, and I have the Samsung odyssey, I got best results with the rift, could set graphic setting to high , and run 1.3 pixel density and everything was smooth ,and now it is unplayable.

please please please undo what ever you did .

 

Running 1080ti , i7 7820x, 32g ram, windows 10, latest drivers 399.07

[some1]

Not suffering any bugs currently I am aware of - well except apparently ASW is not working even though it does lock my fps to 45 fps or 90 fps which is strange if it is not working, but still very smooth.

 

So you have the same issue that others in this topic, stop saying that all is well, that only adds to confusion! You still have degraded performance since FPS is locked to 45 even if you don't use ASW, but since you are used to flying without it, you haven't noticed much change. Actually involuntary locking fps to 45 might have reduce the jerkiness that sometimes occur when FPS jump with ASW off;

 

F10 and menus issues were fixed in the hotfix, but ASW was not, and the current menu problem affects only those with desktop res higher than 1080.

Edited September 3, 2018 by some1

[E61-v1T1]

Rift users with problems, are they all using Rift Core 2.0 Beta? and the channel public testing ?. Just out of curiosity. Could this be an important factor?

 

 

I will do some tests to check if something changes.

[some1]

Gets halfway through loading page, Core 11 goes to 100% and then hung, Ctrl-Alt-Del only way out.

 

VR is completely INOP.

 

Latest Oculus Beta Core, patched Thursday/Friday, latest Nvidia drivers.

 

Could ED have accidentally used an older Oculus API?

 

'Gimp (DISCO vVMFA-122)

 

By any chance, do you wait for the game to load with your headset off? It will show the cockpit only after you put the headset on your head.

[dburne]

So you have the same issue that others in this topic, stop saying that all is well, that only adds to confusion! You still have degraded performance since FPS is locked to 45 even if you don't use ASW, but since you are used to flying without it, you haven't noticed much change. Actually involuntary locking fps to 45 might have reduce the jerkiness that sometimes occur when FPS jump with ASW off;

 

F10 and menus issues were fixed in the hotfix, but ASW was not, and the current menu problem affects only those with desktop res higher than 1080.

 

My fps are not locked to 45 fps without ASW running though.

Sorry to add to confusion I will leave it be, hope they get a fix for you guys out soon.

[slyly666]

Rift users with problems, are they all using Rift Core 2.0 Beta? and the channel public testing ?. Just out of curiosity. Could this be an important factor?

 

 

I will do some tests to check if something changes.

 

 

 

 

 

 

 

 

 

 

hello yes in my case I have oculus rift core 2 beta turned on public test channel is turned on and the unplayable everything blurry and was please to speedy fix.:(:(:(

[Hippo]

Rift users with problems, are they all using Rift Core 2.0 Beta? and the channel public testing ?. Just out of curiosity. Could this be an important factor?

 

I will do some tests to check if something changes.

 

 

I am and have been on beta 2.0 since it first released. Only experienced ASW issue since this update.

[Gryzor]

I am and have been on beta 2.0 since it first released. Only experienced ASW issue since this update.

 

I tested with Oculus dash 2.0 disabled, enabling the old one, han have the ASW not working.

 

ASW works perfectly in other software and applications, and in DCS 2.5.2, please fix 2.5.3 ASW not enabling, and of course do not give us the release version witout the fix, please.

[eaglecash867]

I didn't have the Core 2.0 Beta installed and had the drunk pilot problem with the latest DCS beta update. I enabled Core 2.0 Beta last night, and still have the drunk pilot problem. The current build of the release version of DCS works great both ways. Definitely the new beta causing problems for us Rift users.

[E61-v1T1]

Well, after some tests, I have recovered from the problem I had in the performance, I return to have a stable performance, it seems related to the Oculus Tray Tool.

 

I always used Global Super Sampling 2.0 for Oculus Home general, and for DCS World I had a profile created for where I used Supersampling 1.6. For some reason, since the new OpenBeta the ASW has stopped working, as many users have described it.

 

But I also think that something else does not work as before with Oculus Tray Tool, like the correct application of profiles, and I have the impression that the Supersampling 2.0 that I use in the global option, in some way also modifies the simulator, then logically there is a considerable drop in performance.

 

The solution I found at the moment was to start the Oculus service without using Oculus Tray Tool, although it insists that the ASW is still not working and this makes the DCS World VR OpenBeta useless.