Whirly Fizzle

Be wary of the Raptr In-Game Overlay too. This causes frequent viewer crashes (all viewers) - stack will show the crash is in ltc_game64-111020.dll.

Are you using a really outdated link still pointing at https://www.xstreetsl.com/ ? If so then Firefox will give that warning http://www.xstreetsl.com/ will still redirect to https://marketplace.secondlife.com/ https://marketplace.secondlife.com/ is the link you should be using now for the Marketplace.

You may want to join in the fun over here ----> https://community.secondlife.com/t5/General-Discussion-Forum/Security-orb-height-limits-needs-to-be-capped/m-p/3015899 :smileywink:

Honestly, if you rez a no copy object and rez fails with that "Cannot create requested inventory" error, it's gone. You lost gacha objects which I presume will have been no copy. There is a viewer bug that causes no copy objects which fail to rez for certain reasons (no rez rights, rezzing ontop of mesh etc...) to not display back in inventory until you relog, but for this particular "Cannot create requested inventory" rez fail, no copy objects appear to be always lost for good.

@NigelKent What version of Firestorm are you using? Go to Help -> About Firestorm & copy the exact viewer version listed there.

4.0.1 is a pretty old viewer build so it's strange you were updated to that version. Do you have the same problem after updating to the latest viewer version from https://secondlife.com/support/downloads/ ?

Totally off topic but has anyone else noticed lately that tags will be added to posts that you didn't add a tag for? It just did it to me again on my last reply here & I can't work out why.

Can you go to Help -> About Second Life, click the "Copy to clipboard" button & paste your system info into a comment here.

"Romantica Island" also has the "Estate / Full Region - Buy Down". That region has been there a long time & it's also owned by one of the large estates.

From any region, if you dump caps to log (Develop -> Consoles -> Capabilities info to debug console) & poke in the session log for the ProductInfoRequest URL, you can pull a list of all those region flags. C:\Users\Whirly> curl -sk https://sim8922.agni.lindenlab.com:12043/cap/38e04b90-f6b9-c33b-d71a-83740d30be62 | xmllint -format -<?xml version="1.0"?><llsd> <array> <map> <key>description</key> <string>Mainland / Full Region</string> <key>name</key> <string>mainland_full</string> <key>sku</key> <string>023</string> </map> <map> <key>description</key> <string>Estate / Full Region</string> <key>name</key> <string>estate_full</string> <key>sku</key> <string>024</string> </map> <map> <key>description</key> <string>Estate / Openspace</string> <key>name</key> <string>estate_openspace</string> <key>sku</key> <string>027</string> </map> <map> <key>description</key> <string>Grandfathered / Homestead</string> <key>name</key> <string>estate_homestead_pre20090701</string> <key>sku</key> <string>029</string> </map> <map> <key>description</key> <string>Estate / Full Region - Developed</string> <key>name</key> <string>developed_estate_full</string> <key>sku</key> <string>121</string> </map> <map> <key>description</key> <string>Estate / Homestead - Developed</string> <key>name</key> <string>developed_estate_homestead</string> <key>sku</key> <string>123</string> </map> <map> <key>description</key> <string>Estate / Openspace - Developed</string> <key>name</key> <string>developed_estate_openspace</string> <key>sku</key> <string>125</string> </map> <map> <key>description</key> <string>Mainland / Openspace</string> <key>name</key> <string>mainland_openspace</string> <key>sku</key> <string>127</string> </map> <map> <key>description</key> <string>Mainland / Homestead</string> <key>name</key> <string>mainland_homestead</string> <key>sku</key> <string>129</string> </map> <map> <key>description</key> <string>Linden Homes / Full Region</string> <key>name</key> <string>linden_homes</string> <key>sku</key> <string>131</string> </map> <map> <key>description</key> <string>Estate / Full Region - Skill Gaming</string> <key>name</key> <string>gaming_estate_full</string> <key>sku</key> <string>141</string> </map> <map> <key>description</key> <string>Grandfathered / Full Region</string> <key>name</key> <string>estate_full_grandfathered</string> <key>sku</key> <string>224</string> </map> <map> <key>description</key> <string>Estate / Homestead</string> <key>name</key> <string>estate_homestead</string> <key>sku</key> <string>229</string> </map> <map> <key>description</key> <string>Estate / Full Region - Buy Down</string> <key>name</key> <string>estate_full_buydown</string> <key>sku</key> <string>324</string> </map> <map> <key>description</key> <string>Estate / Homestead - Buy Down</string> <key>name</key> <string>estate_homestead_buydown</string> <key>sku</key> <string>329</string> </map> </array></llsd> So hmm, doesn't appear to be anything to do with a Grandfathered region, that will display as "Grandfathered / Full Region".

I've never seen that before & no idea what it means. I see the same on that region though. If I had to guess, I'd say it meant the region was grandfathered or was on some other special reduced tier rate.

Pat Mendes wrote: Did anybody had similar problems ? How can this be fixed ? Yeah this pops up sometimes - for example see BUG-11548 - Cannot see friend's feed since 8 March 2016 The cause of that particular case was some corrupted data in my.secondlife.com for the affected accounts. I think the best thing to do for this particular issue is to go through JIRA, rather then support. File a JIRA issue in the BUG project here

