Chunk Loading Error?

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
Status
Not open for further replies.

CarbonX

New Member
Jul 29, 2019
14
0
0
I've got no idea WHY this happens, but I do know that it happens in EVERY SINGLE ONE OF MY WORLDS. I'm starting to lose track of the worlds of had to delete because of this error.

Here are some screenshots:

20130126181435.png



20130126181438.png
 

Nessiroj

New Member
Jul 29, 2019
855
0
1
Do you have optifine installed? Often it's just abug in the optifine rendering. Logging out and back in fixes it in general.
 

dementia

New Member
Jul 29, 2019
140
0
0
I have found this happening when i travel to mystcraft ages. It doesn't seem to be a major issue because it is only a few chunks, and relogging frequently fixes the issue. In general avoid building near these chunks because sometimes they revert to being unloaded.
 

Kanadeara

New Member
Jul 29, 2019
14
0
0
Seems to happen in my world too, both to people with and without optifine. Leaving the chunk area and letting it reload or reconnecting usually does the trick for us.
 

Unresolved

New Member
Jul 29, 2019
1
0
0
This happens pretty often for me too. I'm running the DW20 pack v4, don't have Optifine installed and have not created any MystCraft ages. As stated previously, reconnecting or leaving and re-entering the area will fix it. It's also possible to just run around the few missing chunks.
 

masa

New Member
Jul 29, 2019
37
0
0
I am also getting this in all of my FTB worlds, both SMP and SSP. Relogging fixes it.
But I would like to know what causes this and is there possibly a fix coming sometime soon? It is really annoying.
 

masa

New Member
Jul 29, 2019
37
0
0
Well, I have ever only encountered a chunk error once in vanilla Minecraft in the 1,5 years that I have been playing, and it was a single chunk missing (with lit up edges).
However, I do regularly get these wide, black-edged strips of missing chunks in FTB. It is definitely something specific to FTB (or more accurately the mods included in FTB).
 

Project0verkill

New Member
Jul 29, 2019
4
0
0
I've run across it several times today and its getting worse for me. Right after reading this thread i happened across this....


chuckerror1.png



chunckerror2.png


It's the first time its been more than a just a large strip. Re logging seems to fix it until you move about 100 blocks then another one shows up. I wish it was just Optifine freaking out so i could just remove it but that doesn't seem to be the case. Hopefully somebody can figure out whats doing it so we can fix this problem. It's nothing game breaking yet but it is very annoying.

Running Mindcrack v8.0.1
I've added:
[Preview] OptiFine HD D3 Ultra for Minecraft 1.4.6 and 1.4.7
Forge v6.6.0.518
ee3-pre1f
mystcraft 0.9.5.00
 

masa

New Member
Jul 29, 2019
37
0
0
I am getting these pretty much all the time when I move around in the world. It seems to be client-side (or sync issue), since me and my friend are not both seeing the same chunk error. So the one that does not get the chunk error can of course walk over it.
Relogging or moving away farther than the view distance and coming back will fix the chunk error, but it is extremely annoying in any case.
I am running the MindCrack pack v8.0.1 unmodified.
 

Scaffolding

New Member
Jul 29, 2019
170
0
0
The Forge team tried putting a workaround fix in several versions ago but it doesn't seem like it helped, as far as I know it is definitely a Vanilla issue but only vastly more apparent with this modpack. Hopefully the issue is taken care of when the 1.5 rendering engine update(rewrite) happens.
 

masa

New Member
Jul 29, 2019
37
0
0
Does the rendering engine matter with this issue? Since the blocks are missing for the client all together, and trying to walk into the chunk error results in unpleasantries...
 

commandantjones

New Member
Jul 29, 2019
21
0
0
I get this exact problem, but only when using optifine. I've tried C3, D4, and D5, with multi-threaded loading both enabled and disabled, and without fail, I get either a big stripe of chunks missing, or chunks just stop appearing a few hundred blocks from where I load in to. I've tried new worlds, tried all the optifine options I can imagine, but the problem persists. As soon as I remove Optifine, I can load in and they appear just fine, so it has to be an optifine problem, right? I'm using the latest FTB Ultimate, and the Forge version is like 534 or something, so it's not the outdated one that's incompatible. Not sure what to do from here??
 

UrsusVenator

New Member
Jul 29, 2019
1
0
0
I'm playing on my friends homeserver, and today there was a thunderstorm and the power went out when we played. When we now after that started to play again there was a chunk missing from our lawn. It's not clientside,it's on the server so it doesn't help to rejoin,duh. Anyone got any tips on how to fix this? These are the error messages that pop up over and over again in the logg.
2013-06-05 21:48:57 [INFO] [STDOUT] Wrong location! qn['Skeleton'/1102, l='world', x=2862.70, y=35.00, z=3362.70]
2013-06-05 21:48:57 [INFO] [STDERR] java.lang.Exception: Stack trace
2013-06-05 21:48:57 [INFO] [STDERR] at java.lang.Thread.dumpStack(Unknown Source)
2013-06-05 21:48:57 [INFO] [STDERR] at zz.a(Chunk.java:923)
2013-06-05 21:48:57 [INFO] [STDERR] at yc.a(World.java:2338)
2013-06-05 21:48:57 [INFO] [STDERR] at in.a(WorldServer.java:647)
2013-06-05 21:48:57 [INFO] [STDERR] at yc.g(World.java:2255)
2013-06-05 21:48:57 [INFO] [STDERR] at yc.h(World.java:2109)
2013-06-05 21:48:57 [INFO] [STDERR] at in.h(WorldServer.java:516)
2013-06-05 21:48:57 [INFO] [STDERR] at net.minecraft.server.MinecraftServer.r(MinecraftServer.java:680)
2013-06-05 21:48:57 [INFO] [STDERR] at ho.r(DedicatedServer.java:269)
2013-06-05 21:48:57 [INFO] [STDERR] at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:599)
2013-06-05 21:48:57 [INFO] [STDERR] at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:497)
2013-06-05 21:48:57 [INFO] [STDERR] at fy.run(SourceFile:849)
 

dementia

New Member
Jul 29, 2019
140
0
0
Status
Not open for further replies.