CLab

Revolutionizing Minecraft Entity Rendering with CLab Mod

Introducing CLab, a cutting-edge client-side modification that enhances entity rendering in Minecraft by employing Hardware Occlusion Culling (HOC). This mod utilizes GPU OpenGL occlusion queries to directly assess entity visibility, effectively eradicating the errors and drawbacks associated with conventional CPU-driven pathtracing methods.

Key Highlights

• Advanced Hardware Occlusion Culling (HOC)

Employs GPU queries to check entity bounding boxes against the depth buffer, accurately measuring occlusion based on rendered terrain instead of relying on CPU-based world model approximations.

• No False-Positive Culling

This feature is grounded in truthful depth buffer testing, ensuring that any entity with even a single visible pixel won’t be obscured. There’s no need for a whitelist or specific patches for individual mods.

• Non-Intrusive Rendering Layer

Determines whether to activate the entity render method without affecting client-side ticks, animation states, positional interpolation, or any other logical processes. This means that trains, vehicles, and mechanisms function as expected.

• Automatic Leaf Face Culling

Efficiently removes leaf faces obstructed by neighboring leaves, decreasing the burden of terrain rendering.

• Plug-and-Play Setup

No need for an entity whitelist, distance thresholds, or tick-culling toggles. Simply install the mod and enjoy your game.

Technical Insights

CLab employs Hardware Occlusion Culling in the following manner:

1. When rendering entities, it submits the entity’s bounding box as an occlusion query to the GPU (OpenGL Query).
2. The GPU evaluates the bounding box against the pre-rendered depth buffer at the hardware level.
3. The results from the previous frame’s query are checked: if no pixels passed the depth test, the rendering for that entity is skipped.

This creates a significant difference:

| Aspect | Standard CPU Pathtracing | CLab HOC |

|——–|————————-|———-|

| Basis for Occlusion | Simplistic assumptions about the world model | Actual depth buffer rendered by the GPU |

| False Positives (hiding visible entities) | Common, especially near non-solid blocks | Highly unlikely |

| Entity Tick/Animation | Often halted or skipped | Fully unaffected |

| CPU Workload | Ongoing background traversal | Render thread submits AABB only; the GPU handles everything else asynchronously |

| Configuration Needs | Requires whitelists, distance limits, compensatory thresholds | No configurations necessary |

⚠️ Important Compatibility Guidelines

• Hardware Requirements: CLab necessitates a dedicated graphics card with OpenGL version 3.3 or above. While most contemporary GPUs will fulfill this requirement, some older integrated graphics units or outdated drivers may fall short.
• Incompatibility with other Culling Mods: It is essential to avoid using CLab alongside EntityCulling or any mod that alters entity/block visibility. Although these mods deploy different methodologies, they ultimately clash when it comes to visibility decisions. Using multiple culling mods will not boost performance; rather, they could conflict and negate each other’s enhancements, resulting in wasted resources and potential visual issues. For optimal performance, only CLab should be enabled.

Compatibility and Future Development

The current design aims to ensure compatibility with older devices as well as macOS systems. A more sophisticated technique exists, but it would introduce compatibility challenges for these platforms. Testing and development are conducted on a Mac, which currently limits potential advancements. There are plans to shift to a machine with OpenGL 4.6 support shortly. Once that transition is complete, an automatic system will be introduced to choose the most suitable method during the loading phase.