Validate LOD loading, shader depth and current terrain draw paths

This commit is contained in:
Cosmic
2026-10-17 18:13:20 -04:00
parent 9ce739796e
commit 594929b795
3 changed files with 8 additions and 21 deletions
+1
View File
@@ -10694,6 +10694,7 @@ fn loading_frame(hud: &HudBatch) -> Frame<'_> {
bob: glam::Mat4::IDENTITY,
sky: horizon_client::environment::Sky::default(),
distance: 12.0,
detail_distance: 12.0,
depth_far: 1000.0,
underwater: false,
cave_culling: false,
+6 -20
View File
@@ -326,10 +326,8 @@ impl Lod {
}
while let Ok(done) = self.results.try_recv() {
self.pending.remove(&done.key);
if self.plan.nodes.contains(&done.key) {
if done.samples.len() == CELLS * CELLS {
self.ready.insert(done.key, done.samples);
}
if self.plan.nodes.contains(&done.key) && done.samples.len() == CELLS * CELLS {
self.ready.insert(done.key, done.samples);
}
}
if self.covered != covered {
@@ -397,6 +395,8 @@ impl Lod {
"minecraft:lava" => Some(("block/lava_still", false, -1)),
_ => None,
};
let light =
240 | (u16::from(self.context.tables.facts(state).map_or(0, |f| f.emission)) << 12);
let style = if let Some((sprite, translucent, tint)) = fluid {
Style {
layer: self
@@ -414,14 +414,7 @@ impl Lod {
.unwrap_or(0) as u16,
tint,
translucent,
light: 240
| (self
.context
.tables
.facts(state)
.map_or(0, |f| u16::from(f.emission))
* 16
<< 8),
light,
}
} else {
let models = self
@@ -443,14 +436,7 @@ impl Lod {
-1
},
translucent: face.is_some_and(|f| f.translucent),
light: 240
| (self
.context
.tables
.facts(state)
.map_or(0, |f| u16::from(f.emission))
* 16
<< 8),
light,
}
};
self.styles.insert(state, style);
+1 -1
View File
@@ -35,7 +35,7 @@ Which settings each level shows, their descriptions and costs are in `crates/hor
**LOD Distance** is off by default. Enable it in Simple or Advanced graphics settings and choose 64, 128, 256, 512 or 1024 chunks. With LODs enabled, **Full Detail Distance** controls the nearby normal chunks; LOD Distance controls the outer view. Keep the nearby range modest, for example 12 chunks with a 256-chunk LOD distance. Increasing the distant range does not increase simulation distance.
Distant terrain uses progressively coarser surface meshes, streamed in bounded background work instead of loading full chunks out to the distant range. It is available in local Overworld and End worlds; surface LODs are disabled in the Nether. Far samples approximate undecorated terrain: distant caves, decorations, structures and player builds are not guaranteed to match the nearby world. Procedural distant terrain requires a local world's generator; remote servers do not supply their world-generation seed.
Distant terrain uses progressively coarser surface meshes, streamed in bounded background work instead of loading full chunks out to the distant range. It is available in local Overworld and End worlds; surface LODs are disabled in the Nether. Unknown terrain samples use noise/aquifer heights and surface materials, omitting caves, decorations, structures and slope-dependent extensions. Loaded and saved terrain supplies bounded surface summaries, including player edits; small details can disappear between samples. This is a surface approximation, not full block geometry. Procedural distant terrain requires a local world's generator; remote servers do not supply their world-generation seed.
LOD terrain enters the existing world colour and depth passes, so supported shader-pack postprocessing can see it. This does not add Iris material passes or shadow maps: Java packs still have the [existing fullscreen-pass limitations](shader-packs.md). Shader appearance and transitions need testing with the selected pack.