Isometric render errors (chunk render order)

[Psithief]

Chunk generation (particularly around a world's edges) does not appear to be sorted.

I am imagining that c10t assumes a chunk order inside a region file that is not actually enforced by minecraft.

The result is that the chunks are loaded in what is essentially random order, and therefore chunks in the background are being drawn over chunks in the foreground.
Example here

This implies that the chunks from each region file must be sorted into a render order that makes sense.

Version: a6bfe41
OS: CentOS
Debug output:

 --- SCANNING WORLD DIRECTORY ---
world: (whatever)
............     1265 parts
SEE LOG: 74927 level(s) filtered!
 --- DEBUG WORLD INFO ---
mc::world
  min_x: -20
  max_x: 20
  min_z: -20
  max_z: 20
  levels: 1265
  radius: 20
  chunk pos: 0x0
 --- ALLOCATING MEMORY ---
memory usage: 91 MB
memory limit: 1000 MB
 --- RENDERING ---

(continued) http://pastebin.com/r13wg38U

[Ben0mega]

i have never seen this type of error - what were the command line args?

Edit: Also, access to the map/a map that has this error may also help

[Psithief]

@Ben0mega
Every map I have or create has this error.
Here is a small one (zip) with associated map.
The only command line arguments required for this output are -o, -z and -w.

Blame Bukkit for saving chunks to a region file in a way that minecraft will still read without errors but c10t won't.