New to the forums? Click here to read the "How To" Guide.

Developer? Click here to go to the Developer Forums.

Permanent Fix for False "Doesn't meet minimum" message

BitVarBitVar Posts: 23
Brain Burst
I created a scheduled task that runs at startup to fix the minimum requirement for CPU everytime you logon to your PC. It updates your CPU to be an "Intel(R) Core(TM) i7-4770K CPU @ 3.90GHz" which is above the minimum. I did this because there is no way to disable the message and it is HIGHLY annoying since I have a 3770K overclocked which is pound for pound a superior processor to the i5 minimum. Alternatively if you don't feel comfortable with a task you can just grab the Two.bat file below and run it instead (as admin of course). I've provided these at a paste site so you can see the source for yourself and decide if it is safe to run. Make sure when you save these pastes to just save the contents, not the webpage (that would be silly). The task that this creates runs as NT Authority by the way.

1) Save this http://pastebin.com/JwUxfMvy as One.bat on your homedrive (usually C:)

2) Save this http://pastebin.com/q8DJdQaQ as Two.bat on your homedrive (usually C:)

3) Save this http://pastebin.com/dGKviHtH as OculusTask.xml on your homedrive (usually C:)

Once that is done all you need to do is right-click on One.bat, run it as Administrator and it will do all the magic for you, and now every-time you login to your PC (with any account) an administrator task will execute the fix, thus permanent.

If you are curious to see how it looks on my PC check out this screenshot: http://i.imgur.com/VFOyroS.jpg

Good luck and see you in the Rift!

-Bitvar

EDIT: Had to update the pastes, they expired/self-deleted. Using paste-bin this time so maybe they will stay longer.

Comments

  • BitVarBitVar Posts: 23
    Brain Burst
    BTW I also posted this over at r/oculus https://www.reddit.com/r/oculus/comments/4kangn/cpu_minimum_spec_not_met_message_fix/ if you want a sendspace with the files in an archive.
  • NacaryusNacaryus Posts: 224
    Nexus 6
    hi, still no errors with this solution right? i am getting a gtx 1080 and now i stumbled upon this nonsense..lol
  • BitVarBitVar Posts: 23
    Brain Burst
    Nacaryus said:
    hi, still no errors with this solution right? i am getting a gtx 1080 and now i stumbled upon this nonsense..lol
    Not for me. No CPU messages/not meeting spec messages with the solution posted above.
  • FX2KFX2K Posts: 268
    Nexus 6
    edited June 2016
    Nacaryus said:
    hi, still no errors with this solution right? i am getting a gtx 1080 and now i stumbled upon this nonsense..lol
    If the message is triggered by the 1080 (i.e Oculus haven't added it to their catalog yet), then this fix won't solve it.. Also, if it is, then it further proves the catalog check is insufficient, requiring an update / manual intervention each time new CPU's or GPU's are released.

    Anyhow, this workaround is for CPU's that are apparently under spec, basically (as in the OP) it renames the CPU in the registry so Oculus Home knows no different.  The same might be possible with the GPU, but I have no idea on that front.
    CV1: Ordered 6th Jan 2016 - Est Delivery Some time in May...
    DK2: Ordered: 8th of Aug 2014 - Delivered: 14 Oct 2014
Sign In or Register to comment.