Embeddium FAQ

Yes—Embeddium is designed to work with Oculus shader packs and acts as the rendering engine for them. Install Oculus alongside Embeddium, then load your shader pack through the Oculus settings in-game.

Embeddium rewrites the graphics pipeline with modern OpenGL methods, which typically raises frame rates by optimizing chunk rendering and reducing memory overhead. Your actual FPS gain depends on your hardware and how many mods are in your pack.

No—Embeddium and OptiFine conflict because they both replace Minecraft's rendering engine. Choose one or the other, not both.

Check that Embeddium is compatible with your Minecraft version and Forge version. If crashes persist, try removing shader packs or other rendering mods, then re-add them one at a time to isolate the conflict.

Yes—by cutting down memory usage, Embeddium helps prevent the frame rate drops and stuttering that happen during extended gameplay. This is especially noticeable in large modpacks with many loaded chunks.

Slow chunk loading can come from insufficient RAM allocation, too many mods competing for resources, or a slow storage drive. Ensure your launcher allocates enough RAM and check that your modpack isn't overloaded with content mods.

Yes—Embeddium only changes how the game renders graphics, not world generation or gameplay mechanics. Your worlds and progress are safe.

Embeddium is a client-side mod, so you can install it on your own launcher without the server needing it. However, check your server's mod policy first.

Embeddium is a Forge port that includes bug fixes and tweaks specifically for heavy modpack environments, whereas Sodium is the original Fabric mod. Both optimize rendering, but Embeddium integrates better with Forge modpacks.

Visual glitches usually mean a mod conflict or incompatible shader settings. Try disabling shaders temporarily, update Embeddium and your other mods, or check mod compatibility reports for your specific pack.