All I can say is read the last link I posted it starts with the following - “ If You Are Using a Non-WMR headset:
• Oculus users please opt-in to the Oculus Rift Public Test Channel to enable support:
Sure sounds like OCULUS RIFT to me, and this is from the MSFS 2020 people!
I don’t understand why people don’t read the FULL post before starting a flame. All I was trying to do was use was what the MSFS folks told US to do about VR and pass it along for struggling people.
Before I did it, I had a stuttering, lagging, warped mess. Afterwards it works great. Don’t think it was magic. Anyone that wants to try it differently, I say go for it.
Merry Christmas all!
confusing topic but to put right if registry entry not in rift does not work . ASW etc still broken when registry entry in. So improvement is not working to sort of working. The extra stuff in the dev tool only works for wmr . You have to install wmr for that to enble . As far as I know zero benefit for rift users but I could be wrong.
You are correct. I didnt see any successful users of Rift S. Low FPS, lots jiggling/stutters/freezes.
Created bug report in Bug section. Please vote if you agree: Very poor perfomance in VR mode
voted for my hardware expect better
for the life of me can"t my rift s to work in pc or steam. states no headset found. I at the end of my rope
What helped for me is enabling the public beta test channel in oculus service. The sim now runs very smoothly. You can see the rest of my settings in my post:
What settings do you run in OpenXR? I did not notice any effect on my Rift S
It will not have no effect, stop believing all you read on the Internet
Installing OpenXR Dev Tools is useless for Oculus users, and will have zero impact on your experience.
Oculus users can only use the OpenXR implementation on their headset which is the json file inside Oculus directory (mine is at “D:\Oculus\Support\oculus-runtime\oculus_openxr_64.json”), the one you point with the registry.
Pointing instead on the OpenXR runtime (so clicking on the “Define as active runtime” in OpenXR tool) will lead to a logic “No headset Detected” in game.
So let’s assume you install OpenXR (like I did few minutes ago for testing purpose), you can’t initialize your Oculus headset with it as it’s not a WMR headset.
You still can change the settings like described in the video but it have zero impact whatever settings you do (render scale, retroprojection, etc.) like I just tested again few minutes ago, because you can’t use the OpenXR Runtime provided, only the one from Oculus.
So please people stop spreading misinformation and mess something which is already complicated for some
Ok new here and a advocate of the KISS principal (keep it simple stupid) .I have been a simmer since fs2000 and had my share of tweaking over the years so now i just want to fly and enjoy what im seeing. My rig consist of a i9 cpu and a gtx1080ti fed by 36 gigs of 2660 ram all running at stock oc speed. It is easy to get lost listening to all the suggestions about doing this and that if you do not keep track of every move you make to get thing right for you. I fly with a oculus rift S and my OS and Flight sim are on separate mdot2 drives. FS2020 is demanding on my gpu and as temp rises gpu performance decreases as a king of self protection. First thing first get MSI AFTERBURNER or the likes and pum pup your fans to keep temp cool. In NVIDIA CONTROL PANEL set power management to prefer max performance and texture filtering to Hight performance. These former things are basic but often forgotten. To avoid problems with all oculus headsets and FS2020 in the oculus page go to setting ,beta and join the beta gang. Restart your oculus and that alone should get your head set working without any problems. Download oculus tray tool software ,nothing else. Learn how it works and what it does . Now the big secret to success : start with the lowest settings in both FS2020 and oculus tray tool and one by one start to push numbers to a higher setting keeping track of what you did previously. Now that you have an acceptable image and before anymore tinkering STOP,dont look at the fps meter just fly the dam thing. If for some reason you would get the urge to fiddle your settings ,print your settup page as a base line to go back when you get in deep sh… The following link is all the info you need to understand how moving a single slider or going from medium to high can ruin a perfect running sim.VR Bang-For-Buck Performance Guide
My experience is this:
I own a Rift S and my specs are: i7 10700, 16GB, RTX2080super.
The performance is amazing!
I have render scale 100%, almost everything in High with just a couple of things in Ultra and Medium.
The experience and graphic quality is hard to explain.
I set Beta testing in Oculus and in the rift S Device’s Graphics preferences, I set to Prioritise Performance. Just That. (Oh, and I disabled ASW in the Oculus Debugtools)
I flown over big cities and amazing landscapes with smooth performance.
Just post your performance monitor from Oculus.
I never heard of it. What is it?
But anyway, I base my comments on my perception. You could say, the whole experience. The only thing hard to control are the planes with keyboard. I’m waiting for my Joystick to arrive this week…
I posted this on Youtube!
Just know that Youtube applies an extra compression. The experience is actually better.
Here is a link to the .MKV directly from OBS:
Does anyone here have Rift s and rtx2070 (not super) i78700k OC at 5.2 GHz NVMe2. Will the experience be better than Quest 2?
The reason is that I got Quest 2 and since 2 weeks no good result so I ordered the Rift S yesterday hoping it would be better but reading this forum I realised I might have made another big mistake.
I want to use it primarily fot MSFS and XPlane 11. Do I cancel eturn the Rift S order or keep it?
I own G2 but from what I read here, ppl are absolutely happy with their Q2 performance and visual quality so I’m affraid you must be doing something wrong.I wouldnt expect the Rift S to be any better than Quest. Give yourself another two weeks, read the forum carefully, look for the answers and you’ll get there eventually:)
In your case, I would cancel and return the Rift-S.
Or keep the Rift S if you want a plug and play experience
I own “only” an Oculus CV1 and I’m really happy with it as I can get the most of it with my hardware (i7 10700K Oc and RTX3070 OC, 32GB), playing at 45fps ASW ON nearly everywhere with the good plane (some are fps eater, some not).
I have the money to invest in a new headset but currently nothing satisfy me in the market. The G2 with its huge resolution will take my PC down, and it’s WMR which I avoided so far even if some have good experience with it. It’s center spots seems not that good. The Quest 2 is far from plug and play and the number of steps I read around to hope having a good experience PCVR don’t enjoy me, and my IPD is 67 so I’ll have to deal with black bars on left and right.
If I had to choose one I’ll chose right now a Rift S. Good improvement from the CV1 without been too much, my hardware can handle it and it will be easy to configure and use. So it depends if you’re ready to go down in the rabbit hole or not. Or wait like me if some future headset will come to simplify all that.
Thanks for your contribution. I considered Radeks40 advice and cancelled my rift order. I have decided to continue tweaking my Quest 2. So far I have been able to do some IFR flights with the jets, a320 and B787. There are here and there stutters but I still enjoy the flights. Now that I have tested VR, I want more so I’ll have to plan for one with a much better FOV.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.