[FEATURE] - Add an option to disable Oculus Services

michauMiau commented 1 month ago

Before continuing...

[X] I agree to follow Atlas' Code of Conduct
[X] I have searched our issue tracker to verify that the issue hasn't been reported already
[X] I have searched the Atlas documentation beforehand for a solution
[X] I am on the latest version of Atlas, and didn't do an unsupported upgrade

What is your feature request regarding to?

Atlas Playbook

Is your feature request related to a problem? Please describe.

Oculus services take up resources even when not in use

Describe the solution you would like.

Add an option to set Oculus VR Runtime Service (OVRService) Service to run on demand instead of launching automatically and also add a option to the context menu to disable the oculus service

Describe alternatives you have considered.

Manually set the Oculus service to on demand using the services app in windows. The only side effects this causes is not being able to start Oculus (Meta Quest) link from the headset and longer app load times

Additional context.

I am happy to provide further info if needed

Ast3risk-ops commented 1 month ago

How is this related to windows? If you want it, do it yourself.

90% of users won't have the OVR services.

michauMiau commented 1 month ago

This is meant as an additional feature that anyone who needs it can enable it. For example Atlas OS has a feature to disable Nvidia display container. People who use AMD GPUs don't need this but it doesn't mean It's not useful

Ast3risk-ops commented 1 month ago

This is meant as an additional feature that anyone who needs it can enable it. For example Atlas OS has a feature to disable Nvidia display container. People who use AMD GPUs don't need this but it doesn't mean It's not useful

A larger chunk of people have nvidia gpus than an Oculus headset. Most people would just set up ALVR anyway, voiding the need for Oculus Hub entirely (as long as all your games are on SteamVR).

However, you'd have to see what the team says, this is just my opinion :P

kronflux commented 1 month ago

Oculus is not included in Windows, AtlasOS is meant to be installed on a fresh installation of Windows, anything beyond that is out of scope for this project. Nvidia and AMD related toggles are base-level hardware support, not accessories, which is why it would make sense to include these. Windows installs Nvidia and AMD drivers automatically, as they are required for base-level functionality of the PC.

With that being said, if you still insist this is a highly valuable function, I suggest opening a pull request for it, but it is extremely unlikely anyone associated with AtlasOS will research and investigate something they may or may not even have the hardware required to test with, in order to add this functionality for the likely small number of users who would use it.

Ast3risk-ops commented 1 month ago

Oculus is not included in Windows, AtlasOS is meant to be installed on a fresh installation of Windows, anything beyond that is out of scope for this project. Nvidia and AMD related toggles are base-level hardware support, not accessories, which is why it would make sense to include these. Windows installs Nvidia and AMD drivers automatically, as they are required for base-level functionality of the PC.

With that being said, if you still insist this is a highly valuable function, I suggest opening a pull request for it, but it is extremely unlikely anyone associated with AtlasOS will research and investigate something they may or may not even have the hardware required to test with, in order to add this functionality for the likely small number of users who would use it.

I have a Quest 2, but my PC runs Linux :)

Still, personally I'd just use ALVR.

Atlas-OS / Atlas