For information, I just added some explicit notes to the CombineContiguousRegions setting in OpenSim.ini.example saying that it should be false for varregions.

On 19/02/15 06:10, Ian Sheldrick wrote:
Thanks, Dahlia...  that does make sense, more or less...  although in the way 
that when you first launch a varregion it
allows building in the root 256^2 but not anywhere else, it's still in some way 
treating the different 256^2 areas as
separate...  but it's great to fly over my 1024^2 without a bump every 256 
metres  :P

On 19 February 2015 at 13:07, Dahlia Trimble <[email protected] 
<mailto:[email protected]>> wrote:

    No, a varregion is a single region of variable size. A megaregion is a 
single region that tries to mimic several
    traditionally sized regions. Varregions require varregion-capable viewers 
where megaregions should work with any viewer.

    On Wed, Feb 18, 2015 at 9:01 PM, Ian Sheldrick <[email protected] 
<mailto:[email protected]>> wrote:

        I just started working with varregions and was a bit surprised about 
the CombineContiguousRegions=false
        setting.  I know it works, but I don't quite understand the logic 
because surely in a varregion what you have is
        precisely a "combination of contiguous regions".


        On 19 February 2015 at 10:48, CiderJack 
<[email protected]
        <mailto:[email protected]>> wrote:

            As a matter of fact, after reading that megaregions have basically 
been deprecated I did change to
            varregion. However I didn't try it with an existing megaregion, I 
started completely fresh. It works just
            fine now, though so far it only seems to work in my local vanilla 
OpenSim install.

            Now I'm running into issues when uploading to Kitely. I've opened a 
thread on Kitely forums if anyone is
            curious:
            http://www.kitely.com/forums/__viewtopic.php?f=8&t=2520 
<http://www.kitely.com/forums/viewtopic.php?f=8&t=2520>

            One further related question however:
            I am assuming that 'CombineContiguousRegions' needs to be set to 
'false' or disabled when using varregion.
            Is this the case? When testing this, setting to 'true' seems to 
cause problems for building outside the root
            256^2. Just asking for clarity, at this point I don't know what to 
expect anymore! :)

            Thanks,

            ~!CJ



            On 2015-02-19 14:33, Justin Clark-Casey wrote:

                Have you tried switching to a varregion?  I want to say that 
you can
                do this with an existing megaregion config and it will work 
(don't
                quote me).  I do suggest doing this if at all possible.

                I know there are load oar parameters [1] specifically for 
loading
                256x256 regions into a larger varregion.  I don't know how well 
they
                would work for megaregions.

                If you're doing something with Kitely then you would have to 
ask them
                directly as I hear they have proprietary megaregion code.

                [1] http://opensimulator.org/wiki/__Load_Oar 
<http://opensimulator.org/wiki/Load_Oar>

                On 16/02/15 23:06, opensim.users@katijackstudio.__com 
<mailto:[email protected]> wrote:

                    Thanks for the help, Chris.

                    I tried rezzing & editing on the regions with ephemeral 
objects, and rezzed objects behave as
                    expected, that is, as normal.

                    I have tried saving & reloading the megaregion oar in 
question, with no success. What I mean is, the
                    whole megaregion
                    saved/loaded as a single oar, but it didn't fix the problem. 
Also tried it with 'fix-phantom' &
                    backup both before and
                    after, and even rebooted the server which didn't do the 
trick either.

                    This would suggest (as you noted) that 256^2 regions cannot 
be loaded individually into a megaregion
                    and still function,
                    although I think in some of my reading about this issue I 
had seen where people were doing just that
                    and having it work
                    for them (I could be mistaken about this).

                    Can individual regions be saved from a megaregion as 
individual oar files? Guess I need to test
                    that, because at this
                    point the only solution I can think is to completely 
rebuild those three non-root-sims. :|

                    ~!CJ


                    On 2015-02-16 19:55, Chris wrote:

                        I'm unsure of how an OAR would react if it was saved 
from originally a
                        256x256 region and then loaded to a megaregion but can 
you rez
                        anything from inventory and it be edit-able ? You could 
also try
                        saving an OAR of the mega region with the stuff on it, 
then reload
                        from that OAR, it may or may not help. Beyond that I am 
unsure :)

                        On 2/16/2015 12:43 AM, 
opensim.users@katijackstudio.__com
                        <mailto:[email protected]> wrote:

                            ...and to answer the second part of your question, 
