kckarnige / oculusdummy

Oculus Killer, but for the Oculus Client.

IF YOU WOULD LIKE TO CONTINUE DEVELOPMENT CONTACT ME!!

Reasons to use Oculus Dummy

• When you use Link, the Oculus Client opens whether you like it or not, Oculus Dummy makes it a little less annoying, running as a tray application in the background.

• The Oculus Client runs on Electron, meaning ALL UI uses system resources, even if it's the 1,000th time you've opened a page.

• The Oculus Client uses system resources that could be use for more important things:

  • It uses your GPU for a bit on startup.
    • This is more of a nitpick than anything impactful if I'll be honest, especially if you have an iGPU and have it set to use that anyway.
  • Sometimes it randomly decides to use your CPU.
    • This is just stupid, especially if you're playing a CPU intensive game like BaS or Bonelab.
  • It can use an average of 200mb of memory, even in the damn settings menu.
    • Personally, I've seen it use as low as 158mb, up to 267mb of memory.

• The Oculus Client, with Oculus Dummy installed, loads faster, doesn't randomly use your CPU or GPU power, and uses around 40mb of memory when idle.

• Oculus Dummy works perfectly fine with Oculus Killer and Revive.

Reasons NOT to use Oculus Dummy (A sorta to-do list)

You need to switch back to the default client every time you need to:

• Change your refresh rate or render resolution
• Setup a new Oculus/Meta headset (Not something you'd likely do, but worth noting)
• Install and update your Oculus games*
• Change the build of an Oculus game (Ex. Switching B&S from U12 to U9 or BoneLab from Patch 2 to Patch 3 Beta)
• Toggling Developer Runtime Features
  • Changing "over Oculus Link" settings

*: can be done via the Oculus Dash for people who don't use Oculus Killer

Anymore questions?

Yeah? Well check out the wiki, I might've already answered it.

Installation

1. Open your file explorer and go to C:\Program Files\Oculus\Support\oculus-client\resources.

2. Rename the app.asar file to something else, I prefer "app.asar.bak" for clarity, though it doesn't matter.

3. Download this, and move it to the same folder.

4. Enjoy the extra bit of performance!

Uninstallation

1. Open your file explorer and go to C:\Program Files\Oculus\Support\oculus-client\resources.

2. Delete the app.asar file.

3. Rename your backup file (app.asar.bak) back to "app.asar".

4. Make sure to give Oculus Dummy a kiss before you leave it, it still loves you!

Building from source (Windows Only)

1. Clone the repository, I prefer using GitHub Desktop to make things easier.

2. Open the directory in your terminal and run pnpm i or npm i.

3. Run pnpm build or npm run build and wait.

4. The result should be located in the .dist folder, the built app.asar inside should work just like any other release build.

Credits

ArmCord - GitHub Actions build file

@CodTheFish - Testing earlier versions

oculusdummy's Issues

When there's an Oculus software update, OVRServiceLauncher spams the event log

I noticed I had a window pop up briefly every few moments and checked the event manager fo find several hundred entries "The operation completed successfully" by OVRServiceLauncher within just 40 minutes. At the same time, Service Control Manager reports several hundred "The Oculus VR Library Service service terminated with the following service-specific error:
An attempt was made to load a program with an incorrect format." errors.

Undoing OculusDummy allowed the app to update and stopped the messages.

AMAZING

Tried it just now. oculus dummy + ocus killer and IT IS FLAWLESS.