Your browser (Internet Explorer 6) is out of date. It has known security flaws and may not display all features of this and other websites. Learn how to update your browser.
X

Updates to Web Cashier, 4.7.7 Recommended Version

translation services

Beginning June 15, Linden Lab is moving to an updated web cashier for reasons of security (called TLS 1.2), which will affect how transactions are processed. As they have posted with respect to third party viewers,

Actively maintained Third Party Viewers should have versions available that have the required support. Older or unmaintained viewers may not, and you will not be able to use them for L$ transactions after the deadline if you do not update.

Firestorm version 4.7.7 is fully up to date and compatible with the changes about to be implemented. If you are already using 4.7.7, you don’t need to do anything. The other two currently usable Firestorm versions (4.7.3 and 4.7.5) are not compatible with TLS 1.2. Linden Lab has not tested what the specific breakages will be on June 15, but at a minimum, users on these versions will not be able to purchase linden dollars through the viewer. LL’s latest info is that they “believe” that users on older versions will also be unable to make inworld shopping purchases or to send and receive money (see today’s Third Party Viewer Development meeting; video link is set to start at the TLS discussion).

Read Linden Lab’s announcement in full here. From there, you will also be able to test your web browser to make sure you are compatible with the new cashier system outside the viewer as well.

We recommend updating to Firestorm 4.7.7 prior to June 15 if you aren’t yet on this version. We will not be blocking 4.7.3 and 4.7.5 at this time, so updating is voluntary, but it is strongly encouraged.

Other Important Changes Coming Up

JellyDolls

JellyDolls are a recently implemented update to Linden Lab’s official viewer (V3) that allows the user to view avatars over a specified avatar complexity as a single-toned silhouette rather than as fully rendered. The purpose is to improve performance on that person’s system. If you have been told by a V3 user that you look like a purple, brown, or green mass, there is nothing wrong with your avatar or their viewer; your avatar’s complexity is simply over that person’s threshold. See Linden Lab’s explanation and video for more information. Firestorm will include JellyDolls in its next release (though we don’t know when that will be yet).

Project Bento

