|
Luna Lunaria @lunalunaria
Discord at ᒪᑌᑎᗩ ᒪᑌᑎᗩᖇIᗩ, Wolf Territories Grid, Kitely, Utopia Skye, Digiworldz, and OSGrid
Online
Spiritual Seeker, Science Fantasy Writer, Creator in virtual worlds |
Threads
View context
I LOVED The Autopsy of Jane Doe, and of course, the Scarlet Witch is one of my favorite MCU characters
like(1)
View context
It's a little odd for me that this conversation is happening now. When I finally settled in Opensim 5 years ago, the grid I was on was already using ubode and within a year switched to Yengine. There were some really old Xengine scripts that broke on some users regions that took a little work to sort through, but the few scripts I used the grid owner rewrote for me. All of the grids I'm on now, with the exception of Kitely, have used that combination for a long time. Additionally, all my spacecraft dating back 3+ years use ubode and Yengine and have had no issues in that time. Been very happy with the combination.
like(0)
Many of us who run simulators have been doing so for several years. When I started hosting my simulators Bento had not come out yet. You had a choice of ode or bulletsim and Xengine was the only script engine that I am aware of... 0.7x was being phased out in favor of 08x ... I refused to upgrade to 09x until it matured... Remember the memory leaks, @Opensimworld? You will have people who are hesitant to upgrade and there are plenty of valid reasons for it.
liked(1)
The first Opensim grid I joined in 2018 was run by retired IT professional Bill Blight, and he was already using 0.9.0 at that time. Every time Ubit had something new, he and Bill would get together and load it into the grid, then ask me to tell them if my store broke or not. It was wild but fun. For a while, Bill even had his own version of the Firestorm viewer that I loved called Openstorm, but then he had a heart attack and decided to retire from grid hosting altogether. The current NGC development group has his mindset, and I love their willingness to be the first to step into the unknown. I'm on three of their grids now.
like(0)
View context
There's a Luna on each grid that I have a store region on: Wolf Territories, Kitely, and Mobius. For obvious reasons. There are a couple more grids where I have friends. Then there's the Social Luna on OSgrid who represents Lunaria at events around the hypergrid. Her inventory is bare bones so that I don't crash any regions I visit and expose my creations as I travel. Sometimes several Luna's will show up at an event together (current record is 6 on Lbsa at one time, but mixing that many sisters together at one time can have unpredictable results - they tend to be competitive).There's one male alt whose only purpose is to serve as partner to any Luna as needed, but he's not happy about that, so he and Luna tend to throw verbal barbs at one another during dances. And lastly there's a completely separate female with a different name that allows me to work quietly on special projects unrelated to the stores.
like(4)
All of my avatars for the last 14 years, both here and on Second Life, have been strictly business related. When I first joined SL 17 years ago, I was single so I tried the whole relationship / partner thing for a couple of years, but gave it up when they finally confessed they were already married in RL. So I took a break from virtual and it wasn't long after that I met and married the love of my life in RL, and I never looked back. I came back to virtual after that simply because I love to create. Now we both love Luna and everything she's involved in.
liked(3)
View context
All the grids I've been on the last four years or more, with the exception of Kitely, have all used YEngine with no issues
like(1)
I remember that It took Kitely a while to move onto Opensim 0.9.x. Kitely's adaptation of Opensim is rock solid, they have patched the software to do some remarkable things no other grid has been capable of. Adoption may be slow while they are tweaking their improvements to match current code. In the meantime, the older, reliable option is available to those who choose to wait. Cheers.
like(0)
There are already a significant group of grids who have been developing and using ngc 0.9.2 for some time now very successfully - a fork well ahead of anything else going on. I have regions on 3 of those grids
like(0)
Truth be told, I have a few issues with forks, particularly when they aren't maintained by and for a big and popular grid.
One issue is that the maintainer of a fork has to take over changes at the original in order to stay compatible. Especially if we're talking about a one-person project, the maintainer may be rather picky in what's taken over. For example, several forks that were created from OpenSim 0.8.0.* or 0.7.* did not implement the changes in vanilla 0.8.2.1 that led to basic Bakes-on-Mesh compatibility. This gives you an OpenSim NextGen that reports back the version number 0.9.1.0, but that doesn't support BoM at all, even less than vanilla 0.8.2.1.
Another one is that the development of forks may end quickly. NextGen is dead and gone. The once-popular German fork ArribaSim is dead, too. Just to name two. Both were discontinued before even implementing BoM.
If your fork dies, you can be lucky if there's a way to migrate your grid to vanilla. If there's none, you can choose between going on running an increasingly outdated grid with gaping security holes and no support for any new mesh body version that came out in the last two and a half years and re-installing your entire grid. And the feasability of the latter depends on whether IARs and OARs created with the fork are still compatible with vanilla. If too much has changed, have fun starting over from scratch.
I do hope that the NGC developers won't quit anytime soon, also because that'd mean that the Fire and Ice Grid would be one of the next to sit on a dead fork.
liked(1)
One issue is that the maintainer of a fork has to take over changes at the original in order to stay compatible. Especially if we're talking about a one-person project, the maintainer may be rather picky in what's taken over. For example, several forks that were created from OpenSim 0.8.0.* or 0.7.* did not implement the changes in vanilla 0.8.2.1 that led to basic Bakes-on-Mesh compatibility. This gives you an OpenSim NextGen that reports back the version number 0.9.1.0, but that doesn't support BoM at all, even less than vanilla 0.8.2.1.
Another one is that the development of forks may end quickly. NextGen is dead and gone. The once-popular German fork ArribaSim is dead, too. Just to name two. Both were discontinued before even implementing BoM.
If your fork dies, you can be lucky if there's a way to migrate your grid to vanilla. If there's none, you can choose between going on running an increasingly outdated grid with gaping security holes and no support for any new mesh body version that came out in the last two and a half years and re-installing your entire grid. And the feasability of the latter depends on whether IARs and OARs created with the fork are still compatible with vanilla. If too much has changed, have fun starting over from scratch.
I do hope that the NGC developers won't quit anytime soon, also because that'd mean that the Fire and Ice Grid would be one of the next to sit on a dead fork.
Yes, I loved NextGen. Sadly that is no longer being updated and nobody has taken over the project. This is a cold reality. Some forks in the OpenSource world are alive and well... Ubuntu is a fork of Debian. Manjaro is a fork of Arch. Opensim never gained the same traction as other projects and that is unfortunate.
like(0)
My guess is that NextGen arrived at a dead end. Vanilla OpenSim had basic BoM support from 0.8.2.1 to 0.9.1.0 and full BoM support starting with 0.9.1.1. NextGen, which had 0.9.1.0 as its highest version number AFAIK, never had any BoM support.
Now, OpenSim 0.9.1.1 had full BoM support as one of its key killer features. In order to achieve that, a whole lot of work would have been necessary on NextGen, if the modification on NextGen in comparison with vanilla had made the implementation of BoM possible at all.
like(0)
Now, OpenSim 0.9.1.1 had full BoM support as one of its key killer features. In order to achieve that, a whole lot of work would have been necessary on NextGen, if the modification on NextGen in comparison with vanilla had made the implementation of BoM possible at all.
I am pretty sure the latest NextGen has BOM. I understand Hyacinth worked with LaNani on the project to add new features but I have not seen anything as to whether or not she will pick up the project in LaNani's absence. There are plenty of other forks that people can check out though. 'Isthmus' is the most promising derivative and I know the person who maintains it has been around a long time and is dedicated to her work.
like(0)
Well, Otterland runs on OpenSim 0.9.1.0 NextGen, and I know from personal experience that the grid doesn't have any properly-working BoM support. You're likely to return with an avatar that needs repair.
like(0)
View context
Here's a link to a pdf of @JupiterRowland 's list of destinations. Feel free to download it and pass it along. If there's interest, I can also post it in the Opensimworld discord server: https://drive.google.com/file/d/1sr-wkJ5uQDNg80etMl4ZS0jbM...
like(1)
View context
I think you're taking a great step in the right direction :-) I wear a Ruth 2 avatar and so far my mesh clothing has come from the Kitely Market. There's not a lot there yet but I like Pacifica and Rune, along with a couple of others. I'll have to try some of the places Jupiter mentioned as well as Dorena's place. As for my regions, I make everything there except for a fun little party boat that came from Lani Mall on OSGrid.
like(1)
View context
I came by for a short visit and everything looked nice. There were several people there at an event but no one bothered me or hassled me about anything. Will stop by again soon when I have more time.
like(2)
View context
Omg that is so sad. We talked, and danced, and worked together so much, especially during OpensimFest. I will really miss her :-(
like(1)