fix FAR_FIRST and AUTO options

This commit is contained in:
cola98765
2021-12-09 15:20:31 +01:00
parent 5d4698621c
commit cd50be6531
2 changed files with 3 additions and 4 deletions
@@ -551,7 +551,6 @@ public class LodDimension
// We can use two type of generation scheduling
switch (CONFIG.client().worldGenerator().getGenerationPriority())
{
default:
case NEAR_FIRST:
//in the NEAR_FIRST generation scheduling we prioritize the nearest un-generated position to the player
//the chunk position to generate will be stored in a posToGenerate object
@@ -637,7 +636,7 @@ public class LodDimension
}
break;
default:
case FAR_FIRST:
//in the FAR_FIRST generation we dedicate part of the generation process to the far region with really
//low detail quality.
@@ -385,7 +385,7 @@ public class LodRegion
{
if (doesDataExist(childDetailLevel, childPosX + x, childPosZ + z))
{
if (!requireCorrectDetailLevel)
if (requireCorrectDetailLevel)
childrenCount++;
else
getPosToRender(posToRender, childDetailLevel, childPosX + x, childPosZ + z, playerPosX, playerPosZ, requireCorrectDetailLevel);
@@ -394,7 +394,7 @@ public class LodRegion
}
if (!requireCorrectDetailLevel)
if (requireCorrectDetailLevel)
{
// If all the four children exist go deeper
if (childrenCount == 4)