Whirly Fizzle

Caleb Linden wrote: I needed to confirm with the Viewer Project to confirm that RC Bluesteel is now supporting this: http://wiki.secondlife.com/wiki/HoverHeightProjectViewerTesting Please, have at it testing. There is no text on that wiki page. I'll swear it wasn't blank yesterday

Both of you sound like the problem is probably the region you are on. Ina, your symptoms sound like BUG-772 - Simulator refusing to rez objects after 10 hour timeframe. Zizihyde - your problem sounds like capability fail on the region (region restart will fix it) or are you connecting to SL over a cellular network? Cellular networks do not work well for SL since the change over to CDN. You should both get your regions restarted which will hopefully fix the problem. If the region is a mainland region then you will need to contact Linden Lab support to request a region restart - see https://support.secondlife.com/contact-support/ There are a lot of regions in a bad state at the moment because there have been no LL rolling restarts on main channel for a few weeks now.

Flo, do you happen to have iCloud installed on Windows? The missing from database messages are one of the side effects of having iCloud installed - see BUG-7343 for details. Uninstalling iCloud is the only known workaround at this time.

Velk Kerang wrote: I manage to get Singularity up no problems finally. Only thing with it is when I pop fullscreen mode on it the interface half of it goes invisible on me. Like my menu up top vanishes, but i see the names and background chat windows and stuff are invisble, but I see the words and the chat part where ya type is grey. I have to go back to window mode and restart to sort it out. How do you full screen without the view messing up like that? I am thinking that's a Singularity issue myself and wouldn't have that issue on Firstorm. I have never seen or heard of that problem on Firestorm. I'm not familiar with Singularity viewer so I don't know if its a known bug. One thought though - are you running Singularity with basic shaders disabled when you switch to full screen mode? Your description of the symptoms sounds like the problem that can happen running the viewer with basic shaders disabled - much of the user interface will break and turn transparent or display in the wrong colour. You should find the basic shaders checkbox under graphics preferences in the viewer - sorry, don't know where that setting is exactly on Singularity.

Velk Kerang wrote: Most people I know always give me crap cause of my inventory size saying it's why I am having issues, but I am like on my gaming rig I have no issues loading in what so ever, but since it is out of commission atm I am forced to use my laptop I'm pretty sure it is the combination of large inventory plus a slow system that is the problem currently then. I'm actually having the same problem as you at the moment. I have a 107k inventory on my main and I'm away from home at the moment and I'm accessing SL on a very low end craptop (CPU: Intel® Core2 Duo CPU P8700 @ 2.53GHz (2526.99 MHz), Memory: 2000 MB, OS Version: Microsoft Windows 7 32-bit Service Pack 1 (Build 7601), Graphics Card: Mobile Intel® 4 Series Express Chipset Family). The viewer (both Firestorm and the Linden Lab viewer) will often hang so long while creating inventory views while logging in that I'll time out and either never get logged in or I'll appear to be logged in but my location shows as 10,10,10 on the region and I'll be disconnected very shortly after. If I purge my inventory cache before logging in, I have no problems at all - a bit of a pain to do but hey, it works. I will also often have to force quit the viewer when logging out because this system just seems unable to compress my inventory when logging out and just hangs or takes a very long time. Lack of memory is the problem there I think. Again, this is only a problem on my main with the large inventory. On this same home network, If I login my main on my Dads desktop (a fairly decent system for SL) I have no problems logging in or out whatsoever. When I am back at home on my desktop I have no problems either. I do have the same problem at home on the craptop though. I have none of these problems on my alt accounts which have small inventory (10k at most). I have been using the Onlive SLGO viewer while away from home to work around this problem and it's really great. I have no problem at all when using SLGO. You can find details of SLGO here: https://games.onlive.com/landing/slgo and http://www.firestormviewer.org/firestorm-on-sl-go/ You need a good (>5mbps and lossless) connectiopn to use SLGO though. If your connection is good but your computer is a brick from the dark ages like mine, it's a fantasic way to access SL.

I suspect wiping the viewers settings file will allow you to run the viewer again but until you discover the cause of the problem, you will probably have to delete the settings file at the end of every session. Make sure hidden files are set to show. After logging out, delete the settings.xml file. This is located at: Linden viewer: ~/.secondlife/user_settings/settings.xml Firestorm: ~/.firestorm/user_settings/settings.xml This should hopefully allow you to login again on each viewer. Are you using the opensource mesa graphics drivers? You can see this information under Help -> About Second Life/Viewer name. Your problem can sometimes happen with the mesa drivers. If that is the cause then it can usually be fixed by installing the non-mesa graphics driver. I'm not a Linux uswer so I cannot give you any more specific help. Hopefully someone else can

