4 ms·

Seems fair enough for a fairly new software.

by keyle 11y ago

taneq 11y ago
Oculus VR was founded in 2012, and bought out by Facebook in 2014. It's not like they just bashed out a demo on the weekend, this is meant to be production-ready code.
- mappu 11y ago
  Until recently (CV1 engineering samples), the only publicly available software that could be reasonably considered "Oculus Software" was the driver and its configuration utility, clocking in at about ~50MB installed. The support article in question is (presumably) referring to Oculus Home / Oculus Store, which (presumably) don't date back that far.
fungos 11y ago
Don't think so. It looks more like some really bad choices mostly like bad dependencies or hard-coded things or something else. But to me this reflects the product quality and most importantly a big yellow warning on software quality.
- brudgers 11y ago
  To me, closely following the standards for Windows means less code and in particular less code that introduces edge cases for the sake of edge cases.
  - brazzledazzle 11y ago
    Is "installing only to C:\" an actual Windows standard? I'm fairly certain Windows doesn't have a problem installing software to different drives.
    - brudgers 11y ago
      Per the article Occulus installs to C:\program files(x86)\ and that is the standard location for 32 bit (x86) program installation on Windows 64 bit systems. Many, but not all programs [obviously] can be installed at non-standard locations. See Installer and Logo Certification Requirement 2.4 here: https://msdn.microsoft.com/en-us/library/windows/desktop/aa372825(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/windows/desktop/aa3...
      - imron 11y ago
        It's not standard - at least not per any official MS documentation. There are specific API calls you are supposed to make to query the program files directory, which will be different depending on whether you are a 32bit or 64bit program, and where the user/administrator has configured the program files folder to be. This is also like windows programming 101, so I'm honestly a bit shocked to see oculus dropping the ball on this.
        cnvogel 11y ago
        Specifically https://msdn.microsoft.com/en-us/library/windows/desktop/bb762188(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/windows/desktop/bb7... https://code.msdn.microsoft.com/windowsapps/CppShellKnownFolders-7df114ad https://code.msdn.microsoft.com/windowsapps/CppShellKnownFol... hr = SHGetKnownFolderPath(FOLDERID_ProgramFiles, 0, NULL, &pszPath);
- drawkbox 11y ago
  It probably started with a // TODO add file path system. Then they just got to building and it just never got on the update finished list, and many developers started using it internally. Now it is hard to do, or there are so many devs noone thinks it is their job as it isn't completing their milestones for ship. These situations probably got thicker when they were purchased by Facebook. Could have taken 1-2 days in early development max or even 5 minutes at the start, but now it is layers thick. This can happen to many systems either from external libraries, quick prototyping without cleanup or other reasons that just stick around. Then some unluckly schlup gets stuck with the 'Pathing Issue' that turns into a 3 month ordeal, everyone feels sorry for the coder and his life is ruined for months. It could also be those situations where everything was done in '5 minutes' but ends up sapping 3 months of dev time fixing. This happens often in game development, 'Hey dude I whipped up an AI system in five minutes' and then it works but doesn't work, then ends up being the source of bugs for most of the project. Watch out for the '5 minutes' architecture. Hopefully this isn't a sign of quality across the project.

Seems fair enough for a fairly new software.

by keyle 11y ago

Seems fair enough for a fairly new software.

taneq 11y ago

Oculus VR was founded in 2012, and bought out by Facebook in 2014. It's not like they just bashed out a demo on the weekend, this is meant to be production-ready code.

mappu 11y ago
Until recently (CV1 engineering samples), the only publicly available software that could be reasonably considered "Oculus Software" was the driver and its configuration utility, clocking in at about ~50MB installed. The support article in question is (presumably) referring to Oculus Home / Oculus Store, which (presumably) don't date back that far.

fungos 11y ago

Don't think so. It looks more like some really bad choices mostly like bad dependencies or hard-coded things or something else. But to me this reflects the product quality and most importantly a big yellow warning on software quality.

brudgers 11y ago
To me, closely following the standards for Windows means less code and in particular less code that introduces edge cases for the sake of edge cases.
- brazzledazzle 11y ago
  Is "installing only to C:\" an actual Windows standard? I'm fairly certain Windows doesn't have a problem installing software to different drives.
  - brudgers 11y ago
    Per the article Occulus installs to C:\program files(x86)\ and that is the standard location for 32 bit (x86) program installation on Windows 64 bit systems. Many, but not all programs [obviously] can be installed at non-standard locations. See Installer and Logo Certification Requirement 2.4 here: https://msdn.microsoft.com/en-us/library/windows/desktop/aa372825(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/windows/desktop/aa3...
    - imron 11y ago
      It's not standard - at least not per any official MS documentation. There are specific API calls you are supposed to make to query the program files directory, which will be different depending on whether you are a 32bit or 64bit program, and where the user/administrator has configured the program files folder to be. This is also like windows programming 101, so I'm honestly a bit shocked to see oculus dropping the ball on this.
      - cnvogel 11y ago
        Specifically https://msdn.microsoft.com/en-us/library/windows/desktop/bb762188(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/windows/desktop/bb7... https://code.msdn.microsoft.com/windowsapps/CppShellKnownFolders-7df114ad https://code.msdn.microsoft.com/windowsapps/CppShellKnownFol... hr = SHGetKnownFolderPath(FOLDERID_ProgramFiles, 0, NULL, &pszPath);
drawkbox 11y ago
It probably started with a // TODO add file path system. Then they just got to building and it just never got on the update finished list, and many developers started using it internally. Now it is hard to do, or there are so many devs noone thinks it is their job as it isn't completing their milestones for ship. These situations probably got thicker when they were purchased by Facebook. Could have taken 1-2 days in early development max or even 5 minutes at the start, but now it is layers thick. This can happen to many systems either from external libraries, quick prototyping without cleanup or other reasons that just stick around. Then some unluckly schlup gets stuck with the 'Pathing Issue' that turns into a 3 month ordeal, everyone feels sorry for the coder and his life is ruined for months. It could also be those situations where everything was done in '5 minutes' but ends up sapping 3 months of dev time fixing. This happens often in game development, 'Hey dude I whipped up an AI system in five minutes' and then it works but doesn't work, then ends up being the source of bugs for most of the project. Watch out for the '5 minutes' architecture. Hopefully this isn't a sign of quality across the project.