1.21 RC0 is available

I know that the names of other av's appear in blue in both Chat and IM and can be clicked to bring up their Profile. But it is new to 1.21.0 that MY OWN name is in blue in Chat and clickable to bring up my Profile. It get's very confusing. Is this just me or do thers find tyhis too?

This might be just some «usual» SL-glitch, but when I attempt to recompile all scripts in one of my objects, I get at least 3 or 4 messages, that there was a problem uploading the asset...

Maybe, that's because everyone's re-compiling stuff now

Mine, too, very badly so: 1.21 RC0 took me from 11 fps down to 5 fps and the 5 fps feels like my client is about to die: it looks more like 1.5 fps. My breathing swaying avatar freezes for almost a second, then lets go, refreezes for another second, lets go again, refreezes...

In this condition, it's totally unusable.

Another think on compiling... When I choose to compile all scripts in an object, it would be very helpful if the scripts were compiled in order. That way, I could tell whether they were all re-compiled or not. Because when I get an error on one or more scripts, I don't get the «close» button - therefore, I have no idea whether the list was worked through or not...

I've had to return to the normal viewer for the first time in many a long month.

Freezing on opening profiles or similar windows usually results in a crash. Turning the vertex buffer on to fix graphical glitches and eventual crashes causes a crash.

Frame rate is really spotty, standing in the same place I get 35fps in the regular viewer and around 15 in this release. In busy places it's like a slideshow and crashes about every 5 minutes.

I'm loving the new features for sculpties, but the text colour changes seem rather unnecessary and confusing.

Hopefully everything will be ironed out again soon.

If i pull up a script from inventory i can not see any checkbox to use mono (i am using the black theme not that dazzle [redacted]

yes im in a mono region (they all are) and i just did the upgrade to the rcnill client.


I have a script that i think might actually run with mono but lsl2 gives a blown heap

Yeah, compiling from your inventory is broken, you have to drag scripts into prims to compile them for now.

About the update.. why is it asking to update to the latest version 1.20.15.92456 when its a version above that?

thats because your own name never appeared before.. they changed it from saying "You" to actually saying your name and handled like everyone elses, so its clickable... ig uess they could stop that, but why?... I dont see what is confusing with it.

I just think it's silly that you call one client the "Release Candidate" (RC) and the other client "Release Client" (RC), so that whenever you try to abbreviate it when talking with someone about it, you often end up typing an extra paragraph explaining which RC you're talking about.

My solution? I just don't talk about it anymore.

Been not talking about it for so long, that I have no idea what RCO is. Release Candidate Original?

I may just be out of the loop here. That wouldn't surprise me. I'm trying to ignore a lot of things lately.

It DOES seem like the link there is unneeded, and would help the user see which text is their own a little easier, if their own name wasn't linked.

But it is more consistent to have your actual name there, and to have it linked.

I have to say it's less laggy and the camera controls problem I had with 1.20 have been resolved.

However there is a consistent issue with saving subsequent snapshots in BMP which is a real problem for me.

An incident with graphics leading to a crash I suspect was unique to the click path. I had no problems before then, and I was on for quite some time and visited several places.

If you need specific regions for VWR-8914 please let me know.

well, talking about the linux client ... it didn't crash over 4 hours now and the fps where pretty good. Feeling was better than any 1.20 at the first try. Looks even like the spacenavi would be finally be supported in an "official" build soon ))))
Very good step forward !

Thank you

What are the main bugs being pushed with the release next week? i found one myself with texture thats annoying

https://jira.secondlife.com/browse/VWR-8894

vote for it

Another bug:

I had an issue with an object who refused to let me change the description-field. Whenever I typed something, the description immediately got set back to the original...

Anyone else experiencing this?

1.21 RC viewer is a memory hog on my system.

The 1.20 production release sucks up about 225K of RAM when settled in. The 1.21 RC starts in at 450k and then slowly climbs (memory leak?).

I have this problem too with a HUD in Center2 - not tested it in any other HUD location.

Well, of course Release Candidates are supposed to be *better* than betas, they are actually Candidates for Release, as the name implies. If they turn out to be good enough to ship, it should be possible to release them unchanged; they should not contain debug code that won't be present in a Final.

But in fact the SL Viewer RCs are, as you say, beta-quality code. If you're lucky. This RC 0 is extremely crashy, and I've stopped running it except when I absolutely need to use a new feature; the crashes when the graphics are under stress (swinging cam or flycam in texture-rich environments) are just too frequent.

Please read the release notes. They do give the reason why the view crashes so much right now. They have a bunch debug features turn on right now which in time cause the view to crash more often.

Besides that many great improvements. I also figure the debug features are also slowing the viewer down right now.

You're assuming that "Release Candidate" in Linden Lab-speak means the same as in every other language.

The definition of Beta has evolved overtime with SL. At first QA would recieve the code in alpha form and do what was necessary to get it stable enough to release to Siva. Siva was eventually taken over completely by Lindens and the Beta test area is now Aditi. Beta testers (anyone who wanted to log into Siva/Aditi) were able to catch a good number of bugs and hopefully provide repro to make QA's job easier to hand the repro back to the coders to fix the bugs. Several of us were dedicated to bug hunting and it did help but there never was a large enough cross section who would log into the beta grid and help.

As it stands today we have beta releases for Aditi, but now Aditi is for testing changes to the server side code as in MONO or Havok 4. Any changes that are client side are instead released as Release Candidates for the main gird(Agni). Release Candidates are not "better" then beta, they are both beta with different targets.

The system still isn't perfect but the combination of Release Candidates and pjira should still be classified as a resounding success. LL now has many, many more people testing beta clients and reporting bugs.

This RC is the buggiest I've seen in ages. I crash when I put any load on graphics, like trying to make multiple quick movements. I find that I often can't get a pie menu to function when I click on an av to check a profile or initiate an IM. I freeze periodically, even in areas that I KNOW are low-lag regions. It takes an AGE to wear items that are in inventory -- the system sits in "wait" mode forever. I have had to reset the colors on chat so I can see things against normal background -- OMG, those are ghastly default colors! I'm going back to using the standard viewer and wait for some serious changes in the next RC.

Just be glad it is not like it was long ago....every couple weeks there would be a new release. with bug and lots of them. the next day another download. sometimes the bugs were bad and they would have to do a rollback. The final release back then was the beta. it has gotten much better then it was. LL has made some real progress over the years. I mean when I first logged on back then there were fewer accounts than there where people logged on right now. and the whole grid crashing was the norm.

The first RC is normally the buggiest. they even tell you that in the release notes that this is pretty much going to crash

I know about the "old" days, when a normal in-world av load was 30,000 or lower. I've been around for a while. I remember nasty bugs in the standard viewer, and I remember cringing at the thought of Wednesday "improvements." Guess I've been spoiled, though .... The last few RC versions haven't given me much trouble at all. By modern standards, this release is WAY buggier than I've come to expect. Fortunately, the standard viewer is MUCH more stable than in the old days, so I can just go back to using it until LL gets the next RC cleaned up and ready for prime time.

The ordering of the gestures in the Gestures dropdown list is the reverse of that in the standard Viewer. Also, gesture triggers with capital letters in them are not recognized either when invoked from the dropdown list or typed directly into the Chat box. Gestures with failing triggers still work fine if invoked from the Preveiw button of the Gesture Editor. Gestures with all lower case triggers work fine.

BTW, since the order of gestures is reversed, the ones with triggers starting with a capital wind up at the bottom => why it's been observed taht "the ones at the bottom" seem to fail most.