78k isn't really that large an inventory size - I know plenty of people with a larger inventory then this. You shouldn't have a problem logging in on with a fully cached large inventory unless you have a really slow system &/or a really slow connection speed &/or a very "flat" inventory structure. By "flat" I mean you have a lot of items in the main Inventory folder or directly in the main system folders and not in subfolders. The more subfoldering (folders within folders within folders....) you have, the better. Your problem may also be caused by something being wrong with that accounts inventory - for example a crazy number of duplicated calling cards or a very large number of active gestures. You said you use Firestorm viewer so the best way to get help is to file a support JIRA issue with Firestorm (see http://wiki.phoenixviewer.com/file_a_jira) - Firestorm support will likely need to see your viewer logs & get the results of some tests so a JIRA issue is easier. Your problem should hopefully be fixable.

Sounds like the known file picker crash on Mac. This should fix you for all viewers: http://wiki.phoenixviewer.com/mac_crash_upload

Just ignore that "someone" - add them to your wackadoodle list This is the same kind of rubbish that special little snowlakes who "know a Linden"/"date a Linden"/"my brother is a Linden" spout all the time and I can guarentee you it is 100% rubbish told to you from someone who just wants to troll, cause trouble or just does not have a clue and is parotting what someone else told them. Those who do viewer support for TPVs have no special powers whatsoever to be able to see your IP address. Others have already discussed above how anyone can get your IP address in certain situations.

If you are using Mesa drivers and you crash when right clicking certain mesh objects then it will likely be fixed by installing the drivers directly from Nvidia/AMD. If you no longer crash when right clicking if you disable selection outlines then its almost certain to be a driver issue.

Appears to be expected behaviour: MAINT-1841 Use NVAPI to force NVIDIA GPU power management mode to prefer max performance

Oh you already posted here Anthony. I need more coffee....

There's been a few reports of people having this problem since the last set of Windows updates. For example see http://antonyfairport.blogspot.co.uk/2014/12/viewer-freezing-when-detecting-hardware.html Hopefully Anthony will file a JIRA issue with logs, I left him a message asking him to. I wonder if it's the kb3004394 update causing the problem - Microsoft already pulled that update - see http://anandtech.com/show/8782/win7-driver-issues-microsoft-amd-recommend-uninstalling-kb3004394

You can if you really must - but setting above 3k gives no benefit whatsoever. Its placebo. Advanced -> Debug Settings -> ThrottleBandwidthKBPS -> set to your chosen value. Check your log files when you have max bandwidth set over 3k. You will see lines like this: "INFO: LLViewerThrottleGroup::sendToSim: Sending throttle settings, total BW 3000.000000" It is clamped at 3k serverside. It will not go any higher.

CommerceTeam Linden wrote: Friday, December 12, 2014, at 11am Pacific time, several Lindens will be inworld to get your feedback on the Viewer-Managed Marketplace (VMM). We’ll be meeting on Aditi in the “ACME F” region (secondlife://Aditi/secondlife/ACME%20F/128/128/24). This meeting was recorded for those who could not attend. Thanks to Chakat Northspring (panterapolnocy) for the recording.

You should be able to login on the Linden viewer on XP for now, as long as you have the latest service pack installed. XP isn't officially supported by LL anymore but it should still allow login and be functional - though with a high crash rate. How does the LL viewer "not work" on your computer?

http://modemworld.wordpress.com/2014/12/09/latest-amd-catalyst14-12-drivers-continue-sl-rigged-mesh-woes/

I have a collection of those. There was a cool bug last August ( BUG-3547) that allowed those "Avatar physics primitives" (does anyone know the correct term for them?) to be created pretty easily and in large numbers when crossing from a BlueSteel to a main channel region. A neat side effect was being able to create linksets with more then 256 prims. Each time you crossed the region while sitting on an object one of those "thingies" would be linked onto the object for each avatar seated on it, even if the object already had 256 prims or greater.

Try the new Benchmark-RC viewer, this should hopefully have that crash fixed for everyone. http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/3.7.22.297128

Have you tried changing over to Google DNS? Instructions here: https://developers.google.com/speed/public-dns/docs/using If that doesn't help, you should file a JIRA issue. Include a paste of all your system information from Help -> About Second Life. Also run a session where you reproduce the grey avatar problem on other avatars as well as yourself (the longer session the better), then logout and zip up your viewer logs folder and attach it to your JIRA issue using More Actions -> Attach files. This page tells you where to find your logs folder.

Shamonne wrote: What made me back online: Before I clicked "log in", I selected another place to land on from my Favorites. Upon landing I waited a few moments and anticipated a black out. It did not happen. I waited again. I'm good. I suspect that first location you were at, someone rezzed or was wearing a graphics crasher. Your symptoms sound like a driver crash.

I can reproduce it (Firestorm and LL viewer). It depends how your camera was set before sitting whether you can reproduce it though. Lots of seats are scripted in this way, it isn't unusual. To reproduce: Before sitting on the seat, hit ESC a couple of times, right click seat -> Sit Here -> choose animation. Cam is taken over by the script and you cannot change camera view using arrow keys or by hitting ESC. However, if you move camera using the camera floater, camera is then unlocked and you can use the arrow keys to look around. This fails to reproduce: Before sitting on the seat, make sure camera view is not on default - zoom camera out a bit and rotate it and then sit. The script then doesnt take contro of camera and it can be moved with the arrow keys.

Stereo mix used to work in Second Life viewers before FMod was updated to FModEx. All actively maintained viewers now use FModEx, so I'm afraid you are out of luck. For details see FIRE-12519 - [FModEx?] Stereo mix doesnt work anymore

Thanks for checking that. I think the best thing to do is file a JIRA issue. Or is this issue yours? System info appears to be matching... BUG-7887 - Unable to see mesh

Yep, known issue See BUG-5265 - Improvement: Remove the draw distance reference in the viewer when alt-camming on terrain.