Flickering Screen when playing VR with Oculus Rift S

[markushausner]

Hello,
the screen is flashing and flickering. Do i have to make some settings to get rid off this ? It is annoying because you cannot use the mouse correctly and the whole screen is flashing.

[Firpo]

I found out it´s a new problem with Oculus version 26, you can either go back to 25 or sign in for beta 27, many people have no issues anymore

[★Macman★]

You don't get that with the G2 but is common for Oculoss.

[Schmegg]

Macman の投稿を引用：

You don't get that with the G2 but is common for Oculoss.

You don't get it from Oculus either with a decent piece of software. Anyone would think that Microsoft only cares about WMR.

[markushausner]

Well beta 27 helped. Thank you ! Vision is Perfect at the Moment

[★Macman★]

Schmegg の投稿を引用：

Macman の投稿を引用：

You don't get that with the G2 but is common for Oculoss.

You don't get it from Oculus either with a decent piece of software. Anyone would think that Microsoft only cares about WMR.

I started out with the RIFT CV1 (then RIFT S) when it came out on my Dell Quad 3GHz PC which worked perfectly well on the original Runtime 0.7 until they totally blocked that cpu by the SSE4.2 check they included in LONE ECHO as a prerequisite to only allow i5 & i7 og Intel to run it. They claimed it was due to future proofing and yet no other Game has since used it by force. I would guess that even that 10year Quad PC can easily run my G2 and any Vive. Just not Oculus for banning a cpu. The exact same immoral bullying of that company is now seen in having signing in. Germany found that illegal and is banned. I really don't know who they think they are to control us. Clearly it is the same act as CIA with a law until themselves. Their loss not mine. I'm very happy with the G2 except the crap WMR APP.

[Schmegg]

Macman の投稿を引用：

Schmegg の投稿を引用：

You don't get it from Oculus either with a decent piece of software. Anyone would think that Microsoft only cares about WMR.

I started out with the RIFT CV1 (then RIFT S) when it came out on my Dell Quad 3GHz PC which worked perfectly well on the original Runtime 0.7 until they totally blocked that cpu by the SSE4.2 check they included in LONE ECHO as a prerequisite to only allow i5 & i7 og Intel to run it. They claimed it was due to future proofing and yet no other Game has since used it by force. I would guess that even that 10year Quad PC can easily run my G2 and any Vive. Just not Oculus for banning a cpu. The exact same immoral bullying of that company is now seen in having signing in. Germany found that illegal and is banned. I really don't know who they think they are to control us. Clearly it is the same act as CIA with a law until themselves. Their loss not mine. I'm very happy with the G2 except the crap WMR APP.

Whatever. It still doesn't change the fact that MSFS2020 should be able to run smoothly in an Oculus headset. So damning Oculus for their practices whilst simultaneously ignoring Microsofts lack of care supporting a competing headset is slightly incongruous IMHO.

Having said that - I agree with you that changing the landscape post sale like Oculus did is very poor. I'm down on Sony for exactly the same thing. All one can do is not buy stuff from them. But your first comment really doesn't add anything to the discussion that is at all useful to solving the OP's problem.

[★Macman★]

I rather think it solves the problem in moving onto the G2. I said all my history with Oculus but I missed out all the constant on going trauma of every one of their Updates broke a version to need another one which was already in Public Testing. That plus they would never listen to their customers of their best headset to always supply a basic Runtime which sole purpose was to get Customers a working version as a backup but without the Doll's House and crap that goes with it. Not only all that mentioned already BUT the RIFT S has never had any one of the Upgrades which the Quests have like Finger Tracking and increased Frame Rate. They literally sold you guys out to suffer breaking the Runtime whilst experimenting on it as a realease.

Guys, the issue is not MSFS nor Microsoft nor NVIDIA...it's Oculus. This was proved by always going back in or out of PBT & Release. They are a wreckless and careless company without any such good morals what so ever. Solution - leave them. I have never lost money in any VR by moving up and onwards but with Oculus I had to re-install complete OS about 20 times due to their inability to make a working system. Sorry but why suffer over and over.

[Schmegg]

Well, your experience was different to mine - hence the differing opinions I guess. Hehe.

In my case, apart from having issues with an Optimus laptop that I had to figure out myself as their support didn't seem to get it, everything worked quite well for me. Certainly din't have to re-install the OS or anything near as drastic. So other things might have been at play in that case.

Suffice it to say, I've now got a G2 also and it is much better than the CV1. But that's to be expected - it's a couple of generations newer and the CV1 was the very first retail generation. However, if you've got a CV1 and aren't in a position to upgrade just now, it should work OK with MSFS. Mine did. I'd expect the S to be similar.

In reality, this sim is fairly ordinary in VR. Could be absolutely amazing. Just isn't. IMHO. Even with a G2. Comes down to what you are willing to put up with. And it falls under the bar in my case.

[SimPailet]

Hi All, I just shared my experience here: https://steamcommunity.com/app/1250410/discussions/5/3079873089695149360/
You should be able to implement this on pretty much any PC with fair hardware specs.