Hey all, I've been thinking about this supposed limitation of 256x256m sized regions because of the recent discussion on integrating GIS data with it and I wanted to discuss all of the known limitations, mitigating factors, and potentially some solutions to dealing with this.
Now, from what I understand, the Linden client only really knows about 256x256. However, also, so far, the only two things that I've found that really make use of that limitation is terrain, and maptiles. The terrain system is designed in such a way that it makes a region have 256x256m split into 16x16 blocks and therefore there's only space for that. Map Blocks just assume 256x256. Mind you, the client also seems to use it for caching the terrain and objects as well, so it really shouldn't change whatever it is or the client will have an issue Now, the kicker is object positions, avatar positions, textures, border crossings and just about everything else *doesn't care about 256x256 on the client side*. The rest of the 256x256 limitations are in the service. So, solutions.. Now, technically, it's possible to make a region 512x512 and have it generate 4 maptiles and 3 'psudo regions' in the client stack.. the psudo regions would simply be 'terrain senders' and 'terrain update' mechanisms.. and that would work! Any thoughts on this? Best Regards Teravus _______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
