New Release Candidate Viewer: 1.20 RC3 Available

[UPDATE: 2008-04-24 9:27am PDT] Thanks for the quick feedback on 1.20 RC3.  We’ve found and fixed the cause of the crash on editing appearance (VWR-6792) and will be making 1.20 RC4 available later today.  We’ve removed RC3 from the download page.  Please use 1.20 RC2 or the 1.19.1 primary download until RC4 is available.

Hi again everyone.

We’re back to weekly Release Candidate releases. We increased the frequency of Release Candidate viewers last week in an attempt to gather more info/feedback on the Nvidia issues that have been reported (VWR-6343). Second Life 1.20 RC3 is now available and includes a batch of fixes to issues reported in the previous 1.20 release candidates (RC0, RC1 and RC2) and new code that we believe should address the Nvidia issues. Please visit the test software page to download the Second Life 1.20 (RC3) Release Candidate viewer.


  • Fixed: VWR-5080: Certain color combinations hard on visually impaired (and the not-visually-impaired)
  • Fixed: VWR-2404: lossless texture compression on small textures not lossless
  • Fixed: VWR-380: Resized Flexible Prims Render Improperl
  • Fixed: VWR-6275: Character runs when not supposed to.
  • Fixed: VWR-6301: Pulsating/glowing/fading outlines when building.
  • Fixed: removed mac release notes dialog from LLAppviewer::init
  • Fixed: Scrollbar channel missing in 1.20
  • Fixed: Window opens large, then small, then large on startup
  • Fixed: Imposters sometimes render without attachments
  • Fixed: Yellow edit outline detached from selected prim
  • Language tweaks to World Map UI
  • Fixed: Help > Tutorial makes the world disappear
  • Fixed: Help > Tutorial kills the keyboard.
  • Fix for vibrating name tags.
  • Fixed issue with mozilla scrollbars
  • Fixed: Background and Foreground color are the same in all scroll lists

Localization Fixes:

  • Fixed: main Toolbar will not match to its Korean localization xml
  • Fixed: erroneous German translation for Active Speakers

Note: If you are having problems enabling voice after running RC3, quit Second Life 1.20 RC3 and start it again. You should now be able to enable voice.

As always, please continue to report any new issues in the Issue Tracker. Be sure to set “Affects Version/s” to “1.20 Release Candidate“. Resident participation is welcome at our weekly (Wednesdays @ 3pm PDT time) inworld bug triages, too!

This entry was posted in -Miscellaneous, Announcements & News, Bugs & Fixes, New Releases. Bookmark the permalink.

