Whirly Fizzle

Prokofy Neva wrote: I personally find it criminal that Firestorm overrides certain group rules set in the Second Life regular viewer. What group rules does Firestorm override? Proof please! Prokofy Neva wrote: Here's a difference I see with my customers: 1. Those with Firestorm have to relog to make any change in their group membership or powers "take". That's annoying. 2. Those with the SL viewer just make the change during the same session without relogging. Nope, again not true. Whether the user is on the LL viewer, Firestorm, or any other viewer, if the user is added to a new role or their role is given extra abilities, you need to relog to aquire those extra abilities in the group. It has been this way for years. It's a pain in neck but it is not specific to Firestorm.

That's the new Maintenance-RC viewer you are using. Do you have the same problem when using the default release viewer from https://secondlife.com/support/downloads/ ? If this only happens on the Maintenance-RC viewer, can you go to Help -> About Second Life, click the "Copy to clipboard" button & paste all your system information into a comment here.

The FOUNDER of the group could submit a support ticket requesting that the group gets disbanded. It would have to be the group founder that did this, not just a group owner. I have no idea if LL would disband the group in this case but it's worth a shot.

Invisiprims are broken on the latest LL viewer release, see BUG-11562 - SL Viewer 4.0.2 Renders Invisiprims as Grey or Black. That bug is fixed on the new Maintenance-RC, which you can download here: http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/4.0.4.313759 BUT you need to be aware that anyone on any viewer will not see your invisiprims working if they have Advanced Lighting model enabled in their viewer - so they are likely to see your feet/legs sticking out of the shoes/boots. If the shoes are mod, best thing you can do is unlink the invisiprims and delete them and replace them with alpha layers.

Melody Frostwych wrote: Tried Re-installing Firestorm...no luck. Managed to work my way into Preferences and on the General tab, changed something from Russki to Angliski, but still no change. Did you relog after changing the UI language back to English? It needs a relog.

Avatar physics appearance varies greatly with the FPS of the observer. There is unfortunately nothing you can do aboiut that. Bug reports: LL viewer: VWR-25545 - Avatar Physics' calculation needs to be improved Firestorm viewer: FIRE-12386 - Avatar Physics' calculation needs to be improved

Use the beta search with search term "fitted mesh" NOT applier

What happens when you try to TP there? Do you get an error message?

It's a nasty Mac specific bug on CEF enabled viewers. It doesn't affect all Mac systems but for those it does affect there doesn't appear to be a workaround yet apart from to use an older viewer that hasn't updated with CEF. Details: LL JIRA: BUG-11592 - Internal Error: Uncaught Exception is raised whenever these keys are pressed/released: _shift_, _command_, _option_, _control_, or _caps lock_. Can continue but exception is raised continually with these keys. Other keys appear to be fine. Firestorm JIRA: FIRE-18016

Vulpinus wrote: This is weird - is it normal? If it is, I'll go away and stop bothering people, but it really feels wrong and has for ages. At times I can get the thrashing started just by TP'ing from my build platform down to ground level at home. The double-click TP trick stops it every time. It sounds like something isn't right to me. If you can PM me your home location and that store location you are using for testing please. I'm going to see if I can reproduce it. If not, we can get a JIRA issue from you & get logs & do some digging.

It's a bug. See BUG-11602 - When I hold down left click mouse button in M view, my view freezes instead of pans with a hand and a lock in middle or a circle and a slash The bug appears to have been caused by the fix for SVC-7532 This bug happens when wearing a scripted object which uses llTakeControls in a certain way. Your weapon may do this, in which case there is no current workaround for this bug apart from to use an earlier viewer version. It may also be an AO or another scripted attachment triggering the bug though, so detach all attachments & wear the weapon & see if you can then shoot normally. A lot of the Akeyo AO's will trigger this bug so if you are wearing one, remove it.

BillyBuckaroo wrote: ....but the problem we seem to be having is the Objects tab in the About Land properties don't seem to be detecting their prims properly. Is this group owned land? If the land is owned by Group A, Do you have the 'return group owned objects' power in Group A? Do you have the 'return group set objects' power in Group A? Do you have the 'return non-group objects' power in Group A? If you do not have all these abilities, you will not be able to see all objects in the object list. You will only be able to see the objects in the list that you have return powers for.

In the top menu bar of the viewer, go to Communicate -> Block List If you accidently clicked Block on the script dialogs from the animating objects, the objects should show in your block list. Right click each blocked object -> Unblock. Does that help?

I'm afraid you are out of luck running any SL viewer on Windows 10 on a system with Mobile Intel® 4 Series Express Chipset graphics. If you need to use this system for Second Life, the only option is to roll back to your previous version of Windows.

Shisame wrote: Did I do that right? And I am not sure if I have dual graphics or what. I am completely new to all this and have no idea what I'm doing, which isn't good considering that I do intend on being a long time user of Second Life. Perfect thanks. Ok so you have Intel® HD Graphics 520, which is affected by that bug. Your currently installed graphics driver version is 10.18.0015.4279 - that driver does have the flashing bug. The flashing bug was fixed with driver version 20.19.15.4352. Hopefully that laptop doesn't have locked OEM drivers, so you can update directl from intel. The latest driver for your card is this one: https://downloadcenter.intel.com/download/25818/Intel-Graphics-Driver-for-Windows-7-8-1-10-15-40-?product=88355 Download & install that driver. If you are not sure if that's the correct driver for your card, you can use the Intel driver update utility to find the latest driver. Once that's done, check that the flashing is fixed. It looks like that laptop may also have an Nvidia graphics card - NVIDIA GeForce 940M Right click the windows start button -> Device manager. Expand the "Display Adapters" section. Do you see an Intel and an Nvidia card listed there?

