Hi Thinkgeo,
Setting a value of 1 for TileBuffer improves user experience while pannning. Can we set a higher value of 2 or more?
Regards,
Anil
Hi Thinkgeo,
Setting a value of 1 for TileBuffer improves user experience while pannning. Can we set a higher value of 2 or more?
Regards,
Anil
Hi Anil,
I recommend to set it to 2-3. Also, the tile size is a factor we need to consider about. For example, if we have 512*512 map with tile size 256*256. Then we will have 4 tiles in perfect status (You know actually it’s 9 tiles if the tile is crossing the edge, so we just take it as an example here). When we set TileBuffer to 1, so we will put tiles surround the existing tiles. So there will be 12 more. If we set TileBuffer to 2, and 32 more tiles will be added into the map. But in the real world, there will be more than that. If one tile takes 20ms to draw, we can imagine how long the extra time will take. You might not notice the speed because it’s drawing in another thread.
Actually, in WPF, the more visible Logic tree node is maintained, the slower performance we have if we have a normal graphic card. So we don’t recommend to set this value too big.
On the other hand, we have an idea to pre-generate the buffer in the background thread, so there won’t be an actual logic tree node for the buffer and it will enhance the performance a bit. It’s just a though now and we will check it later.
So we recommend to set it to 2-3. Hope it makes sense.
Thanks,
Howard