General News

#SL Clouds, Grey, and Blurry Avatars

by

We seem to be getting another round of poorly rezzing avatars. The particle cloud avatars we know about. That is often a connection issue. I write my fix-it article Avatar Render Problems: Ghost Cloud Smoke Ball Ruth in September 2010. But, something new is up.

The Problem - Extended Bake Fail

Blurry Avatars

For several weeks I have noticed when changing clothes I get a blurry avatar. My skin and clothes start blurry after a change, then rez nice and crisp once, then go blurry again and never seem to finish rezzing.  They stay blurry.

Read more

#SL ADITI Login Inventory Problem

by

If you use the ADITI Preview Grid for testing things you make or the new features coming to Second Life, be warned.

A few of us have recently updated our password, which forces an update of our inventory as it exists in AGNI, the main grid, to overwrite our inventory in ADITI. In many ways for me it is cleanup process for all the stuff I play with in ADITI.

This weekend I changed my password and my ADITI inventory updated. I suddenly could not rez anything from my inventory to the Path Test regions in ADITI. I made the things I needed from scratch and wrote my scripts for testing Pathfinding. When I was ready to log out I saved those things to inventory.

When I returned several hours later and logged in, all the things I made were missing from my ADITI inventory. I’ve been through this a couple of times now. I am so glad I use LSLEditor for writing scripts.

At the user group meetings I found out others are having the problem too. So, my advice is to avoid changing your password until the problem is resolved.

If you have already run into the problem, see JIRA item: SVC-7727. Please click Watch and add any additional information you may have. Remember. The JIRA is not for discussion. Also, ‘me too’ posts do not help if they do not add new information. For ‘me too’ just click watch.

Linden Layoffs?

by

I see on Tateru’s and Inara’s blogs and in loads of Plurks that Esbee and Charlar are leaving the Lab. I’m bummed.

As of yesterday Charlar was proceeding with Advanced Creator Tools. I got my join notice to the new group.

Welcome

Thursday,01 Mar 2012 16:05:28 GMT

This group’s purpose is to provide a channel for some communications related to the Advanced Creator tools. You are the first members because you are also part of the closed beta for the tools themselves, especially the Experience Permission system. This beta will take part initially on Aditi with a private group meeting and forum. Currently I see no reason to require an NDA. What we’re doing isn’t necessarily sekrit, it’s more that we want to work out any kinks with you all in a calm, professional group.

That group is for beta testers helping with the Linden Realms Tools. New permissions systems are needed to go with the tools. So, there is lots to work out. I have no idea what the status of this project is now.

Charlar’s departure will likely put a kink in the Content-Mesh Creation group too.

I’ll miss Charlar.

UPDATE: I do have it from a reliable source that Charlar neither left nor was fired… but, he is not here any more. Figure that one out…

I haven’t heard much about what Esbee was doing. I knew her from when she ran the Viewer Evolution group. I missed her when she left the first time. Recently I haven’t been able to tell she was back. So, I’m neutral on her departure.

Phoenix Firestorm Hour

by

Well after all the tech problems at the Phoenix Hour, now the Phoenix Firestorm Hour, I finally got to see the video of the meeting. I’ll paraphrase it here. As usual I’ll provide time marks so you can listen to the parts that interest you. I try to be accurate, but I have biases and preconceptions so I can hear things differently than they are intended. So, you’ll find the video at: New Linden Lab Policy.

Phoenix Firestorm Hour

I’ll point out here that the paraphrasing I have here is 5,000+ words. The meeting was an hour and 45 minutes not counting time out for crashes and region restarts and the 40 minute delay in starting. If I had stuck it out from my early arrival to the end I would have had more than 3 hours in the meeting. I really think some of the changes talked about here are FAR less important than the fact they regions didn’t stay up.

If you’re in a hurry, there are 250 words at the end that pretty much sum things up.

Read more

Pages: 1 2 3 4 5 6

Oz Answers TPV Policy Questions

by

Innula Zenovka post a link on SLUniverse to an Question and Answers page where Oz Linden answered residents questions about the new TPV Policy. Cummere Mayo start the thread here.

See: Questions about new TPV policy. (Questions only please.)

The most controlversal and misunderstood part of the policy is the idea of what is meant by SHARED EXPERIENCE. So, the number one question is: What is meant by shared experience?

The pertinent part of Oz’s answer is:

A shared experience change is one that modifies the definition of the elements that make up the virtual world, or how they behave, in such a way that users on other viewers don’t experience the same virtual reality.

This rule does not affect changes to rendering, user interface, or the controls a viewer offers for interacting with the world.

Read more

Firestorm-Phoenix Viewer Meeting

by

The meeting was planned to start at 2PM today. They are using 4 regions. One region is used for the speakers and camera crew and the other 3 for the audience.  But, the regions were phasing in and out while I was there. My SL Viewer was crashing, Firestorm crashed, Cool VL didn’t crash but I could not get in and the ‘Can’t Establish Connection’ errors from the FS/PH Support group, makes it impossible to do anything.

The stream from Treet.TV was never put up so no one could hook in and listen. But, the recording should be out Wednesday morning.

So, it would seem about 100 people is the limit for 4 regions…

If you think going into Rockcliffe 1 with 30 people will work, think again. While one can get in, the region is lagged to death and you can’t cam into voice range.

I’ll have to wait until tomorrow.