1.21 RC5 is available

We are releasing the sixth iteration of the Viewer 1.21 Release Candidate (RC5). Please help us to identify any new bugs before it becomes an official download for Second Life.

If you have already been using the Release Candidate (RC4), you will now be required to update to RC5 with the latest bug fixes. But, participating in the Release Candidate viewers is completely optional. You may install this viewer side-by-side with the official 1.20 viewer that you normally use.

RC5 includes a few bug fixes as well as the Security Update of 06-Oct-2008, related to the communications code. A full list of fixes can be found at:
https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release_Candidate/1.21

Please visit the Test Viewers page to download the 1.21 RC5 viewer:
http://secondlife.com/support/downloads.php#download-Testviewers

We expect this to be the final Release Candidate in the 1.21 viewer series, barring any Showstoppers that you may find. Please of course continue to report new issues at jira.secondlife.com. Set the “Affects Version/s” to “1.21 Release Candidate”. We can only investigate and solve issues that are reported there.

No problems with install of this version, memory leakage appears to be minimal compared to previous RC's.

Although the release notes say that VWR-9351 is fixed in this release, while the code was changed, it is still not correct and in some ways worse of a bug than before: http://jira.secondlife.com/browse/VWR-9351

Chaos- thanks for pointing out that sort behavior. We'll take a look.

Snapshots: The bitmap format save option is completely disabled with this RC Viewer version.

I made an admittedly whiney JIRA ticket for this:
VWR-9626

Still not fixed in 1.21 RC5:
PRIM_SCULPT_FLAG_MIRROR does not compile.
Should compile to 128 but gives a 'not defined in scope' error.

I posted this information for 1.21 RC2, 1.21 RC3, 1.21 RC4 and now again.
Don't tell me I did not say

Interest very low on this thread, too bad as this latest version viewer works clearly worse than previous ones - At least for me.

______

Second Life 1.21.5 (98701) Oct 6 2008 10:27:21 (Second Life Release Candidate)
Release Notes

You are at 263993.0, 254725.0, 114.5 in Rumgally located at sim3781.agni.lindenlab.com (216.82.23.8:13002)
Second Life Server 1.24.9.98659
Release Notes

CPU: Intel Core Series Processor (1828 MHz)
Memory: 2047 MB
OS Version: Microsoft Windows XP Service Pack 3 (Build 2600)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce Go 7600/PCI/SSE2
OpenGL Version: 2.1.2

libcurl Version: libcurl/7.16.4 OpenSSL/0.9.7c zlib/1.2.3
J2C Decoder Version: KDU
LLMozLib Version: [LLMediaImplLLMozLib] - 2.01.18662 (Mozilla GRE version 1.8.1.13_0000000000)

Packets Lost: 0/5370 (0.0%)
______


- I still see VWR-8920
- I saw VWR-9065 for the first time by using this latest version
- VWR-9137 is getting even worse
- Avatars take ages to rez, after most of everything is decently rezzed. Seems more like a server issue then, as I see it with the 1.20 viewer too. VWR-9137 seems like a server issue too, but it looks like the viewer version is affecting how bad is it.

Worse of it all, the RC5 version does kick me out of SL every 20 minutes steadily. I just suddenly hear the bell, and I'm faced with the window "You have been logged off SL - you can still go on IMing or you can log off competely", sort of. Crashing was a very very seldom occurrence to me before, and still is with the latest 1.20 viewer.

FPS also worst - I had to narrow down draw distance a little in order to enjoy a decent smoothness.