If your whole system is crashing, you need to dig into the windows crash data to find the cause. BlueScreenView is a nice program which is very easy to use, however it won't give you all the information. My personal preference is to look at the complete/kernal dump (rather then the minidump) using WinDBG which is part of the debugging tools for Windows. If you don't want to attempt that yourself, I can do it for you if you can put the dump files onto Google drive or dropbox or similar. Do you have a file named MEMORY.DMP file located in C:\Windows\ ? If so, zip that up & upload it to Google drive or similar. If you don't want to put the link here, you can send it in a PM.

Vulpinus wrote: Whirly, I've been seeing this for a few days too. You asked a question on the JIRA regarding folders appearing in the Lost&Found that should not be there - I got loads of them there today after having to clear my cache again to regain last night's Aditi work. This needs a fix ASAP - I log into each grid several times a day! Thanks. I added your comment to the JIRA issue.

I can absolutely guarantee my ARs go into the same black hole as everyone elses :smileytongue:

Pamela Galli wrote: Ah, yes I had been conflating them. In any case they are notorious. Except of course LL seems not to be aware. I really don't know the best thing to do about this. It's just crazy though. So many people are losing money & those items are not cheap. Is it ARable for Fraud -> L$?

You may want to take a look at https://community.secondlife.com/t5/General-Discussion-Forum/vendor-not-give-item/m-p/3018303

I'll bet L$100 this person was bitten by the same vendor too - https://community.secondlife.com/t5/Shopping/I-have-recently-purchased-two-items-from-a-dance-Vendor-an/qaq-p/3018211

Vir Linden wrote: Whirly - thanks for checking. I updated the links on the bento testing page to point to copies that are hopefully public. Please let me know if it's still giving you problems. Fixed thanks!

Really doubt it's viewer related, it's happened to me several times on the latest LL viewer & latest Firestorm. It sniffs of either backend asset or inventory server problems or LL have possibly started making backend changes in preparation for the inventory deprecation project (ref 1 , ref 2) & something has gone wrong.

Vir Linden wrote: There are two mesh models available that can be used with the sliders - see http://wiki.secondlife.com/wiki/Project_Bento_Testing for current information on supported models. Can you attach those dae to BUG-10981 please. Links are restricted to Lindens only.

Qie Niangao wrote: Jessica Lyon wrote: Once we have the new RegAPI LL will disable the forced Land Scope Experience. It's temporary and it's for the sake of new residents joining SL. That's interesting, too. Community Gateways won't use Experiences in conjunction with the new RegAPI? I haven't been following it at all, so it's no surprise I'm clueless, but this isn't what I'd expected RegAPI would be about. Basically the problem is that the current RegAPI does not yet have the ability to enable an experience on the fly for the new residents coming through the Gateway. So new resis would have to accept the experience in the usual manner. Many were failing to do this and then having problems with the parts of the orientation that required the experience to work. LL are currently working on a new RegAPI for the Gateway program which will have the Firestorm experience enabled for all new accounts entering through the Gateway. Until the new RegAPI is in use (it's in QA now), the temporary solution was to configure the Firestorm experience so that it gets enabled on the fly without needing to accept it, for anyone who lands on the Gateway regions. For anyone who is curious, you can see how the experience is used on the orientation region (access is limited to new accounts) by creating an alt account with the RegAPI on one of these Firestorm Gateway landing pages: Roleplay Decorating Socializing Exploring Creating Music

Qie Niangao wrote: But as I read tother responses, now I'm not sure whether I understand what Jessica meant. I'm finding this confusing, and I've been scripting with Experiences since they started beta. I can't get in-world to test Linden Realms just now, but it would be interesting to know whether those, too, behave in some different way, as you suggest. Qie, see BUG-11109 Those example experiences are set up in the same way as the Firestorm Experience in that they are enabled for all residents and cannot be forgotten or blocked. These type of experiences can be land scope or grid scope. Only LL have the power to set an experience to behave in this way and they did this for the Firestorm experience as part of the ongoing Gateway testing and to work around a temporary problem with the RegAPI.

SosiaalinenKokeilu wrote: ...its your duty to explain whats going on and why. Not let them find out their trust is being abused. How is your trust being abused? Has the Firestorm experience done anything bad to your avatar while you were on Firestorm owned land?

SosiaalinenKokeilu wrote: Is it really so hard to put these things in your release notes say? v4.7.7 We're forcing everyone into Experience Firestorm, just an FYI. It has nothing to do with Firestorm viewer as such so it doesn't belong in the 4.7.7 release notes. There is no magic in the Firestorm viewer code that forces anyone into the Firestorm gateway experience. No matter which viewer you are on, if you go to one of the Firestorm regions you will have the "Experience Firestorm" enabled. The magic is all LL magic in the way that experience is configured. This experience behaves in exactly the same way for everyone, no matter which viewer you use. Just to stress again, "Experience Firestorm" is NOT a grid-scope experience, it is land-scope only. The experience will only work over Firestorm owned land.