MC-WIKI.net
Embeddium Wiki › Guides › Embeddium Advanced Rendering Optimizations: A Usage Guide

Embeddium Advanced Rendering Optimizations: A Usage Guide

guide

Embeddium provides a set of advanced rendering options that reduce the work your GPU and CPU do each frame. Most of these live in the video settings, and several are toggles you simply turn on or off. A few are numeric fields where you choose a value. Some changes require quitting and relaunching the game before they take effect.

Face and Geometry Optimizations

Use Block Face Culling — When this is on, only block sides that point toward your viewpoint get sent to the renderer. Faces aimed away from you are discarded early, which cuts memory traffic and GPU time. If a resource pack produces visible gaps or holes in blocks, turn this off.

Use Compact Vertex Format — This shrinks the data stored per vertex when chunks are drawn. The result is lower graphics memory use and less bandwidth consumed, which matters most on integrated graphics. The trade-off is reduced precision in position and texture coordinates, which can cause flickering overlaps (z-fighting) with certain resource packs. If Oculus is present, turning this off changes nothing.

Use Accurate Quad Shading — With this enabled, non-vanilla block faces receive lighting computed from the direction they truly face rather than a snapped axis direction. Lighting looks better when the Forge experimental light pipeline is off, which is the recommended setting for performance. It does nothing while that pipeline is on.

Use Render Pass Optimization — Embeddium inspects block model faces flagged as transparent or translucent, checks whether the texture is actually opaque or see-through, and picks a faster render pass when appropriate. This has no effect while a shader pack is running.

Visibility and Culling

Use Entity Culling — Entities that aren't inside any chunk you can currently see get skipped entirely during drawing. This saves work on entities buried underground or hidden behind walls.

Translucent Face Sorting — Enabling this makes see-through surfaces like stained glass and water blend in the correct order.

Animate Only Visible Textures — Only animated textures that are actually on screen get updated. Heavier resource packs benefit the most. If some textures stop animating, disable this.

Fog-based chunk hiding also exists: chunks fully obscured by fog are not drawn, which helps most when fog is thick, such as underwater. It can introduce visual seams between sky and fog in certain situations.

Chunk Building and Upload

Chunk Update Threads — This number sets how many threads build chunks. Raising it speeds up chunk loading and refreshing, though frame timing can suffer.

Always Defer Chunk Updates — When on, rendering never blocks waiting for a chunk rebuild, even an urgent one. Frame rates can rise substantially, but the world may visibly lag behind.

Use Persistent Mapping — A small memory region stays permanently mapped as a staging buffer for chunk uploads, lowering CPU cost and smoothing frame times during chunk loads and updates. It needs OpenGL 4.4 or ARB_buffer_storage.

CPU Render-Ahead Limit — This caps how many frames the CPU may queue while waiting for the GPU. Values at either extreme can make frame rates unstable.

Distance, Quality, and Misc

Render distance governs how far terrain draws; shorter values raise frame rates. Simulation distance governs how far terrain and entities load and tick; shorter values lighten the internal server. Entity render distance controls how far away entities appear. Other quality controls cover clouds, rain and snow, leaves, particles, smooth lighting, biome color sampling range, mipmap count, entity shadows, and the vignette effect.

Use No Error Context — Creates the OpenGL context without error checking. This may help performance slightly but raises the chance of a hard crash instead of graceful error handling. Turn it off if you get sudden unexplained crashes.

Warnings and Compatibility

If a message says video settings need a restart, relaunch the game to apply them. Outdated NVIDIA drivers (older than 536.23) cause severe problems with Embeddium and should be updated. PojavLauncher is unsupported and likely to produce extreme performance problems, graphical glitches, and crashes. Embeddium also reports resource packs that are incompatible or possibly incompatible, and flags conflicting mods known to cause rendering trouble; check the game log for details.