Ah, yes - Ancient Savo has a procedurally generated map, and the camera can be freely moved around. But that just means that whenever the camera is moved the game decides which way to draw each tree. That is done anyway for the sake of basic optimization, for not to draw trees outside the view we anyway need to check which trees are visible and which are not. So then it is just one little extra step to determine the level of detail based on distance between the camera and the tree. Currently my plan is to have three versions of each 3D model; full-detail 3D, low-detail 3D, and flattened to 2D.

This kind of optimization probably is not necessary for a modern graphics card - but I plan to have Ancient Savo on Android and iPhone, and it looks like my desktop 3D performance is about the same as a newish Android phone, so the optimization strategy should make it possible to have the same graphics both on mobile and desktop.