<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Teravus,<BR>
<BR>
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)<BR>
<BR>
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'.<BR>
<BR>
(Btw, can you terraform in a neighbour region? If not, a hacked setup might be a bit cumbersome to administrate)<BR>
<BR>
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). <BR>
<BR>
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.<BR><BR>
Which I believe could seriously rock, eventually.<BR><BR>
And yes, in the 'hack' version, you would have to disable the moving the avatar and objects between regions bit.<BR>
<BR>Best regards,<BR>Stefan Andersson<BR>Tribal Media AB<BR><BR>
<BR><BR>> Date: Mon, 26 Jan 2009 03:11:51 -0500<BR>> From: teravus@gmail.com<BR>> To: opensim-dev@lists.berlios.de<BR>> Subject: [Opensim-dev] Regions larger then 256x256<BR>> <BR>> Hey all,<BR>> <BR>> I've been thinking about this supposed limitation of 256x256m sized<BR>> regions because of the recent discussion on integrating GIS data with<BR>> it and I wanted to discuss all of the known limitations, mitigating<BR>> factors, and potentially some solutions to dealing with this.<BR>> <BR>> Now, from what I understand, the Linden client only really knows about<BR>> 256x256. However, also, so far, the only two things that I've found<BR>> that really make use of that limitation is terrain, and maptiles.<BR>> The terrain system is designed in such a way that it makes a region<BR>> have 256x256m split into 16x16 blocks and therefore there's only space<BR>> for that. Map Blocks just assume 256x256. Mind you, the client<BR>> also seems to use it for caching the terrain and objects as well, so<BR>> it really shouldn't change whatever it is or the client will have an<BR>> issue<BR>> <BR>> Now, the kicker is object positions, avatar positions, textures,<BR>> border crossings and just about everything else *doesn't care about<BR>> 256x256 on the client side*. The rest of the 256x256 limitations<BR>> are in the service.<BR>> <BR>> So, solutions..<BR>> <BR>> Now, technically, it's possible to make a region 512x512 and have it<BR>> generate 4 maptiles and 3 'psudo regions' in the client stack.. the<BR>> psudo regions would simply be 'terrain senders' and 'terrain update'<BR>> mechanisms.. and that would work!<BR>> <BR>> Any thoughts on this?<BR>> <BR>> Best Regards<BR>> <BR>> Teravus<BR>> _______________________________________________<BR>> Opensim-dev mailing list<BR>> Opensim-dev@lists.berlios.de<BR>> https://lists.berlios.de/mailman/listinfo/opensim-dev<BR><BR></body>
</html>