In addition to what's already been said, if you have Nvidia graphics, make sure that ShadowPlay is not enabled in GeForce Experience. That will frequently cause a crash during that stage of launch. Ref: https://jira.secondlife.com/browse/BUG-11530

Vulpinus wrote: To me it seems like there is an issue with Firestorm (maybe LL viewer too - I don't use it) that causes this thrashing when TP'ing somewhere new. There is clearly a link between the thrashing and TP'ing; it has happened too often not to be. That's not suprising that the texture thrashing will start after a TP into a new area. Texture thrashing generally happens when you have run out of texture memory, so movng to a new area with lots of new textures can easily tip you over the edge. Vulpinus wrote: The odd thing is that when it happens, I have found that doing a quick double-click-on-the-ground TP stops the texture thrashing immediately. I mean just TP'ing a few meters, not out of the region or anything like that. This has been going on repeatedly for months, with the quick TP fix working (I think) every time. Before that I was TP'ing out of the region or just relogging to stop the thrashing. Hmm that's really quite strange a double click TP would fix it. It doesn't fix it for me - I lowered texture memory to 64MB to kick off texture thrashing & double click TP close by didn't change anything. When textures are thrashing though, whatever texture your mouse hovers over will have loading priority and should sharpen, so whatever object you double clicked on will sharpen, but nearby textures are still thrashing for me. There is some discussion about the texture thrashing problem on https://jira.secondlife.com/browse/BUG-2514 and on Torley's feed: https://my.secondlife.com/torley.linden/posts/5440cf6176286532390000ad If you look in your texture console when you see the texture thrashing, is the bias stuck at 5? After you double click TP, does the bias drop under 5? You can access the texture console under Develop -> Consoles -> Texture Console. There is an explanation about how to read the texture console here: http://wiki.secondlife.com/wiki/Texture_Console

If you have AMD graphics, you may be seeing this bug BUG-7947 - selection outlines display wrongly when ALM is enabled

Updating to the latest Intel drivers will fix this. If you don't know which driver to get, go to Help -> About Firestorm, click the "Copy to clipboard" button & paste all your system information here. Also, does your new laptop have dual grapgics? If so, you don't want to running with the Intel graphics anyway.

What graphics card do you have? Some really old cards like the Mobile Intel® 4 Series Express Chipset cannot run any SL viewers on a Windows 10 system, even with the latest drivers.

Can you give the exact login failure message you are seeing? Is it this one? Unable to connect to Second Life.Often this means that your computer's clock is set incorrectly.Please go to Control Panels and make sure the time and dateare set correctly.

That problem is a much older issue - see SVC-7129 - Attachments to group notices malfunction after some time The server used to time out group notice attachments after one hour and this was recently raised to 24 hours in October 2015 This helped but still did not totally fix the problem.

JohnCrooner wrote: That's the version I got when I hit download on the main page. I'm on an older OS (10.7.5) Thats probably why. Any suggestions or do I need to upgrade my OS to test??? Can you go to Help -> About Second Life, click the "Copy to clipboard" button & paste all your system information in here.

Usually this problem is a region issue. If you login directly to a different region, does that fix the problem? If so, the affected region needs to be restarted. Details here: https://jira.secondlife.com/browse/BUG-7557

The only problem I know of currently with Nvidia is when ShadowPlay is enabled in GeForce Experience. On Windows 10 systems only (though it seems ALL Win 10 systems are affected), all SL viewers are highly likely to crash during launch and if you do manage to get past login, the viewer again has a 90% chance of crashing when you go to Help -> About or Help -> File a bug. JIRA issue for that crash is at BUG-11530 - Viewer crashes in nvwgf2umx.dll or nvwgf2um.dll when Nvidia ShadowPlay is enabled when opening Help -> Report bug, Help -> About, & sometimes when detecting hardware during launch Nyll Bergbahn wrote: I see a number of OEMs are now installing Raptr as standard on new machines. Why is Second Life so badly affected? It isn't just SL viewers. There's countless threads on various games forums where Shadowplay. Raptr or other "game overlay" type software is causing game crashes. This kind of software has always been a PITA. Example: PSA: Game no launching or is crashing? Try disabling Raptr. Another one causing problems is Asus ROG Gamefirst software. That's particularly nasty - it can cause a BSOD as soon as an SL viewer is launched - it doesn't even get to the login screen. Faulting program is: AsusGameFirstS Faulting IP is: NETIO!StreamInvokeCalloutAndNormalizeAction+60 From the system dumps I've seen from users it appears to be caused by nfc_driver.sys (Network Flow Control SDK WFP Driver (WPP)) which is bundled with the Gamefirst software. Disabling Gamefirst gives an instant fix. Full bugcheck for the Gamefirst crash: http://pastebin.com/UbePfWMM