Distant Horizons and C2ME: Compatibility Settings
C2ME can change chunk-generation and IO behavior, which makes it important to test the combination carefully. The official compatibility guidance recommends disabling specific C2ME features when diagnosing DH world-generation problems.
Common symptoms
- world generation crashes with C2ME installed
- LOD generation stops near newly generated terrain
- the game freezes during exploration
- the problem disappears when C2ME is removed
Step-by-step fix
Reproduce with a clean profile
Test Distant Horizons without C2ME first. This confirms whether the base loader, DH build, and world are working.
Disable multithreaded world generation
Use the official Mod Support guidance and disable C2ME world-generation features when testing generation conflicts.
Check optimized IO and serializer options
If the issue remains, compare C2ME settings for optimized IO and garbage-free chunk serialization rather than changing DH settings at random.
Test a new world
A world-generation conflict may only appear with a particular generator or mod combination. Compare a clean vanilla world before reporting the issue.
Include the full mod list
Record Minecraft, loader, DH, C2ME, world-generation mods, Java, GPU, and the first meaningful crash-report error.
Sources and verification scope
Reviewed by the DistantHorizonsGuide Editorial Team against the public release listing and project distribution page. These instructions are conservative troubleshooting steps, not a guarantee for every modpack. Exact menu names and compatibility can change by Minecraft, loader, and DH build.
Still stuck?
Record your Minecraft version, DH version, loader, shader pack, GPU, and crash log before asking the community. That information makes compatibility problems much easier to diagnose.