05-25-2016 09:00 AM
12-02-2016 06:23 AM
Scawen said:
@KarlG and @StevenPicard - I have attached the original OculusSetup.exe to this post. It is the one from March 28th and it doesn't have the incorrect check for SSE4.2 - I think it will install the latest runtime that is available now, so hopefully that solves the problem.
Obviously you shouldn't run an exe posted by someone you don't know. I'm the developer of Live for Speed ( www.lfs.net ) and this is the exact file downloaded from Oculus ( www.oculus.com/setup ) back in March.
@cybereality if this is not allowed then obviously you can delete it, but it'll be interesting to know if it solves the problem. It really seems that some of your 'engineers' have got confused between minimum requirements and recommended requirements. Unless there is any truth in the suggestion that this is a deliberate artificial restriction due to a marketing deal with Intel, as suggested on the reddit thread about this subject. I prefer not to think you would engage in that type of practice.
12-02-2016 06:49 AM
zboson said:Maybe you can describe how you patched this so that people can do it manually for future releases. Is it just a CPUID check? Can this be fixed easily with a hex editor?
12-02-2016 06:58 AM
OpticKing said:
zboson said:Maybe you can describe how you patched this so that people can do it manually for future releases. Is it just a CPUID check? Can this be fixed easily with a hex editor?
He didn't actually. That was simply a version of the installer before the 4.2 check was implemented, still gives the latest runtimes, so should be the go-to for anyone with this issue.
03-12-2017 06:31 PM
03-13-2017 12:03 AM
03-13-2017 02:00 AM
03-13-2017 03:31 AM
Scawen said:
@Shoehash your comment is totally irrelevant. This thread is about a bug in the Oculus installer for the CV1. It refuses to install the software if the CPU doesn't support SSE4.2 instructions, although the software only requires SSE4.1 as was stated in the Oculus requirements when the CV1 was originally released. It's a very bad bug which stops people using their CV1 and would take 1 minute or so to fix, but Oculus has refused to fix it so far.
03-23-2017 08:30 PM
03-28-2017 06:13 PM
03-28-2017 07:10 PM
Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.
If you need an agent to help with your Meta device, please contact our store support team here.
Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.
Check out some popular posts here:
Getting Help from the Meta Quest Community
Tips and Tricks: Charging your Meta Quest Headset