Fences for sloped tiles are stored in a way that may not be logical

For steep slopes all fence edges are stored in the upper voxel.
For non-steep slopes on the edges where both corners are raised, the fence is 
stored in a voxel above ground.

In the later case it may make sense, but for the two lower fences of a steep 
slopes it would make more sense to store the fence at the lower voxel.

The reason why it is implemented as it currently is to have fences stored in 
the voxel that renders them. Thus the render engine doesn't need to lookup any 
other voxel. However, when building stuff etc. things become a bit more 
complicated as you need to first figure out which voxel to look at before you 
can check if there is a fence.

The point of this issue is to document that it may be wanted to move towards 
the other solution.

Also the current solution do have a glitch. Se the right raised tile on the 
attached file.

Original issue reported on code.google.com by leif.li...@gmail.com on 17 Aug 2014 at 8:19

Attachments:

render-order-glitch.png

dashdan / freerct

Fences for sloped tiles are stored in a way that may not be logical #55