Whirly Fizzle

Alyssa Quicksand wrote: Mobile Intel 4 Series Express Chipset Family (Microsoft Corporation WDN 1.1) Nothing is working to load SL what am i mising or am i unable to load SL on this system? I'm afraid you are out of luck. No SL viewer will run on a system with Mobile Intel 4 Series Express Chipset graphics on Windows 10. There are no Windows 10 drivers available for that card that will work for SL viewers. If you need that system to run SL, you need to roll back to Windows 7. The only other choice is to use a text viewer or an SL streaming service like Bright Canopy.

JIRA issue has been filed at BUG-11128 - Sim Traffic counter has not changed in 5 days

JIRA issue has been filed at BUG-11128 - Sim Traffic counter has not changed in 5 days

The broken triangles effect on the mesh objects where the textures have transparency looks like https://jira.secondlife.com/browse/BUG-8801 It's Mac specific & it will reproduce on all graphics settings on all up to date viewers. There is no workaround that I know of.

Dresden wrote: Since I have the group hidden from search and have it set so that no one can join, would it really be a huge issue if I just left the group in order to just be done with it? ...Dres Will it let you leave? If you are the last Owner of the group & you attempt to leave, you will get the error: "Unable to leave group. You cannot leave the group because you are the last owner of the group. Please assign another member to the owner role first." If you can leave the group, I would just do that & forget about it.

Your group may not have disbanded because defunct accounts may still be members of your group but they won't show in the members list in the viewer - this is BUG-5586. The last server roll included a change which looks like it may fix this problem however - http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/15#15.12.14.309144 Some of the group member counts as reported in the viewer will now be larger. These member counts will include inactive users, and will only updated on a daily basis. This change is to help with some of the problems we have encountered recently with group functions.

The beta grid syncing is still broken. Currently LL support are handling the syncing manually on a case by case basis, so what you need to do each time you require a sync of password &/or inventory onto beta grid is to file a support ticket to request a sync - https://support.secondlife.com/create-case/ There will be a new Aditi inventory sync method coming soon - for details see the "Aditi Inventory Syncing" section on http://modemworld.me/2015/12/20/sl-project-updates-512-tpvd-meeting-aditi-inventory-changes/

No, you cannot transfer inventory from one account to another unless you can login and the inventory items are transfer. You will need to file a support ticket & wait for LL support to fix your broken account so it can login.

There are a lot of people having this new "Updating friends list..." login failure, which seemed to start last Tuesday. Noone seems to know what's causing the problem yet. It's account specific and affected accounts cannot login on any viewer. Whatever is wrong it appears to be something wrong with those accounts at the back end to do with a transform being run on those accounts which is failing with a parsing error. Affected accounts cannot be logged in on any system. All the JIRA issues & forum reports about this problem have been linked to https://jira.secondlife.com/browse/BUG-11032 From the feedback people have given from their support tickets, support don't seem to realise there is a problem yet.

There are a lot of people having this new "Updating friends list..." login failure, which seemed to start last Tuesday. Noone seems to know what's causing the problem yet. It's account specific and affected accounts cannot login on any viewer. Whatever is wrong it appears to be something wrong with those accounts at the back end to do with a transform being run on those accounts which is failing with a parsing error. Affected accounts cannot be logged in on any system. All the JIRA issues & forum reports about this problem have been linked to https://jira.secondlife.com/browse/BUG-11032 From the feedback people have given from their support tickets, support don't seem to realise there is a problem yet.

It's a new bug in the latest viewer release - see BUG-10415 - [Valhalla] profiles and marketplace are asking for a login each session It's listed as a resolved issue in the release notes & it did seem to be fixed in earlier Valhalla-RC viewers but the bug came back in the released version of the viewer. When the viewer prompts for login when attempting to view a profile, login and make sure to tick "Remember me on this computer" & the viewer shouldn't prompt for login again unless you use a different account or purge the cef_cookies folder from the viewers settings per account folder.

There are a lot of people having this new "Updating friends list..." login failure, which seemed to start last Tuesday. Noone seems to know what's causing the problem yet. It's account specific and affected accounts cannot login on any viewer. Whatever is wrong it appears to be something wrong with those accounts at the back end to do with a transform being run on those accounts which is failing with a parsing error. Affected accounts cannot be logged in on any system. All the JIRA issues & forum reports about this problem have been linked to https://jira.secondlife.com/browse/BUG-11032 From the feedback people have given from their support tickets, support don't seem to realise there is a problem yet.

In addition to what Lindal said, the problem could be your inventory. Test if you also get disconnected when logging an alt in, If this problem only happens with one of your accounts then best thing to do is file a support ticket under Inventory (un-rezzed) issues & get your inventory structure checked & fixed.

Bento Mocap Fingers, by Abramelin Wolfe.

