1.22 RC9 - Now available

The 10 th iteration is out now:

Release Notes for Second Life 1.22(9) - February 12th, 2009
Bug Fixes:

Fixed VWR-11780[c]: Texture Memory cannot be set lower than 128Mb
Fixed: GStreamer crashing issue

Bug Fixes from the Public Nightly Viewers:

Fixed VWR-11910[c]: SLVoice crashed when using RC8
Fixed VWR-11828[c]: Sculpts either load extremely slowly or fail to load altogether
Fixed VWR-11736[c]: Raycast picking: Prim with one transparent face does not allow click on the inside of the prim
Fixed: Issue with voice chat presence being misreported by the Vivox SDK

Localization Fixes:

Fixed: Truncated Japanese text


... and I mentioned it before the Linden's

The tenth iteration of the 1.22 Viewer, Release Candidate (RC) 9, has been released!

If you've been using RC8, you will be required to update to RC9, which may be installed along side the official 1.21 viewer. Please keep in mind that participation in the viewer Release Candidate cycle is entirely optional.

RC9 includes some voice-related fixes, a fix for slow sculpt loading, and a new raycast fix. As always, complete release notes can be found at:

http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release_Candidate/1.22

Though we feel we're very close to the official 1.22 viewer (r-e-a-l-l-y soon!), we still need your help to find crash cases and provide essential feedback. So, please download the Release Candidate from the URL below and start experimenting:

http://secondlife.com/support/downloads.php#download-Testviewers

Don't forget to report new issues at jira.secondlife.com - and be sure to set the “Affects Version/s” to “1.22 Release Candidate”. Before you log new issues, please review the Release Notes to see if there are already open issues to which you can add comments. Remember... we're only able to investigate bugs that are reported in JIRA.

Not your fault, Ramzi - with the databases going wakkawakkawakka because they feel so violated after getting "maintained" I'm sure even a viewer code guru like yourself would be involved in the wtf??? brainstorming. I think you can be forgiven for a little inattention to the forums under the circumstances

Of course theres always the OTHER possibility, that the deployment folks put it out there and omitted the "Notify Ramzi" task from their change control request but lets not go there, ok ?

it's rezzing very fast and fps are great but definitely crashes me within max 5 minutes after caming thru a high end graphics sims. tested 5 times, same result.
it used only ~600mb when crashing which is great, but yeah, back to my working viewer.

(edit: had those gesture and object rez errors too)

Second Life 1.22.9 (110075) Feb 10 2009 12:43:24 (slrc)
Release Notes

You are at 256924.6, 301743.1, 3604.6 in INSILICO located at sim3040.agni.lindenlab.com (216.82.20.29:12035)
Second Life Server 1.25.5.109327
Release Notes

CPU: Intel Core 2 Series Processor (2708 MHz)
Memory: 2048 MB
OS Version: Microsoft Windows XP Service Pack 2 (Build 2600)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 9600 GT/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
Audio Driver Version: FMOD version 3.740000
LLMozLib Version: [LLMediaImplLLMozLib] - 2.01.21721 (Mozilla GRE version 1.8.1.13_0000000000)
Packets Lost: 0/2344 (0.0%)

Yeah, I'm getting gesture load errors, then crash 5 mins later. So, I deleted all my gestures, and it gets a "cannot rez object" even though I didn't rez anything, then crash.

The land in the distance has light blue patches as I fly along.

I was seeing gesture load errors and random bulk crashiness last night while still in RC8. A few events of "Sorry, I just crashed." "Don't worry, me too." Events lately. Can't say I can blame the client just yet. (>_<