after disabling megaregions, the
                            ephemeral objects are once again
                            corporeal -- that is, the data loads in the build 
window, and they are no longer phantom...

                            On 2015-02-16 19:24, 
opensim.users@katijackstudio.__com
                            <mailto:[email protected]> wrote:

                                Actually yes, I did enable megaregions with 
everything in place BUT
                                after enabling, I then re-loaded each 256^2 
region from individual oar
                                files, used 'fix-phantoms' and 'backup' in the 
console, and then saved
                                the whole megaregion oar. At this point the 
objects on the
                                non-root-sim are phantom/ephemeral.

                                I then loaded other misc. oar files into all 
four regions of the
                                megaregion, and then loaded the megaregion oar 
again just to make sure
                                the oar file worked. Everything 'looks' like 
it's there, but only the
                                objects on the root sim really are there.

                                Since the phantom/ephemeral issue is persisting 
at this point, I then
                                do another 'fix-phantoms' and 'backup', waited 
a few minutes then
                                rebooted the server. No change, problem 
persists.

                                ~!CJ


                                On 2015-02-16 18:55, Chris wrote:

                                    Did you enable megaregions while you had 
content on it? As far as I
                                    know this has a tendency to break your 
content if you enable it with
                                    stuff rezzed out on your regions. What 
happens if you disable
                                    megaregions?

                                    On 2/15/2015 11:39 PM, 
opensim.users@katijackstudio.__com
                                    <mailto:[email protected]> 
wrote:

                                        Been having a problem with objects not 
on my root sim pretty much no longer
                                        existing. Sometimes they look like
                                        they're there, but when selected there 
is no data in the build window, and the
                                        avatar can pass right through them
                                        like they're phantom. When loading the 
oar to Kitely, the objects don't even
                                        appear to be there, they're just gone.

                                        I should start by saying that I've been 
reading through the Kitely forum,
                                        reading through the OS wiki page for
                                        megaregions, followed references to 
countless blog entries & other forums, and
                                        they're all saying the same thing
                                        -- use 'fix-phantoms', and then typing 
'backup'.

                                        I can save & load megaregions locally & 
the non-root-sim objects will load up
                                        (visually) but in substance there is
                                        nothing there. But again, when I load 
one of these 'working' megaregions to
                                        Kitely, the objects don't even load
                                        visually.

                                        All I can find is telling me to use 
'fix-phantoms' and 'backup' and that should
                                        solve the problem. Unfortunately I
                                        am not finding this to be the case. Is 
there something I'm doing wrong?

                                        I'm using OS 0.8.0.3.

                                        ~!CiderJack
                                        
_________________________________________________
                                        Opensim-users mailing list
                                        Opensim-users@opensimulator.__org 
<mailto:[email protected]>
                                        
http://opensimulator.org/cgi-__bin/mailman/listinfo/opensim-__users
                                        
<http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users>


                                
_________________________________________________
                                Opensim-users mailing list
                                Opensim-users@opensimulator.__org 
<mailto:[email protected]>
                                
http://opensimulator.org/cgi-__bin/mailman/listinfo/opensim-__users
                                
<http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users>


                            _________________________________________________
                            Opensim-users mailing list
                            Opensim-users@opensimulator.__org 
<mailto:[email protected]>
                            
http://opensimulator.org/cgi-__bin/mailman/listinfo/opensim-__users
                            
<http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users>


                    _________________________________________________
                    Opensim-users mailing list
                    Opensim-users@opensimulator.__org 
<mailto:[email protected]>
                    
http://opensimulator.org/cgi-__bin/mailman/listinfo/opensim-__users
                    
<http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users>


            _________________________________________________
            Opensim-users mailing list
            Opensim-users@opensimulator.__org 
<mailto:[email protected]>
            http://opensimulator.org/cgi-__bin/mailman/listinfo/opensim-__users
            <http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users>



        _______________________________________________
        Opensim-users mailing list
        [email protected] <mailto:[email protected]>
        http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users



    _______________________________________________
    Opensim-users mailing list
    [email protected] <mailto:[email protected]>
    http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users




_______________________________________________
Opensim-users mailing list
[email protected]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users



--
Justin Clark-Casey (justincc)
OSVW Consulting
http://justincc.org
http://twitter.com/justincc
_______________________________________________
Opensim-users mailing list
[email protected]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users

Reply via email to