On Apr 27, 2011, at 4:34 AM, Sergiy Byelozyorov wrote: This paper by the Intel's Opensim guys is one at least: Dan Lake, Mic Bowman, Huaiyu Liu. "Distributed Scene Graph to Enable Thousands of Interacting Users in a Virtual Environment" http://www.pap.vs.uni-due.de/MMVE10/papers/mmve2010_submission_7.pdf . They had a big scalability test last week -- I was unfortunately unable to participate in the end, and haven't heard yet of new results, but that paper at least describes some of the approach.
> of it before, however I always considered OpenSimulator a an open-source > implementation of Second Life server and nothing more. As I have found out, I > was wrong - OpenSim does support other protocols than SL. I became curious to > know if you also support other architectures than Second Life's, since to our > opinion regions are not scalable enough with Second Life. Please help me > answering the following questions about what can current Yes, the initial idea of Opensimulator is to be a generic 3d app platform -- SL viewer and the LLUDP protocol, and the embedded assumptions about region sizes and much of VW functionality there, being just one type of an app and client. Every once in a while folks have refactored 'SLisms' out of the core, moving them to the Linden ClientView module that implements that protocol. The reality, however, is still that it's pretty much made after the SL model and basically only used with LLUDP, and mostly only slviewer based clients. I think also some of the devs and many users like to prioritize that -- for some it suffices that it works as a slserver clone, and most important is that it'd do it well. The little experimental Sirikata and now MXP client modules are removed as are unused. The IRC ClientView is fun and useful, though! :) In realXtend dev the SL model hasn't sufficed, 'cause we need also other features (like storing and synching arbitrary, application defined data) so it's been implemented in a module (modrex does the Naali style EC sync with a few custom messages). Opensim devs also agreed a while ago that refactoring Opensim scene core around such a generic extensible model would be good, and we even hired one os core dev to implement it, but the work was unfinished because he got busy with other things (and left opensim dev alltogether). It is AFAIK an open question still whether Opensim will develop as a more generic platform in the future, and if it'll be refactored for scene extensibility -- the plan from late 2009 is attached as a PDF in an email to this list: Refactoring SceneObjectGroup - Introducing Components. http://lists.berlios.de/pipermail/opensim-dev/2009-December/008098.html . An article that explains the idea and status somewhat from reX perspective is at https://github.com/realXtend/doc/blob/master/arch_article/simple.rst (or as pdf, https://github.com/realXtend/doc/blob/master/arch_article/simple.pdf?raw=true . That explicitly does *not* address scalability, this was just to comment that other architectures & other protocols part. Your actual questions are better answered by someone who knows the scene code better, but I'll throw my guesses in in the meantime anyway (and I've read the code a couple of times :) > Can OpenSim create non-square regions? Can OpenSim create overlapping > regions? Can I bound my regions also in 3rd dimension? Not currently. Megaregions can be non-square, though (e.g. 1024x4096). > Can OpenSim separate part of the volume of a region to a dedicated server > (think of a very popular bar with lots of users in the castle)? Opensim itself not, but the Intel folks have been doing this with server side proxying at least .. that article describes their Client Managers, which are between the end user clients and the underlying scene servers, and allow partitioning (I think also dynamically). > Most of these questions are inspired by Sirikata, which was the first world > that I have learned about. I do not expect that you are able to do all that, > since Sirikata's approach to scalability is interesting indeed, we've been also considering using their system for large worlds on the server side in reX, or alternatively adopting the same techniques in new (currently still very simple, with no scalability at all) Tundra server that have written there. With Tundra we are now really happy with the ease of development, both of content & scripting etc. to make e.g. games, and of the platform itself, but probably need to address scalability soon (later this year) so am trying to follow and understand how things with Sirikata, Opensim etc. go. > Sergiy Byelozyorov ~Toni > Computer Graphics Chair > Universitat des Saarlandes > Tel.: +49 (681) 302-3837 > Web: http://graphics.cs.uni-saarland.de/sbyelozyorov/ > > _______________________________________________ > Opensim-dev mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/opensim-dev
_______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
