Some chunks are "wrong".

[sirdiego]

I don't know where they come from or when they get created.
Every time i rerun overviewer some of them reset to be "right" again but others are wrong instead.

[CounterPillow]

We've seen reports of this before a couple of times on IRC and I think someone even uploaded a world that exhibited the issue, but we never bothered to investigate properly.

Since I (or any of the overviewer coredevs) have never seen the issue happen to one of our own maps, it'd be useful if you could list some information about your setup; e.g. what operating system you're running on, whether you render from a live map, your configuration file, and any additional information you think may have an influence.

Thanks for reporting it.

[gabsoftware]

I have the same issue.
The server is Spigot latest version (1.7.10), installed on a Linux Debian 7 with 2 GB of RAM.
It seems to happen when the render update occurs while people are playing, although I'm not entirely sure of that. Maybe the render does not use a clean copy of the world.

[sirdiego]

Hi guys,

I am running an vanilla mc 1.8 server also on Debian with 4 GB of RAM. I also generate the map from the live world without a copy.
So maybe it really has to to with players on the server while rendering.

[MasterofJOKers]

We had this problem, when we were still running overviewer on the live world. Since we switched to rendering a backup copy of the map the problem hasn't occured again to my knowledge.

[iccle]

We have the same issue running vanilla mc 1.8 generating the map on the live world.

[14mRh4X0r]

I'm having the same issue, Minecraft 1.8 with FML 8.0.9.1016, rendering from a live world. I'd like to see this solved rather than dismissed as "not supported", as this makes it a lot easier to provide a live map to players.

[eminence]

Have any of you seen this issue while rendering a world after stopping your minecraft server?

[MasterofJOKers]

Since minecraft servers nearly always run, it might help to stop the server from saving the world via save-off command and let it save again after running overviewer via save-on. We only do this for the backup though and never had a problem rendering there.

[iccle]

I use save-off/save-on as part of the shell script that performs the map generation and POI generation, it makes no difference during render.

[Staric1982]

I have this issue too several times. Solved by deleting folder with rendered map and re-render map from the scratch.
All renders did at night, so no players online.

[LeadMagnet]

I have this issue only on one world which was created in 1.6.4, migrated to 1.7.10, then to 1.8.1 Pre 1. Nether and End views are fine. All other worlds created in 1.8.1 render without issue. Rendering taking place off-server. I have noticed that a --forcerender option on the initial render corrects the problem 99% of the time.

[halfsight5000]

I am Also experiencing this issue.

The Overviewer is running on Windows 7. This generates the map from a network shared folder of a 1.8.x minecraft server on OS X 10.10 and puts it back onto another network share that rsyncs the render to my apache. It's all automatic. This only happens when somebody is on the server. If I bounce the server then I can re render without issue, if nobody is on the server.

The output I get in the cmd when this happens is saying that the chunk may be corrupt rather than in use. A suggestion would be to only try the chunk a certain amount of times. it seems to try over and over and over again, making the render take a really long time. Or if it is running when y scheduled task runs then it goes the yellow text for map didn't finish rendering last time.

My resolution is to setup another rsync for the map so I am rendering from a copied and saved map.

Either way, this app is the best.