I'm still having dropped FPS in the new RC and epic lag spikes during TP/culled object rezzing. I don't know what word to use exactly. But, when "new" prims enter the screen, my frame rate drops below 0.5fps. Grayed out textures are still taking forever and a day too. (>_<

Oh... And I noticed keypad controlled camera movement changed. If I haven't [Alt]+Click'd on anything, 1.20.xx will center on my avatar on [Alt]+{Arrow Key}. In 1.21.xx it will stay centered ahead of where my avatar is facing. (I use my keyboard a lot. (^_^)y) It's not painful in any way, but, it changes thins. (=_=)

same here but with abit more fps ~10 compared to 60-70 normal, annoying as hell when going any where that isn`t fully rezzed

CPU: Intel Pentium III/Pentium III Xeon (0.25 micron process) with external L2 cache (2833 MHz) (Quad core Q9550 @ 2.83GHz)
Memory: 2048 MB
OS Version: Microsoft Windows XP Service Pack 3 (Build 2600)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 8800 GTS/PCI/SSE2
OpenGL Version: 2.1.2

libcurl Version: libcurl/7.16.4 OpenSSL/0.9.7c zlib/1.2.3
J2C Decoder Version: KDU
LLMozLib Version: [LLMediaImplLLMozLib] - 2.01.18664 (Mozilla GRE version 1.8.1.13_0000000000)

And, how many times does he need to say it...

In the inventory window, right click on any object and select Copy Asset UUID and all you get is zeroes.

This is happening in both 1.21.5 and 1.20.17

http://jira.secondlife.com/browse/VWR-9645

I'd expect this on _most_ items, though Copy Asset UIID should be grayed-out or not appear if it's not full perm.

Does it also happen on full perm objects?

It is happening on all full perm objects whether I am the creator or not.

Non full perm objects have the option grayed out.

Voted.

What's the JIRA number? I'll vote for it.

Edited - the source in SVN seems to define this constant -
lllslconstants.h:
129 const S32 LSL_PRIM_SCULPT_TYPE_MASK = 7;
130 const S32 LSL_PRIM_SCULPT_FLAG_INVERT = 64;
131 const S32 LSL_PRIM_SCULPT_FLAG_MIRROR = 128;

indra.l:
504 "PRIM_SCULPT_TYPE_MASK" { count(); yylval.ival = LSL_PRIM_SCULPT_TYPE_MASK; return(INTEGER_CONSTANT); }
505 "PRIM_SCULPT_FLAG_MIRROR" { count(); yylval.ival = LSL_PRIM_SCULPT_FLAG_MIRROR; return(INTEGER_CONSTANT); }
506 "PRIM_SCULPT_FLAG_INVERT" { count(); yylval.ival = LSL_PRIM_SCULPT_FLAG_INVERT; return(INTEGER_CONSTANT); }

Are you compiling to LSL2 or Mono code?

Edited - I added a comment to http://jira.secondlife.com/browse/VWR-5647 and Qarl said he'd look into it within *minutes*, while I was still investigating. Dora: they really are looking hard at anything you report in Jira for 1.21.

I will also add my voice to those saying that my client FPS is roughly 10 less than it is in 1.20.17 for the same scene, camera position and graphics settings.

This is apparently related to the problems that have been causing rez failures yesterday and today, so it's a server side thing.

More at /327/5d/285954/1.html

Yes, I understand. The status blog requested that we open support tickets giving the UUIDs of objects that fail to rez. Unfortunately, we can't do that if all we get for a UUID is zeroes.

Right, that doesn't work on objects in inventory, it does work for non-object assets like textures, scripts, notecards. This isn't a new thing. The request for UUIDs in the status blog simply wasn't a well thought out one :/

Argent is right - with the advent of mono, all compilation is done on the simulator (even LSL compilation, so.)

and the new constants haven't yet merged with the server code. so that's the problem. i'm looking into how to make that happen sooner rather than later.


K.

If you're still around, Qarl, since you seem to know the most about this subject, what exactly are the effects on a sculptmap when you check the Inside-Out or Mirror boxes, or both, and how can that be replicated with a standard sculptmap? (I'm looking to replicate having both checked, for the record)

I have been running SL for more then a year using a ATI Radeon X1300. Since the last update non of the available vieuwers will let me be logged in for more then 2 minutes before everything freezes...even my CPU. (need to manual reset it)
I tried 4 different viewers. And reinstalled a variety of recent drivers -including the latest of cause- that worked well for anything BUT SL.
Anyway, I don't know if this is the place to address this issue. Wonder at least if I am the only one.

^_^

I continue to get regular freezes and forced logouts, as mentioned by others. No obvious triggering conditions.

The error is exactly the same in LSL2 and in MONO
I'm happy someone are working hard and I hope they will succeed
To me the JIRA is a closed book. Once I had a look inside but never again...

I did the compilation in both LSL2 and MONO with exactly the same outcome: a 'not defined in scope' error

i have tried downloading the RC 1.21.5 10 times, and each time it hangs up on the intsall, and always when it reaches the mozilla protion of the install, and each time it states that it can't read the information from the file. ande LL Support wouldn't help saying that they don't support the RC

Lionheart, reboot your computer, go find the install folder (C:\Program Files\Release Candidate is default on XP, don't know about Vista).

Delete that folder and everything in it then retry the install.