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

Firestorm Release 5.0.7.52912

translation services

It’s been a whopping six months since our last release, so this one is well overdue. We’ve had oodles of QA testing time with this build, and a special thanks goes out to our dedicated Beta testers and our contributing Preview group members.

This version brings us up to parity with LL 5.0.5 codebase, and although this release doesn’t have a lot of new shiny features, it sure is loaded with bug fixes, so we’re still considering this a significant update. With this release we will stick to our three-version rule, and in two weeks’ time we will apply a block to our three-versions-old 4.7.7 for Second Life logins. It will continue to work for OpenSim. Versions 4.7.9 and 5.0.1 will continue to be usable for now.

It is worth noting that a great deal of this release comprises bug fixes, features and improvements from Linden Lab. They’ve been VERY busy and VERY productive, so folks shouldn’t be saying LL isn’t actively developing, because they sure are, and they deserve lots of credit for their efforts.

 

A short list of highlights is below, and there’s a full change log and a comprehensive review by Inara Pey:

  • New region and parcel access controls (Linden Lab);
  • Added ability to set custom folders for uploading items (Linden Lab);
  • Fixed broken scaling & bounding boxes when uploading mesh in multiple parts (Linden Lab);
  • Added group ability to “Ignore Landing Point” (Linden Lab);
  • Added “Duplicate” feature into Build-Object submenu (Linden Lab);
  • Added “Copy outfit list to clipboard” for Current Outfit folder (Linden Lab;
  • Improved layout of the Snapshot floater (Firestorm);
  • List the attachment spots in “Attach to” lists in alphabetical order (Firestorm);
  • Added toolbar button for “Show friends only” (Firestorm);
  • Many more including countless bug fixes, performance improvements, crash fixes etc.

 

As always, we recommend doing a clean install, but it is not necessary. For a text tutorial on how to do a clean install, CLICK HERE, and for a video tutorial, CLICK HERE.

 

  • Difficult to judge about productive or not. These enhancements are really small, and the list of bug fixes is not that long either. When we say they deserve credits for their efforts, it makes it sounds like they are not paid developers and that there is only one developer who has to do all that by himself. I’d call them productive when you know exactly how much resources are committed to what goals, and whether they have accomplish them time or not.

    Stweed

    June 21, 2017

  • I was wondering how long it would take for a grouchy comment to appear *shakes head*..

    Chuck El

    June 21, 2017

  • Yes, it is bad that the first comment on a new release has to take a negative spin, but i guess that is the nature of people. We are quick to criticise and slow to applaud and say thanks.

    soda sullvian

    June 21, 2017

  • Totally agree with you @Soda Sullvian,
    @Stweed needs to show what he/she has done to contribute to the running of SL, to develop it, and all the other things he/she spewed above.

    I beta test Firestorm so I get to see the improvements as they happen 🙂

    Well done LL and Firestorm for the new release.

    xXsnookumsXx

    June 21, 2017

  • The list of changes in this blog post is only a tiny number of all the fixes & new features in this release.
    For the FULL list, please see http://wiki.phoenixviewer.com/firestorm_change_log_5.0.7.52912#change_log_since_50152150_release

    If you want to see all the code too, go to http://hg.phoenixviewer.com/phoenix-firestorm-release/log & start at commit 52912 and work your way back to commit 52151.

    If you still don’t think that’s a lot of work, then there isn’t anything I can say to convince you otherwise 😉

    Whirly Fizzle

    June 24, 2017

  • And the prize for the whining dickhead of the year who offers nothing constructive whatsoever goes to … Stweed! Come on up and collect your trophy. Like your comment, it consists of dross.

    Rufus Attis

    September 11, 2017

  • I will withdraw my previous comment IF people who have done this work are not paid developers or they are offering their free labor to the SL community. If this is the case, they deserve to be named as our heroes and we should make a bigger effort to recognize these heroes !!

    Stweed

    June 21, 2017

  • since you feel it is so easy, I am anxious for the release of your viewer.

    soda sullvian

    June 21, 2017

  • Do you have ANY idea of what goes into coding? This is version 5.0.7… and the one in current use is 5.0.1 – It’s always trial and error, especially when working with new features, since you have to figure out how to make everything work together. New coding to make, old coding to adjust, test test test test…. Small list? A LOT of effort to get it done.
    Paid or not – it’s still a lot of work put into each update.

    kaia krystal

    June 21, 2017

  • Firestorm people only listen to bugs and suggestions from their friends and entourage; several of my friends placed the same two requests and they couldn’t care less. We have been bitching like hell about that stupid outfit problem and the fact that the groups we choose NOT to have the chat enabled, enables by itself. But since we don’t lick Jessica’s ****, we’re not heard.

    Leda

    June 21, 2017

  • You are aware that if a bug exists in the LL code that the Firestorm team has to wait for LL to fix it. They can and do fix bugs in the actual Firestorm code. A good way to check is to run the LL viewer and see if the same issue happens. If it does, file a Jira with LL if one doesn’t exist or upvote if one does.

    Crim Mip

    June 22, 2017

  • What outfit problem?

    Tamraen

    June 24, 2017

  • What are the two requests? Did you file JIRA issues for them? If you did please can you give me the links to the JIRA issues.

    I don’t know what outfit bug you are referring to. Can you give more details or a link to your JIRA bug report?

    Re the group chat issue.
    If you have “Receive group instant messages” unticked for Group A and you then manually open Group A chat, this will cause the “Receive group instant messages” setting to be set to enabled.
    This is expected behaviour – the same thing happens when you send an IM to a blocked avatar, it causes the avatar to be removed off your block list.
    There is also a problem when “Receive group instant messages” is unticked but sometimes you still receive messages from that blocked group just after login.
    Unfortunately this can’t really be properly fixed without serverside support for group chat muting being added. Group chat mute is a Firestorm specific feature with no serverside support.
    If you have a chatty group that’s likely to post a new chat message while you are logging in, a few messages may sneak through.
    Unless LL decide to add serverside support for group mute, I’m afraid this is as good as it gets.

    Whirly Fizzle

    June 24, 2017

  • “Backspace won’t act as delete on Windows…” REALLY? – I used to hit Backspace to delete, now what?

    Abby Fraser

    June 21, 2017

  • Well, I would think that since pretty much ALL Windows Keyboards have this little thing called a “Delete” key… that you would use THAT one. Since that is the function normally assigned to it anyways.

    KendraD

    June 24, 2017

  • Unfortunately it became apparent that people were accidentally deleting inventory items by hitting the backspace key in error. Because this looked to be a common case of inventory loss, LL decided to disallow backspace as delete on Windows systems & Firestorm picked up that change. Backspace will still delete on Mac as there is no delete key on a mac keyboard.

    Whirly Fizzle

    June 24, 2017

  • “list of bug fixes is not that long”
    right….there are over 50 fixes, changes and improvements since the last release. I don’t know what counts as long but that doesn’t include every change not listed from the LL changes which FS has caught up with. Firestorm developers and the beta testers are voluntary and unpaid. Obviously the LL developers are paid but that has nothing to do with the extra features added to Firestorm. As always I should point out I use a variety of viewers on Windows and Linux, not just Firestorm, lest I be accused of being a Firestorm zealot 😛

    Mondy Brangwin

    June 21, 2017

  • As far as im aware all Firstorm devs are NOT paid and DO this for the Sl community

    Jenny

    June 21, 2017

  • Correct, no one on the Firestorm team is paid. We are all volunteers.

    Whirly Fizzle

    June 24, 2017

  • If I run the same global company of 5000 employees and pay over USD 130K to senior developers, I will not use the word “very productive” to describe the LL release, and I will point out that the release only has 31 minor bug fixes, and not to suggest people get the credit they deserve. The post is a bit misleading. Even with 1% of employees to work on this, it is not a very productive release by any industrial management standards. Maybe the author is being sarcastic to motivate management to do better next time!

    Yes, Soda. I can probably give you 2 viewer releases with half the size of the company.

    Stweed

    June 21, 2017

  • You are a bit ignorant, just saying. There are around a dozen devs still working on SL on the server side. I’m not sure how many are working on the viewer itself since that’s subcontracted (bet you didn’t know that). There aren’t a lot of new wizbang features the last little while in either the LL Viewer or in this Firestorm release. There have been a LOT of bugs dealt with though. Not mentioned is the improving of code that wasn’t buggy, but just not very well written. I’m glad this release happened. It means if a major new feature is released it won’t be nearly as arduous to merge the code. I honestly wish they’d do this more frequently, but it is being done by volunteers.

    Crim Mip

    June 22, 2017

  • This was very much a “Maintenance release” with lots of bug fixes rather then big new features yes.
    However there were a lot more then 31 minor bug fixes – not sure where you got that number from.

    For the FULL list of all commits, please see http://wiki.phoenixviewer.com/firestorm_change_log_5.0.7.52912#change_log_since_50152150_release

    If you want to see all the code too, go to http://hg.phoenixviewer.com/phoenix-firestorm-release/log & start at commit 52912 and work your way back to commit 52151.

    Whirly Fizzle

    June 24, 2017

  • Linden Lab is not a 5000 employee organisation; they total less than 500 employees and this includes Blockworld and Sansar teams as well as Second Life.

    Beq

    June 24, 2017

  • Don’t know why some are bitching about fixes? I been in here 9 long years now, and you know what, ? There are still archaic bugs that still remain, that LL dont want the bother to repair. Firestorm team can only improve Second Life as far as LL infrastructure will allow it. This is now a shameful dinosour that in real terms compared to gaming and Simulators 8 years on has not changed in any big way , except for mesh. The fact remains as an Airport owner, i have given up finding £50 a week for these, because LL still wont take the time to try and make sailing and flying fast Aircraft seamless oceans. Its no good forking out 5000L$ for the latest Boeing 737, if it doesn’t get to its destination 60% of the flights. Mainland is a mess, You still can’t terrain properly, which makes parcels not worth buying, nothing has been done by LL to stop cagers, and greifing tools to be used from outside an adjacent Parcel. I have had to buy an expensive maligna X hud, to stop farting idiots from ruining my sim. So i gone back to estate Homestead where 5000 prims and if you find a good landlord (NOT a reseller) thats a huge improvement for us UK folk struggling with day to day $=GBP rate fluctuations. I have challenged LL many times, that their currency can not be play money, because its floated on the real time Worlds financial economy, and I dont see this on WOW or Star Wars, or the Walking Dead MMORGS. Firestorm does a good job in my opinion, Its LL stuck in 2006 still, and lately, Clubs have actually been discriminating against what people wear. I was ejected from a sim the other day because my body is the old one from my day rezz October 2007. because i didnt have a mesh body or Clothes, I was shockingly ejected for not meeeting the high standards.!!!!!!!!! What about the high stanadards of £3000 I have paid out to LL since 2007, and for me, into aviation and rescue craft, Nothing has changed to make flying and sailing better than it was in 2010. I find the Firestorm the best so far, mt win 7 gaming comp dont like phoenix for some reason and crashes on start up. I got no complaints about Firestorm and will upgrade it later,. thanks for all you hard work

    michaela destiny

    July 2, 2017

  • Sheesh, give it a rest already! How much more of a fool are you going to make of yourself? How much deeper the hole you’re going dig for yourself?

    Rufus Attis

    September 11, 2017

  • No! I have to agree with Stweed since there is only one developer that developer is way too slow releasing new versions of Firestorm. People can get very impatient waiting for a new update especially when the support team can’t help you with the issues. I would know because I have dealt with an issue they can not solve for me, and ever since these new releases of Firestorm. When the older versions were around I never suffered the issue that I do have now. They keep saying it’s not a firestorm well I am sorry to say it is a Firestorm because many, many years ago on the old version of Firestorm I never had those issues. I think they have done something to the code of Firestorm which reproduces the problem. But, on the side not of everything else it looks great works fantastic for everything else. Now I might of said this before in the past, but there is one thing that the developer should have not removed in Firestorm, and that is the translator in Firestorm I will tell you why now. There is people all over the world in Second Life that do not speak English I have seen it a lot, and I have seen them buy the google translator hud to translate there language to English. I feel, as if, this was a stupid movie, and I wish for it to be brought back in the near future.

    Patrick Stargazer Skeetman

    June 21, 2017

  • No, there is not just “one” developer. There is a team working on this viewer, for free, giving up their time so that people like you can moan and complain at their hard work. Just because you don’t know who they all are doesn’t mean they don’t exist.

    Mondy Brangwin

    June 21, 2017

  • Patrick,

    Please read this in its entirety, because I am attempting to educate you as to how things really work. First of all, it is not very nice of you to complain about a free product that is put out by people doing this for free. Yes, that’s exactly what the Phoenix Firestorm team is. A group of people like you and me, with programming skills, who put out a viewer to log into Second Life. They do not get paid for this. They are not employed by Linden Labs.

    For someone without any knowledge of how developing software works, you seem quite confident to diagnose problems and point out flaws. For instance, you have said that you know for a fact that a certain feature used to work but now it doesn’t and that is proof that they can fix it.

    This is similar to saying that you know that your tires can give you a smooth ride because you’ve had a smooth ride before. When your mechanic points out that the tread is fine, you complain and complain. Finally, they give you new tires, and then you’re upset when the ride STILL isn’t smooth when you drive down the unpaved and rocky road that you forgot to mention to your mechanic.

    The point I am making is that there are a LOT of complex interactions that take place in order to make SL work. And when I say a lot, I mean millions. Yes, millions, when you break them down into tiny pieces. Windows plays its part, the Internet (TCP/IP) plays its part, your video card plays its part, the LL servers play their parts (and so does the O/S that runs the servers), and Firestorm plays its part as well.

    You simply do not KNOW what worked years ago and why. You’re guessing.

    Software developers spend months and years to create something that is insanely complex and wraps it up into a neat interface for you. You are either ignoring, discounting, or have contempt of the fact that you cannot see 99% of what happens behind the scenes.

    A lot of development is invisible. The foundation. Just because you don’t see it, doesn’t mean that significant efforts weren’t made.

    Eric

    June 23, 2017

  • What is the new problem that you only have on more recent versions of Firestorm?
    If you filed a JIRA issue, please give me the link to it.
    Firestorm still has 2 working translators: Preferences -> Chat -> Typing -> Translation. However, the Google translation services are not free & never have been. If you pay Google and get a Google API key, you can use the built in Google translator. The Bing translator, which is free, still works for those who already have an old Bing AppID. But Bing no longer provides new AppID keys so you can’t use this service unless you already have a key. There is nothing we can do about the fact Microsoft killed the Bing translation service. Hopefully in the future a new free translation service can be added.

    Whirly Fizzle

    June 24, 2017

  • Yes, we can see why. 🙂

    Rufus Attis

    September 11, 2017

  • /me shakes my head and agrees with soda
    Thank you FS team for all you do. 🙂

    Ziggy Alcott

    June 21, 2017

  • To clarify, my comment is not referring to Firestorm team effort into getting the release out. My comment was referring to the last paragraph regarding calling Linden Lab efforts very productive. (I am not trying to say that LL is unproductive either. I don’t even think that LL developers themselves think they are too productive either) I understand that FS team relies on releases from LL in order to integrate into the FS release.

    Thank you for all comments, and thank you for the blog admin in accommodating my different point of view.

    Stweed

    June 21, 2017

  • LL certainly has a lot of developers on hand, but how many are actually working on the SL viewer? I have no numbers, but i will guess not many. I think most have moved over to Sansar and what we are seeing now is that a few developers who really like SL have stuck around and are, by any measurement, being more productive than what we were getting two to three years ago…with supposedly more people. Try some of the beta viewers and look at what all they are doing and it is a measurable increase in effort by a smaller group. I say kudos to them, paid or not, for picking up the pace.

    soda sullvian

    June 21, 2017

  • kaia krystal … can you point me to one specific bug fix / enhancement in this release that is not minor, such that we can all appreciate more? Put things into context for us, so that people can truly appreciate and perhaps learn something. I personally know some of the FS developers, and I also looked at the code commits, and I led much bigger software development projects in the industry, so I think I know what I am talking about.

    Stweed

    June 21, 2017

  • Does anyone able to get this new texture changer to work? I press ctrl- dot and comma, nothing happens. Texture not cycling through. What did I miss?

    Dave

    June 21, 2017

  • Please try this & let me know if it works.

    1) Rez a box & edit the box (right click -> Edit).
    2) In build tools, select “Select face” & left click one face on the box so it is highlighted.
    3) CTRL + . should then select each face in turn.
    CTRL + , should select each previous face in turn.
    SHIFT + CTRL + . will include the next face in the selection.
    SHIFT + CTRL + , will include the previous face in the selection.

    4) Link a few boxes together to form a linkset.
    5 ) Edit the linkset & enable “Edit Linked”.
    6) Select one link in the linkset.
    7) CTRL + . should then select each link in turn.
    CTRL + , should select each previous link in turn.
    SHIFT + CTRL + . will include the next link in the selection.
    SHIFT + CTRL + , will include the previous link in the selection.

    Also see the top menu bar of the viewer, Build -> Select Elements.

    Whirly Fizzle

    June 24, 2017

  • Thanks Firestorm team. I like your viewer very much.

    Minetheree

    June 21, 2017

  • So do I, but I have one very small request if anyone is listening. (Yes, I just piggy-backed. I’m a bad boy. Slap my wrist!) No doubt others have requested this before me, but I’m going to request it again. Like so many others, I suffer from the “splayed fingers” irritant EVERY TIME I TP into a new place. Of course, this can be solved by going through the Avatar>Avatar Health>Stop Avatar Animations routine, but this involves 3 clicks EVERY time, which is wearisome, to say the least. Any chance of a shortcut?

    Rufus Attis

    September 11, 2017

  • Hi Rufus, sorry for the slow reply here.
    Are you by chance wearing Bento hands?

    Whirly Fizzle

    September 22, 2017

  • Sorry, a question comes to mind reading Inara’s blog:
    “Fix for user never de-clouds with a large inventory after inventory fetch (BUG-6192)”

    What is that large inventory size please?

    Minetheree

    June 21, 2017

  • As far as I can tell, that fix just makes the contents of the Current Outfit Folder try to fetch first, rather then being one of the last folders to fetch in inventory.
    There isn’t really a specific size of inventory that caused the problem, just the larger your inventory was, if you logged in with a clean cache it would take a while to rez your avatar while waiting for the Current Outfit folder contents to fetch.
    When this happened, if you manually expanded the Current Outfit folder to force it to fetch immediately, that would work around the problem too.

    Whirly Fizzle

    June 24, 2017

  • Download the installer, uninstall the version I am using, install the new one… wait wait wait… for 5 hours with a window installer with: greyed out cancel button, greyed out back and close button.
    Really, you should improve that basic thing… so far still stucked in the extraction of the plugin dlls. Will think it twice before updating anymore… since it takes soooooo much.
    Other than that so far I have not a problem with firestorm.

    User of firestorm

    June 21, 2017

  • The installer should take nowhere near this long. Firestorm should install in a couple of minutes.
    It sounds like something got stuck. Please reboot your computer and try running the installer again.
    The problem could also be caused by your antivirus software or even Windows waiting for a prompt from you to allow the install.
    Check in the bottom taskbar to see if there is a prompt hidden there asking your permission to proceed.
    If you are still having problems getting 5.0.7 installed, please file a JIRA issue (http://wiki.phoenixviewer.com/file_a_jira) and support will help you.

    Whirly Fizzle

    June 24, 2017

  • Well. The foregoing is a bit of a moan fest, but by and large this is a good release (good, not great and I certainly didn’t feel the earth move for me on first login). However it is a good product of the hard word of a number of folk, most of whom will never see a cent for their effort.
    Thankyou Firestorm Developers.

    Ayesha

    June 21, 2017

  • Atualizei meu fire, mas a nova versão não abre, fica dando erro de crash e que precisa ser fechado, nem abre, já dá o erro ao tentar carregar, meu windos é o pro 10. Não sei o que fazer. Me ajudem por favor!!!!

    cristiany castro

    June 22, 2017

  • Translation [Portuguese]: I updated my fire, but the new version does not open, is giving crash error and that needs to be closed, nor open, already gives the error while trying to load, my windos is pro 10. I do not know what to do. Help me please!!!!
    —-

    Oi Cristiany,

    Tenho medo de não saber qual é o problema sem mais informações.
    Por favor, você pode enviar um problema no JIRA (consulte http://wiki.phoenixviewer.com/file_a_jira) para que possamos obter as informações do sistema e os logs do visualizador para ver o que está causando o problema.
    Obrigado.
    —-

    Hi Cristiany,

    I’m afraid I don’t know what the problem is without more information.
    Please can you file a JIRA issue (see http://wiki.phoenixviewer.com/file_a_jira) so we can get your system information and viewer logs to see what’s causing the problem.
    Thanks.

    Whirly Fizzle

    June 24, 2017

  • Hello,i installed the new version and start testing it…when i take pics in high res,no shadows or aanything on (as i ussed to take with last version) after i save it the iewer crashes -_-
    I choosed to install the update as i was hoping for a fix with my FPS issue i have on my main account,for weeks now (issue i have put in a jira post but nobody gave me any answer…odd) but no..it didnt fixed that either and worse,this crash issue made me uninstall it 🙁
    Pitty…

    adriana pinklady

    June 22, 2017

  • Can you give me the link to the JIRA issue you filed & I’ll take a look.

    I can only take a guess what’s going wrong with saving the snapshots without more information, but please try this & let me know if it fixes the problem.

    Top menu bar of the viewer, World -> Photo & Video -> PhotoTools.
    In PhotoTools, under the Light tab, click all the D(efault) buttons to reset the Shadow & Ambient Occlusion settings to default.
    Some of those settings are pretty dangerous (especially Shadow Resolution) & they can cause performance loss if left enabled when not taking snapshots.
    Having too high a Shadow Resolution setting for your card can also cause the viewer to crash when saving large snapshots.

    If that doesn’t fix the problem, please can you update your existing JIRA issue with the details.

    Whirly Fizzle

    June 24, 2017

  • I saw you posted the JIRA issue in your comment below. Thanks!

    Whirly Fizzle

    June 24, 2017

  • Kudos to the team!

    Sylvie Jeanjacquot

    June 22, 2017

  • LL does release updated versions on regular basis, As i’m being a LL viewer regular user can attest.

    zz bottom

    June 22, 2017

  • ((hugs))

    As always big thanks to the FS team. They do a lot of work and are great representatives for the SL community we are all part of.

    Having said that, we have to remember that the FS team of volunteer developers can probably only to a very limited extent venture into debugging LL code and apply FS bug-fixes not pertaining to FS add-ons. Looking-away from the likely lack of access to any of the special debugging-aids which (are/ought to be) available to the LL development team, It will cause a maintenance nightmare as LL continue to pour-out updates.

    And believe me, I know what I am talking about, after having worked with software engineering and operating systems for 30+ years.

    marjolaine

    June 22, 2017

  • Update for my previous comment 🙂
    I have updated my AMD vcard driver,to the last version and reinstalled this Firestorm update.Still testing but for now i dont crash in teleports(thing previous happent when i tried to use a newer vcard driver),the FPS issue is still there(see my post https://jira.phoenixviewer.com/browse/SUP-18482),i still crash when i try to take high res pics but not all the time(thats weird). Will come up with more updates (if im allowed)
    Thank you

    adriana pinklady

    June 22, 2017

  • Thanks for the JIRA issue.
    I’m leaving you a comment there now.

    Whirly Fizzle

    June 24, 2017

  • Update ^^
    The FPS issue got worse than it was with previous version,also there is another issue i noticed. Some mesh clothes just get “broken” and only if i detach and put it back the problem is solved,altho on the next tp they break again 🙁 This also never happent with previous version

    adriana pinklady

    June 23, 2017

  • I made a note of your forum comments on your JIRA issue & I just left you a reply there with the information I need.

    I suspect the “broken mesh” issue is actually this:
    https://jira.secondlife.com/browse/BUG-7239
    https://jira.secondlife.com/browse/BUG-6803
    https://jira.secondlife.com/browse/BUG-11309

    Those are all essentially the same bug – mesh will get stuck at a lower LOD level until you right click the mesh or zoom the camera in & out. Sometimes it even needs a relog to fix it.
    This problem is the most common just after login or after a TP or after being zoomed far out with your camera & zooming back.
    This issue isn’t new on Firestorm 5.0.7 though, it’s a pretty old bug affecting all viewers so I’m not sure why you are only seeing it now.
    We’ll work through the problem on your JIRA issue though in-case it’s something new.

    Whirly Fizzle

    June 24, 2017

  • Hello,thank you so much for looking into my problem. I have sent all the infos you asked (hope i did it right)
    For now,i see the crashing during snapshot is gone i just hope it stays that way…about the lag i experience with the new update,i see im not the only one complaining…
    The broken mesh thing seems it didnt affect me untill now..so i dont know (?!) if its the viewer or the new vcard driver( i had to use a very old driver for few years now,bcs when i tried to update i couldnt use the FS atall,i was just crashing and crashing no matter what i was doing,just trying to tp or simply sitting in one place. Now im updated to last driver for my AMD vcard)

    adriana pinklady

    June 24, 2017

  • Hello Firestorm Team,

    Thank you for this update! It took less than 10 minutes to download yesterday. I did completely remove the previous version including from my registry. This version seems to be faster… loads faster and my animations via the built-in viewer respond faster. I already had high performance from the previous version. I did read about all the bug fixes! Yay!

    CPU: Intel Core i7-6850K 3.60GHz, OC 4.199Ghz
    CPU cooling: Corsair H100i v2
    RAM: Corsair Dominator Platinum 2800Mhz 64GB
    Motherboard: ASUS X99-E WS/USB 3.1
    GPU: Nvidia Titan X (Pascal) 12GB
    SSD: Intel 750 Series 1.2TB PCI-Express 3.0 NVMe
    Monitor: Dual, ASUS 24″ 144Hz 1ms response
    PSU: EVGA NEX1500 1500 Watts
    Case: CaseLabs Magnum MH10
    OS: Windows 10 64-bit

    Cable
    Download: 119.21 Mbps
    Upload: 11.89 Mbps

    Thank you again!

    Janet Smith

    June 23, 2017

  • Ever since I updated to this version, I have nothing but problems with this “llceflib_host.exe” thing that just slams my CPU to hell.

    First start, and 1 instance appears with already taking 40+%.
    Click to login, 2 more appear with ~30%.
    CPU @ 100%, FPS @ 0.5-0.7

    Can’t move, type, turn it off. Tried rebooting, re-installing, turning off my other programs running. I have no more ideas what to do.

    Keth

    June 23, 2017

  • Just delete the post. Seems it’s working now.

    Keth

    June 23, 2017

  • Thanks for letting us know.
    I suspect you may have had a stuck llceflib_host.exe process that didn’t quit when you logged out of the viewer.
    Those stuck process can really chow down on the CPU.
    When you are logged out of the viewer, you should be able to find the zombie llceflib_host.exe in task manager & quit that process.
    If that still doesn’t help, a reboot should fix it.
    Just to note that it’s normal to have multiple llceflib_host.exe processes running. There can be rather a lot of them if you are around a lot of media content.
    All the llceflib_host.exe processes should quit when the viewer logs out though but occasionally you can get one of the stuck as a zombie process.

    Whirly Fizzle

    June 24, 2017

  • Since installing this update, it’s been nothing but extreme lag when loading into SL. My inventory is unresponsive, I’ve crashed quite a few times just trying to either load in or just crashes on itself. I don’t think they did enough bug testing for this version. I’m reverting back until this gets fixed. And yes, I did a clean install and all my drivers are up to date.

    Garren

    June 23, 2017

  • Please can you file a JIRA issue so we can get your viewer logs to see why this is happening.
    Thanks!
    http://wiki.phoenixviewer.com/file_a_jira

    Whirly Fizzle

    June 24, 2017

  • I have a slight problem with my viewer since the update. I use V3 style chat headers on a hybrid setting. I’m very heavy into roleplay so immersion is my thing. Since updating, my /me posts no longer behave the way they used to.
    Before I could make a /me emote and it would show :
    Display Name emote
    Now when I do the same thing, I get :
    Display Name (Username) emote
    No matter what I try, I can’t seem to the V3 headers to only show my display name when I emote.

    Despite that, the update is good. I feel a performance boost and rezzing in new sims seems to be quicker. Keep up the good work!

    Hel

    June 24, 2017

  • Hel- Make sure you have the “Usernames” unchecked in preferences.

    ctrl+P>PREFERENCES>GENERAL>UNCHECK USERNAMES

    When it’s checked —-> [07:06] Zïɠɠγ (zsigmond.alcott) sings
    When it’s unchecked—->[07:06] Zïɠɠγ sings

    Ziggy ALcott

    June 24, 2017

  • Yes, this is a new bug that only got caught after release.
    Ansariel already fixed it ready for the next release – please see http://hg.phoenixviewer.com/phoenix-firestorm-lgpl/rev/9d36b6c73a94

    The next release is likely not to be too far away actually. We need to get LL’s new asset-HTTP changes out fairly quickly because the old backend service will be switched off “soon” (few months yet) which will mean all older viewers without those changes won’t be able to fetch animations, wearables, sounds etc.

    Edit to add: Here is the bug report
    FIRE-21298 – Usernames in emotes of the V3 header of the chat window

    Whirly Fizzle

    June 24, 2017

  • I’d wondered about the asset-HTTP thing forcing another update. I’m glad it’s happening soon because it does make a noticable difference. I’d imagine this is also going to force a few other viewers to do updates or become unusable. I’m actually surprised LL hasn’t given an ultimatum regarding Bento compatability yet since there are some reasonably popular TPV’s that still don’t support that.

    Crim Mip

    June 29, 2017

  • Yeah, any viewer that does not update with the new asset HTTP changes will be pretty much unusable once LL turn off the back end systems for the old protocol.
    We have no date when the old back end will be turned off yet, but oz tentatively said the new year, but it could be sooner.
    LL will give TPVs plenty of notice though.

    Whirly Fizzle

    July 2, 2017

  • Isn’t that pretty much going to break every bot (“scripted agent”) on the grid? As far as I know, they’re pretty much all driven by code using libopenmetaverse, and that hasn’t been updated in ages…

    The Nth Doctor

    July 12, 2017

  • FS keep on going! As for me , i want one thing badly. its called … FOLDERS FOR OUTFITS. like you know, several. Thats all folks 😉

    KylaVixen

    June 24, 2017

  • what would be great if they could develop paid group list and normal group list so people that are creators don’t have to give up groups they paid for, for a non paid group

    wickked

    June 24, 2017

  • Only Linden Lab can raise the limit on the number of groups you can be a member of.
    If you are a premium member, you can join up to 60 groups now though.
    On Firestorm, we do prompt you when you try to leave a group that isn’t free to join, so you don’t accidentally leave.
    Example: https://prnt.sc/fnp2yc

    If you mean that you would like 2 separate group lists in the viewer UI, one list for free to join & one list for paid groups, then please file a feature request for this on the Firestorm JIRA.
    How to file a JIRA issue: http://wiki.phoenixviewer.com/file_a_jira
    Thanks!

    Whirly Fizzle

    June 24, 2017

  • I am very pleased that the disable group chats for groups that have notices disabled has been fixed. That alone made this a worth while upgrade.

    kali wylder

    June 25, 2017

  • The update is working just fine for me, and I’m even able to post photos on the feeds again since the update, but there is one odd thing going on. Every time I log out of FS since the update, I get the “Firestorm quit unexpectedly” message from my iMac. Not a big deal, but… odd.

    Sylvia Tamalyn

    June 25, 2017

  • Yeah we have a logout crash affecting some Mac systems which seems to be new on 5.0.7.
    There is a bug report filed for it here: https://jira.phoenixviewer.com/browse/FIRE-21292

    Whirly Fizzle

    July 2, 2017

  • Hm, kinda expected the vision spheres to be added in this update, especially given the time it took between this and the last.

    Zayin (Matteste Elton)

    June 26, 2017

  • I have noticed a few issues since updating the viewer to this new update. It take FOREVER for mine and other avatars to render. I have crashed twice already and I was just sitting there. Lag is always an issue however I find it to be the same. Rendering time is my biggest problem so far.

    MzLiv

    June 28, 2017

  • Do you happen to be using Webroot antivirus?
    Can you try whitelisting the viewer cache folder in your antivirus software & see if this fixes the problem.
    Instructions: http://wiki.phoenixviewer.com/antivirus_whitelisting

    Whirly Fizzle

    July 2, 2017

  • Still using WinXP with CtrlAltStudio (which is Firestorm actually) on my main PC and have no problems except for that shit called “Bento” but i don’t care about bentocrap.
    Seriously.
    So, fuck you very much, keep bullying about new releases and stuff.

    WinXP

    July 2, 2017

  • Sorry but the newer SL viewer codebase will not support XP. CtrlAltStudio viewer is a fork of Firestorm 4.6.9, which is very old now.
    Please consider updating your XP system to at least Windows 7. There are changes coming that will break all older viewers & those changes are server side & we can do nothing about it.

    Whirly Fizzle

    July 2, 2017

  • Forgot to add – under WinXP 3 windows with SL are working with CtrAltStudio
    Any new Firestorm under Windows 7 is crashing almost immediately with a message “textures discarded due to insiffuent memory”.
    i think it’s happens because of you are morons.

    WinXP

    July 2, 2017

  • That’s an out of memory crash.
    Is your Windows 7 system 32bit or 64bit?
    If 64bit, make sure you are using the 64bit version of Firestorm, which won’t suffer from out of memory crashes.
    Unfortunately 32bit operating systems are horribly prone to out of memory crashes.
    If you’d like help troubleshooting the crashes on your Windows 7 system, please file a JIRA issue so we can get yoiur system information & logs & see what’s causing the problem.
    How to file a JIRA issue: http://wiki.phoenixviewer.com/file_a_jira

    Whirly Fizzle

    July 2, 2017

  • This has nothing to do with your viewer in particular, but if it is possible for you guys to block viewers…why hasnt that copybot viewer been blocked as it has been an issue for many stores, court cases and all. Wouldnt it be easier to just block it?

    Current Store owner

    July 3, 2017

  • Unfortunately it’s not as simple as that. There are many copybot viewers, not just one.
    Some of the copybot viewers based on the Firestorm code have actually been blocked from login but it’s pretty easy for the copybot viewer creator to change the viewer code so that our block system no longer works.
    We can do nothing to block copybot viewers that are not based off Firestorm code either & there are many of those.
    Only Linden Lab can block those viewers from logging in, but again it isn’t that simple. Many of the copybot viewers spoof a legitimate TPV viewer name & version number.
    The only way LL could effectively block all copybot viewers would be to close source the viewer code and only allow the Linden Lab viewer to connect to the grid & even then it’s likely someone would find a way around that restriction eventually. Even then it would still be possible for people to steal content with other 3rd party tools – if the viewer (any viewer) renders the content, it can be stolen because that data is sent to your computer.

    Whirly Fizzle

    July 4, 2017

  • Theres a terrible glitch when i turn my graphics up and use depth of field.

    Roz

    July 3, 2017

  • Can you explain what’s going wrong?

    Whirly Fizzle

    July 4, 2017

  • never had problem until this version, actually firestorm crashes after 30-40 sec after log in
    Tried to unistall and re install a couple of time but no luck

    lorella bravin

    July 4, 2017

  • I was doing my presets for when i take photos and when i turned on depth of field and zoomed in on myself, i looked to be deformed. My head, hair, arms and hands stretched out to the ends of the screen. The only thing that didnt deform was where my camera was focused. I have AMD graphics, i did have webroot that i paid a subscription for. I uninstalled it and once i did that it was still an issue, but then my avatars skin became poorly pixelated too. I went back to the previous viewer and things work fine now, except the fact that everything keeps blurring up.

    Roz

    July 4, 2017

  • And yes i did a clean install for both

    Roz

    July 4, 2017

  • silly question, why cant Firestorm make a click “clean install” button? so we dont have to dig around and remember how to every update?

    Ilsa

    July 6, 2017

  • I installed the latest and greatest viewer just this afternoon, and ran into some problems.

    I did a clean install, and during installation I got a couple of “Failed to open file for writing” errors. I used the “try again” button to no avail and finally pressed the “skip” button.

    On log-in I get a missing file warning … Media_Plugin_cef

    I am instructed to install the missing file – I’d love to, but where do i get it? I assume it was the file that failed to open during installation. And now some things don’t work like the search and “areas of interest”

    Mewling Moy

    July 7, 2017

  • When are you gonna add some kind of auto update ffs,every time we goota do this.

    Nelli

    July 10, 2017

  • First off I want to thank all Firestorm and LL for their hard work 🙂
    Just wondering when to minor things will be addressed:
    Improper Link numbering in edit window
    The ability to use arrow keys to move always
    These have not worked for several releases. Are they unable to be fixed? Or overlooked as not important? Not sure where the problem lies, or pointing fingers, just curious to why it still is broke, lol 🙂

    Sean Tempest

    July 17, 2017

  • For arrows to move you go to:
    Preferences > Move & View > Movement (tab) > check “Arrows Always Move Me” (top of the list)

    Not sure what you mean by improper link numbering in the edit window, but I hope the above at least gets you moving the way you want.

    Mewling Moy

    July 17, 2017

  • Does anyone know how to save and upload prims textures etc? I used to use second inventory but it’s hard to find a decent one now

    Jonn Luik

    July 27, 2017

  • “You can no longer purge trash from Recent Items tab, because you might think you’re deleting just the recent items, but in fact it’s everything.”

    Bring this back please, it’s rather annoying not being able to do this. If it’s in the trash it’s there for a reason… to get purged!

    trine

    July 31, 2017

  • I wish to say I admire Whirly’s patience pretty much! 🙂

    Pointer

    August 14, 2017

  • hey, after a few days of installing firestorm and having optimum performance, it starts having errors says its not designed to use with windows pc… lol. I have to do reinstalls every 3 days lol. :/

    Gemma

    August 25, 2017

  • I am having the same problem as Gemma. I have not had any new updates to windows that would cause this.

    Cyanna

    September 3, 2017

  • Are you both using McAfee antivirus software?

    Whirly Fizzle

    September 22, 2017

  • Did a clean install of this new update and my frame rate has significantly dropped from 20-25fps to now only 2 or 3fps on sims. This makes it practically impossible to go anywhere.

    JIRA link: https://jira.phoenixviewer.com/browse/FIRE-21589

    Shota

    August 26, 2017

  • “They’ve been VERY busy and VERY productive, so folks shouldn’t be saying LL isn’t actively developing, because they sure are, and they deserve lots of credit for their efforts.”

    The new viewer is fine. Keep up the good work – HOWEVER – It seems to me there was post by Firestorm back in December/January asking users how SL could improve revenue. Well here’s your answer – STOP THE COPYBOTS and allow the detection of viewers again. I’ve seen no efforts in this most important area and even Linden Labs is shunning the responsibility of backing up their own TOS now – Making SL totally worthless in the end.
    Second Life – User Created, Proprietor Destroyed.

    Christopher coffee

    August 27, 2017

  • Newsflash for you bucko: So called viewer detection relies on specific tags/data that the client program transmits which is actually easy enough to alter by the end user.

    Furthermore there really isn’t much a copybot client can actually copy these days and honestly some of the content that it can still copy is easily enough found and accessed.

    Oh and it’s not the job of third party developers to ID other client programs – Linden Lab has their own system and metrics they utilize, despite your belief otherwise.

    When TPVs still had the option to show what client program others were using there was no shortage of users berating or abusing others over their choice of client program, thus the rule in place disallowing such things as well.

    In short – get your facts straight.

    Dark Wolf

    September 21, 2017