[Opensim-dev] Regions larger then 256x256

[Stefan Andersson]

Teravus,
 
you're revisiting our old, old, vision of having a many-to-many between scenes and regions, I think. (Where regions would be the IP endpoints, and the scene the graph)
 
If I understand you correctly, we would separate region from scene, letting the regions manage their bit of terrain, but having one region have a 'scene' that was 768x768, centered on the mid 'region'.
 
(Btw, can you terraform in a neighbour region? If not, a hacked setup might be a bit cumbersome to administrate)
 
So, the physics engine would communicate with the scene, but something would have to 'route' scene updates to the right scenepresence (avatar to the root, terrain to the right child). 
 
And if it does, as all presences are 'root' presences today (as per an earlier post by Diva) I think that that would mean we are on our way towards a _true_ (as in 'not a one-off hack') many-to-many scene/region relationship.
Which I believe could seriously rock, eventually.
And yes, in the 'hack' version, you would have to disable the moving the avatar and objects between regions bit.
Best regards,Stefan AnderssonTribal Media AB
> Date: Mon, 26 Jan 2009 03:11:51 -0500> From: teravus at gmail.com> To: opensim-dev at lists.berlios.de> Subject: [Opensim-dev] Regions larger then 256x256> > 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> Opensim-dev at lists.berlios.de> https://lists.berlios.de/mailman/listinfo/opensim-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20090126/2b36cad9/attachment-0001.html>