New to the forums? Click here to read the "How To" Guide.
Developer? Click here to go to the Developer Forums.
Developer? Click here to go to the Developer Forums.
Disable "Your computer doesn't meet Rift's recommended specifications" message in Oculus Home?
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Comments
@jon ;
I5 3570k water cooled overclock set to 5 ghz. I have a 980ti and have no issues playing every VR game on maxed out settings. My system plays flawlessly. I could easily upgrade to the newest chips but my I5 3570k chip destroys the new chips at their normal clock settings. My single core mark is considerably faster than the 4590. So yeah, I would love it if we could remove this notification. At least do what the Vive does and provide an actual VR test that actually tests something and doesn't just read from a list. Even The Nvidia Experience on my pc says I pass all the VR tests.
That's a purty wall mount. I've considered that very case but was concerned about dust coming in through the top. How often do you clean it (it looks very tidy there).
I love that case, it's been on my wish list for a while... Just waiting for a CPU that is worth upgrading from my i7 2600K, which can pass the 5.25GHz mark if I want:
http://valid.canardpc.com/show_oc.php?id=1672808
Unfortunately, our CPUs are not good enough for Oculus Rift, tho! LOL
https://forums.oculus.com/community/discussion/37165/permanent-fix-for-false-doesnt-meet-minimum-message
Thanks, @BitVar
I kinda doubt they'll add in such a feature anytime soon. They're focused more on selling, evangelizing and building up their SDK support.
This is a fix just for the CPU tho. I haven't had a need to look into the GPU, but the same concepts should work for it.
I have the same 3770k and 980ti, no issues at all. Even able to turn up pixel density without issue. Can I stop getting harangued every time I start using my Rift?
https://forums.oculus.com/community/discussion/37165/permanent-fix-for-false-doesnt-meet-minimum-message
I haven't tested it myself, as my CPU is above the minimum spec, but I have no doubt that his solution works.. no one has posted otherwise.
(thanks again, @BitVar!)
But wow, that annoying message in Oculus Home remains due to my "3.2ghz" CPU. Though it works, I don't want to change my CPU type in registry. And I'm not buying a new CPU until Skylake-E hits. I just want oculus to make this message an option you can disable in the UI!
I think this hardware check is just too simplified to work correctly and the message without the option to disable it is very annoying.
Oculus should create their own benchmark which could run at the beginning of the Rift setup and it could determine if the system is performing fast enough for the Rift or not. And if it's not fast enough the user should still have the option to continue after acknowledging the fact that the system is too slow to run every VR game as some games are not so performance hungry.
It really seems that Oculus tries to overly simplify the software and its development leaving out options which could be easily added like disabling annoying messages, auto-update or the Oculus service.
I am confused about the USB3 for the sensor though. I am using the sensor in a USB2 port (cause it won't work in any of my USB3 though the Headset does work well) and surprisingly I got no flicker, no stuttering, no slow headtracking recognition at all (at least not in my perception).
This: "Let me check a "Yep, I know, I might get sick and fall over" checkbox, and have that message GO. AWAY."
16 GB Quad Channel DDR 3 1600 Mhz with 250 gb SSD
GTX 980
working with DK2 to make something great!
The only caveat to such a check would be overclocked systems which could be easily overlooked by simply not adding an overclocked chip to the whitelist, but allowing the check to activate the usage of the toggle for that specific user. (or just do some simple math to confirm that the MIPS/FLOPS would still pass scaled down to stock speeds, since almost all chips report their stock MHz in the CPU ID)
As for other computer components, I would imagine a similar approach could be used for GPUs, though I'm not sure how necessary that would be given the limited number released over time. This isn't a hard problem to solve. If Oculus put out a call to develop a real fix for ongoing hardware qual, I'd be happy to help.
https://forums.oculus.com/community/discussion/37165/permanent-fix-for-false-doesnt-meet-minimum-message
Looking through the two batch files and xml, it looked fine, so I ran it. It works as advertised.
.
.
.
So, to summarize, using Rift on sufficiently fast CPUs that aren't in Oculus' arbitrary supported list of CPUs without constantly being badgered by a warning message requires editing your registry and restarting your Oculus services on every log in by using third party batch files uploaded by a community member.
Oculus, you should be ashamed.