Yeah, you're completely correct that it's still "pre-alpha" in status. I fully understand that.<br><br>I didn't mean it how it came across, my expectation is definitely not one of reliable stability at this early hour in OpenSim development. I more intended to indicate that this issue with new region creation is just an issue I noticed during my testing and learning console commands.<br>
<br>But I do occasional "production-level" implementation just to see how it handles things. Never doing anything I'd cry over if (when) it fails. :)<br><br>- Len<br><br><div class="gmail_quote">On Sun, Feb 14, 2010 at 12:40 AM, Melanie <span dir="ltr"><<a href="mailto:melanie@t-data.com">melanie@t-data.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hi,<br>
<br>
please don't treat OpenSim as a "product". OpenSim is a toolkit and<br>
a sample application and it is pre-alpha.<br>
<br>
I really don't like to see the expectation of "Fully working",<br>
because OpenSim is written and rewritten at such a rapid rate that<br>
"Fully working" is not likely to happen anytime soon.<br>
<br>
OpenSim is NOT PRODUCTION READY and anyone using it in production<br>
does so at their own risk.<br>
<br>
Melanie<br>
<br>
Mark Malewski wrote:<br>
> *> That used to work, but was broken some months ago.*<br>
<div><div></div><div class="h5">><br>
> Are there any plans to fix this bug? (or fix whatever has been broken?)<br>
> It's extremely hard to update documentation, or write tutorials when things<br>
> are constantly "breaking" or "not working".<br>
><br>
> Len, maybe wait for the latest OpenSim 0.7 RC to get released, and see if<br>
> maybe the problem can be fixed (or the fixes can be added) to the OpenSim<br>
> 0.7 RC release (which hopefully will be a "fully working" release, and<br>
> hopefully 0.7 RC will be released soon).<br>
><br>
> Mark<br>
><br>
><br>
> On Sat, Feb 13, 2010 at 5:44 AM, Melanie <<a href="mailto:melanie@t-data.com">melanie@t-data.com</a>> wrote:<br>
><br>
>> That used to work, but was broken some months ago.<br>
>><br>
>> Melanie<br>
>><br>
>> Len Brown wrote:<br>
>> > Greetings all!<br>
>> ><br>
>> > I recently wanted to familiarize myself better with many of the console<br>
>> > commands and among them I tried my hand at using the console to create a<br>
>> new<br>
>> > region while in-world. I came upon the following issue:<br>
>> ><br>
>> > I'd already created my first region, named "TestRegion" in the normal<br>
>> > fashion and logged into the region and was flying around - all was<br>
>> normal.<br>
>> ><br>
>> > I then typed into the console:<br>
>> ><br>
>> > create region NewRegion NewRegion.ini<br>
>> ><br>
>> > Then followed the normal practice for naming the new region (NewRegion)<br>
>> and<br>
>> > assigning it port 9001, etc.<br>
>> ><br>
>> > But in-world the new region did not appear. When bringing up the world<br>
>> map<br>
>> > it was shown there, but not in the mini-map. I teleported to my home<br>
>> > position (128,128 default) and then the new region appeared in the mini<br>
>> map,<br>
>> > but I was still unable to fly into it - in-world it showed nothing was<br>
>> > there.<br>
>> ><br>
>> > I ran the shutdown console command then restarted the OS server and when<br>
>> I<br>
>> > logged in the new region was then visible in-world and I could fly into<br>
>> it,<br>
>> > with everything working as expected.<br>
>> ><br>
>> > Is this a typical situation or something new? Previously I always had<br>
>> all<br>
>> > my regions listed in a single regions.ini file and since my home region<br>
>> > started first, I could log in and actually watch the regions around me<br>
>> > appearing in-world. I'm guessing there's some kind of communication<br>
>> error<br>
>> > keeping the new region created via console from appearing in-world, yet<br>
>> > showing up in the map and mini-map.<br>
>> ><br>
>> > My Operating System for this example is Windows 7 Home Premium, all<br>
>> updates<br>
>> > applied. Oh, and this is with the 0.6.8 binary release, not a currently<br>
>> > build.<br>
>> ><br>
>> > I'll be pleased to file a bug report if this is indeed an undocumented<br>
>> bug.<br>
>> > I could not find anything specific to this issue in the jira myself.<br>
>> ><br>
>> > Thanks all!<br>
>> ><br>
>> ><br>
>> ><br>
>> > ------------------------------------------------------------------------<br>
>> ><br>
>> > _______________________________________________<br>
>> > Opensim-dev mailing list<br>
>> > <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
>> > <a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
>><br>
>> _______________________________________________<br>
>> Opensim-dev mailing list<br>
>> <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
>> <a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
>><br>
><br>
><br>
> ------------------------------------------------------------------------<br>
><br>
> _______________________________________________<br>
> Opensim-dev mailing list<br>
> <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
> <a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>- Len W. Brown <br> <a href="mailto:lenwbrown@gmail.com">lenwbrown@gmail.com</a> <br> <a href="http://www.lenfocenter.com">http://www.lenfocenter.com</a> <br>