X-Factor Optimization 1.0.3

X-Factor Optimization 1.0.3 is a focused rendering-performance update built on top of the optimization stack introduced in 1.0.2.

The main addition in this release is Greedy Meshing 0.5.3+26.2, configured specifically for X-Factor's existing Sodium-based rendering stack.

Rather than adding another large group of mods, 1.0.3 focuses on reducing the amount of terrain geometry that has to be submitted and rendered.

Major Highlight: Greedy Meshing

Added:

Greedy Meshing 0.5.3+26.2

Greedy Meshing optimizes chunk geometry by merging compatible adjacent block faces into larger quads.

Instead of rendering many individual faces across a large flat or uniform surface, compatible faces can be represented by a much smaller amount of geometry.

The goal is to reduce:

Terrain vertex count
Quad count
Draw workload
GPU geometry processing
CPU-side terrain rendering overhead
Rendering cost at high FPS and higher render distances

This complements X-Factor's existing rendering stack rather than replacing it.

X-Factor Greedy Meshing Configuration

X-Factor 1.0.3 ships Greedy Meshing enabled with an aggressive performance-focused configuration.

Greedy Meshing: ON
Aggressive Greedy: ON
Greedy Water: OFF
Merge Oriented Blocks: ON
Debug Wireframe: OFF
Debug Comparison: OFF
Debug Triangles HUD: OFF

Aggressive Greedy

Aggressive Greedy is enabled.

This allows Greedy Meshing to merge more terrain geometry than its conservative mode, including merges that cross some ambient-occlusion boundaries.

The result can be fewer quads and lower rendering workload, although lighting across very large merged surfaces may look slightly different from vanilla.

Greedy Water

Greedy Water remains disabled.

Water meshing is considerably more experimental, so X-Factor does not enable it by default.

Oriented Blocks

Merging of supported oriented blocks is enabled to extend the optimization beyond only the simplest terrain cases.

Performance Results

This update produced one of the largest rendering-performance improvements observed during X-Factor development so far.

In my testing, enabling Greedy Meshing produced FPS increases exceeding 900 FPS compared with X-Factor 1.0.2 in both:

Singleplayer testing
Multiplayer testing

This result was observed on the development/test system and should not be interpreted as a guaranteed +900 FPS increase on every computer.

The actual improvement depends heavily on:

GPU
CPU
Render distance
Resolution
World geometry
Number and type of visible blocks
Server environment
Existing FPS before the update
Shader usage

Greedy Meshing is particularly effective when a scene contains large amounts of compatible terrain geometry that can be merged.

The important result for X-Factor is not only the peak FPS number: 1.0.3 substantially reduces the amount of terrain geometry that the existing rendering stack has to process.

Why This Works Well With X-Factor

X-Factor already contains several optimizations aimed at different stages of the rendering pipeline:

Sodium
Rendersnap
ImmediatelyFast
More Culling
Optimized Block Entities
Particle Core
Signs Faster
BadOptimizations
Gnetum
Iris

Greedy Meshing attacks a different part of the problem.

Culling

Mods such as Sodium, Rendersnap, and More Culling try to avoid rendering geometry that should not be visible.

Greedy Meshing

Greedy Meshing reduces the amount of geometry required for surfaces that still need to be rendered.

Rendering optimizations

Sodium, ImmediatelyFast, Rendersnap, and the rest of the rendering stack then process that reduced workload.

The result is a layered approach:

Cull unnecessary geometry
        ↓
Merge compatible visible geometry
        ↓
Process fewer vertices and quads
        ↓
Render through the optimized Sodium stack

This is why Greedy Meshing can provide a meaningful improvement even in a pack that already has extensive rendering optimization.

Compared With X-Factor 1.0.2

Added

Greedy Meshing 0.5.3+26.2

Added configuration

config/greedy_meshing.json

Greedy Meshing defaults

enabled=true
aggressiveGreedy=true
greedyWater=false
mergeOrientedBlocks=true
debugWireframe=false
debugComparison=false
debugTrianglesHud=false

Removed

No mods were removed from the 1.0.2 manifest.

Updated

No existing Modrinth-managed mods were replaced or version-changed in this release.

This means 1.0.3 is intentionally a focused update: the tested 1.0.2 optimization stack remains intact and Greedy Meshing is added on top.

Retained From X-Factor 1.0.2

The performance additions introduced in 1.0.2 remain included:

