[sldev] This is no Place for a Rant!

[Nik Radford]

Lol,

Honestly, I don't know what the healthy number for inventory is, as 
no-one has ever announced one. However I have noticed that those who 
complain about inventory loss are those with (in my opinion) a very 
large inventory.

The dynamic shadows branch has also been around for about 6 months! So 
yes the linden in question could of been very busy in his lunch hour, or 
on his free time at home. He perhaps loves writing shaders and graphics 
code and thus finds it fun and so devotes alot of his spare time to the 
shadow experiment!

And as far as I'm aware. Shadows haven't even been announced for the 
main branch, or that they are ever going to make it into the main client 
at all. It's just one linden having a bit of fun seeing what he could do.

Will wrote:
> oops looks like someone has been busy on their lunch hour ...btw pick 
> a healthy number for amount of inventory and then keep it a secret ....
>
>
> ----- Original Message ----- From: <admin at terminaldischarge.net>
> To: "Will" <wdemauro at verizon.net>
> Sent: Monday, February 02, 2009 10:55 AM
> Subject: Re: [sldev] This is no Place for a Rant!
>
>
>> Most of the time, inventory loss isn't due to the items disappearing, 
>> but
>> the items never getting loaded into your inventory by the client. Large
>> inventory sizes suffer most from this problem I do believe. Sometimes
>> item's will be in your inventory and other times they won't.
>>
>> Time to clear down your inventory me thinks. Then clear you cache!
>>
>> the reason they ask you to clear your cache, is so it forces your client
>> to re-download data rather than using data it's already gathered on your
>> hard-drive.
>>
>> As for Dynamic Shadows, I believe that's still only one lindens pet
>> project is it not? I haven't been able to find an RC or FirstLook viewer
>> that contains the shadows. Moaning about a single linden working on
>> Dynamic Shadows is like moaning about me working on my website in my 
>> lunch
>> break at work!
>>
>> Jesubs people.
>>
>>> Loss? We Don't Have No Stinking Loss
>>> -------------------------------------------------------------------------------- 
>>>
>>>
>>> For over a month when I log on my inventory is a crap shoot ... it 
>>> floats
>>> between 1k and 5k short of what it should be. Finally had enough and 
>>> spent
>>> the required 4+ hours in live chat, "yes I'll clear cache" "yes I'll go
>>> someplace quiet" "oh no problems with my network connection- that's so
>>> good
>>> to know" then I'm told to take everything off and clear cache again and
>>> relog ... ok .. ok so I put everything I'm wearing, huds hair jewelry
>>> shirt
>>> shoes etc into a new folder in a "clothing emergency" folder ... god 
>>> damn
>>> don't you know it disappeared!!!!! honest to god - huds hair jewelry 
>>> all
>>> gone - not an effing trace..... wait, there is a trace- three live help
>>> people can "see" the missing items but can't do a bloody thing!!!
>>>
>>> OK! live chat has run out of stuff they can do so it's on to a support
>>> ticket, go into great detail what has been covered, include the 4+ 
>>> hours
>>> of
>>> chat (bulk of it was having me relog all over creation) wait the 48 
>>> hours
>>> and get a form email extolling the virtues of clearing cache and 
>>> relogging
>>> in a quiet area.
>>>
>>> One odd thing- a $50 usd sexgen bed unit that disappeared over a 
>>> year ago
>>> came back- so much for that round of live help back then that "couldn't
>>> see
>>> it" (don't judge me)
>>>
>>> Forget memory leaks and stability issues ... inventory volatility - 
>>> isn't
>>> it
>>> about time for dynamic shadows?
>>>
>>> _______________________________________________
>>> Policies and (un)subscribe information available here:
>>> http://wiki.secondlife.com/wiki/SLDev
>>> Please read the policies before posting to keep unmoderated posting
>>> privileges
>>>
>>
>>
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>

-------------- next part --------------
Skipped content of type multipart/related