Aishagain

https://status.secondlifegrid.net/incidents/74w5jwb6c2xq Third time lucky (or the American translation)??

No ETA: Just let me clarify that...NO. You can copy and paste some things but nothing functional can be transferred unless YOU created it yourself, including photographs, in which case a copy will already be on your computer. If you copy/paste full perm scripts or create copies of photographs/Textures you are infringing on other folk's and LL's (clearly stated in SL's Terms of Service) intellectual property rights. Doing so is an offence.

This previous post demonstrates why this website issue is important, and more than that, directly affects Tilia. I must say that I am surprised that the issue has not been fixed by now. LL are usually highly proactive when an issue hits them in the pocket! Could your issue @Vihmakass be as simple as clearing your browser cache?

Let's not call whatever you are talking of as SL 2.0. That designation was given, right or wrong, to LL's abortive Sansar project which failed for many well-discussed/chewed over reasons. A mobile version of SL may appeal to younger adopters but for me it would not and could never "feel" like SL. I am not part of the new vanguard that wants everything on a hand-held device, no matter how advanced. I just cannot believe it would have sufficient "prescence" to interest me.

I don't have a lawn, we only do mud here. Any offers on MudOS?

@Twist Mechanique then do as @Monty Linden tells you...escalate to LL support.

Wow! this certainly woke afew lurkers up. I am minded of the old adage that "Empty vessels make the most noise". I suppose it depends on what is in that vessel. I feel sure this was tried once before some years back. It withered and died through lack of support and unreliability.

@Monty Linden or @Rider Linden why is this issue recurring and when will it be fixed again?

The fact that they (Linden Lab) are still "working on it" several weeks after they foisted this clearly unfinished and badly broken server/viewer combination upon us is a testament to their attitude that a broken "shiny" is better than the existing system. Some of us just want the thing to work, not be ultra realistic and the current setup is a huge step backwards. I had not realised just how bad SL sailing looked until I tried it using the latest FS alpha. In that regard I agree wholeheartedly with Henri.

@Vicious Hollow hah you misunderstood my point, but I also made it far too crudely. The QA testing used to be done on Aditi, but as I recall the lack of population there rendered the testing invalid, so small RC parcels of simulators (RC Ferrari is one) on Aditi (the Main Grid) were pressed into QA use. Since Magnum represents about 10-15% of the SL real estate (I understood it to be 75% Main Server, c15% Magnum and 5% each for Blusteel and LeTigre) it is, I understood, used to gently introduce changes to SL. This present change is NOT good.

Does anyone here feel that this thread represents the opening of the proverbial "can of worms"? I cannot quite bring myself to believe that the LL devs did not foresee this, and that being so, they have proceeded with a breathtaking (even with reference to them) degree of disinterest (lack of concern).

As a further comment to the above I would add that while it is not particularly bad that an avatar arriving on a Magnum region does so with a load thump, though at a club or busy store it is extremely disruptive, moreover the sound accompanies any object creation/rezzing whether it be physical or phantom and that IS ridiculous. We are now told that QA testing of new simulator software is done on the Main Grid; I for one do not appreciate being used as a test subject in my day-to-day SL.

I agree with that, though I cannot imagine why! What's going on, @Rider Linden? Further to this, I note that one of the issues that this simulator release was supposed to resolve was the matter of collision sounds. Clearly this is not the case!

Yes. I heard them today on Magnum 2023-12-06 7120498613 at Warehouse 21 and very annoying they are too. What is wrong THIS time? Something got reverted? I have not noticed it on any Main Server region yet.

@filz Camino Indeed your data convinces YOU, of course. but I am capable of critical thinking and I'll manage to get through my life, one way or another, by relying on experts.

Oh dear. You had to say that. "Facts" are open to interpretation and individual bias. They can be, and often are, cherry-picked. "Expert opinions" are mostly derived from extensive personal experience. I know which, In this day of marginal honesty, I prefer to accept.

Red. I seriously doubt that the others would run SL. None of them are what I'd call good for SL.

They're damned if they do and they're damned if they don't warn us. It's an "Oops" moment from Linden Lab and Rider Linden assures us that it'll "should" be fixed by this week's restarts. So don't shoot the messenger!

The Login issue is only (I say "only"...it's important if it affects you) a small number of users and there seem to be various causes, some of which are known, some unknown. There was a faling server node somewhere in one of the multitude of routes that a user's signal gets to SL. At least one of those appears to have been repaired. The is also a very peculiar login bug that affected Firestorm users. The latest version of FS 6.6.17 has a fix for that. There is also some weirdness within the SL login server cluster and I have no idea whether that is being looked at or not since the Status page notice is still up. So far I have been immune on all my alts, for once I appear to be lucky. but if you are still in the barrel go to the SL support portal and raise a ticket, that way LL will see you are affected.

That is what was said at the beginning of the month. LL are aware and they SAY they will fix it. Let us hope so, because it is very intrusive.

Having heard much inworld about this issue, I think the best solution in the interim is to try (and most likely) fail too log in with thr Linden Viewer and to pack up the logs and add them to the LL JIRA...I can't see one yet. Without those Logs LL are going to be fighting with their hands tied. The solution tagged "highly likely" at this point is one fubarred server node between the hapless users and SL.

This is a silly question and one that may have already been adressed but is there any corealation between this login stalling issue and the Operating system for are using? Like is it just Mac or are all OSs being affected? I ask because I am still completely unaffected.

OK this is odd. I got in with absolutely no issues. I'm running FS 6.6.17 70368, which is the latest release,but it was an RC when I d/l'd it. I wonder if the login bug-fix mentioned in the notes is the cure? Or am I somehow special? ETA at 7:54 SLT: several TPs later I'm still OK.

@auntiemisha Your decision to revert to 6.6.14 is wise and is the course recommended by FS Support themselves. There is a fixed version on the way currently it is only a Release Candidate, not the full-fat release but I am running it at present and it seems OK. That said I was not afflicted by many of the glitches and bugs some folk have been so maybe my experience is not typical. In good conscience I could not recommend folk substituting the current FS PBR viewer, though it is improved and a much better one is due soon

Quite!