Aethelwine wrote: I looked up a solution and found that setting debug settings "TextureLoadFullRes" to True, fixes the problem. You really should never set TextureLoadFullRes to TRUE. That advice gets given out a lot on "help" notecards & it's very bad advice. Setting TextureLoadFullRes to TRUE effectively simulates a memory leak, will slow the viewer to a crawl even on a good system & you will likely crash very soon from out of memory. Any viewer you changed that setting on, you should revert it. The constant blurring & sharpening of textures you are seeing sounds like "texture thrashing". This happens usually because the viewer runs out of texture memory and the textures will then constantly unload and reload - blur/sharpen/blur/sharpen. The textures will usually load and stay sharp while your mouse is hovering over them. This has been a problem for a long time with SL viewers that only allow up to 512MB of texture memory, which can quickly run out in texture rich areas. There is no real workaround for this problem apart from switching to a viewer that allows more then 512MB texture memory and even then the problem can still be triggered by certain scenes with a silly number of large sized textures and how much milage you get from a viewer that allows more the 512MB texture memory depends on your graphics card. This is probably why you don't get the problem on Firestorm - Firestorm 64bit allows you to set texture memory up to 1024MB, Preferences -> Graphics -> Hardware Settings -> Video texture memory buffer. Some things to try that may help: Certain HUDs are known to cause almost instant texture thrashing because of the large number of 1024 sized textures they use - for example The Shops style HUD, The Shops shopping HUD, the Toddleedoo avatar HUD and the WowMeh mesh avatar HUD - pretty much all the HUDs that come with mesh bodies will cause a texture thrashing problem when worn. If you are wearing one of these HUDs, remove it and relog and the problem should be much better. Only wear the mesh body HUDs when you need to use them. See BUG-6242 for a discussion about these HUDs. The texture thrashing may be being exacerbated by an another texture heavy attachment you are wearing, not necessarily a HUD. Test this by resetting to the default avatar and relogging and see if the texture thrashing stops. If it does, add back your attachements one at a time to see if you can find the culpret. Usually its mesh attachments that can worsen this problem. To set back to the default avatar, activate the Develop menu in the top menu of the viewer with CTRL+ALT+Q, then Develop -> Avatar -> Character Tests -> Test female/male. Make sure you are on the latest graphics driver version. Some old drivers (especially for Intel & AMD cards) will cause texture thrashing to happen more frequently. Go to Me -> Preferences -> Graphics -> Hardware -> Texture Memory slider. If the slider isn't set to 512MB, set it to 512MB if the viewer will let you (this depends on your graphics card if you can set the 512 max value here). The lower the value here, the more quickly you will run out of texture memory and the faster texture thrashing will start. Enable the texture compression setting. Preferences -> Graphics -> Hardware -> Enable Texture Compression (needs a restart). Enabling texture compression may ease the texture thrashing but beware - it's lossy texture compression, very lossy, and you will very likely see a noticeable pixelation on many textures. it will help to close down all active group chats. The avatar profile icons can eat up precious texture memory. You have to close the group chat window. It doesn't matter if you do not have the group chat window actually visible on screen, the profile textures will load into memory as soon as the group chat opens. If you have a few group chats open with a large chatters list, those profile icons can eat up at least 200MB of texture memory. For a discussion about this texture thrashing problem, see this thread on Torley's profile feed: https://my.secondlife.com/torley.linden/posts/5440cf6176286532390000ad Also see the comments on issue BUG-2514 Aethelwine wrote: I don't have this problem on firestorm, but firestorm has a different problem and keeps deciding to stop loading textures after a while. So for example when exploring a new area of a sim often only half the scene will load, or I go to a shop and after a while, it stops loading textures until I restart the viewer. That shouldn't happen. To get that problem looked at, best thing to do is to file a Firestorm JIRA issue so we can get your system information, viewer logs and settings files. I suspect a settings problem there, seeing as you have already changed TextureLoadFullRes to TRUE. Whatever is going wrong there should be fixable because it isn't normal.

Your login credentials for the LL viewer are stored in the bin_conf.dat file located in C:\Users\USERNAME\AppData\Roaming\SecondLife\user_settings. bin_conf.dat is encrypted using your machine ID. The viewer uses WMI to get your machine ID. If you update to Windows 10 from an earlier version of Windows or after some of the bigger Windows 10 updates (like Threshold 2), your machine ID will be changed. Nothing you can do about that, blame Microsoft If your machine ID has changed, the viewer login credentials cannot be decrypted. So its totally normal for the viewer not to be able to decode your login credentials in this case. Once you have logged in once though, your login credentials should then be saved with your new machine ID so you should only see this problem for each account once. If your login credentials continue to fail to decode, then something else is wrong. You said other programs were also affected. Any program that encrypts data with your machine ID will have the same problem.

Project Bento initial feedback - Excellent write up from Inara Pey.

Discussion about Project Bento from todays third party viewer meeting - including bone-translating animations

