Problem with tree rendering

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Starts a shard.

What is the expected output? What do you see instead?

It must show the scenery with trunk behind leafs. What I see is leafs behind 
trunk.

What version of the product are you using? On what operating system?

fluorescence rev 6deccbde9416, on debian 6, under shphere shard.

Original issue reported on code.google.com by iurigu...@gmail.com on 6 Mar 2012 at 12:03

Attachments:

• fluorescence.png

[GoogleCodeExporter]

Is this on OSI mul files? If yes, please provide some coordinates where I can 
find this spot. 
If not, please click on some of the erroneous items (that prints some debug 
information to the log file) and attach the log file here.

Original comment by spin@fluorescence-client.org on 13 Mar 2012 at 10:50

• Changed state: Accepted

[GoogleCodeExporter]

I know how the original client does this for dynamics: It just renders first 
what comes first. 

If you add the trunk and then the leafs it looks fine, but if your refresh the 
leafs might flip behind the trunk. I have not checked the item order on resent 
in the netcode, but I guess the server sends the leafs first then.

Not sure what happens for Statics but there is no info in the mulfiles. I can 
imagine, that it is hardcoded.

Best solution for both cases, static and dynamic, would be a tree config file 
where you can add leafs and trunks and the client will always render leafs in 
front of trunks if on same location.

Original comment by Tarion86 on 19 May 2012 at 8:39

[GoogleCodeExporter]

As far as I know, tree trunks have tiledata flag 'background'. When I was doing 
some rendering, I always draw first items with 'background' flag and then draw 
any other.

Original comment by janink...@gmail.com on 29 Jun 2013 at 5:53