
Oculus Mod | Shaders for Modded Minecraft
Oculus Mod brings shader pack support to modded Minecraft, so you can finally run packs like Complementary without giving up the rest of your mods.
You've spent weeks building up a modded world, and shader packs still feel out of reach. That's exactly the gap Oculus fills. It's an unofficial fork of a widely used open-source shader mod, maintained by Asek3 and rebuilt to run inside heavily modded installs. The idea caught on, to the tune of roughly 38 million downloads, and it has powered some of the biggest modpacks around.
Classic Shader Packs Run Without Edits
Backwards compatibility is one of the project's headline promises. Packs written for the old ShadersMod format should run as-is, with no modifications required on your end. That covers the long tail of older packs many players already have saved. Once a pack is active, you get the same per-pack settings screen and shader keybinds as the upstream shader project, so tuning shadows, clouds, and water feels familiar. There's also a Shader Packs screen right inside the video settings menu, which keeps switching packs down to a couple of clicks.
Performance With Rubidium or Embeddium
Oculus is not a renderer. It layers shader support on top of one, which is why a companion mod is mandatory. Older files pair with Rubidium, while the newest releases call for Embeddium instead. With the right renderer underneath, the mod is built to fully utilize your graphics card, which is what gives you headroom with shaders on.
The real gotcha is that the required renderer changes between releases, and pairing the wrong one is a common crash cause. Check the dependency list printed on the exact file before anything goes into your mods folder. Also know that Create's Flywheel rendering backend shuts off its optimizations while shaders are active, which makes big Create builds noticeably heavier. A separate community Flywheel compatibility mod restores that loss, and it's the standard fix in shader-running Create packs.
Modpack Compatibility and Known Render Quirks
Making shaders behave alongside other mods is a stated goal, framed as a best-effort promise rather than a perfect one. In practice, Oculus has carried massive packs, including All the Mods 9 running Complementary Shaders. Heavily modded scenes can still produce render quirks, though. The project's public tracker documents cases like a MekaSuit and the player's hand failing to draw with shaders on, or moving Immersive Engineering machines going invisible. If something like that bites you, update Oculus and your renderer together, since matched versions clear up most render bugs. Stubborn mod combinations can be version-sensitive, and stepping back one renderer build has resolved startup crashes in reported cases.
How to Install Oculus
Oculus runs on Forge and NeoForge, with no Fabric or Quilt builds at all. It exists because the original Iris targets different loaders, so Asek3 keeps this fork going on its own. One note up front: this is a client-side mod, unsupported on dedicated servers, so skip the server install entirely.
- Install Forge or NeoForge, and make sure the loader lines up with the Oculus file you plan to grab.
- Add the matching renderer. Most files need Rubidium, while the newest release calls for Embeddium. The split mirrors how Iris works with Sodium: the renderer does the heavy lifting, and Oculus adds shader support on top of it.
- Download the Oculus file for your loader and Minecraft version, then drop it into your mods folder. Keep the December 2024 release date in mind when you pick, since nothing newer exists.
- Keep OptiFine out of your mods folder entirely. The project is blunt about this: Oculus is not and never will be compatible with OptiFine.
- Move your shader pack .zip files into the shaderpacks folder inside your game directory. If that folder doesn't exist yet, launch the game once and it should appear.
- Open Video Settings, then the Shader Packs screen, and select your pack. Toggle it in game with the shader keybind, and tune it through its per-pack settings.
One courtesy to remember: bug reports go to Oculus' own tracker, not to the Iris developers, since they don't maintain this fork.
Oculus FAQ
Does Oculus need to be installed on the server?
No. It's a client-side mod, required on your own game and unsupported on dedicated servers. Installing it server-side gains nothing, and dedicated servers don't run it at all. Each player who wants shaders simply installs it on their own game.
Why does Minecraft crash when I launch with Oculus?
The renderer pairing is the usual suspect. Different files require either Rubidium or Embeddium, and mixing the wrong pair is a common crash cause, so match the dependency list on your exact file first. If the pairing is already right, certain mod combinations are picky about the exact renderer build, and stepping back one Embeddium release has fixed startup crashes in reported cases.
Is Oculus still being updated?
Not actively. The newest files shipped in December 2024 and nothing has landed since, so there are no releases for newer Minecraft versions. For the latest game versions, the shader mod Oculus is based on now ships its own official builds instead.
Can I use Oculus in big modpacks?
Yes. Broad compatibility with other mods is a design goal, and it has been the shader engine behind major packs running Complementary Shaders. Expect the occasional mod-specific render quirk in heavily modded scenes, like machines or armor pieces failing to draw, but keeping Oculus and your renderer on matched versions fixes most of it.
If you want the full picture on the upstream project, start with the shader mod Oculus forks, and our shader pack installation walkthrough covers folder setup in more detail. The general mod installation guide and the matching loader guide round out the rest of a fresh modded setup.
Compatibility & downloads

Discussion
No comments yet
Be the first to start the discussion.







