https://github.com/kckarnige/oculusdummy

Oculus Killer, but for the Oculus Client.
https://github.com/kckarnige/oculusdummy

electron lightweight meta meta-quest oculus oculus-client oculus-killer oculus-quest oculus-rift oculus-software open-source replacement vr

Last synced: 11 months ago
JSON representation

Oculus Killer, but for the Oculus Client.

• Host: GitHub
• URL: https://github.com/kckarnige/oculusdummy
• Owner: kckarnige
• License: mpl-2.0
• Created: 2023-10-30T11:14:03.000Z (about 2 years ago)
• Default Branch: main
• Last Pushed: 2024-08-13T16:14:00.000Z (over 1 year ago)
• Last Synced: 2025-03-02T01:39:55.949Z (11 months ago)
• Topics: electron, lightweight, meta, meta-quest, oculus, oculus-client, oculus-killer, oculus-quest, oculus-rift, oculus-software, open-source, replacement, vr
• Language: JavaScript
• Homepage: https://kckarnige.online/OculusDummy
• Size: 697 KB
• Stars: 9
• Watchers: 1
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • Funding: .github/FUNDING.yml
  • License: LICENSE

Awesome Lists containing this project

README

          
Check out what the creator of Oculus Killer is working on!!


For more information, check out their Discord!!


Check out my slightly older brother!






    

        

        

     








    

        

    



## 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 if your using this, but worth noting)*

- Install and update your Oculus games\*

- Change the build of an Oculus game *(Ex. Switching B&S from 1.0 to U9 or BoneLab from Patch 4 to Patch 3 Beta)* *

- Toggling Developer Runtime Features

    - Changing "over Oculus Link" settings

> *\*: can be done via other means such as the Oculus Dash, the Quest mobile app, or the Meta website*

## Anymore questions?

Yeah? Well [check out the wiki](https://github.com/kckarnige/OculusDummy/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](https://github.com/kckarnige/OculusDummy/releases/latest/download/app.asar), 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](https://github.com/ArmCord/ArmCord)* - GitHub Actions build file

*[@CodTheFish](https://github.com/CodTheFish)* - Testing earlier versions