Whirly Fizzle

What's your budget? I recently got a new Windows 10 laptop with dual graphics. CPU: Intel® Core i7-6700HQ CPU @ 2.60GHz (2591.98 MHz) with Intel® HD Graphics 530 Discrete graphics card: Nvidia GeForce GTX 960M/PCIe/SSE2 SL viewers run really well when using both the onboard Intel graphics and the Nvidia graphics, both handle Ultra graphics setting without any problems. I'm actually really suprised how well the Intel 530 graphics perform on SL - quite shocked even. I was expecting a huge difference in viewer performance when running with the Nvidia card and there really isn't that much of a difference. This is the system I got: http://www.pcspecialist.co.uk/notebooks/optimusVII-17/ Exact specs: http://www.pcspecialist.co.uk/computers-for-next-day-delivery/241/ I got it through Ebuyer though & it was quite a bit cheaper then it would have been buying directly from PC Specialist.

Which viewer are you using? In the top menu bar of the viewer, go to help -> About Second Life / viewer name, click the "Copy to clipboard" button & paste all your system information into a reply here. There may be a clue in your system info about why you are crashing so much (old intel drivers with the known memory leak for example). Really need your viewer logs to see what's causing the crash but lets see what the system info shows first.

Pretty old report from 2012, but see http://radegastclient.proboards.com/thread/61/login-error there is a bug in the code that processes inventory folder names during login. You probably have a folder in your inventory that is all numbers and long, something like 4464133165465141365464.

BarbaraAnnKy5 wrote: As an aside, Firestorm viewer stopped working entirely after Windows 10 update. When I try and launch Firestore i get an error message that says something about video drivers. If only Firestorm (or Alchemy) fails to run since the Win 10 update but the LL viewer runs fine then It's most likely you have Intel HD/2000 or 3000 graphics which wont run on any viewer using the Windows 10 manifest. You can get Firestorm to run if you install the 32bit version (64bit just won't run on Win 10 with those Intel cards) and patch the 32bit install with the "intel fix" - http://wiki.phoenixviewer.com/fs_intel_fix_32bit Also on the LL viewer, you can disable the jellybaby avatars totally by setting Maximum Complexity to "No limit" (far right on the slider) under Me -> Preferences -< Graphics -> Advanced.

Cerise Sorbet wrote: As a fancier plan for frequent grid changes, you might set up viewer shortcuts with different settings files for use with each grid, and tell each to use a different cache directory. That's the best thing to do for now I think. It's a mess. If you clear cache then login to Aditi, which you have to do after a sync has run to get your recently created Aditi assets, then you login to Agni, Agni inventory ends up polluted with Aditi assets which all spit "missing from database", "Cannot create requested inventory" errors. So another cache clear is needed before relogging into Agni. If this automated sync is here to stay, we really need seperate caches for each grid by default.

Try unticking "Enable audio enhancements" - it shows as ticked on your image. That can cause the demon voice problem on Windows 10 with SL voice/

Hmm this should work the way you want on Firestorm Viewer provided you have your Preferences set correctly for that behaviour. Preferences -> Move & View -> Movement -> Pressing letter keys affect movement (ie. WASD) instead of starting local chat Preferences -> Chat -> Typing -> Deselct chat after sending a message / De-focus chat history too. Does that help?