ChinRey wrote: The only big concern here is lag. All those extra bones will of course add more load on the client computers, making SL even less accessible to the general public than it is today. They did make a note about possible performance issues on older systems on the Knowledge Base Bento post. What are the system requirements for Project Bento? Some older graphics cards and drivers may encounter difficulty rendering the increased number of joints, and you may experience a change in framerate as a result. If possible, upgrade your OS or driver to the latest version. You may also disable the new joints in your graphics settings, resulting in reduced animation quality but improved graphics performance. The effect of disabling the new joints isn't just "reduced animation quality" though, it causes bento avatars to look like this, but I guess it's expected. 

I created a JIRA filter for all Bento bug reports & feature requests. I'll keep that updated as new issues come in.

Teager wrote: - I wholeheartedly disagree with the decision to block animation of bone location Adeon filed a JIRA issue to request allowing the animation of bones positions. BUG-10990 - [bento] A formal method of bone-translating animations is vital for the creation of proper facial expressions.

irihapeti wrote: Flash I have given away, bc most Flash-enabled websites now say: plugin required See this comment for how to get Flash working on Valhalla.

Not sure if this is a bug or expected behaviour - it seems that anything rigged to the new joints either partly disappears,collapses or melts when viewing that avatar as an imposter? There was a guy on aditi with a mesh head using the new bones & his head melted when viewed as an imposter. This was at ground level. This gif shows the effect with the bento_angel.dae test content. See how the wings & tail get clipped when the avatar becomes an imposter. The wings actually flicker quite badly when the avatar is an imposter but the flicker is too fast to show on the gif. https://i.gyazo.com/177186beee1ee3750a6a0c06eaefb211.gif Edit: Filed a JIRA issue for it - https://jira.secondlife.com/browse/BUG-10991

Hmm it's working okay for me on old webkit viewers and on Valhalla. I can hear sound from your example URL too. System info: Second Life 4.0.0 (308641) Dec 4 2015 12:20:51 (Second Life Release)Release NotesYou are at 167.8, 154.8, 21.0 in Testylvania Sandbox located at sim8922.agni.lindenlab.com (216.82.41.98:13000)SLURL: http://maps.secondlife.com/secondlife/Testylvania%20Sandbox/168/155/21(global coordinates 332,712.0, 306,331.0, 21.0)Second Life Server 15.12.01.308474Retrieving...CPU: Intel® Core i7-4770K CPU @ 3.50GHz (3491.92 MHz)Memory: 16268 MBOS Version: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601)Graphics Card Vendor: NVIDIA CorporationGraphics Card: GeForce GTX 750/PCIe/SSE2Windows Graphics Driver Version: 10.18.0013.5906OpenGL Version: 4.5.0 NVIDIA 359.06libcurl Version: libcurl/7.38.0 OpenSSL/1.0.1h zlib/1.2.8J2C Decoder Version: KDU v7.2Audio Driver Version: FMOD Ex 4.44.31LLCEFLib/CEF Version: 1.4.0-(CEF-WIN-3.2526.1347-32)Voice Server Version: Vivox 4.6.0017.21209Built with MSVC version 1800Packets Lost: 0/847 (0.0%) -------------Sound Devices------------- Description: Speakers (Realtek High Definition Audio) Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0892&SUBSYS_1458A002&REV_1003 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: RTKVHD64.sys Driver Version: 6.00.0001.7071 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 10/22/2013 12:38:24, 3692632 bytes Other Files: Driver Provider: Realtek Semiconductor Corp. HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX 2.0 Listen/Src: No, No I3DL2 Listen/Src: No, NoSensaura ZoomFX: No Description: Realtek Digital Output (Realtek High Definition Audio) Default Sound Playback: No Default Voice Playback: No Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0892&SUBSYS_1458A002&REV_1003 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: RTKVHD64.sys Driver Version: 6.00.0001.7071 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 10/22/2013 12:38:24, 3692632 bytes Other Files: Driver Provider: Realtek Semiconductor Corp. HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX 2.0 Listen/Src: No, No I3DL2 Listen/Src: No, NoSensaura ZoomFX: No---------------------Sound Capture Devices--------------------- Description: Microphone (Realtek High Definition Audio) Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: RTKVHD64.sys Driver Version: 6.00.0001.7071 (English) Driver Attributes: Final Retail Date and Size: 10/22/2013 12:38:24, 3692632 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF Description: Realtek Digital Input (Realtek High Definition Audio) Default Sound Capture: No Default Voice Capture: No Driver Name: RTKVHD64.sys Driver Version: 6.00.0001.7071 (English) Driver Attributes: Final Retail Date and Size: 10/22/2013 12:38:24, 3692632 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF

polysail wrote: Mind you perhaps I'm just being paranoid~ But ~ This level of complexity is what I'm dreading. Advanced JIRA search is the best thing since sliced bread. But maybe I'm biased...