frame rates and freezes

[Kanth]

DaddyAce,

Just to be clear because i didn't see this detail in your post:

The only time the rift appears as a display option in windows is when the oculus software is running.
As soon as you close oculus software, the rift display disappears from windows.

So you either need to launch the oculus software manually by clicking on it and leaving it running or put the rift on your head and click through the warning and leave it running , before it will show up as a device in windows.

[DaddyAce]

Yes, did that.  Ran thru the sequence you suggested.  Find single monitor thru Win display settings, then close that.  Run Oculus software, the go in again.  I can see 3 monitors on your example, but Win 10 on my machine still shows only one in Display Settings, and since it shows only one I tried "Detect", which only yields "Didn't detect another display"....despite that I can put my Rift on and see that it's working, and can actually have the Rift on my forehead and hear the background music and see the Oculus Dash menu (both on my monitor and in the Rift), at the same time Windows says it doesn't detect another display.  But thank you for your help, and the good news it that the Rift does actually work.  Meanwhile I'll write it off to Windows weirdness short term.  I expect to soon not be able to use it for a couple of months, and hopoe software issues smooth out before I return.   

[DaddyAce]

Ooops!  I take back the working fine part......just tried running Aces High with Rift and BETA software installed.....won't work now and I get a vague message in the rift about "Critical Error  Oculus isn't working correctly....."

[DaddyAce]

Update....seem to have it working with Aces High again....I don't think I changed any settings....just fiddled around exploring, trying to find some setting to change that would make it work, without any apparent luck, other than I tried again after several failures and reboots, but it seems to be working again.   

 

[1stpar3]

  Thats just weird! All I did was run update that oculus had and poof. Only thing I can think of is with Windows? Do you have the BIG update, the one that can cause nightmares? I rolled my WIN10 back to before that particular update, some time before Thanksgiving as it was causing havoc    Well come to think of it, I believe I rolled back and then redid the update? I really cant remember. I have dxdiag report from Sept and just ran a new one and WIN version numbers are identical    THINK I rolled it back? 
Operating System_Windows 10 Home 64-bit (10.0, Build 15063) (15063.rs2_release.170317-1834)

[1stpar3]

  Checked my updates and the CREATORS update WAS NOT installed...so I did remember it correct OR did I    Anyway, I dont have the Creaters update running my Win10 1 more thing the Public Test panel switch in Oculus is turned on.

[DaddyAce]

Yes, 'twas annoying.  But it seems to work fine now other than not showing 2 displays.

I had to roll the Fall Creator's update back as well.  My puter would not run anything worth a darn with that monster.  I also did have a rare stability issue back then too, which has completely cleared up since I upgraded my PSU & CPU ( I was suspicious of my old PSU).

I don't get it, the rift shows connected in the Oculus software, but doesn't show in things like "Display Manager" or "Device Manager"....the Oculus sensors do show in Device manager, but the Rift doesn't show at all.

But it's okay, at least it works in game.   ....and I flew a few sorties and don't recall the pauses I was getting before the new Oculus software....

[Bizman]

Checked my updates and the CREATORS update WAS NOT installed...so I did remember it correct OR did I    Anyway, I dont have the Creaters update running my Win10 1 more thing the Public Test panel switch in Oculus is turned on.

Do you mean you don't have the FALL Creators Update (1709) installed, or are you still "missing" the earlier Creators Update (1703), too? Just for clarification...

[Randy1]

I have the creators update and use tthe public beta check option on the oculus software and do not have a problem with rift.

AH I start the oculus software first.  Then put on the headset, then using th oculus dash, I click on the Desktop.  That gives me access to the windows desktop.  Then I click on the AH icon on the windows tool bar to launch AH.

[1stpar3]

I have the creators update and use tthe public beta check option on the oculus software and do not have a problem with rift.

AH I start the oculus software first.  Then put on the headset, then using th oculus dash, I click on the Desktop.  That gives me access to the windows desktop.  Then I click on the AH icon on the windows tool bar to launch AH.

Right, last section of this topic was dealing with the resolution and Rift showing up as a display device. Wasnt about getting it to work, well for most lol Daddy JUST HAS to be DIFFERENT

[1stpar3]

Do you mean you don't have the FALL Creators Update (1709) installed, or are you still "missing" the earlier Creators Update (1703), too? Just for clarification...

I guess I have the 1703 update. The only place I saw those numbers were in my DXDIAG I did yesterday. Was in my last post operating System_Windows 10 Home 64-bit (10.0, Build 15063) (15063.rs2_release.170317-1834)  rechecked my update history and YES all 1703 updates were installed. The 1709 Fall Creator was NOT installed   :aokDidnt notice both were referred to as "Creators Updates"

[DaddyAce]

...... well for most lol Daddy JUST HAS to be DIFFERENT

    Unfortuntaely I think you may have me pegged,    and I think I know some folks who may agree with your assessment 1stpar!  Although I don't seem to understand or have control over some of the vagaries of my puter!   

[Puma44]

I'm having a strange occurrence.  After following Kanth's guidance of turning on Oculus, checking W10 display options and confirming the Rift is selected, opening the game within Oculus, going to video settings and confirming the VR is correct, I deselect the "Disable v sync" box (which is checked), get the restart game message, restart, check the game video settings again and find the "Disable v sync" box is again checked.  So, I cancel that, go into the game and get no better than 45ish for a frame rate.

When Kanth first put up her very helpful guidance, it worked perfectly and I was getting 90s frame rates.  I've reread Kant's post twice and confirmed all the settings.

For some reason that I don't understand, the "Disable v sync" box will not stay unchecked.      Am I doing something wrong or is this a bug? 

I also checked and have the 1709 update installed.

[1stpar3]

  Its a bug,mine does same thing

[DaddyAce]

I suspect mine is doing the same Puma, at least in terms of Vsync being disabled.  I was just flying in the MA, and had noticed tearing, especially on the reflector sight, and noticed my frame rates were up over 100.  I think having Vsync enabled would keep FPS (at least on my machine) at 90 with no tearing, which is what I was initially getting.  So far for me the Beta has been a bit of a hassle on my machine.  I do think the pauses are shorter and less frequent.  But I also have something odd going on in that my software will not show the Oculus as a display, but nonetheless it works, usually.