Benson Gravois wrote: I upgraded to the latest version of firestorm annd now whenr ever I go to log in i get this message pop up. "We were unable to decode the file storing your saved login credentials. At this point saving or deleting credentials will erase all those that were previously stored. This may happen when you change network setup. Restarting the viewer with previous network configuration may help recovering your saved login credentials." Anyone know what this means or how I can fix it? Thankyou in advance, you guys are great, Benson That message can happen for various reasons. It can happen if you login over a different network as the messages says but there are other causes. Your login credentials (usernames and passwords) are stored in a file named bin_conf.dat stored in your user_settings folder (located in C:\Users\USERNAME\AppData\Roaming\VIEWER_NAME\user_settings. This file is encrypted & hashed with your system ID/Mac address so it can only be decoded on the system where the file was created. If the viewer cannot decode this file for some reason then you will see that error message at login & the viewer cannot retrieve your stored usernames & passwords. Causesinclude: Change of network Using settings backed up on a different system (though the error will only appear on first session with those settings). Updating OS (eg updating to Windows 10) or any other kind of Windows update which changes the machine ID (some Windows 10 updates will cause this) - but again the error will not happen every session in this case. Outdated root certificates on that system (if there is a problem with CA.pem). Some data written to bin_conf.dat is corrupted & the viewer cannot decode it. Test on the Linden Lab viewer (https://secondlife.com/support/downloads/) & see if the same problem happens. Try renaming your settings folder (Rename Firestorm folder to Firestorm_old) in C:\Users\USERNAME\AppData\Roaming\ If that does not help, you can revert back to old settings by renaming the folder back to Firestorm (or Firestorm_x64 if you are using the 64bit viewer). If you can't work out what's causing it, file a Firestorm JIRA issue and include your log files. Logs should give a good clue what the problem is.

You always sound so angry Steph lol That bug is not fixed yet. If you had bothered to read the comments on that issue, you will see many cases of that bug posted, the latest which was on March 14th 2016. The OPs problem is not with IMs. Their problem is that all their friends show as offline at login. This is usually a region problem and is covered by that bug report.

steph Arnott wrote: IMs are nothing to do with region issues. They can be actually. If a region gets broken in a certain way, any IM you send out from that region to an avatar on a different region will not be received. The filers problem of all contacts showing offline at login is almost certainly going to a case of https://jira.secondlife.com/browse/BUG-7557 It's pretty common for a region to get in this state, usually when it has not been restarted for over a week, but not always. The only way to fix it is with a region restart.

That problem is usually an issue with the region you logged into. A region restart will fix it.

NHC TVs will not work for anyone using a CEF based viewer. They will still work on older viewers using Webkit. This is not something that can be fixed in the viewers. The NHC creator must update their TV to be compatible with CEF. In a nutshell - the NHC TVs use redirects from http to data uri and Google block this because it is a security risk. Full details on https://jira.secondlife.com/browse/BUG-11485

The new Aditi inventory sync went live a few days ago. Main grid inventory is now merged into Aditi inventory. Each day that you login to Aditi, a script will run once a day to merge inventory from main grid to Aditi. There is no opt out, everyone who logged into Aditi will get synced within 24hrs.

ChinRey wrote: SL performance has certainly degraded significantly recently. For a start there seems to be something wrong with the way the latest versions of the viewer handle the texture cache. One thing I've never ever noticed before is that my avatar doesn't even show up as a white cloud right after startup. It takes a while before the texture for the could aprticles load so at first I show up as a mass of swirling grayish squares. Same with the selection particle beam. When I select an object to edit, I get a stream of squares as the beam, then after a second or so the particle texture loads. That's a new problem on the latest LL release. I filed a JIRA issue for it. BUG-11636 - Particle textures loaded from the viewer repository of textures often fail to rez correctly If you are seeing that happen on the latest Firestorm 4.7.7 release, though it's something different. Firestorm doesn't have the changes merged in yet that caused that. As far as the other problems mentioned here, I haven't seen any of those but they sound like general connection issues or possibly an agressive antivirus slowing down texture loading.

LL removed Danish & Polish from their viewer some time in late 2014. Polish has been added back but it's only available in the QuickGraphics RC viewer currently.

If you are only having these problems when logging into or after teleporting into one certain region, it is very likely a problem with the region itself. The region location isn't visible on your images so I can't check. All your symptoms suggest that region has capabilities failure - any service that uses caps will be broken. A region with caps fail will be broken for everyone. A region restart will fix that. Usual symptoms of caps fail are - all friend list names will display as "Loading...", groups list will be empty, no mesh will rez, voice will not connect, inability to initiate any IM sessions, disconnect when teleporting out of the region. If only yourself has the problem on that region or you have the same problem on all (or most) regions, it's most likely to be a DNS problem at your end. This will cause the same set of symptoms as caps fail because the DNS problem means that you failed to get the caps locally. This kind of DNS problem doesn't happen that much these days. Switching over to Google DNS should fix it.

https://community.secondlife.com/t5/General-Discussion-Forum/highest-hight-possible-in-sl/td-p/1021925

.Make sure you have no stuck processes left running from old sessions before you install the viewer. This happens a lot, especially with the win_crash_logger & llceflib_host Look for the following processes in task manager & end them. There may be multiple of each: win_crash_logger.exe, slvoice.exe, slplugin.exe, llceflib_host.exe. Then run the installer. A reboot before installing will work too.

Highest I managed was 1 million meters before the avatar just totally breaks down

bebejee wrote: Flying extremely high is no fun... It's great fun! This happens.

Usual cause of this is a problem with the region you are logging into. If this only happens when you login to a certain region then this region needs to be restarted to fix it. See https://jira.secondlife.com/browse/BUG-7557

Another recent case of this at https://jira.secondlife.com/browse/BUG-11595 The cause in this particular case was ESET antivirus software.

You are most likely wearing an attahment on your feet/lower legs that use invisiprims. Invisiprims are broken (well, more broken then before anyway) on the latest LL release viewer. For details see this bug report: BUG-11562 - Maintenance Viewer Breaks Content Using Invisiprims

Maddy is correct, it's the same bug you are seeing on Firestorm. We have a Firestorm JIRA issue for this bug here: FIRE-17916 - [CEF] Web profiles in the viewer often display as "locked" and need a login to view

I presume you're using the Linden lab viewer. The latest release of the LL viewer renders invisiprims as either grey or black instead of "invisible". For details, see this bug report BUG-11562 - Maintenance Viewer Breaks Content Using Invisiprims There has not been a Linden reply on that JIRA issue yet so it's unclear whether LL will fix this problem or not. Invisiprims have never really been supported and have been broken for a number of years for anyone with Advanced Lighting Model enabled in the viewer anyway.