Watch this video for an idea as to the significance of the destroyed content.
http://www.youtube.com/watch?v=Cr3_bqlYQwQ That video was posted on http://jira.secondlife.com/browse/VWR-14049 which is pretty obviously a duplicate of http://jira.secondlife.com/browse/VWR-13868 but I'm not closing it since it has more angry people piling in. It is not limited to small art pieces like that necklace and pretty much a lot of period jewelry and outfits. I have heard reports of half of people's stores vanishing causing them to try putting stuff back when the prims are still there. I expect to hear about "phantom prims, and all sort of stuff. No announcement was made about such a catastrophic nuking of Second Life before it was rolled out. There was nothing I saw in release notes indicating LL had elected to destroy content in this manner. Again, as long as rendermaxnodesize is available to be overridden then it is a matter of educating the residents. Or LL could raise the limit to 8192 and most builds would be fine and only people with computers not even qualified to connect to SL would experience impeded frame rates. LL needs to increase the minimum hardware requirements to 2GB and nvidia 8000 or better GPU anyway. ________________________________ From: Tigro Spottystripes <[email protected]> To: Moriz Gupte <[email protected]> Cc: sldev <[email protected]> Sent: Thursday, June 18, 2009 11:34:53 AM Subject: Re: [sldev] Rendering Limits would it be too hard to make things that are above the limit be LOD'ed down gradually, and only start unrendering things when a huge chunk of everything on screen is already at lowest LOD? Also, any such limits should be a slider with a typeable textbox next to it on the graphics tab of the preferences screen IMO. Moriz Gupte escreveu: > I think rendering limits are inevitable, resources tend not to be > unlimited. There will be disagreements regarding rendering > prioritizations/limits ... this is to be expected. Perhaps one > approach would be to see how much pain is inflicted on the community > if a limit is imposed. If most don't even notice it, then it's > probably a proper rendering limitation...which would then qualify as > an 'optimization'. One thing is very helpful though, and think Soft > has done some of it already, is to publish these limitations and how > it impacts rendering (must be easier for LL to initiate that than the > community). *forgive me * if this is published somewhere already, may > be share the link. > > > > On Thu, Jun 18, 2009 at 8:53 AM, Soft<[email protected]> wrote: > >> Try creating a 128x128 sculpted prim, then link 255 of those together >> in a 16x16 grid (remove one to make 255). Then scale them down as far >> as they'll go and wear it like a badge. You should start to see some >> prims in the set vanish. >> >> On Thu, Jun 18, 2009 at 2:59 AM, Ambrosia<[email protected]> wrote: >> >>> This is news to me as well. Rendering limits? Which? I personally have >>> not noticed anything that I might recognize as a new rendering limit? >>> >>> On Wed, Jun 17, 2009 at 16:02, Harleen Gretzky<[email protected]> >>> wrote: >>> >>>> Can you elaborate on what the new rendering limits are? >>>> >> _______________________________________________ >> Policies and (un)subscribe information available here: >> http://wiki.secondlife.com/wiki/SLDev >> Please read the policies before posting to keep unmoderated posting >> privileges >> >> > > > > _______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/SLDev Please read the policies before posting to keep unmoderated posting privileges
_______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/SLDev Please read the policies before posting to keep unmoderated posting privileges
