Cool VL Viewer forum

While it is not Cool VL Viewer specific, it will affect users of this viewer:

After removing the classic clouds support from their viewer, LL is now going to remove them from their server, meaning even the residents using viewers that are able to render them will soon not see them any more !

The Cool VL Viewer (in which you can even adjust the altitude of the classic clouds: something that would be easy to implement in other viewers as well) and Singularity for the actively maintained viewers, plus all “deprecated” viewers, at least up to v2.7 *cannot* render them in RC Magnum already.

I filed a bug report (https://jira.secondlife.com/browse/BUG-1456) but Maestro Linden closed it as “expected behavior”. I’d suggest that anyone interested in classic clouds (which I find way prettier and realistic than Windlight clouds) also file BUG reports on the JIRA to let LL know that we still want classic clouds in our SL experience !

See also the related topic on SL's forum (you could petition there too, I suppose).

Done!

I wouldn't expect anything, though. There have been countless petitions to bring back last names and they fell on deaf ears. (I hate this ¨Resident” business.)

Im thinking it was just one of those had to happen if lag is going to come down or something depressing like that.
Its been going to happen for a long time now and though its sad its been done reasonably sensitively and slowly compared to many lab things. For me it doesnt begin to compare to the importance of the names debacle, where they threw away one the most addictive things about SL chasing clients outside their niche who in my opinion were never going to stay.
http://wiki.secondlife.com/wiki/Viewer_ ... 2011-05-06
08:28 Oz Linden but as I said, they are essentially just a particle effect, and our thought is to package that effect as a generator you can pick up and place as needed

It's amusing to see how Oz can lie... Windlight clouds are waaaaay more impacting on the frame rate than classic clouds !... You can easily test this by yourself. As for the server-side lag, all they had to do is to make classic clouds optional (i.e. if the user want them, their viewer sends a capability request that is used by the server to flag that user's viewer as requiring classic cloud update packets) and/or to reduce the frequency of the classic clouds update packets.