Meethinks network issues at the lab and some server-side naughtiness that came with 1.25.x are the sources of some of these problems. (>_<

hey!

slviewer 1.22.RC9 :
downloaded
installed
logged in
sim rezzed
opened fast timer -> pump spikes at ~500ms
random freezes
viewer crash
all sl files damaged
i have had to reinstall viewer 1.20.17 - the last working version for me

You are at 235597.6, 299435.7, 27.4 in xtropia located at sim7904.agni.lindenlab.com (8.10.148.143:13000)
Second Life Server 1.25.5.109327

CPU: Dual i386 (Unknown) (2000 MHz)
Memory: 1024 MB
OS Version: Darwin 8.11.1 Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386 i386
Graphics Card Vendor: ATI Technologies Inc.
Graphics Card: ATI Radeon X1600 OpenGL Engine
OpenGL Version: 2.0 ATI-1.4.56
LLMozLib Version: [LLMediaImplLLMozLib] - 2.01.21723 (Mozilla GRE version 1.8.1.13_0000000000)
Packets Lost: 8/11384 (0.1%)

pumpbug still exists with this version
http://jira.secondlife.com/browse/VWR-11692

The new RC has been working sweet for me. Fastest image and sculpts loads ever. Been jumping around to high texture sims like Bare Roses and working smooth.
No lock ups, no SLVoice crashes, I would say pack it and ship it.

:/ Here we go again

Interesting; I have a similar one, since quite a while (might even be before 1.22): you only see the attachments of an avatar, but not the ava himself. To fix that, you need to move the camera _very_ close to that ava (or just run into him .

Hmm, now a good bit of the land at the Ahern WA has tuned into flashing colors, flat colors flashing blue and pink and teal and so on.



How delightful.

Perhaps it's Dazzle II.

modern art Looks a bit like "RENDER_DEFERRED" on a Pixel-Shader 3-GPU, but then all textures have that color..

I've had that issue for as long as I can remember, well into last year. Does it just do it for land in the distance or also water void areas (no sims) too? Either way it's always in the distance and in square blocks.

CPU: Intel Core 2 Series Processor (2400 MHz)
Memory: 6142 MB
OS Version: Professional (Build 7000)
Graphics Card Vendor: ATI Technologies Inc.
Graphics Card: ATI Radeon HD 3870 X2
OpenGL Version: 2.1.8395 Release

/me too. I always figured it was just some "don't know what to draw here!" weirdness.

CPU: AMD (Unknown model) (2611 MHz)
Memory: 2048 MB
OS Version: Microsoft Windows XP Service Pack 2 (Build 2600)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 9800 GT/PCI/SSE2/3DNOW!
OpenGL Version: 2.1.2

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

Came in with 1.20 see Jira here:

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

I've just updated my overlay ebuild to 1.22.9 for the gentoo users out there.

http://overlay.techwolf.net/

I was more than happy with RC 22.8 and had no issues with it at all, but since I swapped up to RC9 I've noticed a significant increase in texture loading time, and it's twice crashed completely on trying to move camera round in a texture-heavy environment. This is significant - I don't actually remember the last time I had a client crash. Certainly not within the last half-dozen installs of the RC.

CPU: Intel Pentium 4 (Unknown model) (3059 MHz)
Memory: 2047 MB
OS Version: Microsoft Windows XP Service Pack 3 (Build 2600)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 8600 GT/PCI/SSE2
OpenGL Version: 2.1.2

*wants RC22.8 back - and in the meantime is switching to Kirsten Lee viewer*

1.22.9.0 R1 CV (Windows) is up for grabs

Looks like someone wearing a megaprim to me.

Originally posted in wrong forum... Ooops.




I need to ask a fairly dim question

As I see it, these BETA versions we are trying are really just tweaking and fiddling with things, the odd bug fixes, clean up's and tweaks.

To be honest, I've been running the BEAT for the last 3 or 4 revisions of it, and to be 100% honest, I'd not even know I was running the Bets as it seems to perforrm, look and function (for me) exactly the same as the official current release.

Perhaps I'm lucky, but I've not seen any of the bad graphical glitches posted about on these forums.

So, do I therefore take it, that when this Beta version is "ready" so to speak, this is going to be the new Release version?

Meaning, we're not actually going to get anything "New" in way of features at all?

Or, are the "New Features" part of SL programming done by a different team/dept than the Beta bug/fix people and we will actually see new things appear?

I know many just want bugs fixed and nothing else, but there are so many things screaming out to be tweaked/enhanced. I guess I'm hoping each version will bring obvious improvements to some things, rather than just bug fix's (which are of course great) but nothing to actually see that's new.

Dear Mr. Linden...

Maybe my reply is a bit off-toppic but I'm often helping users who 'aren't that good with computers'. Not surprisingly people tend to choose their computer based on it's prizetag and don't pay much attention to video capabilities...
A sad but unfortunately common example:

* System: HP Compaq Presario CQ70 Notebook PC ............... Oh boy!
Intel(R) Pentium(R) Dual CPU T3400 @ 2x1.2Ghz .................... Hmmmmm...
3Gb RAM / MS Windows Vista Basic (SP1) ............................... Tha HORROR!
* Video: Intel Cartiga / 1440x900px, 32bpp (60Hz) / 1309Mb .... Intel Cawhah...?!?

To make it even worse(!) Mobile Intel® 4 Series Express Chipset Family driver 7.15.10.1608 (latest), wich STILL has issues with its 1440x900 mode wich makes Windows Vista restart the driver leaving the SL-viewer completely paralized in many cases, full screen or not doesn't seem to matter! This event i noticed myself using SL-Viewer < 1.22 RC8, from here the driver seems to respond more stable.

Further examination with 'OpenGL Extensions Viewer' (freeware graphicscardtester (o.O) ?!? found at http://www.realtech-vr.com/glview/) showed it passed OpenGL test 2.1 (2.0 full support, not supported in 2.1: GLSL v1.20 and GL_EXT_texture_sRGB).

This configuration causes the SL-Viewer to use the default lowest settings, many of my 'custommers' are using these settings eversince they bought their new computer and are often amazed when i turned those sliders up, becouse many of 'em don't dare to touch them!

The HP / Intel / Microsoft virus is spreading rapidly! Isn't there realy no way to show a bit compassion towards their restless, victommised users? I think it would be widely appreciated!

Thanks for doin a great job ........ ^x^ ...... no problems with RC9 so far!

Could be.

However it occurred right after seeing the light blue land in the distance everywhere as I fly along, along with light blue "trim" on sim borders, so it looked like a variation of that.

The light blue all over the place is bad enough on it's own. Couple that with gray textures and deformed sculpties and going places is not much fun.

I've always seen that, you never noticed it before? It's caused by gaps between the water level when you have sims with different water levels set. There's several sims like that near Ahern.