For an explanation of what this project is, see Linden Lab’s post here. LL rolled out support for Project Bento to the SL servers this week, which means the infrastructure is there for people to start making Bento avatars and using Bento-compatible viewers. However, the viewer code is not fully in place, and neither Firestorm nor the main V3 release has support for Bento yet. If you see the occasional distorted avatar (there should not be very many at this stage), it might have been created with extra bones Bento allows. Firestorm will support Bento in the future.

  • Personally would love to update, but 4.7.7 has this big time annoying bug where people go completely invisible. while this also seem to happen on 4.7.5 i found it happens a whole lot less on there.

    From what i gather, if you cam an boxed in area, and hit escape and then walk in to said area, those you cammed inside that area, go invisible as in only your scripted radar sees them, for for minimap and local radar and viewer, they no where to be found.

    Jaraziah Lowell

    June 3, 2016

  • Not updating isn’t really an option if you need to have functional L$ transactions.
    The problem you are seeing sounds like it may be http://jira.phoenixviewer.com/browse/FIRE-14439 or similar.
    It could also be expected behaviour if the parcel has avatar privacy enabled (Avatars on other parcels can see and chat with avatars on this parcel – disabled).
    Avatars who are inside the parcel boundaries and below the parcel height (which is ground height + 50m) cannot see avatars outside of this area. This height boundary for parcel privacy is in place to allow parcels which deny public access to be private, since strangers can enter the parcel above the parcel height.

    Whirly Fizzle

    June 3, 2016

  • The reason I will not update is I use the viewer for a combat game and a HUGE combat feature was removed with this new version , with the current version I have I can click advanced>show render weight of avatars and use this feature. I will just not shop 🙂

    Gia

    June 7, 2016

  • Gia, are you enabling show render weight to make all floating text disappear?
    If so, you can still do this in Firestorm 4.7.7, in fact you have total control whether you see floating text at all and how far away you can see floating text.
    Preferences → User Interface → 3D World → Floating text fade distance (in m) – Sets the distance where floating text starts to fade.
    Preferences → User Interface → 3D World → Floating text fade range (in m) – Sets the range it takes for floating text to fade from fully visible to invisible.

    If the problem is something different, please let me know.
    You will have to update sooner rather then later – it won’t be that long before all older viewers will be unable to fetch any inventory at all – LL will be disabling the old inventory service at the back end & everyone will have to update their viewer.
    If there is a problem with your combat game on 4.7.7, please let us know asap & it can hopefully get fixed before the next release.

    Whirly Fizzle

    June 7, 2016

  • Actually, Gia was using it to make hovertext visible at a distance — a tweak known to many of us who do meter combat. It disappears, yes, with that tweak, but when it comes back (the next time said text changes), it’s visible halfway across the sim.

    Good to know there’s still a way to make it visible at a distance!

    Aaron Kukulcan

    June 9, 2016

  • Ahhh yes.
    The fact the hover text was visible over large distances after disabling render weight was actually a bug. It was LL who fixed that bug in their viewer & Firestorm picked up those changes.
    Another case of http://imgs.xkcd.com/comics/workflow.png , which happens so often in SL 😉
    Anyway, on 4.7.7 you should be able to control the distance you see hover text much more easily now.
    If the settings I gave you do not work as they should for your combat meters, please let me know.

    Whirly Fizzle

    June 9, 2016

  • It’s working! The only problem is the maximum distance this way seems to be lower (96 m rather than 128 m), even if I set the value higher via a debug setting or by adding it to Quick Prefs.

    Aaron Kukulcan

    June 10, 2016

  • It does rather sound as if this distant hovertext trick amounts to cheating on a combat sim. Don’t forget that hit boxes don’t lie down and wish they had thinner tunic buttons.

    I once got accused of cheating by wearing a camouflage uniform.

    Wolf Baginski

    June 13, 2016

  • so with white screen issue I reported (and filed the Jira on) when using 4.7.7 and no solution to it yet. I will now be forced to a viewer I can’t use just Brilliant!

    Wesley

    June 4, 2016

  • Wesley, can you give me the link to your JIRA issue? I can’t find anything about a white screen filed under a “Wesley” account.
    Thanks!

    Whirly Fizzle

    June 4, 2016

  • re-submitted the Jira its on Jira Case- Fire-19455

    Wesley Gunder

    June 12, 2016

  • I am currently using 4.7.7 so none of this effects me, but I truly feel for those who are unable to use it for what ever reason.

    To me, it smacks of the same mind set that Microsoft had when forcing everyone to Windows 10.

    Do these people work for the government? “You WILL do what we want you to do, like it or not – it’s in your best interest, and we know what’s best for you.”

    Mewling Moy

    June 4, 2016

  • Switching cashier to use TLS 1.2 is out of Linden Lab’s hands. It has to be done to comply with new legal requirements mandated by the PCI Security Council.

    http://blog.pcisecuritystandards.org/migrating-from-ssl-and-early-tls
    “All processing and third party entities – including Acquirers, Processors, Gateways and Service Providers must provide a TLS 1.1 or greater service offering by June 2016. “

    Whirly Fizzle

    June 4, 2016

  • 30 June 2018 for transitioning from SSL and TLS 1.0

    The Payment Card Industry Security Standards Council (PCI SSC) is extending the migration completion date to 30 June 2018 for transitioning from SSL and TLS 1.0 to a secure version of TLS (currently v1.1 or higher).

    fu LL fools

    b

    June 14, 2016

  • Someone asked Oz about the compliance date being extended at last weeks simulator user group and his reply was that LL legal compliance team said the change still needed to go ahead before June 30th to be compliant.
    There are some conditions that still need to be met to qualify for that date extension.

    Whirly Fizzle

    June 14, 2016

  • yes. but “date to 30 June 2018
    for transitioning from SSL and TLS 1.0”

    cant they read ?

    b

    June 14, 2016

  • The same mindset of Microsoft for making people upgrade FOR FREE to a better system? oh, you mean.. wanting to help? then yep, I think you’re right.

    Someone that used to help

    July 7, 2016

  • It is pretty astonishing to me that people are upset about Linden Lab and Firestorm making this change. I get that some people can’t upgrade their viewers for whatever reason, but this change is being made to ensure that people have the highest level of security possible to protect against hacked financial transactions. I don’t get why people would be resistant to this concept.

    Thea

    June 4, 2016

  • I am not resistant to the change of the viewer and if you think that is my complaint then you need to learn to listen/ or read better. My Gripe is being forced to a new viewer that flatly doesn’t work so I am still on 4.7.5 Oh and by the way the security measure actually is still lower then the Government standard, this so called security update doesn’t protect squat!

    Wesley Gunder

    June 12, 2016

  • Then I be wishing you get robbed and I be laughing.

    Sonic the Hedgehog

    July 12, 2016

  • JellyDolls?
    you want new people to make a million complaints to support, or just quit? or other people to quit just implement that ! That has to be the stupidest idea I have heard of for SL
    I don’t know about you, but i do not like it when people say my avie is blurry or not visble or orange mist, IF IT is a jelly doll, I and I imagine others will be totally p*ssed off !

    Princss Alexis Hannah Greymyst

    June 4, 2016

  • If you do not want to see any JellyDolls, you can disable the feature in the viewer.
    This will not stop others seeing you as a JellyDoll if your avatar complexity is above the threshold they have set for complexity though. What level others set in their viewers is their choice.
    If you keep your avatars complexity moderate then pretty much no-one will see you as a JellyDoll.
    Having a low complexity avatar does not mean having a boring & bland avatar at all. There are plenty of good creators who produce well optimized & great quality avatar attachments.
    Unfortunately there are also plenty of creators who don’t & this change should encourage creators to optimize their content better because now people will avoid using the badly optimized content which causes everyone rendering them to suffer performance problems.

    Whirly Fizzle

    June 4, 2016

  • That “Jelly Dolls” sounds to my like what we had for ages for one or the other reason. In the past it has been called a bug, now it’s a new feature *lol* In other words, Linden Lab was unable to find the right ballance between adding new features and to cope with the resources required for it. The result is not what I understand of what once had been promising called “Shared User Experience”. Don’t take me wrong, I like features that give me more control.

    Shy

    June 7, 2016

  • Don’t like performance Increase then TURN IT OFF! NO ONE PUT A GUN TO YOUR HEAD TO FORCE YOU.

    Sonic the Hedgehog

    July 12, 2016

  • how do we all launch a complaint about this JellyDolls idea?
    why doesn’t Linden Labs fix some of the JIRA items or something rather than implent this?

    Princss Alexis Hannah Greymyst

    June 4, 2016

  • If you want to complain about the JellyDolls feature, best place to do that is probably this forum thread: https://community.secondlife.com/t5/General-Discussion-Forum/Jelly-babies/m-p/3031284

    Whirly Fizzle

    June 4, 2016

  • Actually, this thread may be better: https://community.secondlife.com/t5/Second-Life-Viewer/Rendering-Complexity-Quick-Graphics/td-p/2973607

    This one has Linden watchers.

    Whirly Fizzle

    June 4, 2016

  • thank you for that link Whirly

    Princss Alexis Hannah Greymyst

    June 4, 2016

  • Princss Alexis Hannah Greymyst

    June 4, 2016

  • Just turn off the feature. People aren’t going to think there’s some kind of bug when they join SL. They’re noobs, not idiots. Well, maybe I should take that back, some of them are idiots…but most are smart enough to know that this would be a feature of the viewer. Especially since it would probably be part of any tutorial given on joining. Also, the jelly dolls doesn’t cause rezz issues or lag…It actually takes away the lag. You can set the level to your preference, not the default, but still keeping it at the default is pretty good. When I tested the beta viewer, it was automatically set to 80,000 arc. And if you really don’t like the feature, turn it off. It’s fully controllable to turn off. But some of us would rather see a jelly doll than be lagged out by someone who doesn’t understand the concept of wearing a piece of jewelry with 200 textures and scripts and lag. In the end, just turn it off.

    LizzyL

    June 25, 2016

  • There appears to be a hiccup either via Firestorm or SL on the new TLS. Receiving a can not authenticate issue in world when trying to purchase Lindens

    Hollywood Topaz

    June 4, 2016

  • The TLS change isn’t live yet – it will be live on June 15th.

    Check that your payment information is correctly set up in https://accounts.secondlife.com/billing_information/?lang=en-US & that you have “Buying L$ in Second Life Viewer” enabled for the payment method.

    If you are still having problems purchasing L$ in Firestorm then please check if you can purchase L$ when using the LL viewer at https://secondlife.com/support/downloads/
    If you ONLY have the problem on Firestorm, file a Firestorm JIRA issue: http://wiki.phoenixviewer.com/file_a_jira
    If you have the same problem when using the LL viewer too (you probably will), you will need to contact LL support directly by filing a support ticket here: https://support.secondlife.com/create-case/

    Whirly Fizzle

    June 4, 2016

  • TLS 1.2

    seems they had to implement this one, it was a regulation that Linden Labs HAD to comply with , so of course we do as well.
    one consolation–> won’t be anyone on an old viewer anymore,
    bad part –> some people who don’t understand the need for companies to comply with regulations and have their customers comply as well may quit , but understand THIS WAS AND IS better than no Second Life at all !

    Princss Alexis Hannah Greymyst

    June 4, 2016

  • https://blog.varonis.com/ssl-and-tls-1-0-no-longer-acceptable-for-pci-compliance/

    posted around a year ago … SSL and TLS 1.0 No Longer Acceptable for PCI Compliance

    Last month, the PCI Council released version 3.1 of their Data Security Standard (DSS). While most of the changes in this minor release are clarifications, there is at least one significant update involving secure communication protocols. The Council has decided that SSL and TLS 1.0 can no longer be used after June 30, 2016.

    so in short…. Linden Labs had until June 30 and that is the reason why

    Princss Alexis Hannah Greymyst

    June 4, 2016

  • I’m SO frustrated by this. I’d tried 7.7, but I play a combat game in SL, and there was a feature under dev>render metadata>lights that I used to get a better view of health meters, which doesn’t work in the new version. So I switched back – it’s super important to me. Sigh. I’ll have to use another viewer for shopping I guess.

    Ardis

    June 4, 2016

  • Ardis, can you explain how that setting used to help you see health meters better?
    Are you talking about health meters that use floating text above the avatars head and you need to see that floating text over a long distance?
    If so, 4.7.7 actually has a new feature which is perfect for this!
    In 4.7.7 there are new options to control how far away you can see Floating Text and the ability to totally disable all Floating Text if you want.
    Preferences → User Interface → 3D World → Floating text fade distance (in m) – Sets the distance where floating text starts to fade.
    Preferences → User Interface → 3D World → Floating text fade range (in m) – Sets the range it takes for floating text to fade from fully visible to invisible.

    If this doesn’t fix your problem, I’d really love to know how changing Lights in Render Metadata helped you see the health meters better. If this is a new bug on 4.7.7 then I need to know details so I can get a bug report filed & we can get it fixed.
    Thanks!

    Whirly Fizzle

    June 5, 2016

  • Any way you can make that floating text distance 2-3 times further That is what Ardis is talking about before you could change the render metadeta on then off and achieve this function but worked for alot further maybe the length of the sim perhaps 300M.. Think if its 150meters that might be plenty

    Niccole Inglewood

    June 5, 2016

  • Yes you can do this on Firestorm 4.7.7.
    Preferences → User Interface → 3D World → Floating text fade distance (in m) – Sets the distance where floating text starts to fade.
    Preferences → User Interface → 3D World → Floating text fade range (in m) – Sets the range it takes for floating text to fade from fully visible to invisible.

    Whirly Fizzle

    June 5, 2016

  • Well now I understand more what the JellyDolls is, and while I typically defend both the Dev’s with the Firestorm Viewer, as well as Linden Lab in many cases. This is something, I cannot get on board with. As this does not fix the problem, that we all have with grey avatars. This actually encourages the problem. And my personal feeling, is that this basically is nothing more then a dressed up version of Ruth Fix. But I do understand what LL is stating, with regards to the complexities of avatars causing lag. But turning a person green, blue, purple, red does not fix the problem as you might as well just say OK f it and turn them grey.

    So my question now, is since Linden Lab put Server Side Baking on the grid. why can’t LL tell the server to automatically optimize the avatar or viewer when entering a new region?

    So I kind of agree with most of the user base, if this is the best LL has to offer us. then just leave it alone, and let us use d-render people to reduce the lag. As there are short cuts, that allow users to d-render an entire region if needed.

    animorf Kawadias

    June 5, 2016

  • they think this is a good solution to solve client side lag and supposedly there will be an avatar complexity slider to either adjust or turn off, they also think this is a way to get people to come up with better hair and better attachments and better avies that don’t bog everyone else down, BUT I AGREE THOUGHT SERVER SIDE BAKING WAS SUPPOSED TO TAKE CARE OF THIS, AND IF THIS IS BEST THEY COULD COME UP WITH MAYBE THEY SHOULD OF LEFT IT ALONE, this is essentially the same as a ruth fix or turning people grey as you said

    Princss Alexis Hannah Greymyst

    June 5, 2016

  • I’ve been using the ‘Jellydolls’ feature for some time as it was included in the beta version that had graphics presets. In use, it’s not that bad. With the threshold set to the point that reducing it further had minimal effects on my frame rate in a crowded area, 80-90% of AV’s rendered. Increasing it to include the few that didn’t dropped my frame rate by 5-10 on average but caused a much larger drop more than once. It’s your choice to buy badly designed AV’s and attachments, but it’s now my right not to let that diminish my own SL experience. I will admit I’m a bit surprised LL would implement this, but I’m glad they have. I’m sure there will be some drama at first while people sort out who the creators making the really abusive items are. Those will either have to fix the issue or go out of business.

    I’m sure by the time Firestorm implements it, much of that will be taken care of. Getting graphics presets would be nice not to have to wait 4 months or longer for though. I understand if you’re waiting for Bento to finalize. That’s going to have to roll out fast once it goes fully live. I hope LL cracks the whip on that.

    Crim Mip

    June 5, 2016

  • how do they decide what is a complex item or an abusive item?
    is it prims? textures? scripts? badly-written scripts? badly made meshes ?
    how?

    Princss Alexis Hannah Greymyst

    June 5, 2016

  • The Avatar Complexity reading is the same as the Avatar Render Weight – just the name was changed. It’s also essentially the same as the old ARC – Avatar Render Cost, though the formula has been tweaked slightly since the days of ARC.
    The formula used to calculate the avatar complexity cost is basically still this one: http://wiki.secondlife.com/wiki/Mesh/Rendering_weight

    Whirly Fizzle

    June 5, 2016

  • Based on this post, it seems you don’t understand JellyDolls at all. First and foremost, it’s an optional feature. You don’t have to use it. It’s the alternative to derendering avatar attachments for those whose graphics performance is degraded by extremely high-load avatar attachments in their view, or derendering those avatars completely. I used to be one of those, before I got a computer with dedicated graphics processing. Not all are so lucky, so they can use this feature to lighten the load when avatars are too complex to draw easily. As I understand it, this may also render some of those graphics crashers ineffective, if the offending object is worn as an attachment. As soon as the avatar attaches such a thing, render complexity goes over the threshold and they become just a silly-looking silhouette. Brilliant, I say!

    Paige Theseus

    June 5, 2016

  • so basically it just another ruth fix or grey person fix but colourized

    Princss Alexis Hannah Greymyst

    June 5, 2016

  • wasn’t server size baking supposed to fix this?

    Princss Alexis Hannah Greymyst

    June 5, 2016

  • No, this has nothing to do with server side baking.

    Whirly Fizzle

    June 5, 2016

  • No.
    I’m guessing by “Ruth fix” you mean the option to show unloaded (cloud) avatars as a grey silhouette avatar until they load.
    The jellyDoll silhouette avatars are basically special imposters that display for avatars whose avatar complexity reading is higher then the Maximum Complexity setting you set in graphics preferences.
    This feature was added so the user can block fully rendering high complexity avatars to improve their viewer performance.

    Whirly Fizzle

    June 5, 2016

  • “As I understand it, this may also render some of those graphics crashers ineffective, if the offending object is worn as an attachment. As soon as the avatar attaches such a thing, render complexity goes over the threshold and they become just a silly-looking silhouette.”

    Yes that’s correct.
    As long as you don’t fully disable maximum complexity, you can stand right next to someone with a graphics crasher attached and be totally fine.
    The griefer avatar jellydolls almost instantly when they attach the graphics crasher object. At most you will experience 1-2 seconds of lower FPS & then performance is back to normal. Most importantly – no crash!

    Whirly Fizzle

    June 5, 2016

  • well I got to admit I do like the idea of not having to render griefer attachments if jelly dolls can stop that

    Princss Alexis Hannah Greymyst

    June 5, 2016

  • I don’t really understand your question Ani.
    The JellyDoll feature has nothing to do with serverside baking or the “Ruth fix”. I’m not even sure what you mean by Ruth fix actually.
    I’m guessing you are talking about the option to render unrezzed (cloud) avatars as a grey silhouette until they have finished loading.

    Whirly Fizzle

    June 5, 2016

  • the ruth fix , it is basically putting yourself as noob avie
    the ruth fix was commonly used when avatars were not loading and were doing the orange mist thing
    see reset defualt male and female avatars under character tests

    Princss Alexis Hannah Greymyst

    June 5, 2016

  • Ah gotcha!
    Well that “Ruth fix” will usually work to get your avatar rezzed if it’s stuck as a cloud.
    The usual cause of your avatar being stuck as a cloud is the avatar is not wearing one of the 4 essential base parts – skin, shape, hair or eyes.
    Replacing outfit will fix that problem as long as the outfit contains at least the 4 base parts, which the default female avatar does.

    This fix is nothing to do with JellyDolls though.
    JellyDoll avatars are not meant to render fully – they are supposed to look like coloured silhouettes.
    JellyDolls are blocked from rendering because their complexity is above your maximum Complexity setting in the viewer.

    Whirly Fizzle

    June 5, 2016

  • server side baking was meant as a means to make avatars rez faster, so this has nothing to do with the jelly dolls solution ?

    Princss Alexis Hannah Greymyst

    June 5, 2016

  • No, nothing to do with JellyDolls.

    Before Server Side Baking (SSA), avatar bakes were done locally on the users system, those bakes were sent to the region & the region sent the bakes out to all other viewers in the vicinity.
    This had many problems because the users system may have problems rendering or sending the correct local bake (old graphics drivers, antivirus software problems, poor connection etc) so it was fairly common for you to see the correct avatar bake locally & observers to see you stuck in the old avatar bake, or vice versa.

    With SSA, the avatar bakes are generated by the “bake ovens” on the server instead of the local avatar bakes.
    This is much faster & much more reliable then local avatar baking.
    SSA fixed a lot of bugs with avatar baking.

    The JellyDoll feature isn’t really anything to do with avatar baking.
    Removing high complexity avatars from the scene by rendering them as a JellyDoll could well speed up the loading of non-JellyDoll avatars in the scene though (actually the viewer performance will be faster overall) because the most complex avatars in the vicinity won’t be rendered fully.

    Whirly Fizzle

    June 5, 2016

  • So your second option is to kindly tell someone to detach there avatar because someone is lagging them?

    If Someone told me to remove something, I will not. They would have to leave or I would force them to leave because It’s my avatar and I can do whatever the hell I want because I have free will to wear anything I want.

    Sonic the Hedgehog

    July 12, 2016

  • I don’t like 4.7.7 because it steals over 10K of my inventory 🙁

    deviantdolliie

    June 5, 2016

  • Most cases of missing inventory are caused by a borked viewer cache & it’s easily fixed with a cache clear.
    While on Firestorm 4.7.7, go to Preferences -> Network & Files -> Directories -> Click the “Clear Cache” button -> Apply -> OK.
    Then relog into alow lag region, for example Pooley & wait for your inventory to fetch.
    If this doesn’t help, then work through the relevant steps on this wiki page: http://wiki.phoenixviewer.com/fs_missing_inventory
    If you still have missing inventory, then check that your inventory is all there on the LL viewer from https://secondlife.com/support/downloads/

    If your 10k of inventory is also missing on the LL viewer, then contact Linden Lab support by filing a ticket at https://support.secondlife.com/create-case/

    If your inventory is ONLY missing on Firestorm, then please file a JIRA issue (http://wiki.phoenixviewer.com/file_a_jira) & Firestorm support will help you.

    Whirly Fizzle

    June 5, 2016

  • This update bites the big one! I can’t take a snapshot without it crashing. If this continues I will be unable to continue working in SL. No Snapshots, no pictures of products, no business. Someone please fix this!!!!!

    FeydaAnn Ferryhill

    June 5, 2016

  • If you are on a Mac & only crash while saving snapshots to disk, then it’s probably the known Mac file picker crash.
    See this wiki page for how to stop the crashes: http://wiki.phoenixviewer.com/mac_crash_upload

    If not, and you only crash when saving very large sized snapshots when shadows are enabled, then check your settings for Shadows & Ambient occlusion – some of the shadow & AO settings exposed in Phototools can make you prone to crashes when saving supersized snapshots if they are cranked too high for your system.

    Go to World -> Photo & Video -> Phototools.
    On the Light, DOF/Glow & Gen tabs, click all the “D” buttons to reset those settings to defaults & then see if you still crash.

    If that doesn’t help, please file a JIRA issue (http://wiki.phoenixviewer.com/file_a_jira) so we can get your crash logs & see why you are crashing.
    Thanks!

    Whirly Fizzle

    June 5, 2016

  • Think I’m probably one of the few people that like the jellydoll idea.

    When I was a basic avatar, and started to buy mesh attire, beause Alpha’s could hide the basic sl avatar skin the mesh actually looked well made.

    Wasn’t until I went to Slink’s full mesh avatar and then tried to use same mesh on top of it, and come to realise that 75% of the mesh I had paid 1000’s for was actually total cr*p.

    This was mainly due to the lack of bone structure positioning, as most designers know on basic skeleton they can be as sloopy as they like and the alpha will hide that same sloppiness.

    So anything that makes creators and designers actually do decent work and optimise their works so everyone can use correctly, then to me that can only be a good thing.

    xXsnookumsXx

    June 6, 2016

  • This isn’t going to have any effect at all…zero…on designers to change their product. It’s going to hopefully encourage people to get computers capable of rendering properly.

    Lee McKay

    June 8, 2016

  • Well Lee McKay, that’s it!!! Screw you!!!
    I have seen these kinds of comments too often and if that is what people should do… Then you, if you have an inworld store, should be blacklisted and people should never go buy any crap that you are selling.

    If you don’t have, you should be permanently derendered, muted and blocked so no one ever has to deal with your bullshit opinions.

    NOT everyone has the damn money to buy a $2000.- computer so keep that fucking opinion of yours to yourself. Dumbass!!

    Kitty

    June 13, 2016

  • The moment halfway through reading a post, thinking it was a funny joke, then you realize the poor person was serious. So we should all wear 2005 noob outfits, because someone can’t afford a $300 computer? go fish. Also learn about the price of used pc parts, and what is ACTUALLY required to make SL run acceptably with good settings. you’ll be surprised of how stupid your statement sounds, afterwards.

    Someone that used to help

    July 7, 2016

  • 2000 for a new PC? So you want a gaming rig? My PC was 1500, but my 400 dollar PC ran SL just fine on low graphics. So what if people don’t come in all pretty and I lagged in certain places… I saved my money for a new PC that ran SL like a beast on high. Took me a few years, but I did it. And no, I can’t afford a 2000 PC. I just saved my money for it. 3:D

    Relle

    August 9, 2016

  • Whirly Fizzle

    June 7, 2016

  • I’m absolutely not against a new release with Jelly Dolls and security improvements.

    What bugs me is the timeframe and the problems involved with the upgrade. I did not upgrade yet, because I simply experienced problems due to the CEF upgrade and a new problem with texture rendering I was unable to sort out so far. Linden Lab could have done their home work regarding the necessity for the TLS 1.2 migration and the replacement for Quicktime long time ago.

    Shy

    June 7, 2016

  • What are the problems you are seeing with CEF & texture rendering?

    Whirly Fizzle

    June 7, 2016

  • Wish i could update but i cant, keeps yelling my graphics isnt suported, have tried but no succes. there is no update for my grapics either, so i really cant even if i wanted….

    littlebee Humby

    June 8, 2016

  • I suspect you are on Windows 10 with older Intel graphics.
    If that’s the case, you need to install the *32bit* version of Firestorm and apply the “Intel fix” as instructed on this wiki page: http://wiki.phoenixviewer.com/fs_intel_fix_32bit

    If this doesn’t help, please file a JIRA issue (http://wiki.phoenixviewer.com/file_a_jira) and support will help you get the update installed.

    Whirly Fizzle

    June 8, 2016

  • that worked, thanks

    littlebee Humby

    June 9, 2016

  • If you buy an item to rez on your land the creator almost always tells you ahead of time the number of prims and the land impact. The major issue right now is that nobody advertises render weight for items you actually wear. If that was a requirement it would make the whole jelly blob much easier to deal with. As it is right now, you could buy an item and not be able to wear it because of a horrible render weight. This happened to me recently with a necklace that was over 100k render weight on its own. Being forced to put on the marketplace render weights would go along way to making this transition easier on everyone.

    Ael

    June 8, 2016

  • Good idea. Buying a really expensive outfit/bling/gadget/weapon/whatever that you can’t use would get really frustrating. Would forcing vendors to disclose that be practical? (Demos should give a decent read on cost when they’re available, shouldn’t they?)

    Aden Davids

    June 25, 2016

  • The 4.7.7 heats up my graphics card BADLY, I had to downgrade to to still use firestorm. There is obviously some rendering or other 3D bug or bugs. 4.7.7 heats my graphics card to 67C while the other versions keep me around 37C to 43C depending if I’m in a new area.

    A Sl User

    June 11, 2016

  • 37C to 43C is the typical temperature for an idle card so I’m a bit surprised you run that low when logged into an SL viewer.
    67C is about normal when playing SL, especially if you have a laptop system, which all have poorer cooling then a desktop.
    When not logged into SL, my Nvidia 960M is ~40C & my Intel HD 530 is ~55C. This is on a fairly new Windows 10 laptop.
    If you feel that 67C is too hot. check that your graphics are set the same on both versions. You may have Advanced Lighting model enabled on 4.7.7, but not enabled on the earlier version.
    Imo, 70-80C is a pretty normal temperature when a card is under load, when playing 3D intensive games.

    Whirly Fizzle

    June 11, 2016

  • My card at startup idle is 22C, then after 10 minutes it at 32C if I do not do anything, after loading 4.7.7 it goes between 38C to 67C in a matter of about 45 seconds. On 4.7.5 it sticks around 36C-38C and jumps near 45C-47C when loading a new area but when goes down to 36C-38C. I been getting these temperatures with Firestorm for the past 2-3 years on the same desktop computer with a AMD Radeon HD 7950 Graphics Card. I was testing other viewers for TLS 1.2 compatibility and Cool VL Viewer and Singularity on HIGH i still stick around 38C-42C (I did this to test it), when I normally run Firestorm on low with Transparent Water, Lighting (FULL) and Bump Mapping and Shiny enabled as well as high terrain, Draw distance 64, particles max 256. This is the only version of firestorm i hit more then 47C on constant normal use. Even the Linden Lab Viewer 4.0.5.315117 I get the same temperatures as Firestorm 4.7.5 I just can’t use RLV functions as I normally do. So it has to be something with the new Firestorm 4.7.7.

    A Sl User

    June 14, 2016

  • I don’t really understand the need to write so much technical information about all this. This is not NASA, its just a computer program for a game. But in time since Phoenix was gone, Firestorm couldn’t replace all the joys that one gave us. Firestorm is one of the viewer that is coming down slowly and it will be like that until it finally dissapeares for good.

    Nose Resident

    June 11, 2016

  • SL is not GAME!

    Good Bye, Dead Emerald Viewer User. We hate you Emerald Users, Phoenix Viewer rose from the ashes of the now deceased Emerald Viewer.

    Sonic the Hedgehog

    July 12, 2016

  • I was using the fix version 47975 because my vídeo drivers has not new update. So now i need Use SL default viewer? and Forget Firestorm forever?

    SparkNoiZe

    June 12, 2016

  • If you have older intel graphics on Windows 10, then you need to install the *32bit* version of 4.7.7 & then apply the “Intel fix” – full instructions are here: http://wiki.phoenixviewer.com/fs_intel_fix_32bit If that doesn’t help, please file a JIRA issue (http://wiki.phoenixviewer.com/file_a_jira} & support will help you.

    Whirly Fizzle

    June 12, 2016

  • It’s funny how people find the smallest thing to complain about here, starting to think the majority of people are just flouncing.

    Rebecca Rathbone

    June 12, 2016

  • Before I was using the version: 4-7-5-47975_setup.exe
    with the fix version replaced: intel_fix_47975OS
    Now I was forced to install the version: 4.7.7 and the older fix does not work. So where i do download the intel_fix for version 4.7.7 ?
    Now i was using SL default viewer to login.

    SparkNoiZe

    June 12, 2016

  • The Intel fix for 4.7.7 is here: http://wiki.phoenixviewer.com/fs_intel_fix_32bit

    Whirly Fizzle

    June 12, 2016

  • Thanks

    SparkNoiZe

    June 13, 2016

  • I’m on Firestorm version 4.7.3.47323 (4.7.3.47323). I can’t see TVs or any media period already. It’s annoying because I could then it just randomly stopped. I can see thumbnails and hear (though it would freeze and can’t fix that either). YESSSS, everything is updated and meets the requirements. I was recently told I am having the issues because of Firestorms changes. So, does this mean if I update I can see movies, TVs and media with ease, control and perfectly?

    Naomi

    June 14, 2016

  • It’s hard to say what’s causing your problem with media on 4.7.3 without more information.
    If you are also unable to see web profiles or use search in the viewer as well then the most likely cause is your antivirus software is blocking slplugin.exe from running.
    Best thing to do is to update to Firestorm 4.7.7 and if you are still having media problems, let me know.

    Whirly Fizzle

    June 14, 2016

  • ” The TLS change isn’t live yet – it will be live on June 15th.”

    its June 14th, LL did set it up NOW !

    b

    June 14, 2016

  • The change isn’t live yet.
    If you are currently having problems buying L$, it’s probably because of the unscheduled maintenance – see https://community.secondlife.com/t5/Status-Grid/Unscheduled-Billing-Maintenance/ba-p/3039933

    Whirly Fizzle

    June 14, 2016

  • @ Whirly Fizzle
    tYvm, but when u fix 4-7-7-48706 for mac ?

    !!! worst fs ever for OS X 10.8 !!!

    0 CoreFoundation 0x00007fff92af5b06 __exceptionPreprocess + 198
    1 libobjc.A.dylib 0x00007fff9734c3f0 objc_exception_throw + 43
    2 CoreFoundation 0x00007fff92af5948 +[NSException raise:format:arguments:] + 104
    3 Foundation 0x00007fff8ee3c4a2 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 189
    4 AppKit 0x00007fff9119d976 -[NSEvent characters] + 179
    5 Firestorm 0x000000010649601e _Z23extractKeyDataFromEventP7NSEventP18NativeKeyEventData + 94
    6 Firestorm 0x0000000106497291 -[LLOpenGLView flagsChanged:] + 33
    7 AppKit 0x00007fff91305b81 -[NSWindow sendEvent:] + 8504
    8 AppKit 0x00007fff91301644 -[NSApplication sendEvent:] + 5761
    9 Firestorm 0x0000000105d12b92 -[LLNSApplication sendEvent:] + 146
    10 AppKit 0x00007fff9121721a -[NSApplication run] + 636
    11 AppKit 0x00007fff911bbbd6 NSApplicationMain + 869
    12 Firestorm 0x000000010465f134 start + 52
    13 ??? 0x0000000000000002 0x0 + 2

    Systemversion: OS X 10.8.5 (12F2560)
    Kernel-Version: Darwin 12.6.0
    NVIDIA GeForce GT 640M

    http://www.firestormviewer.org/firestorm-update-4-7-7-48706/

    b

    June 14, 2016

  • That crash will be fixed in the next release.

    JIRA issues:
    Firestorm viewer: http://jira.phoenixviewer.com/browse/FIRE-18016
    LL viewer: https://jira.secondlife.com/browse/STORM-2127

    Whirly Fizzle

    June 14, 2016

  • tyty 🙂

    b

    June 14, 2016

  • ********************UPDATE*********************

    The TLS 1.2 switch has been flipped.
    The good news is there is not much breakage at all on outdated viewers after all.
    See Inara Pey’s blog post – Second Life TLS 1.2 update – what works, what doesn’t.
    https://modemworld.me/2016/06/15/second-life-tls-1-2-update-what-works-what-doesnt/

    Whirly Fizzle

    June 15, 2016

  • I have updated to 4.7.7 very grudgingly for the 2nd time. The first time I had to downgrade because it was too laggy for me but since it was basically force upon us I didn’t have much of a choice or I wouldn’t be able to make any transactions. Anyways, I’m still lagging horribly and I tried another viewer but I just can’t get used to it so I’m basically stuck with FS also for personal reasons.
    Anyways, the one this I absolutely HATE about FS 4.7.7 is having my auto responses appear in my IMs when someone IMs me. I don’t need to see my auto responses, I wrote them out, so obviously I know what they say so what is the point of having them appear in EVERY IM I get?
    I sincerely hope that gets re-disabled in the very near future because its very annoying. I keep my auto responses activated because I have people that think they need to spam me or conference chat me every 2 seconds or try and tp me every other second.

    PLEASE FS team, take that back off. It was nice not seeing your own auto responses in your IMs. It’s VERY annoying and when you have a rather lengthy auto response, you miss messages that could be important and I have cataracts and when you have trouble seeing, it makes it all that much more difficult.

    miranda Sapphire

    June 16, 2016

  • Are you only suffering from lag on Firestorm 4.7.7 or is this a problem on all viewers?
    We actually had a request to make your auto-response message visible in your IM window, so this seems to be something people wanted.
    That change could be made optional though.
    File an improvement request JIRA issue (http://wiki.phoenixviewer.com/file_a_jira#how_to_give_us_your_logs) & ask for it to be made optional.

    Whirly Fizzle

    June 19, 2016

  • It’s VERY annoying to have a long autoresponse, as you say.. so PLEASE cut it down to an acceptable level. *facepalms*

    Someone that used to help

    July 7, 2016

  • I use older viewers as well… no problems with inworld purchases at all whatsoever. This is typical make believe… to scare.
    Yes you can’t buy L$ inworld with an older viewer, but other than that… no problems whatsoever. I never buy L$.

    The rest where real money is being exchanged from and to L$ (which is via the webbrowser) needs TLS 1.2. Which is webbrowser
    based. All of those are 1.2 compliant since years.

    Inworld payments… 0.0 problems with older viewers so far with any viewer. It may change but that’s just not now.

    Please don’t copy simply what LL communicates without any criticism… They are prone to make believe very strong….
    Sure things will change over time, but no panic.
    Having the latest viewer usually is trouble… specially FF which is very buggy (all releases).

    I always skip updates unless i really have to… Makes the experience speed up and much more reliable.

    Linda Brynner

    June 20, 2016

  • “Having the latest viewer usually is trouble… specially FF which is very buggy (all releases). I always skip updates unless i really have to… Makes the experience speed up and much more reliable.”

    WTF?!?! And how the HELL do you know that FS is just ohhhh so riddled with bugs, in every release, when you just sit on your ass and stagnate with old ones?

    How about taking care of your system so it will take care of you? Or educating yourself to learn what your system is/isn’t capable of? THAT’S advice worth listening to, guys.

    Coming from someone who updates as soon as one is available, and been a avid SL user for over SIX YEARS.

    Leona

    June 22, 2016

  • “Inworld payments… 0.0 problems with older viewers so far with any viewer. It may change but that’s just not now.

    good to know, tx !

    Please don’t copy simply what LL communicates without any criticism… ”

    yes. LL is LLame 😛

    b

    June 24, 2016

  • Please everyone update your system and connection – I don’t want to look JellyDoll to you!!! :((((

    Ziggy Alcott

    June 21, 2016

  • Updating has caused all sorts of problems with my avie and I really regret doing so. I placed a ticket and nothing has happened! I cannot enjoy the game this way, and Im going to have to cease from using this viewer.

    Kiara Mazi

    June 22, 2016

  • Robert0 gave you some suggestions on your support ticket at http://jira.phoenixviewer.com/browse/SUP-17178

    I’ll leave you a comment on your ticket too.
    From your attached images, it looks like you have a mesh avatar & the mesh is rendering in a corrupted way. Do you happen to be using Webroot antivirus software?

    Whirly Fizzle

    June 24, 2016

  • Okay I started getting blurry vision trying to read through all of this. I had to do the client fix for the work around for the video card on the last version. I’m not going to be going out to buy a new laptop any time in the near future. Can someone tell me how this client is affected by that?

    Noel Zelmanov

    June 23, 2016

  • I’m guessing you mean that you had to apply the “Intel fix” here http://wiki.phoenixviewer.com/fs_intel_fix_32bit

    Any viewer that includes the Windows 10 manifest (which is needed to correctly detect the Windows 10 operating system) will have this problem for systems with Intel cards that are not supported by Intel for use on Windows 10.
    Any card with a “No” against Windows 10 support on this list are affected: http://www.intel.com/support/graphics/sb/CS-034343.htm
    Other viewers which use the Windows 10 manifest & have the tools update changes will also be affected, for example Alchemy & the new release of Singularity.
    The LL viewer is not yet affected because it doesn’t use the Windows 10 manifest but as far as I know, it’s being added soon.

    There is nothing really that can be done about this unless Intel decide to support those cards & create drivers compatible with Windows 10 & it’s most likely they won’t. They consider those older cards as on legacy support now.
    The Intel fix is just a replacement binary that has the Windows 10 manifest stripped out.
    This fix will only work for the 32bit version of the viewer. The 64bit viewer version will just crash when doing the benchmarking tests, even with the manifest removed. Again, it doesn’t look like this can be fixed for 64bit on the older Intel cards for systems on Windows 10.
    So most likely if you have an affected Intel card on Windows 10, you will only be able to use the 32bit version of Firestorm & apply the Intel fix for all future releases.
    If you wish to use the 64bit version of Firestorm then you will need to roll back to Windows 7 or 8.1. There shouldn’t be any systems that came with Windows 10 pre-installed with an unsupported card.
    You may also have the problem with the same cards on Windows 8. The fix for that is to update to Windows 8.1.

    Whirly Fizzle

    June 24, 2016

  • i downloaded the latest firestorm the 4.7.7.48706 and when i signed on i was a cloud i tried to relog that didnt work , i tried to restart my computer that didnt work , i tried other versions of firestorem still i was a cloud so i went back to this current version i even did a character test and a force appearance update (rebake) and still that did not work im still a cloud what else can i do to fix this

    sherrimoon residend

    July 5, 2016

  • Hmm a character test from Avatar -> Avatar Health -> Reset default male/female avatar usually fixes a cloud avatar problem – most times it is caused by not wearing one of the 4 essential body parts, skin, shape, eyes or system hair.
    Try going to a different region & then doing another character test or outfit replace. It’s possible the region you were on is broken after today’s rolling restart – there seem to be quite a few regions that came back online in a bad state.
    Also see http://wiki.phoenixviewer.com/fs_bake_fail

    Whirly Fizzle

    July 5, 2016

  • Am I the only one who had a horrible experience with this update? I mean every time I try to log in, I crash. I cannot get at least 5 minutes of game play w/o crashing. >.> Is it my computer?

    niceperson123

    July 8, 2016

  • It’s impossible to say what’s causing the problem without more information & viewer logs.
    Best thing to do is to file a JIRA issue (http://wiki.phoenixviewer.com/file_a_jira) & support will help you.

    Whirly Fizzle

    July 10, 2016

  • Are there any long term plans of supporting VR view (borrowing and updating code from CtrlAlt viewer or from Oculus project viewer, for example) now that LL might be dropping the support for Oculus consumer version?

    Random metaversian

    July 9, 2016

  • As far as I’m aware, CtrlAltStudio viewer doesn’t support the CV1, only the DK2. The CtrlAltStudio code viewer is also based on a very old Firestorm code base so it wouldn’t be straight forward just to port over his changes to Firestorm now. None of the Firestorm developers has a Rift so it’s pretty unlikely Rift support would be added to Firestorm unless LL add it to their viewer first. If the devs cannot test with a Rift, you would end up with a viewer a lot more buggy then the latest LL project viewer even 😉 It looks like the CtrlAltStudio dev is looking at adding support for the CV1 though, since LL pulled their project viewer: http://ctrlaltstudio.com/blog/2016/04/05/oculus-cv1-support

    Whirly Fizzle

    July 10, 2016

  • I STILL cannot install 4.7.7 on Win Vista 64, even after hours of research, reinstalls, and restarts. I’ve tried everything I could find from across the internet, including the typo-riddled AppFix from Firestorm. Nothing works.

    Are you ever going to address and fix this issue? Or should I go find another viewer to use?

    Machaer

    July 13, 2016

  • There isn’t a workaround – you cannot install the 64bit version of Firestorm on Vista, it’s a bug, see http://jira.phoenixviewer.com/browse/FIRE-17953
    The bug is already fixed for the next release.
    For now you can install the 32bit version of Firestorm, that will work just fine.
    Be aware though that you should be thinking about updating to Windows 7 or later. Once CEF is updated to a more recent version, no media will work on Windows Vista, including the ability to use search or view web profiles.
    There is nothing we can do about this, CEF/Chromium & Google (Chrome) all stopped supporting Windows Vista at the same time as XP.

    Whirly Fizzle

    July 14, 2016

  • Ah, KNOWLEDGE at last! Thank you for the info.

    Yes, I looked at FIRE-17953, that was near the end of my search for answers. I’ll muddle through until I’m able to upgrade to a desktop, and thus, the OS. I’d rather not use another viewer, I am to used to Firestorm after a few years. Thanks again for the reply.

    Machaer

    July 16, 2016

  • Reading all those posts makes me appreciate just how patient and knowledgable Whirly is. Wow.

    Jayd

    July 27, 2016