03-28-2016 04:08 PM
05-22-2016 01:26 PM
AdKiuCM said:
This registry workaround is probably fine, but it misses the point. I do not want to be forced to cheat the system changing CPU name. Also in my case I have got multiple USB 3.0 controllers. Rift will be plugged into compatible while other "non-compatible" will be used with other equipment.
05-22-2016 04:10 PM
05-25-2016 04:36 PM
05-27-2016 04:34 PM
05-28-2016 11:58 PM
AdKiuCM said:
This registry workaround is probably fine, but it misses the point. I do not want to be forced to cheat the system changing CPU name. Also in my case I have got multiple USB 3.0 controllers. Rift will be plugged into compatible while other "non-compatible" will be used with other equipment.
05-29-2016 01:32 AM
05-29-2016 05:03 AM
RobHermans said:
A useful post by @BitVar to remedy this:
https://forums.oculus.com/community/discussion/36677/permanent-fix-for-false-doesnt-meet-minimum-mes...
I haven't tested it myself, as I have an above minimum CPU. Looks super legit though. B)
05-29-2016 06:43 AM
05-29-2016 08:12 AM
Keylo415 said:
I just stumbled upon this thread.. I too have an I5 2500k cpu. My question is, does this message get in the way of game play , and if so how much?
05-29-2016 08:29 AM
jon said:
Keylo415 said:
I just stumbled upon this thread.. I too have an I5 2500k cpu. My question is, does this message get in the way of game play , and if so how much?
Gameplay? no.
There's just
a strong correlation of people who overbuild their machines and people who pre-ordered Oculus Rifts. To those of use with water cooled, overclocked 3770k's that stomp the minimum requirements, having to put up with a banner in Oculus Home and on every launch screen that flaunts our computer's age unnecessarily is a bit of a kick in the groin. Business-wise, kicking your customers in the groin is high on the list of "you probably shouldn't do that" things.
.
.
.
See what you've done Oculus?
See how sad it looks to be told it's "too old"?
The CPU LEDs don't even light up anymore it's so depressed.