150 Responses to New Release Candidate Viewer: 1.20 RC3 Available

  1. Batman says:

    Fixed: VWR-2404: lossless texture compression on small textures not lossless

    We’ll see…

  2. Bank Robber says:

    Fix for vibrating name tags


  3. WarKirby Magoijiro says:

    Holy shit, Fixed VWR 2404 :O

    Bridie, I have to say, I frankly don’t believe you. After the number of false fixes we’ve had on this…

    Some testing is in order, it seems. We’ll see if it really is fixed.

  4. Byakuya Runo says:


  5. WarKirby Magoijiro says:

    Ugh. The linden water is still pitch black

    This was introduced in RC2, but was NOT in the RC1. Can we please have that fixed. Glow is broken too.

  6. shanti says:

    Three times in a row crash when initiating edit appearance. boo. Back to an alt viewer…again…. I crash at LEAST 6 times an hour – sometimes in succession. And I am Nvidia – still crashing – related? who knows, but i can’t stay on. That i DO know :(((

  7. Kristi Maurer says:

    Nobody has mentioned this, but can we PLEASE PLEASE PLEASE PLEASE have the “FLY’ button back by the movement controls where it belongs?

  8. Lina Olaria says:

    Please fix the NVIDIA problem. Not even the graphics workaround works consistently any more.

  9. Tiny Mind says:

    Can your Attachments still be SPOOFED and SHOUT on Main Chat by a malicious-script in this Release??

    We’ll see….


  10. WarKirby Magoijiro says:

    And classic clouds are black too. This client isn’t lookinggood so far

  11. Lindal Kidd says:

    Fix the:
    -disappearing system skirts
    -avatar, camera, and prims selected for editing rotating without mouse or 3D mouse input
    -avatar sinking while hovering (applies to as well)
    – prims and selection outlines appearing to be several inches from their actual position until editing handles are released.

    Put the Tools menu back on the main menu bar.

    Restore the ability to substitute custom UI colors and textures that was removed with RC2.

    Thank you!

  12. WarKirby Magoijiro says:

    @8 Lina Olaria: I’m having problems with an ATI card. What is the Nvidia problem you speak of? Anything to do with black clouds and water?

    @9 Tiny Mind:

    That spoofing is a serverside bug. A viewer update cannot fix it.

    It will be fixed in the rolling restart that’s happening now, and will deploy to the whole grid within a few days.

  13. A tad frustrated says:

    I took the forced update. So far all it seems to do is crash. And of course I had a class scheduled for tonight.

  14. Xoza Shadow says:

    Yay, I hope this fixes that flickering that seemed to crash me at times.

  15. Selkit Diller says:

    Beacons crash the client instantly. Try it. Enable beacons-always-on. Foomp. Dead. Also… Dazzle’s still horribly ugly, and definitely needs an easier means of recoloring than dropping files into several different directories. And let’s not even talk about reskinning it… revert the UI. Most of us didn’t ask for this.

  16. Promise Bracken says:

    Every time I go into Appearance, the viewer crashes. So far, it’s 5 times. I can do this all night.

    Unfortunately, I’m late delivering a custom tattoo, so it sux for me. lol

  17. Tiny Mind says:

    Well, never had the time to find out about the SHOUT exploit. Logged in with this loser-viewer.. Crashes right to the desktop a couple of minutes later with no warning or explanation. Log in somewhere else… three minutes later… CRASH to Desktop again.

    So far this release rates: EPIC FAIL.

    Tiny Hope.

  18. Tek Revnik says:

    Same here – edit appearance consistently crashes new client.
    Intel-based Mac w/nVidia

  19. Kyder Ling says:

    Thanks for the new update.

  20. Selkit Diller says:

    Truly useless RC. Enabling beacons crashes it instantly, editing appearance crashes it, and apparently, daring to leave it on for more than a few minutes also crashes it. It’s ugly, it’s unstable, and if you’re thinking of trying it, kids… *avoid*. The only reason to use this viewer is for scripted glow and being able to set sculpty edge-stitching without needing to use a script.

    Totally useless.

  21. Leah McCullough says:

    I can’t connect… it keeps crashing everything i try to login 😦

  22. Naomah Beaumont says:

    Editing appearance crashes the client on the mac version. I wouldn’t be so annoyed, except that 1.20.2 was reasonably stable.

    I’ll file a bug in the Jira.


  23. Flea Yatsenko says:

    Editing Appearance always crashes me.

  24. Tiny Mind says:

    CRASHED Again. Do yourself a favor, Lindens, and pull this monstrosity from the DL page before you incur yourselves further embarrassment. Tell the script-kiddies working there, no second-helping on dessert tonight for making us suffer the indignities of this Release Candidate.


  25. Rocky Pickles says:

    instant crash on editing av.

  26. Larkum Woodget says:

    I had black Linden water with an ATI card (X600) which was fixed when I downloaded the latest drivers for my card.

  27. thegrimmling Snook says:

    wow, I had a pre-working system for the SL client, but release client 3 crashes as soon as it tries to draw the environment.

    Even if I delete the Use data, the RC3 does not work for me and I am on a Vista Machine using an IGM 945 videocard that is made for directX 10.

    All previous release clients did work until this one.

  28. thegrimmling Snook says:

    in fact, the “regular” client works fine and everything else did Until THIS RC3.

    Roll it back and give us the display options for either Dazzler or classic. I hate the new GUI

  29. Pelthar Beaton says:

    Same as for the others, edit appearance crashed me immediately. I’m on NVidia 7600 GST, and my OS is XP 64-bit. I need Windlight for my work in SL, and I was unable to do anything for weeks…

  30. Ludwig Prinz says:

    Are any principles of software development applied at Linden Labs ?

    Throw all source code together, make sure it compiles and out of the door ?? Where is Quality Assurance and Regression Testing ?

    Not very convincing to start RC3 and crash within the first minute.

  31. Burp says:


    Apperance Mode = Crash
    Beacons Always On = Crash
    Standing there for 10 minutes = Crash
    Having a working RC = Priceless

    Ok question. I have’nt had a decent RC working since the new 1.20’s and since RC2, theres even a stuttering for the display as in, it chugs really bad with Dual Core 3.46, 4 GIG Ram and Nvidia 8600GT, now I realize this isn’t JIRA, but i’m curious if you have multiplatform testbeds with different processors, OS’s, ram, graphic cards etc etc that you run these RC’s on prior to release? If so, can we have details on what you run these on?

  32. Rocky Pickles says:

    upgraded to showstopper.. borked on mac intel and amd high end test boxen.. jira updated

  33. Argent Stonecutter says:

    You can reinstall RC1 and change (in the shoprtcut or arguments.txt file) the command line argument to “–channel” to something else (like “Second Life Spicy Brains”), and it won’t force you to upgrade.

  34. MrBill Kurri says:

    Like several befor me have mentioned….EVERYTIME….I go into appearence….I crash….but guess you can see that in all the crash reports that have been generated by me…smiles
    Also I crash when ever I do ALT. to focus on an object and zoom out to it or rotate cam around it….
    Yes…please put the tool tab back up on the tool bar…..sighs
    Thanking you for your efforts in trying….looking forward to your success….

  35. Zorin Frobozz says:

    Advanced -> Rendering -> Features -> Dynamic Textures

    Turn it off; this is a workaround for the edit -> appearance crash. It doesn’t seem to affect anything in world, so I don’t know what the feature does. But at least for me, it fixed the problem so I can keep using RC3 for the moment.

    I wish the pref would be saved between sessions though.

  36. Marv Rayner says:

    1. Viewer crashes upon entering Edit Appearance.
    2. Color selections for UI still contrast too much with actual camera views.
    3. Contrast between text and background in Inventory still way too low to be easily readable. The 1.19 and prior UI colors worked much better than the 1.20 UI colors. For me, Dazzle is a failure and continues the tread of every significant change to the UI since the last viewer of the 1.17 series making the user experience worse while ignoring all user feedback.
    4. The vertical size of the Communicate window is still over one quarter of the vertical screen size at it’s smallest in 1280 x 1024. It has been this was since the first 1.18 viewer, making it extremely difficult to do anything other that talk in IMs with the window open. Why? Why is the huge vertical size of the Communicate window so sacred to Linden Labs? I am very serious in this question.

    My verdict on this Release Candidate is UNUSABLE due to the Edit Appearance crash bug. In my opinion, the last truly usable viewer was the 1.17 series, before the current Communicate window.

  37. I’m sorry, Linden Labs. I really don’t complain a lot. I adore SL. But, I really really really don’t like Dazzle. It burns my retinas. Seriously! My eyes are strained from looking at it. The new icons are fine. I can get used to those. But the eye-searing brightness, coupled with the weird lack of opacity that plagues my attempts to drag things to my inventory and actually *see* what folder they are going into……..I’m sorry, but I ditched Dazzle and went back to using 1.19 v. whatevertheheckitisnoq

  38. Yami Katayama says:

    definitely a crash problem with Nvidia cards. I’ve switched to an alt viewer because of these crashes since RC1 – God, let’s hope they don’t make this one live.

  39. Crusher Soderstrom says:

    Finaly we can build normal again after the fix VWR-6301

    TNX Linden

  40. Ann Otoole says:

    edit appearance crash. starts with a small window and then grows to full screen.

    the edit appearance crash indicates no unit testing protocols are in place. Come on this is a basic unit test case.

    time for the new CEO to bring in powerful development management to review and deal with staffing properly.

    oh yea, the developers need to have their annual performance evaluations done by the SQA team. Bet that would get some rears in gear. Oh.. assuming there is a serious SQA team composed of people with 10+ years each of expertise in hard core SQA.

    Please stop calling this a release candidate because it isn’t.

  41. Jessicka Graves says:

    It’s still Dazzle. It still burns my eyes. The new CEO, and the new blog-reader Linden (Kate?), for the love of any possible gods or God, get rid of Dazzle.

    I don’t need to repeat what everyone else says above.

  42. Angelina Sinclair says:

    Please at least create a option for the normal skin and the dazzle skin. I can’t stand the dazzle skin, I visit far too many dark sims to be having such a bright and nearly blinding skin on my viewer.

    I would be glad to help test this viewer if it wasn’t for the dazzle skin.

  43. thegrimmling Snook says:

    THere is more than an Nvidia card issue, it also applies to IBM Mobie chipsets.

    The entire setup is fine until the actul rendering of the world after the loading of the reigon, blah, and textures.

    Please rollback to RC1 that worked, this one is a nightmare.

    I’ll state before, I am on a 945GM chipset IBM Mobile and all the windlight and RC clients worked until this one (not including that oen that had an issue if you had the option to choose a starting point), please revert back tot he previous client.

  44. In RC2 and RC3, glow does not work for objects on the HUD.

    Likewise, as others have stated, editing appearance is an instant crash. Fortunately, I’m not one of the vain sort and only noticed because I tried to confirm that report.

  45. Photon Pink says:

    UI “experts” said the new colors are “more accesable” though, and will help retain more new users. How could “experts” be wrong? I mean, they probably have a fancy resume, even. 😛

  46. MR Little says:


    “We plan to
    release Skinning Phase 1 before we make 1.20 mandatory (hopefully well before– we are trying to keep mandatory updates to a minimum), so we will support switching skins before imposing this release on everyone. However, this is the look we are planning to support going forward.
    That being said, because the majority of the objections to the new look appear to be contrast and color scheme issues, we are going to immediately prioritize a project to provide an in-client interface for modification of custom colors and maintenance of these customizations across updates, just like we do for other settings.” — Steve Linden (SLdev mailling list)

  47. Eleanor Anderton says:

    1. “Friends” tab will not load.
    2. Cannot access chat lines from groups.
    3. Cannot acces Groups tab.
    4. Cannot access Groups chat lines.

    Give up and turning off! A social network where you cannot communicate!

  48. Sumiko Yokosuka says:

    I can’t log in because as soon as it begins to connect it either crashes or it says that the region I’m in is logging out.

    Way to go, guys.

    So am I now no longer able to enjoy SL? This will not be good for your eventual hoped for IPO if regular people who can’t afford $2,000 computers can’t get in.

    You screwed up. Please fix it. Now.

  49. gristle Deadlight says:

    Can’t get this newest RC to run on my laptop. Bought one of the 3Dconnexion 3D control things Torley talked anout now I can’t use it.

    Thought I’d seen somewhere you could add arguments to the SL shortcut to be able to run the older RS’s. Like you do for multiple instances of SL. Anyone know anything about it.
    Thanks, gD

  50. Ryu Darragh says:

    Scripted glow is available in any client. Simply (1) Declare Constant:

    integer PRIM_GLOW = 25;

    Next (2) insert into code:

    llSetPrimitiveParams([ PRIM_GLOW, integer which_side, float glow_value ]);

    Or, (3), do it the hard way:

    llSetPrimitiveParams([ 25, integer which_side, float glow_value ]);

    Just remember to remove the constant if compileing in the 1.2X.X clients.

  51. Vittorio Beerbaum says:

    @47: this is a RC viewer, it’s supposed to being used as test client (to collect bugs). Use the official version for a more stable client.

  52. Argent Stonecutter says:

    Gristle@48, read message 32. 🙂

  53. Lupercaleb Walcher says:


  54. Thili Playfair says:

    How to crash client 101

    – go into Appearance mode
    – set nighttime by using shortcuit ctrl-shift-n
    – several debug setting is broken or instant crash you

    heres some exsamples;

    advanced / character / show look at
    advanced / character / show point at

    instant crash;
    advanced / character / display agent target

    Good going

  55. BlueWall says:

    Hmmm, not too bad so far 🙂

  56. Please fix the issue of the disappearing skirts. This issue is affecting clothing designers’ businesses across the grid!

  57. Sumiko Yokosuka says:

    Went back to an older Second life viewer and now I can log in! Yay!

    And my inventory is listed in black and white again, which makes it much more readable than the blue background with black type in the new release candidate viewer.

    I’ve deleted the new release candidate off of my computer, too.

    The setup I have now is fine. Please don’t screw it up with another non-working mandatory update.

  58. Siobhan McCallen says:

    PLEASE fix the nVidia bug!!! This needs *priority* focus! I got an nVidia card because of the high recommendation it had on the Second Life website…now, it’s becoming more and more useless. I walk around, I crash. I stand around and talk, I crash. I stare at a wall, I crash. I dare to cam around — video driver crashes and restarts, killing the client!

    What the hell?!?! Please stop playing around with fancy fonts and UI chrome, pull people off tree LOD, and put ’em on this!

  59. Shaunee Gabardini says:


  60. Cotytto Bonetto says:

    crashes on entering appearance mode every time And from reading here this is wide spread. Instant showstopper. This one needs to be pulled back. let’s go back to RC2 until you get this worked out. Yes…it is a test client…we tested it…it doesn’t work.

  61. Dytska Vieria says:

    Fixed: Window opens large, then small, then large on startup This is not fixed – it still makes a window, then maximizes it. 1600×1200.

    It would be nice if the statistics bar would remember its location.

    It would be nice if Advanced->Character->Character Tests->Go Away/AFK When Idle would remember its settings.

    There are probable other settins(.xml) items as well and there already is a jira on it with a lot of votes.

    Please disable the anti-aliasing feature until you get it right – it is far better to control anti-aliasing with the graphic card software than to NOT HAVE ANY ANTI-ALIASING AT ALL with the RC viewers. There already is a jira for this with a lot of votes.

    When editing something especially overhead, the camera will skew when panning. There already is a jira on it, but the bug apparently is confusing to identify. Please fix it.

    Why does LL even have votes for Jira when the bugs with the most number of votes are ignored?

    I appreciate the progress, but please fix the critical bugs that affect everyone!

    I wont even mention VWR-3258, The first WindLight never had these problems last year, now it does. I broke down and replaced a very nice X1650 ATI card for a 7600GS nVidia card just to be here. Probably not many have done this, which may explain the increase in crashes, login failures and just plain old problems using the client.

    Besides the barf-colors of Dazzle, it runs stable here…

  62. Buck says:

    Appearance causes crash for me too (though the first time I tried, it waited until I exited the editor). (@34–Thanks for the workaround!)

    Dazzle–about the *only* thing I like about this is the icons. 🙂

  63. Nite Zelmanov says:

    Undoubtedly the under the hood changes in the dazzle branch are necesary for the long term health of the code, but please read the writting on the wall here – put this back into first look where it belongs. M Linden, are you reading this?

    Crashing here, there, and everywhere is normal when you’re trying to refactor badly coupled code, please try to patch forward any useful non-UI coupled changes, but take the UI stuff back to the lab for another good round of testing. You’re scaring us by saying you’re considering releasing this mainline.

  64. Krow Ames says:

    Idea: Old viewer and new viewer options for the new “dazzle” look. A lot of us just don’t like it. It’s too bright, to be honest. Some people like the new changes, some people don’t. How about an option to change between “retro” and “Dazzle” or some such?

  65. Dytska Vieria says:

    … and it definitely crashes on appearance editing!

    PS – please fix:

    VWR-6267 and VWR-6402

  66. Rocky Pickles says:

    this one is a non-starter for almost everyone. just jerk it and try again in the morning 🙂

  67. gristle Deadlight says:


    Thank you Argent Stonecutter

  68. Kit Ristow says:

    Dynamic reflections utterly messed up–which bothers me, as I believe the current release doesn’t have the option to enable them. And yet another confirm of the consistent crash on editing appearance.

  69. Congratulations! First viewer in a long time that looks great, but crashes constantly. Kudos

  70. spirit Wingtips says:

    extremely fustrated: eversince i downloaded the update all i do is crash crash crash crash! not once did i get on.

  71. My Avi is barely standing still, it is like an earthquake the entire time
    on the old viewer i used to get rid of that with the cam springyness settings which are gone now. Any suggestions?

  72. Stitch Yoshikawa says:

    Does it seem like the Programmers have no idea what they are doing? They just put out a new release to screw up our SL lives. I went to edit appearance it automatticaly made me naked and then crashed. WTF? Fix the problems before moving on…

  73. Jenny Carlos says:

    lol, Thats funny. I dont think they even test these viewers before they release them lol. I havent crashed this much in SL in ages and havent even tried this new viewer you guys are talking about here lol. Im thinking of trying it in hopes I can walk again. I cant even walk a few steps with both the old viewers without freezing and have to let off the forward arrow key and press it again over and over and walk in steps to even walk around in SL at all . And this is EVERYWHERE in SL on my 3 grand tower lol. Real great work here lol.

  74. BlueBORG Potluck says:

    Well Seems the Scriptkiddies have struck once again.
    I wish i had one of they’re computers they’re testing these fixes on then maybe just maybe i can get back in world and enjoy sl as i did when i first logged on over a year 1/2 ago, Please linden’s fix this. and they wonder why i still use a free account. i pitty those of you paying for service like this or i should say lack of service. I’d say welcome to the new CEO but from reading the past blogs it just might be another linden labs smoke screen to make everyone feel as if they’re pulling they’re heads out of the’re a$$’s and gonna fix this place up. but seems they once again released another FUBAR’d so called fix that’s yet broken. Where’s that Uninstall icon again???

  75. Stitch Yoshikawa says:

    I can barely walk too, plus when I do the way the camera moves is making me sick. It wont stay still and it moves more then it use to. I also want the tools menu back on top and not in the bulder menu. Still cant find it when I need it. My friends are wondering why I havnet been on SL lately, its because its making me sick and Whats the use when I keep crashing for moving.

  76. Cotytto Bonetto says:

    Be sure you all go over to the jira and vote on

    Nice to put your thoughts and frustrations here but that is where things get attention and get fixed. So far the appearance mode crash report has only 3 votes.

  77. Shadowquine says:

    Hm. I liked the sound of some of the fixes, but all I can do with RC3 is crash on login.

    Back to 1.19 yet again. Better luck next week…

  78. Bad points:
    1. Mighty mouse bug definitely still there (I know it wasn’t declared fixed in this version)
    2. Appearance editor crashes
    3. Beacons/sunset trigger crash
    4. UI still has Windows XP look (not good)
    4.1. Text and window background colours are definitely in need of more subtlety

    Good points:
    1. Random screen flickering black (like 1 frame of blackness) seems to have gone from this release
    2. LOVE the anti-aliasing (up to 16x) in advanced graphics tab on the Mac client!
    3. Seems to be a few less overall common freezes
    4. Possible tiny increase in FPS
    5. Seemed to be a bug in the last RC that would make the viewer hang when given inventory from a vendor/avatar. Now appears to be fixed

  79. sasja says:

    Where is the fix for tripping over every bump you walk over ?
    In the beginning it was funny to fall over every step I walked over, but now it’s getting annoying.
    Really annoying.
    So is the bumpines of my camera, walk behind me 1 meter and it’s like someone walks in to me, camera all over the place.
    Not so happy here :o(

  80. Ann Otoole says:

    it is ludicrous to have to vote in the pjira to get bugs fixed.
    if pjira is for voting then theres other votes that need to be done.

    that being said a true defect that is documented properly requires no votes to be fixed provided a real software engineer at LL sees it.

    make sure the edit appearance crash is marked as a showstopper. you can’t create clothes without edit appearance.

  81. Dytska Vieria says:

    Seriously, don’t you (LL) have a checklist to run through before releasing a new RC? You know, a step by step list of tasks that cover everything? Such as, edit appearance, put on a skirt, what does it look like? Does it disappear?

    It is safe to assume, obviously not, which is a serious management issue. RC-3 should not have been released at all! Neither should have RC-2 or RC-1 or RC-0 for that matter.

    We do enjoy helping with your bugs, but it seems that LL changes more than just what they say they do in the Release Notes and break more things than they fix. And, the things that they fix are not what is important!


  82. SoulFire Msarko says:

    I’ve been running the RC since a week after I started on Second Life ( About 2 months ago ).. and I’ve had little issues. It seems I’ve been one of the fortunate ones because I’ve experienced very little problem with any task. However, after the update tonight – I’m crashing constantly – especially when teleporting – and I’m logged off if I stay in one place too long. I won’t go into a huge venting session because frankly it seems that enough people are frustrated enough….

    What I will say is that this update is horrible and for the first time in 2 months I’ve actually logged in on the standard viewer – something I’d rather not do ever. It would be VERY helpful if the RC Updates were not mandated – and completely optional. I was aware of the Nvidia issues previously – yet running a Nvidia G-Force 4 I suffered no issues.

    Rollback the force update please and fix it before making us install it. I realize we’re basically beta testing, but when something like this DOES happen, it would be nice to reinstall an older RC version till the issues are addressed – especially severe ones that leave us crashing.

  83. yep crashing on appearance mode as well,
    please roll back to the previous version till this is fixed!

  84. Healer Ladybird says:

    I keep crashing when i try to edit appearance???? 3 times in a row already and i do have nvidia card!

  85. richard says:

    wow this is a piece of crap!!!!!!!!!!!

  86. iliveisl says:

    thanks! it runs really well. the only thing that messed with me on the previous one was that shakey, outliney, blurry deal on the build menu. lol, but i thought it was my martinis! 🙂 runs good on this nvidia machine (or is it the olives in the martini! either way, life is pretty good)

  87. Qie says:

    @79: tripping fix is in 1.21 server-side, coming soon to a sim near you.

    PROCESS SUGGESTION: You may get more useful data if a new RC were voluntary for a few days while you assess whether you’re getting any information or just seeing the same crashes over and over. It could be that some RCs just are better skipped as mandatory updates, till a quick patch or two can be applied.

  88. Sean Heying says:

    Send it back to First Look.

  89. rado says:

    I welcome new Candiidate, but with Geforce7600 of Nvidia, with my PC becoming problem still, it increases the phenomenon where when the starting viewer the window becomes instant small.

  90. Keryth Qian says:

    5 crashes within minutes of logging in and editing appearance..which had to be done as av was grey so long after log-in. Rebake also crashed me. Standing still…crashed me.

    I truly hate that my preferences once set, revert and have to be reset every time I log in: ie: logging IMs. I do NOT log IMs ever. However on top of everyone’s IM to me it says that IMs are being logged. How many people want to chat privately knowing their IMs are being logged…why is this a default?
    Since the update, property lines show as a I have to have a little list to go back to my selected preferences.

    I didn’t take the regular SL update so that I could continue to use Nicholaz running on 1.18.5 3…so I now have ONE choice of viewer..Nicholaz.

    Dazzle..I agree..crazy colors and the light blue inventory page is difficult to see..and if you have something attached or is hard to ascertain that without checking each item.

    Well I do have Nicholaz….

    BTW I have the 512 NVidia 7950 card with latest driver..

  91. McCabe Maxsted says:

    A reminder to everyone who wants to try different skins for Dazzle:

  92. Jenrose Meredith says:

    Thanks for the warning guys, I loved the 1.19.1 release candidate and have not been able to tolerate or use effectively anything since RC 1.19.4. I use the RC exclusively for building above 768, but am not even bothering with that for now.

  93. Flaran Riggles says:

    To all with problems who need Windlight try the latest viewer from Nicholaz, Eye Candy Ec=e. This runs and memory leak is fixed.

  94. Cris says:

    Instant crash before login screen on nvidia geforce 8600 gt…

    It happens since Windlight became stable… Ran perfectly Windlight versions… :(((((

    Now I can’t use the stable version, RC versions, nor dazzle versions… great, isn’t it? Thanks god I had and old stable version without Windlight…

    And the funny thing is that Windlight worked great for me before going stable…

  95. Jaca C says:

    Yep crashed on editing appearance

  96. Mutifex Darragh says:

    Can’t run this update at all. Tried downloading twice and it seems corrupt.. Get a pile of error messages on install while it is unpacking files. Epic loss..

  97. Rascal Ratelle says:

    Although there has been noticeable Improvements in some areas the following are STILL unresolved.

    * Serious memory leaks.
    * Grid instability and poor performance
    * Teleports fail quite regularly, especially under heavy load
    * Sim performance varies wildly (NOT due to client content either)
    * Low FPS
    * Serious texture latency
    * World maps are very slow loading
    * Crashes and viewer hangs and freezes
    * Ongoing friends list presence issues
    * Group chat totally borked (Still an issue)
    * Group Notices not getting to all members of a group
    * Random animations starting out of nowhere (and no, not an attack)(Intermittent)
    * Sailing off into void space after crossing a sim line
    * Did we mention crashes? Why yes, yes we did.
    * Major bugs not being corrected month after month, year after year (prime example: llTargetOmega)
    **Bots and bot farms.***
    * LL spending time on items no customers really want or care about.
    *** LL totally ignoring customer voting results and @#$# well doing what they want anyway (prime example: voice… which was majorly voted AGAINST by LL customers).***
    * Absurdist pricing on sims and land (namely: $295 and $350 a month for a piece of virtual land is ridiculous. The only thing it does is stuff LL’s pockets with $$$ and keeps most people for being able to afford a sim).
    * Total failure of LL to prevent minors from entering the grid, resulting in continual hassles with immature children (not that some of the “adults” are any more mature… it just adds to the problem and drama).*

    … and the list goes on and on and on.

    Why list these things? We’re not just griping. We’re listing these things to point out issues that Second Life customers deal with every single day… issues that Linden Lab continues to ignore (or put on the back burner, or “it bothers us too” into the obscurity pile) year after year.

    And then people wonder why there are constant gripes on the blog.

    That would be why.

  98. Brutus Martinek says:

    yeah i can’t even log into this client. it crashes everytime.

  99. uh-oh says:

    @97 “* Total failure of LL to prevent minors from entering the grid, resulting in continual hassles with immature children (not that some of the “adults” are any more mature… it just adds to the problem and drama).*”

    I agree, get the children off the adult grid. Are we supposed to be flagging our land as adult content? It appears no one is. Maybe M Linden will decide to make the right move and make identity verification a requirement before you log in. How how letting us know when this flagging is supposed to be used. I think a lot of people are either confused about if they have to use it or just plain refuse to.
    In any case, get the children off this grid.

  100. Nikkie Jua says:

    Fixed: Window opens large, then small, then large on startup, not really, it still opens small and then large for me.

    I do crash in editing mode, when I disable Dynamic Textures, my av turns gray and the editing screen does not load completely, so i cannot use editing at all, because I cannot see what I’m doing.

    Beacons always on does seem to work for me.

  101. Jessicka Graves says:

    @99, not a lot of people want Age Verification crammed down their throats (though judging by LL’s reputation, it will most likely be). And especially don’t want Age Verification, on top of Dazzle, on top of all the crashing, bugs, and continued problems, some that have lasted a year or more by now.

  102. Kiki Devin says:

    Hmm.. The crashing is starting to suck.. I crash at login.. and what is worse is how when u try to move the cam keeps moving but not in the direction that your av is?? what is that about? I feel like im drunk.. =( very sad, i am starting to hate these viewers as well as sl cuz of all the problems i find myself using alt viewers which shall remain nameless

  103. Nibb Tardis says:

    Don’t be stupid ! How can you push a new RC every damn week ! A week isn’t even enough for your internal QA to do proper testing !

    What kind of quality process have you got in that shop ?

  104. Balpien Hammerer says:

    OK, I get it. These crippling changes are meant to get us to leave. I understand, servers overloaded, so what to do, break things so people leave. Got it. I just sold all of my land, no more tier from me to the Lindens but fewer prims for you to simulate.

    Details: this viewer just broke every product made out of flexi-prims. All wings are now stiff, that beautiful undulating pattern is now gone. All beautiful billowing skirts and now stick nearly straight out. Curved cascading curtains now stick out. I verified this does *not* occur with and it did not happen with the previos 1.20.x build.

    Way to go, guys. How did this pass QA gates? Do you have a QA?

    Now once again, STOP adding features until the bugs are fixed. Go look at your friends to the south in San Jose: Adobe. They have adopted a feature stop approach. When the bugs go above a certain level, they STOP permitting develoeprs from adding new features until the bugs are FULLY attended. Guys, get disciplined about this!

    Get these bugs fixed and maybe I’ll buy land again, but I am no longer going to pay for carelessness and whim.

  105. Marie Sims says:

    Sorry, but when animation’s loading window can be fixed? Probably i am the one, but anytime when i tried to load animations and if it has time more 30 sec, i can not close Load window… always needed restart SL :(((

    thank you for advance,

    btw, crashed on editing appearance..

  106. eve express says:

    no successful log in yet, just repeated crashes. so glad i’ve sold my land and am getting ready to down grade membership, as someone else said, this is no longer worth paying for.

  107. Chrys Melnik says:

    Repeated crashes -cant get in, until I reverted back a client. Thanks to 32 Argent Stonecutter for the advice – hey want a job at Linden?

    “You can reinstall RC1 and change (in the shoprtcut or arguments.txt file) the command line argument to “–channel” to something else (like “Second Life Spicy Brains”), and it won’t force you to upgrade.”

  108. Nibb Tardis says:

    It’s pretty normal that developers break things in their code. What isn’t normal is that nobody catches bugs as obvious as these. Don’t tell us this RC worked flawlessly on your machines.

    A product as complex as the SL viewer should need at least a week or two of full-time developer testing. That means everyone using the viewer and testing whatever they coded. And then an extra week of validation testing with real use cases, like “upload a texture”, “Edit appearance”. This has to be formalized and documented so that the release can be approved and signed off by management (if there is any).

    Your QA process is rubbish. This viewer hasn’t even been smoke tested ! How did it ever get released ? Who approves a build for release at LL ?

    You need to get your act together and start implementing quality processes just like everybody else in the industry.

    But then again it’s probably too late. Another couple of months like this and there won’t be anyone left to complain. So keep it up.

  109. My1st Doobie says:

    Im QUITTING and taking all my cash out…

    SL SUX !

  110. cosa nostra says:

    “this afternoon in M his office”

    M ‘hi bridie’
    Bridie ‘hi M’
    M ‘are u a monkey bridie ?’
    Bridie ‘why ?’
    M ‘because I said hi and you copied me by saying hi also’
    Bridie ‘oh sorry’
    M ‘u know that saying sorry is a sign of weakness’
    Bridie ‘really ?’
    M ‘so you are a weak monkey !’
    Bridie ‘*snif*’
    M ‘to the point now, what happened with the RC3 ??’
    Birdie ‘oh, mmmhh, hehe’
    M ‘is that all you can say, or are u able to answer my question in a professional way ?’
    Birdie ‘the RC3 is not my fault M, they pushed me to launch this update’
    M ‘who is THEY ?’
    Birdie ‘the others’
    M ‘so you are blaming the others ?’
    Birdie ‘yes & no’
    M ‘yes & no, are u taking drugs or something ? just be factual, after checking the blog site, I see youre name on the blogheader, it doesnt say OTHERS’
    Birdie ‘euh hehe yes M’
    M ‘did you checked if the RC3 was gonna work ?’
    Birdie ‘I thought it would’
    M ‘thinking is not enough, guess u understand that!, we are a professional business and company here ! think when ya are on holiday’
    Birdie ‘I wanted to help by launching it asap’
    M ‘listen monkey, instead of helping, u just launched a non-working upgrade who is affecting our precious customers who are paying there asses of for a service, an upgrade who hasnt been even QA tested for days or even weeks, also youre action is ego driving without consulting others teams, this indicates also that ya are a non-teamplayer and therefore a danger to work in this organization … right ?’
    Birdie ‘But M’
    M ‘NO buts here, I dont like excuses’
    Birdie ‘hehe’
    M ‘and stop laughing, u behave like a kid’
    Birdie ‘sorry M’
    M ‘STOP SAYING SORRY !!!!!! %@&%’
    M ‘ok thats how I deal with unprofessional staff, I dont know who got you HIRED here, I dont care really, U ARE FIREDDDDDDDD !!!!’
    Birdie ‘*snif* *snif* *snif*’

    to heal the pain a bit have some fun folks ;o)

  111. Ann Otoole says:

    @104 – I’m not seeing any problems with flexi prims. if they destroy flexi then i’m out of business. I already saw onyx go out of business because of the rotation bug and i am seeing a lot of people leaving. I think the new CEO needs to get in here immediately and start dealing with things hard ball. However, somehow, just a gut feeling, I doubt he will.

  112. Tepic Harlequin says:

    Crashes when trying to edit Appearance, happened twice in a row, only change is viewer, might need some slight adjustments?

    Thanks 🙂

  113. Toad Mougin says:

    Hurrah!! – I have anti-aliasing back :))

  114. oof says:

    Birdie : M! Look! We got the whiners for the release candiate again on the blog, they never learn!

    M: What do you mean?

    Bridie : We release a RC thats not ready for public use, and the ones using it to run their businesses screw themselves and blame it on us, never fails!

    M: /thuds

    Bridie: M click my butt to use my Chim and type /99 stop when your finished.

    M: (does the chicken dance) So you’re telling me that these people upgrade to a non public release, complain about skirts falling off then make false statements about selling all their land and leaving SL when all they have to do is run the regular 1.19 viewer?

    Birdie: Now you know why Phillip went to Europe!

    M: …

    Birdie: By the way, who replaced you in the mail room?

    M: Phillip.

  115. Rat Barzane says:

    Crashing when I try to Edit appearance…
    I notice I’m not the only one with this problem..
    Rather inconveniant since I am trying to make clothes lol

  116. So far I seem to be one of the happy ones – works for me. Nvidia 6600 GT on Windows XP … maybe this Vista bs is causing problems? ^^

    Just wanted to say something positive here 🙂

  117. Your Conscience says:

    Yet we -still- cannot log in above 768m >.>

  118. montanacorleone says:

    Back to the drawing board Lindens. How can you miss something like Appearance crashes unless you do zero testing?

    You should start calling this an alpha, not a RC. What a joke.

  119. LILLY says:

    If this viewer is not working for you, why do you keep complaining this much??? It is a TEST VIEWER !! So yes, it has bugs. Maybe Linden can change the title, because many not-native english speakers do not know what Release CANDIDATE means, and they are all going to download it after this blog post. People, if this one is not working, go DOWNLOAD THE NORMAL SL VIEWER, on the standard download page. That default release viever has WINDLIGHT TOO !!!! and it working smoothly!!! So, for all complainers, don’t download a candidate release !!

  120. Carrie Grant says:

    Still waiting for a Mighty Mouse fix =(

  121. Sugar Silverstar says:

    So far have crashed 8 times out of 10 and logged out once, and still system skirts are not fixed and the camera keeps moving after i stop on my subject or swings wildly all over the place when i try to use camera controls.. what did you guys fix exactly?

  122. Ann Otoole says:

    odd… teleporting to a location at 702 meters puts me on the ground even though allow direct teleport is enabled. So basic teleport functionality is broken too? how can this even happen? the code worked before. your not fixing things. your breaking things. you need to hire some consultants. hey i have a great idea! i bet M knows where to get consultants! PWC! (Hey M, and i bet you know this, if you bring in PWC make sure its for a single price. Otherwise you know what they will do.)

  123. Evangeline Biedermann says:

    Sadly, i agree with the ranting.. it’s hard to stay objective when one fix seemingly comes along with a handful of bugs.. fine.. now i don’t break into a run trying to walk across my living room.. but.. where the hell is my system skirt.. and YES.. i can’t fix that in APPEARANCE.. cos i keep crashing.. turning off dynamic textures didn’t help as then textures don’t seem to rez..i end up with the head of one skin..the body of another..IS SOMEONE AT LL HAVING A LAUGH??? i’m working as a live model.. but as soon as i go afk for a pee.. i crash.. not that it’s obvious.. crashing silently.. time keeps ticking.. music keeps one talks to me…oh! i’m gone again!!!! PLEASE!!!! i can’t go and replace the hair i’m pulling out in RL by TP’ing to a hair store and buying a handful of new styles! yours thoroughly fed up!

  124. Spank Lovell says:

    A quick try of this RC seemed to work for me however I CANNOT ignore the number of people who:

    a) have crashes while in appearance mode etc
    b) hate and detest Dazzle

    And if I cant NEITHER SHOULD LL!!

    Guys I raised this question at a townhall meeting (What happened to those eh?) “What is your Quality Control process?”

    It seems that something gets broken with every RC, and I agree with others who have asked you to stop calling it an RC when it is patently an Alpha.

    PLEASE make your QC procedures public. I would dearly love to know, whats your testing process, documentation procedures, methodology, etc.

    I’m sure others would also love to know and YOU NEVER KNOW you may get useful feed back.

    I love SL guys but releasing things like this just knocks your cerdibility right back. The new CEO has his work cut out for him. I hope he has the metal.

  125. Ann Otoole says:

    @119 – LILLY, the problem is that this is a release candidate meaning they are about to deploy it as the main viewer. The residents of sl are very worried about this because it means someone is about to release something that will seriously damage the sl economy.

    All LL needs to do is stop labeling non-unit tested code as release candidates and call them alpha releases and follow the correct SQA path. then maybe a release candidate will show up once a year. thats about how long it will take at this rate. i hope some changes are made to improve this situation.

  126. Evangeline Biedermann says:

    ahhh!! LILLY @ 111 to answer your question:

    i’m using the Reclease Candidate because i’m lead to believe that some of the bugs that make second life unbearable in the Regular Viewer are FIXED!!!

  127. Chris says:

    Lilly, if nobody complains they release the RC as the standard and then these same people can’t play at all. Do you not think it’s better the gripes are HEARD? what part of RELEASE CANDIDATE did YOU not understand? This has already cleared internal QA and is strongly tipped for RELEASE. If they don’t say what’s wrong with it, it will be RELEASED! We’re lucky to get 150 chances to say what’s wrong with it.

  128. SL Player™ says:

    Patiently waiting for the big M’s vision speech

  129. Someone Else says:

    Client crash trying to dereference memory at 0x00000004 in Windows.

  130. Trin Bailey says:

    Voice still doesn’t work…

  131. Trin Bailey says:


    it is impossible to get the advanced menu. debug mode

  132. Pepper Haas says:

    I agree that the last good UI was 1.17. Every revision since is completely unwanted and has made it so much worse. Dazzle, from what I hear (I refuse to upgrade unless forced) is the worst, ever, and whoever thought of AGAIN changing the UI and uglifying it like that, should go back to computer design school and take the class where it’s taught that changing the User Interface is something you avoid at all costs.
    If they force me to upgrade Dazzle and these sad sorry RC candidates that disappear your skirts and mess up all your textures and make you reset all the light and shades every time — I am so out of here.

  133. apachie says:

    just crash again…..

  134. LOL AT ALL WHINERS says:

    u all stop whining that is why it is a Release Candidate. So all can test it if u want to. If u dont like it go back to what u were using. Me personaly havnt crashed yet or had any probs. All is good with it to me. So much complaining going on and no answers. Yes I agree all ran much better a yr ago but SL didnt have the same amount of users either.

  135. LOL AT ALL WHINERS says:

    Oh and by the way i been on it for just over 6 hours now so I think if was a horible client as some suggest I would of crashed now. Or maybe some just like to hear themselves talk that is why gotta complain all the time

  136. Trin Bailey says:

    @ 134 :

    Read entry #125.

    It might help…

  137. Nibb Tardis says:

    No. A Release Candidate is software that is in the final stages of validation. It has been thoroughly tested internally, features and UI are frozen, it is stable and ready to be rolled out as the official release, hence release CANDIDATE.

    The purpose of a RC is to simply to make sure you haven’t missed any last minute bugs that might crop up on some exotic systems. That’s all.

    This release however doesn’t even pass basic smoke tests, such as login and edit appearance, look at the water, look at flexy prims, look at glowing prims… This release hasn’t been tested at all, so this should not be a release candidate.

  138. Crash Logger says:

    … since sending crashlogs never works … on editing appearance:

    Nvidia GeForce 8600 GT/PCI/SSE2/3DNOW! GL_VERSION 2.1.2
    Driver 174.74

    2008-04-24T08:46:34Z INFO: LLAgent::sendAgentSetAppearance: TAT: Sent AgentSetAppearance: head upper lower eyes
    2008-04-24T08:46:37Z llrender/llvertexbuffer.cpp(95) : error
    2008-04-24T08:46:37Z ERROR: LLVertexBuffer::setupClientArrays: Cannot use LLGLImmediate and LLVertexBuffer simultaneously!

  139. Kugel says:


    All these issues with Nvidia here, all the issues with ATI (which strangely enough nobody whines about here?!?!).

    /me sighs and goes back to his game of solitaire.

  140. Vic says:


    Maybe if you would get up your camping chair you’d crash.

  141. Mylene Cazalet says:

    I still have the flickering black triangles in the left upper corner, which bother me, and numerous mac-users with the Intel GMA 930 chipset since the introduction of the 1.19 viewer. It severely disturbs the pleasure of being in SL. It seems that reporting these kind of bugs in jira doesn’t help much……

  142. Sean Heying says:

    From Wikipedia: Release Candidate (

    “The term release candidate refers to a version with potential to be a final product, ready to release unless fatal bugs emerge. In this stage, the product features all designed functionalities and no known showstopper-class bugs. At this phase the product is usually code complete.”

    This is Pre-Alpha and seriously shows that Linden Lab has no QC procedures

  143. Flew says:

    I suggest the Lindens try to play SL on a normal pc for once… do they dont get that with all the new wind/light and dazzle stuff its almost impossible to play anymore? my avarage frame rate is now 2.0 and drops even below 1.0. I want an old simple viewer without all the extra’s (that i didnt asked for in the first place)…maybe then i can finaly build,script and make new products again. Only the happy few with new fast computers can still play SL normaly…most others has major problems trying to play SL.

    Im really thinking about cashing out and never play SL again :/

  144. Adamas Carter says:

    I only used it for a few minutes, so I don’t know if the crashing is fixed, but this is still laggy as *expletive deleted*!

    The interface is nice, though. Would it be possible to graft the color scheme onto the release version?

  145. Raven Primeau says:

    Well it’s the first of the ugdated 1.20 RCs that hasnt given me problems so far, saying thar I never had to do any of the things ppl seem to have problems with.

    It just never crashed during my breakfast fix of SL this morning GMT I know the concurrent users was low, things loaded quickly and smoothly but I will reserve judgement till tonight when I can give it a more thorough test.

    To me the trouble is that LL seem to be working on everything at once so pinning problems down must be incredibly difficult.

    will watch the final posts with interest especially the ppl who are leaving/left/outta here but still posting

  146. It’s a Release CANDIDATE, not a beta test version, IN all normal software development processes the release candidate is a version, that full fills “This versions is a good and tested that we think it can go main release without changes.”
    LL have also several timed changed a RC to main viewer with out changes (some recent times in despite that the feedback from the user community been there is still some major issued needing to be fixed.) Release candidate are supposed to be as stable as released software, when that isn’t it’s a sign on the internal test process is broken.

    / ❤ from Nad

    (( If I been test leader at LL:
    The recommendations from test would have been NOT ready
    for release on 1.19.1RC4 and 1.20.0RC3
    I would also had hoped to say that windlight and dazzle
    projects both had to small goals to go into suer drop. Both
    projetcs missed some essential user requirement to make
    good stand alone drops to the user community. They needed
    both to be bigger projects, maybe that would have needed some
    changes in time plan i can’t say.

  147. Ivantwin Rogers says:

    I don’t care if second life have some errors, the release candidate is a pre release, and that is no a official program

    I love Second Life forever!!

  148. TheBlack Box says:

    VWR-2404 is NOT fixed.


  149. Darling Brody says:

    I am not a casual user of SL, I am in-world for 10+ hours a day and I must say I hate the new colours… HATE HATE HATE.

    You need to have a thick dark frame between the viewer controls and the world to make it easy to focus on what is going in-world without the controls grabbing your attention. This is why a TV set has a black band around the edge of the picture tube to frame the picture and why the old viewer with the dark borders around controls was so nice to use. The viewer controls are too close to the sky colours, it makes my eyes hurt!

    Also windows like Inventory are transparent even when selected. This makes it hard to focus on the inventory list while there are background objects showing through.

    Please revisit your class in Screen Design 101 !!!

    Darling (my eyes hurt) Brody.

  150. Kugel says:

    HAHA… install.. run.. appearances …. CRASH .. .ROFLMAO

Comments are closed.