REGARDING : January 14,2020. Windows 7 Support End-License.
My question is about the fact that Oculus wont support windows 7 anymore.... So do you just remove DirectX 11 ? .... i mean I'm not very happy with this as i hate Directx12 <3... But mostly i wonder WHY since ... you dont need to remove directX11 .. Why just not keep it as an Extra package :D? you'd save 10 Sec of Compiling .. Not like it can be a big deal at any level BUT For LowEndSpecs PC... and Hard Enthuziams like me who NEED to run as efficient as possible with less power used as possible. I'm not upgrading to windows 10. I already have DirectX12 on my windows 7 :) . So If i had a favor. Do not Fix it if there is NO problem.... Do not just make the Oculus Client Detect that i am using windows 7 to pop a message box saying : Upgrade to Win10. This "check" will be the thing i will use to ***** your Client if you even Create it.... Now i can smeel lots and lots of Crys for Chrismas...at least in Canada thats how it sounds Like : "MY RIFT DOEST WORK ANYMORE MOM!!! Call the poLICE!...."
In short. Why remove Windows 7 support, What has changed(The big change from win7 to Win10 is only or even DirectX11-X12 related?).I dont need information, its all in the LOGS, but... would be gladly appreciated if i can Patch my Win 7 to keep on working with oculus. whitout Burning my PC components, Or at least knowing what i'm putting at risk with unpatched Win 10 Calls running on Win 7.
Past Situation to Learn from:
My personal Issue i had with the RIFT was In OculusSetup itself. A prompt Saying : You are missing CPU instructions SSE 4.2, Which i TOTALY did miss. But i still bypassed. This Instruction is to manage Multiple USB3 Synchronously. THus if not Interpreted, CAN still be used but as RAW CPU instruction, which are WAY heavier then Compiled Instruction sets.So 3 Sensors was out of Question,at least on usb 3.0 or could have burned my Components... Thats a Big CON right here, and i completly agree with if there is any; policyes towards not using the Recomended setup.
It just Makes Sense to 'End Win7 Support' To keep that "PLUGNPLAY"
From an Executor Perspective.Its easier to Replace DirextX11 by X12. Its Easy And you call it a Day whitout Effort.
From a Software Dev Perspective you could use DirectX999 at the end of the day, you know you'l make it work.
I Will probably need a member of the SoftDev Team:Someone who writed/Readed the OculusClient"sourcecode" ,To get me the accurate "changeLog" in the "Dependency" of OculusClient. If for some Godknown reasons the Oculus Rift Drivers will no longer have an "Windows 7" Compiled Build... I mean seriously. Just change MakeFile Version or. VC++2019 to VC++2015, hit COMPILE. and thats a Compatible Supported Build.
EVEN If it doesnt work. Release it to the public. They will Figure it out. Die hard Fans thats would spend entire MONTH on similar problem.
However... this time around the blame is all on You guys :'D
Seriously "i" am dealing with "Unsuported Software" from a product that
(1) Is still Supported RIGHT NOW (1)
So DRIVER compatibility SHOULDN'T be an issue
but apperently its the main TOPIC ._.
Windows 7 is software, Drivers are usually made for software.
If Windows 7 not supported, does that mean it won't be VC redist 2015 Compatible anymore?
IF thats the case... i'm telling you this is definitly ASKING for ANGRY gamers to reverse engeeneer oculus into source code and simply making it work, Because the GUY at the TOP didnt bother wasting an EXTRA CLICK on the "COMPILE" BUTTON. This is at least insulting... but also lacking profesionalism when you advertise you're product runs on 8GB of RAM. But Windows 10 eats 4gb on IDLE, so basicly it DOESN'T work AS intended AS SOON you Step Outside the "Oculus Software". Stutters, and Sync-drops. Everything should JUST works... Unlike Some other Compagny that Lost my faith.
(2) IF its Software Compt. Always Going to be a WORKING Solution (2)
Theoricly the OculusClient.exe Shifting from DirectX11 to DirectX12, Thats not even what i'm affraid of.
DX12 is Win7 Compatible
I dont mind using DirectX12,Creating new services...
I'm scared that after 2020Jan14 That the OculusClient doesn't run on Win7, because it was TWEAKED to RUN on Win10, and to EXIT on Win 7. I'm scared that there will be "OSCheck" in the OculusCLient that would just tell me to upgrade to Windows 10"returning"call(function.exit)". WHICH are NOT NEEDED?. If its NOT BROKEN, DO NOT "PRETEND" like you Fixed it, or that its uncompatible. SAME as what happend to "MISSING CPU SSE 4.2 Instruction" EVEN If it could BREAK my Computer: Do not STOP us from doing what we want. Just WARN us, give the explaination : SSE 4.2 : Fire : Can terminate you're computer if not used properly. And most people They only readed "Missing CPU" and already gave up. I can hear everyone from the other Spectrum that i come from. "Wouldn't this hurt the NAME, the image, Include a 1 button KILLSWITCH? for the hardware to BREAK"! MosT the People, do not even know. They will just do what they know. Install the OculusCLient on Windows. Thats it. Done. Where it really matters is for those who MAKE computers. Those will be the REAL judge at the end of the day if you're product Sold_or_Sucked. HOWEVER, When you put a Wall, a simple last minute descision. "SSE4.2.CHECK". Like in the OculusInstaller, That requires me to Use an SSE4.2 Compatible CPU PC 1) Install Oculus 2) Swap Hard drive back to NON 4.2 SSE CPU PC 3) It just Works like a charm. This type of SITUATION is VERY embarasing as it makes me rethink my loyalty towards the product i've commited to, even for the simplest question as "Did they even Tested their own product before Trowing in a GTX 1060 MINIMUM req Spec SHEET?". Thus why Oculus is Looked at in weird ways when comparing to Competitors HEADSETS. The software is full of "UserFriendly"Check that aren't MEANT for "NormalUsers" Exemple :Minimum Requirements : Ryzen 3 x1300T SO NOBODY is gonna install OCulus and expect to to work PROPERLY Using : Phenom X6 1055T : That MISSES CPU instructions(That already sounds bad enought) -As a software Dev, you wasted 15 Minutes Making the "SSE4.2.CHECK" -As a Personal User, i also wasted 30 minutes to get around that "SSE4.2.CHECK", which could have been implemented as a "Warning, "Hurt me plenty";Button"
:) Sincerily, ÐarkMøðns