BadOptimizations
FerriteCore
ScalableLux
Signs Faster
Tick Sync
Eslium
Put A Plug In it! (PAPI)

The existing core optimization stack also remains:

Sodium
Lithium
Rendersnap
ImmediatelyFast
Async
Ferrite
More Culling
Optimized Block Entities
Particle Core
Modernica
Gnetum
Iris
ViaFabricPlus

X-Factor's custom components also remain:

Client State Guard
Rendersnap Sodium Menu Compat
X-Factor Compatibility Patcher
xfactor-compatibility-patches.txt

Shader Compatibility Notice

Greedy Meshing provides its largest benefit when its terrain-meshing path can operate normally.

Shader packs may reduce the available optimization because Greedy Meshing has more limited compatibility with shader-modified terrain rendering.

X-Factor continues to include Iris, but no shader pack is forced.

Players comparing performance should test with the same shader state in both versions:

Shaders OFF vs Shaders OFF

or:

Same shader pack vs Same shader pack

Comparing a shader-enabled run against a shader-disabled run is not a valid measure of the 1.0.3 improvement.

Visual Differences

Because Aggressive Greedy is enabled, very large merged surfaces can have slightly different ambient-occlusion or lighting transitions compared with normal per-face terrain rendering.

This is an intentional performance trade-off in the X-Factor configuration.

If a specific block, texture, or lighting situation renders incorrectly, report the exact block and location together with screenshots and the full log.

Benchmarking X-Factor 1.0.3

For meaningful comparisons with 1.0.2:

Use the same Minecraft world or server.
Use the same player location.
Use the same camera direction.
Let chunks finish loading before recording a static FPS comparison.
Use the same render distance.
Use the same simulation distance.
Keep resolution identical.
Keep shaders in the same state.
Disable VSync.
Use Unlimited FPS when testing maximum rendering throughput.
Run each test more than once.

For chunk-traversal testing, use the same route where possible.

For multiplayer testing, server population and network conditions can affect results, so several runs are preferable.

Spark Profiling

X-Factor performance testing can be performed with Spark using the client profiler.

Useful test workloads include:

Fully rendered static-world baseline
Unlimited-FPS rendering
Rapid chunk traversal
Multiplayer gameplay
Entity-heavy server areas
Menu navigation
Allocation profiling

A high FPS number alone does not identify whether a build is healthy.

Useful metrics also include:

Frame-time consistency
CPU hotspots
Allocation rate
Garbage collection
Render-thread contention
Chunk-worker utilization
GPU utilization

The objective remains high throughput without introducing runaway CPU paths, excessive allocations, or unstable world transitions.

Updating From X-Factor 1.0.2

A clean launcher update should be sufficient because 1.0.3 does not replace the existing optimization stack.

After updating, confirm that the mods folder contains:

greedy-meshing-0.5.3+26.2.jar

The included configuration should be available at:

config/greedy_meshing.json

Do not install a second Greedy Meshing build alongside the version supplied by X-Factor.

As with previous releases, avoid using a launcher-wide Update All Mods action. Rendering-mod updates can change compatibility behavior and may not match the combination tested for the pack.

Compatibility

Minecraft: 26.2
Mod loader: Fabric
Environment: Client-focused
Rendering: Sodium-based
Shaders: Iris included
Server installation: Not required for Greedy Meshing

Reporting Rendering Problems

When reporting a Greedy Meshing or rendering issue, include:

X-Factor version
Minecraft version
GPU
GPU driver version
CPU
Render distance
Resolution
Whether shaders are enabled
Shader pack name, when applicable
The affected block or terrain type
Screenshots of the rendering problem
Full latest.log

For performance reports, also include:

X-Factor 1.0.2 FPS
X-Factor 1.0.3 FPS
Whether FPS was capped
Whether VSync was enabled
Test location
Singleplayer or multiplayer
Spark profile link when available

Summary

X-Factor 1.0.3 is intentionally smaller than the previous update, but its impact can be much larger.

1.0.2 expanded optimization coverage.

1.0.3 reduces the terrain geometry that the rendering stack has to process.

With Greedy Meshing enabled and tuned for X-Factor, development testing has shown FPS gains exceeding 900 FPS in both singleplayer and multiplayer scenarios.

Results will vary by hardware and workload, but this update represents a major step forward in X-Factor's raw rendering throughput.

Join the X-Factor Discord

X-Factor Optimization