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

4.7.3.47323 Release!

translation services

I cannot remember a time when getting an update out had been so difficult! This highly anticipated 4.7.3 update has been plagued with bad luck, last minute showstopper bugs, trials and tribulations, but this is a good thing, as it means there’s nothing left to go wrong! UNLESS …you’re on Windows 10 with an Intel HD2000 or HD3000 graphics card, in which case please read Intel fix. It also will no longer run on WinXP or Mac 10.6.

4.7.3.47323 brings us to parity with Linden Lab version 3.8.2, including Viewer Managed Marketplace, Experience Tools, attachment bug fixes and much more! It also comes with plenty of our own new features and bug fixe,s and we’re very excited to be able to get this out to you now. You wouldn’t believe how much work has gone into it!

Shortlist of change highlights below. For a complete list please visit the RELEASE NOTES. Special thanks to Whirly Fizzle without whom we’d all be lost.

  1. Project Layer Limits (from LL) – Allows you to wear up to 60 layer wearables of any type. So you can wear 20 alphas/30 tattoos/10 shirts or 60 tattoos if you really want to.
  2. Other shiny from LL – Experience Tools, VMM, fixes for attachments falling off on teleport.
  3. Many RLV fixes, which fixed all the problems with RLV wardrobes and attachments that plauged the 4.7.1 beta
  4. Ability to create subfolders within the Outfits folder has been added back.
  5. Fully merged up to LL 3.8.2 codebase plus cherrypicked fixes from Bear and Lion.
  6. IM and group chat tabs can now be rearranged by dragging and dropping into desired position.
  7. 64bit Linux (non beta).
  8. Added an option to only allow conference chats from people on your friend list.
  9. 64bit builds allow setting texture memory up to 1GB, which results in 2GB max textures in memory. This should greatly improve “Texture Thrashing.”
  10. Chalice Yao’s simple avatar shadows feature – This feature attempts to lighten the load placed on your GPU when rendering complex rigged meshes (such as avatar bodies) when running with shadows enabled in the viewer.
  11. New option to block / reject all group invites, without the need to enable Unavailable mode.
  12. Lots of fixes and improvements for photographers including Depth of Field now working underwater, collapsed snapshot floater now displaying a mini preview image, snapshot floater now remembering last used snapshot option.

For a more in-depth look feel free to visit Inara Pey’s 4.7.3 REVIEW

As per our three-version rule, and given that I said 4.7.1 beta would not count towards it, we will be applying a block only to versions 4.6.1 and 4.6.5 in the coming weeks. If you are still using one of those please update!

 

Jessica Lyon
Project Manager
The Phoenix Firestorm Project, Inc

  • […] Firestorm 4.7.3 release announcement – Firestorm […]

  • Ummm… so is it me or does anyone else have the issue of the viewer crashing as soon as it says “Initializing VFS” ?

    Shadowarchangel

    August 19, 2015

  • Shadow, are you using Windows 10 on a graphics card that Windows 10 doesn’t support, like Intel HD 2000 or 3000?
    If so, please see http://wiki.phoenixviewer.com/fs_intel_fix_32bit_fs473

    We have also seen some users on older AMD cards on Windows 10 have this problem on 4.7.3 when using the 64bit viewer version.
    If you install the 32bit Windows version it should run fine.

    If you are still having problems, please file a JIRA issue so we can get your system information & logs: http://wiki.phoenixviewer.com/file_a_jira

    Thanks!

    Whirly Fizzle

    August 19, 2015

  • I had the same issue, multiple installs/reinstalls/deleting settings etc didnt help, i had to install the earlier version to actually be able to log in again.

    Dion Diavolo

    August 30, 2015

  • Using Windows 10, ATI 7970, latest drivers.

    Dion Diavolo

    August 30, 2015

  • Dion, could you file a JIRA issue so we can take a look at that?
    http://wiki.phoenixviewer.com/file_a_jira

    Whirly Fizzle

    August 31, 2015

  • After update of El Capitan Public Beta 5, all Japanese letter became square shape.

    Phawuth K

    August 19, 2015

  • Yep, known problem on El Capitan – see http://jira.phoenixviewer.com/browse/FIRE-16318

    Whirly Fizzle

    August 19, 2015

  • I love the update because of the addition of the VMM (I don’t really like VMM much anyway but if I have to use it, I’d rather use it with my favorite viewer ♥). My only issue is when I have advanced lighting turned OFF, my mesh and the textures glitch all over the place, seen here: https://imgur.com/IFruLhH
    Should I file a report for this, maybe?

    Mieli K.

    August 19, 2015

  • When you disable ALM, do you also have Hardware Skinning disabled?
    If Hardware skinning is disabled, the shading on some meshes can be very broken – blotchy or just a plain white texture – that’s unfortunately expected on rigged mesh.
    If you do have hardware skinning enabled then yes, please file a JIRA & be sure to include your full system information from help -> About Firestorm: http://wiki.phoenixviewer.com/file_a_jira

    Whirly Fizzle

    August 19, 2015

  • Yeah, I have hardware skinning enabled. I’ll file a report now ^^ It was working fine before I updated and before I updated my graphics driver, too, so I’ll include all of that. Thank you!

    Mieli K.

    August 20, 2015

  • Thanks Mieli!

    Whirly Fizzle

    August 20, 2015

  • Were screen space reflections removed? If so, why?

    shiraku

    August 18, 2015

  • Yes, they were removed. http://hg.phoenixviewer.com/phoenix-firestorm-lgpl/rev/30f89533cb77 – AFAIK they were buggy.

    Chakat Northspring

    August 19, 2015

  • They were removed a while ago now – before the 4.7.1 beta.
    SSR has been broken since materials support was added to the viewer.
    They would cause objects with a specular texture set to either render totally black or have a plastic look.
    This caused headaches for creators using materials because customers complained they didn’t see the content correctly, so SSR was removed.
    If SSR can be fixed not to have these bugs, then it will be added back in.

    Whirly Fizzle

    August 19, 2015

  • Bonjour , sur la version 4.7.3 on ne peut pas changer la langue en français , elle n’existe pas ?

    lisabellia

    August 18, 2015

  • Comme mentionné dans ce blog: http://www.firestormviewer.org/progress-report-3/ – certaines traductions ont été enlevés, parce qu’ils étaient incomplets.

    Chakat Northspring

    August 19, 2015

  • LL has removed a bunch of languages from the base viewer.. You can read about it here… http://www.firestormviewer.org/progress-report-3/

    drake1 Nightfire

    August 19, 2015

  • So far I am very pleased with this latest update and it was well worth the wait. I cannot give enough “kudos” to Jessica and the team for their hard work and patience to bring us all a stable viewer. I am sure things will crop up but that is the nature of the beast in programming. My hat goes off to each of you for the hard work and many, many hours put in and totally voluntary at that. Keep up the awesome job! – Felicia

    Feliciana Zabaleta

    August 19, 2015

  • Again The Firestorm team has put out a world class viewer. A huge pat on the back. They are wonderful giving team that opens their doors to the open source community striving harder everyday for perfection.
    I call them the working peoples viewer everything is there open and everyday working hard to keep that secure stable program. A program that makes your virtual world render for you.
    I thank you FS and all the developers that keep hacking away like a stone cutter creating art for the millions to see.
    Thank you for the wonderful tool.
    Thank you.
    Lord Drakeo.

    Lord Drakeo

    August 19, 2015

  • The Phoenix Firestorm Project Team,

    Thank you.

    Janet Smith

    August 19, 2015

  • Augh, and I JUST did a clean install of the latest version! Rage >:C

    @ShaunDreclin

    August 19, 2015

  • it dosent works

    Al H

    August 19, 2015

  • Then please help us know why and help you: http://wiki.phoenixviewer.com/file_a_jira

    Chakat Northspring

    August 19, 2015

  • any possibility to run under WinXP?

    Sym

    August 19, 2015

  • Check the release notes linked in this blog post, please – there was a build tools update and viewer will no longer work on unsupported Windows XP.

    Chakat Northspring

    August 19, 2015

  • Where is the french version?

    Eric

    August 19, 2015

  • As mentioned in this blog post: http://www.firestormviewer.org/progress-report-3/ – some translations were removed, because they were incomplete.

    Chakat Northspring

    August 19, 2015

  • Yay, the feature list sounds great. I need everything of it.

    Canis

    August 19, 2015

  • […] 18th August 2015 the Firestorm team announced a new version of the Firestorm Viewer 4.7.3.47323. This is a major release including Experience Tools, Project Layer Limits, the return of the […]

  • I get a virus warnung from AVG antivirus for IDP.Alexa.43 when trying to install on windows 7.

    Canis

    August 19, 2015

  • I used: Phoenix-FirestormOS-Releasex64-4-7-3-47323_Setup.exe

    Canis

    August 19, 2015

  • Sorry for my remark, I have learned, that the message in AVG means “the program behaves like a virus would behave”, it doesn’t mean “there is a virus”, so it may be false-positive.

    Canis

    August 19, 2015

  • Yep, lots of people who use AVG have reported that.
    Jess has contacted AVG to report the false positive.

    Whirly Fizzle

    August 19, 2015

  • You can also run a check with Virus Total online: https://www.virustotal.com/

    Whirly Fizzle

    August 19, 2015

  • The version works great! Thank you Jessica and all the Firestorm team for your very hard work! It’s much appreciated.

    Steve Mahfouz

    August 19, 2015

  • I’m Brazilian and use the firestorm for many years. Never thanked, but I was always an admirer of his work. I think you do not realize the importance of the work you and your team done to us, and not always appreciate. Thanks! 🙂

    Ayeres Zifer

    August 19, 2015

  • Well I think you forgot the Brazilians, because this new version, not be translated into Portuguese? Now be sad lol

    Ayeres Zifer

    August 19, 2015

  • As mentioned in this blog post: http://www.firestormviewer.org/progress-report-3/ – some translations were removed, because they were incomplete.

    Chakat Northspring

    August 19, 2015

  • POR FAVOR COLOCAR UMA VERSAO EM PORTUGUES DO BETA NE,AFINAL A COMUNIDADE BRASILEIRA NO SL E MUITO GRANDE

    vvampyrassedutora

    August 19, 2015

  • PLEASE PUT ONE IN PORTUGUESE VERSION OF BETA NE, AFTER ALL THE BRAZILIAN COMMUNITY IN SL AND VERY LARGE

    vvampyrassedutora

    August 19, 2015

  • As mentioned in this blog post: http://www.firestormviewer.org/progress-report-3/ – some translations were removed, because they were incomplete.

    Chakat Northspring

    August 19, 2015

  • Norton blocked this new viewer damm now i cant get up
    second lfe anyone can tell me what to do ?

    jannah

    August 19, 2015

  • Jannah, see http://wiki.phoenixviewer.com/antivirus_whitelisting
    If you still need help getting the viewer past Norton’s block, please file a support JIRA and support will help you – see http://wiki.phoenixviewer.com/file_a_jira

    Whirly Fizzle

    August 19, 2015

  • I’m very disappointed, withdrew in Portuguese language, I have to go back to default viewer.

    leon S K

    August 19, 2015

  • As mentioned in this blog post: http://www.firestormviewer.org/progress-report-3/ – some translations were removed, because they were incomplete.

    Chakat Northspring

    August 19, 2015

  • THANK YOU THANK YOU THANK YOU
    I had to switch to LL viewer to script for Experience tools and that was driving me nuts. 🙂

    Blaise

    August 19, 2015

  • Good work, FS folks! I’ll definitely be using this viewer over that sluggish Linden Lab VMM beta.

    I won’t be able to use it for every day Second Life yet, though, because Linde Lab hasn’t addressed the Unresponsive Mouse Wheel (UMW) bug yet.

    UMW on the latest FS viewer demonstrated in this video: https://www.youtube.com/watch?v=4fJlkMOULM0

    A JIRA issued @ LL: https://jira.secondlife.com/browse/BUG-9923

    Long-standing JIRA @ FS: http://jira.phoenixviewer.com/browse/FIRE-12485

    A survey of affected systems in the SL Community Forum: https://community.secondlife.com/t5/Second-Life-Viewer/Mouse-Wheel-Unresponsive-On-My-Mac/td-p/2959141

    It’s probably an issue that has to be addressed by Linden Lab themselves. Up to then, again, even though FS has all these cool building tools, I’ll have to keep on using Singularity.

    Arduenn Schwartzman

    August 19, 2015

  • Kudos to the whole team! What an impressive release! Thanks for all the hard work and putting up with all the whingers. What you all do for free for all of us is really awesome!

    whina

    August 19, 2015

  • I can see how much work has gone into this viewer release. Thank you so much!
    Jessica, I wonder if you could comment on the position with the update to Marine’s latest RLVa specification. I know she has introduced some really good features, but it is beginning to seem that updating RLVa never quite “makes the cut”.
    Many of us have Marine’s stuff with menu features we can’t use.
    I hope this will be a priority for the next release.
    Keep up the good work.

    Karen Walworth

    August 19, 2015

  • As far as I’m aware, Kitty is working on the RLV update now.
    There was a lot of RLVa work that had to be done for 4.7.3 to fix all the RLVa problems with AIS3 & the BigBird changes and unfortunately this took up all the time.
    On a happy note though, all the RLVa attachment problems seen in the 4.7.1 beta should be totally fixed now 🙂

    Whirly Fizzle

    August 19, 2015

  • Kudos, kudos, kudos!!!!!! Well done team. I was hopeful that the issues with HUD’s, clothing, hands, feet, etc. coming off during TP’s or in my case sailing and sim crossings. After I installed this version, I picked one of my sailboats that has been notorious for losing the boat’s HUD and also added a GPS HUD as well. I selected a course that one of the cruise clubs recently offered for it’s Sunday cruise, about 1.5 hours. I’m happy say that after arriving at the Finish, I had not suffered any lost HUD’s! YAY! I did lose my mesh feet and one hand but normally, I don’t wear these to sail – it was part of my test of this new version. So, very well done….my concern was addressed and I’m happy. Thanks again Firestorm! Thanks Obama!

    pepys

    August 19, 2015

  • I switched to FS because the SL viewer forced me to update to a new viewer which does not run on my Mac OS 10.6.8. Can I continue to use the 4.7.1 version?

    Karst

    August 19, 2015

  • Check the release notes linked in this blog post, please – there was a build tools update and viewer will no longer work on any version of OS X below 10.7.

    Chakat Northspring

    August 19, 2015

  • Yes, you can continue to use 4.7.1.
    I’m sure you’re sick of hearing this but you really should think about updating your operating system to Mavericks or Yosemite.

    Whirly Fizzle

    August 19, 2015

  • I’m having trouble getting the installer to unpack correctly. I don’t know if its a problem with my machine or what but I’ve never had it happen before. Tried several restarts and have practically nothing running…

    Bharv

    August 19, 2015

  • Bharv, hard to say what the problem is without seeing the installer logs.
    First thing to try is deleting the old installer, clear web browser cache (important) and download a fresh copy of the installer.
    If you are still having problems, please file a JIRA issue & we can get your installer logs: http://wiki.phoenixviewer.com/file_a_jira

    Whirly Fizzle

    August 19, 2015

  • Lol pepys:) You really should try a viewer made by a sl sailor, ukando, latest version with improvements to world map when sailing, released Yesterday.
    But well, all follow the big one, so for those who do, congrats, finnaly you are entering on the latest dimension, the one that black dragon, kokua, ukando and ll official viewers users already know about, besides Cool vf viewer, for those still used to v1 interface.

    zzpearlbottom

    August 19, 2015

  • Any of then is got VMM enabled and able to run WinXp or Win 7 ??

    Betty

    August 25, 2015

  • I think the only VMM capable viewer which run on XP is the CoolVL Viewer. I’m not 100% sure even that will run on XP now.
    All other VMM enabled viewers should run just fine on Windows 7.

    Whirly Fizzle

    August 26, 2015

  • Hmm, Norton threw a hissy when I tried to log in, telling me there was suspicious firewall activity. Any clue why or is Norton just overreacting again.

    Tal

    August 19, 2015

  • sl voice would attempt to connect at login & this usually triggers a Firewall prompt.

    Whirly Fizzle

    August 19, 2015

  • I don’t know why Norton is throwing a hissy fit, it didn’t with the previous version and the SL Viewer is happily running.

    Something about this viewer is causing Norton to file it as suspicious activity. This isn’t new, I’ve seen this regularly with High Fidelity, for example. There are workarounds, but maybe the Firestorm team need to talk to Norton.

    Ciaran Laval

    August 22, 2015

  • We haven’t actually had more complaints then usual from Norton users for this release, just the usual problem with slplugin being blocked, which has been an issue for years with all the antivirus software on all viewers.
    Did Norton flag 4.7.3 for you too Ciaran?
    We did have a really bad problem with Norton a couple of releases ago & their support was excellent and sorted the problem out quickly. They even sent a Norton support agent into SL on Firestorm to check it out.
    Jess heard back from AVG today and they have fixed the false positive. Users having problems with AVG will need to update their definitions.

    Whirly Fizzle

    August 22, 2015

  • Norton Firewall was flagging Firestorm-bin.exe. I allowed it for one session and it seems to have sorted it out.

    I’ve even gone back into Norton Firewall, removed the program control and started Firestorm again, which then adds the rule back to the Firewall automatically without complaint.

    Ciaran Laval

    August 23, 2015

  • Thank you for the release!
    I love to be back on 64 bits on linux woohoo!

    Aaack Aardvark

    August 19, 2015

  • Dloaded it last night and put about 10 hrs on it so far. All seems very stable, great work Jess & team~!

    Ziggy Alcott

    August 19, 2015

  • Hmm, for combat lands this gone be annoying; the Conversation windows does not hide when entering mouse look ?

    Jaraziah Lowell

    August 19, 2015

  • Whirly Fizzle

    August 19, 2015

  • I am not able to find the controls to enable mirrors.. can someone help me?
    It might be one of the most desired features by residents ever! while it has been hugely underestimated on its impact to realism in second life the same way mesh was before it was even beta.

    1potato2potato

    August 19, 2015

  • I’m guessing you are refering to this feature? https://jira.secondlife.com/browse/STORM-2055

    Mirrors are not in any released version of Firestorm. Linden lab would need to add the feature to their viewer first before TPVs could add it as it would be against the shared experience.
    You need to be able to compile the viewer yourself to add the mirror feature using the patch on the JIRA issue.

    Whirly Fizzle

    August 19, 2015

  • “Layer Limits (from LL) – Allows you to wear up to 60 layer wearables of any type. So you can wear 20 alphas/30 tattoos/10 shirts or 60 tattoos if you really want to.”

    i want to kno if older TVP / FS 4.6 can see that if i use 10 tattoos!?!
    did u test it ???

    ” fixes for attachments falling off on teleport. & The payment confirmation threshold amount is now customisable: Preferences > Firestorm > Protection > Confirm before paying: L$[AMOUNT] & Ability to create subfolders within the Outfits folder has been added back. ”

    3 x Kudos FS team TX!

    b

    August 19, 2015

  • Yes, older viewers can see the extra layers.

    Whirly Fizzle

    August 19, 2015

  • for X64
    was ok for 2 days but now
    still to many bugs
    wtf LL/FS ??

    b

    October 4, 2015

  • You’ll need to give more details then that. I’m not psychic lol.

    Whirly Fizzle

    October 9, 2015

  • Just wanted to thank everybody who has worked countless hours in providing us with all the fantastic releases all i say say is fair play and keep up the awesome work 🙂 as for win 10 yeah i had a lot of problems and it crawled and kept getting this error no matter what i did even reinstalled http://prntscr.com/86ja37 so i reverted back to 8.1 luckily i had my fs settings saved 🙂 such a nifty feature be lost without it. Huggs To All ♥

    Leto

    August 19, 2015

  • […] é, além de ininteligível, no mínimo irrisório… Para o que temos para hoje leia mais aqui e depois corre lá e […]

  • Love number 4, I really hated when the ability was removed, really happy it’s back.

    LOVE number 9, I which we could bump it up to 4GB since the main reason for low frames is the very limited video memory compared with the huge amount of extra large texture maps being slapped on everything today, people kinda forget each of these 1024×1024 takes 4MB, I bought a bike that has 90MB worth of textures alone, suddenly you see why that 512MB limit was just a massive bottleneck.

    Absolutely hate number 1.
    The thing is, like I mention before, with mesh creators started using ridiculously huge texture maps for very small things.
    Tiny constructs will have several 1024×1024 maps, and I’ve seen some of those where 90% is just dead space.
    To the point, in the old days you had your skin 512×512, then a few layers, that was it.
    Just imagine the render cost of someone with 60 layers! That’s beyond absurd. Not to mention I bet you people will have a pile (or all 6) under a mesh body, so it’s not doing anything for them, but it’s there for your viewer to download and deal with…

    Dean Haystack

    August 19, 2015

  • No matter how many clothing/tattoo layers you have on your body, everyone else will only have to download and render the exact same three textures that have been downloaded since 2003. All those layers are still baked into a single texture by the SSA system.

    Theresa Tennyson

    August 19, 2015

  • Theresa is correct.
    I’m wearing 60 layers here on my upper body and as you can see, there is only a single baked texture for the upper body section: http://prntscr.com/86nsz1

    As far as I know, each baked texture on that window is limited to 512×512, apart from the eyes, which are limited to 128×128.

    Whirly Fizzle

    August 19, 2015

  • eheh, still fail to see why i would need so many layers, while the gross of second live players; is wearing a mesh body and thus only… one layer… that being the total alpha. Though some still use the head, so yay.. 29 layers to decorate my face ? *giggles* Would rather see the ‘default’ avatar mesh aka the second life body to get an overhaul and become more detailed. With just adding layers, one fails totally to repair meet the demands of the gross of players. But that might be just my humble opinion.

    Jaraziah Lowell

    August 20, 2015

  • I’m not sure what groups you’re hanging around with, but mesh bodies aren’t being worn by the “gross of players” (I assume you meant “majority of”?) in any of the areas *I’ve* been in… At *most*, it’s been about one in five, and often less than that.

    That being said, I can’t say I’ve ever needed to have *that* many clothing items layered on at the same time, either…

    Polythene Pam

    August 21, 2015

  • The numbers don’t lie. There have laterally been millions of mesh bodies sold/given away, and all new signups get mesh body now. LL doesn’t even use the default body for their own starter AVI’s anymore. (Which is a nightmare for a noob).

    Noctorne

    October 26, 2015

  • Awesome! Kudos on the return of a 64-bit Linux viewer!

    Seth Ock

    August 19, 2015

  • […] 4.7.3-47323. It is the viewer Managed Marketplace capable viewer. The team has post up on the blog: Firestorm Viewer 4.7.3-47323 Release! They explain they had some problems getting this version out and it is therefore a bit latter than […]

  • For those like myself who might have a generation or 2 behind on AMD systems and on Windows 10 I found when i did a complete clean install (Meaning manually delete Your Firestorm folders in both the roaming and local directories and use the uninstaller to clear the Firestorm Application, don’t even use a back-up you have to start fresh here. Once that is done you can then run the installer, its ok if its 64bit that doesn’t really matter with AMD set-ups since there not using intel graphics.) then this new one runs just fine.

    Wes

    August 20, 2015

  • Awesomesauce. *This* is the best viewer you released! And yes, 64bit Linux, great ! Wonderful!

    YT

    August 20, 2015

  • Still don’t have the ability to save outfits, even with this new update. Now I can MANUALLY set them, but it gets tedious and annoying.

    Other than that, I’m glad that the Viewer Market Management is finally on my favorite viewer. Got so many things to upload!

    Vox the Sergal

    August 20, 2015

  • Vox, are you getting an error message when you try to save outfits? We need more details to know what’s going wrong there.

    Whirly Fizzle

    August 20, 2015

  • There was a bug that silently made creating outfits fail, when an old `Bald Head` was used. Basically as the item was or is corrupted on LL side, and thus not truly exist an link could not be created and so failed. I my self made a new one and that fixed it for me, but that was a while back that i had that and figured that out.

    Jaraziah Lowell

    August 20, 2015

  • Yeah I suspect it’s that issue.
    AIS3 is more picky about “corrupted” assets or any asset in an outfit that there is something wrong with in some way & the outfit will refuse to save – ref https://jira.secondlife.com/browse/BUG-9353
    Anyone having this problem needs to be looked at on a case by case basis though to see which asset in their outfit is causing the problem and why.

    Whirly Fizzle

    August 21, 2015

  • I had one account that was refusing to create outfits after updating to the new FS. Using the suggestion above about possibly correupted item data, I tracked the problem down to an older bridge’s broken link that was somehow trying to be worn. After recreating the bridge, outfits now save correctly.

    Elic Epsilon

    August 28, 2015

  • Hello,

    After performing a clean install via the Tool Tip Tuesday video, I installed the new update and restored my original settings. When I logged back in I noticed some of my mesh hair on the back were lit up when I zoomed out a few clicks. Does that have anything to do with ALM being enabled? Everything is enabled except for Ambient Occlusion. I clicked on the Rendering tab, but couldn’t find anything there. Could it be a glitch? I took a screenshot and cropped to show you an example https://goo.gl/photos/BPMNQbtQoLKKXxMY8

    With that said, I’d like to give a huge thank you to Jessica and her team on releasing a wonderful update. I haven’t familiarized myself with any of the new features, well, except for the VMM. I decided to add my in-world photographs to the MP, again.

    Thanks again,

    Frank

    Frank

    August 20, 2015

  • Are you only seeing that effect when ALM is enabled?
    It’s hard to say what’s wrong without more information but if the problem only happens when you have ALM enabled, I suspect you are standing near a projected light source, which can cause textures that have transparency to render too dark – see https://jira.secondlife.com/browse/BUG-5852

    This is not a new bug in 4.7.3 though, its been a bug since Materials was added.

    Whirly Fizzle

    August 20, 2015

  • @Whirly Fizzle As soon as I log back in I will double-check with ALM enabled/disabled. I will add that I was near my campfire to the left of me. I had the setting on ‘smoulder’. Also, does it matter which Windlight I have selected? I was using Coastal Afternoon when I took the screenshots, but changed to Nam’s Optimal Skin & Prim and it seemed okay. I don’t remember if I had ALM enabled or not.

    Frank

    August 22, 2015

  • I have tried both versions of the new viewer, both will not work with my intel card, i have used the fix for x32 but still very laggy, i have adviced my friends not to upgrade, i have gone back to the beta build for x64 that works fine

    Trebor Rufus

    August 20, 2015

  • Customer comes first, never technics…. unless it is IT (hence SL).

    While the new build tools easily can support XP, it is a technical decision to not to. it has nothing to do with ‘outdated’.
    Compiling to XP is quite simple, but a bit more work (really little)… So i presume it’s laziness and a typical IT look at the world never minding the customers.

    XP users worldwide: 11.74%
    Windows 8.1: 13.09
    Vista: 1.84

    Mind you, many users in SL use low-end computers and i still meet relatively many still running XP, Linux and older mac OS.

    How so is XP outdated? If it works, it works.
    Atm, there’s nothing one can’t do what others can do if one is totally not interested in all the online app rubbish, stores and other online services, nagware and what have we more.
    I’m productive and creative, and that’s all that matters.
    I use both W7 and XP, and hardly notice much difference…

    W8 and 10 are crap which i run away from hard…. (10 = ridiculous, compulsive nagware).

    Security risks?
    That’s a matter of profound protection by other means than MS.

    Again, this whole thing is IT driven (from their point of view) and has nothing to do with customer care whatsoever.
    2% Less crash rates? Sorry, this meaningless figure doesn’t make a valuable argument.

    I’m happy with Windows 7 and XP, but don’t tell me that the Firestorm developers are not using LS native code, because this shows they do that on parity (not just this time) and just add stuff.

    Nice to have FS with all the extra gadgets, but please cut the crap by claiming things you do not do (which is typical IT bla bla).

    Sorry for the rant, but i’m straightforward on this.

    I just think that SL and FS are compromising accessibility to SL seriously while the worldwide active user base already is a huge laugh. It’s really nothing and by cutting multi-platform support (XP, bit older Macs, Linux limitations), technicians/developers
    are staring at their own belly.

    Not smart this move…

    Yes XP and some later Mac OSes are old, but i thought… customer first and as SL has been going steadily downhill on daily logins ( i keep track since 2007 ), SL/FS should not be lazy…

    If it can be done, then it can be done… it’s that simple.

    Not smart this move. Certainly and especially not it FS wants to be the exceptional one…

    Sorry again for the rant, but i really tend to be straight forward on this issue.

    Linda Brynner

    August 21, 2015

  • “While the new build tools easily can support XP…”
    Great, you must really know your stuff! You can attach your patch to a JIRA issue in a couple of weeks then?
    hg patches are preferred please.
    Instructions here: http://wiki.phoenixviewer.com/fs_make_a_patch

    Thank you 🙂

    Whirly Fizzle

    August 21, 2015

  • Thanks for your feedback Linda, and thank you for being so frank and honest with your opinion. In return I will show you the same respect by being equally straightforward. ‘You have absolutely no idea what you are talking about.’ However, to demonstrate that we actually DO care about xp, and as Whirls has also requested above… We WILL be entirely welcoming of your code patch very soon since you said “Compiling to XP is quite simple, but a bit more work (really little)” I am sincerely looking forward to bringing Firestorm into compatibility with WinXP again and crediting you with that success. Thanks again!

    Jessica Lyon

    August 21, 2015

  • So you still drive a horse and buggy to the store Linda? After all…”If it works, it works.”?

    MG Canonmill

    August 21, 2015

  • Its Sad that 11% still using XP if that the case, or good news means a ton of people that are easy to destroy their PC due to the fact Microsoft wont patch or fix any security issues. Granted security is always lowest priority to Microsoft same goes with being on the forefront of technology, other than the days of windows 95 MS has yet to really release anything that has been a game changer or innovative, simply do what they do best use others ideas.

    2nd’ly if you want new technology better improvements better quality graphics you have to keep up with the technology, otherwise we would still be stuck in days of no windlight no mesh and ugly avatars. Does suck but one can get a modern day PC for quite a good value, even a used one a couple years old one can get cheap

    Jenny

    August 21, 2015

  • Some valid points, Win 10 is not gaining customers, cause most revert as soon as they found the exploit of Ms to check for valid software.
    Maybe not a big issue on Usa but on most countries of the so called 3th world and even 1st one.
    Also the fact that LL stopped developing some of the most used languages in Sl, like Portuguese, French and more.
    But these are not issues of firestorm but decisions of the lab.
    Same with the end of the support to xp, linux and old mac os.

    zzpearlbottom

    August 21, 2015

  • I am IMMENSELY happy that you added hover height to quick prefs.

    Soto Hax

    August 21, 2015

  • My concern isn’t with FS, and not really with LL, although I think both have little to offer as far as keeping older systems viable in SL.
    I have a pretty high-end system and rarely run into any problems, but I was able to afford replacing an old system a short time ago – not everyone is able to plop down over a thousand dollars just to run SL.
    I’m running Win 8.1 and I’m happy with it. I refuse to install Win 10 which is turning out to be the most invasive OS of all time.
    I was able to go into “god mode” and get rid of that annoying nag to “up-grade” to Win 10, but not everyone knows how to do that.
    So, for now, I’ll plug along with Win 8.1 and I suppose at some point FS will no longer support that OS. That will be the point at which I will be forced to leave SL after over nine years.

    JackFrom VA

    August 21, 2015

  • amen to that

    Pasion

    August 22, 2015

  • The last release of XP was SEVEN years ago. It’s far more likely that Second Life itself will be shut down long before Firestorm has to drop Windows 8 support.

    Redwood Rhiadra

    August 22, 2015

  • You dont need to spend 1000 dollars for a pc to run sl… You can buy one under 500 probably even a used one on ebay or sorta that will run SL with a Breeze.. Plus Windows 10 is free upgrade.. I bet by the time they no longer support 8.1 you will have longed upgraded to 10 for other reasons… This will be how MS makes its money Subscription based OS so you can believe they’ll do something after a few years to ensure nobody can use an OS lower than 10

    Jenny

    August 25, 2015

  • I need old version 4.7.1 beta, Where can I download ?
    because I run windows XP32

    Mayumi.H

    August 21, 2015

  • Old viewer versions can always be found here: http://wiki.phoenixviewer.com/fs_older_downloads

    Whirly Fizzle

    August 21, 2015

  • Thanks for releasing a Linux 64 bit version. It’s a little crashy, but I am guessing you do get the crash dumps so you can look at them?

    Jayd

    August 22, 2015

  • Yes, if you send the crash reports in we get them.
    Though we cannot tie the crash reports to a certain avatar, they really just get zapped through a python script so they are in a nice readable format & can be sorted by most frequent matching crashes etc.
    If you are having frequent crashing problems, best thing to do is file a JIRA issue and include system information & log files after a crash & we can at least see why you are crashing and hopefully fix it.
    See: http://wiki.phoenixviewer.com/file_a_jira

    Whirly Fizzle

    August 22, 2015

  • What worths a release that does not support at least the 6 basic languages that LL use in their web and viewer (No more Portuguese and French!) You’re going to lose all your brazilian and french users

    Felipe

    August 22, 2015

  • Please see http://www.firestormviewer.org/progress-report-3/ which explains why those languages were removed.
    If we can find translators then those languages will be added back.

    Whirly Fizzle

    August 22, 2015

  • I’m having an issue with talking in public chat (haven’t tried IMing anybody) as of the latest update. It seems to happen at random, but sometimes when I hit enter to send, my text will send 2, 3, and sometimes even 4 times in a row.

    Any information on this?

    Blizz

    August 22, 2015

  • That problem is usually caused by packet loss or a weak wifi connection.
    Check if you have the same problem on all regions first.
    Power off your router/cable modem for a few minutes & reboot the computer for good measure.
    If you are wireless, try wiring up and see if you have the same problem.
    If the problem persists, you can contact Firestorm support for help in troubleshooting the cause: http://wiki.phoenixviewer.com/getting_help

    Whirly Fizzle

    August 22, 2015

  • My Wi-fi signal is far from weak. I have a 300 Mbps connection with full bars. I am on a desktop, but due to the placement of the router in the house, I’m unable to wire up so I’m using a dual band wireless card. Even after rebooting, this problem still persists. I do have the same problem across multiple regions. I suppose I’ll make a ticket about it. In the mean time, have some screenshots:

    http://s15.postimg.org/yhpu5n9e3/Not_weak.png
    http://s29.postimg.org/jjkkaydyv/Still_happening.png

    Blizz

    August 23, 2015

  • Yep, a ticket is a good idea.
    Next things I would do to try to narrow it down a bit more is:
    1) Do you have the same problem on other viewers?
    The best viewer to always compare Firestorm to when you have a problem on it is the LL viewer from https://secondlife.com/support/downloads/
    2) Do you have any other computers in the house connected to the same network & can you reproduce the problem on those systems?

    Whirly Fizzle

    August 23, 2015

  • Still happens in the default viewer, albeit less often.

    My other half was experiencing the issue at some point, but says it has stopped for him. He was on a different machine. I’m unsure what is going on here.

    Blizz

    August 24, 2015

  • That kinda sucks that people using Mac 10.6 cannot go any higher. We would like to have nice upgrades too, but maybe can’t get newer computers. I have been here since almost the beginning and feel kind of like we are getting phased out if we can’t get better machines.

    Pasion

    August 22, 2015

  • You may be able to update to Yosemite on your current Mac.
    Check to see if your system is compatible here: http://www.apple.com/uk/osx/how-to-upgrade/

    Whirly Fizzle

    August 22, 2015

  • I’d like to thank whoever is responsible for the inventory performance improvements – my inventory is 195K, and it used to take over an hour to load from a clean cache. After installing this new version, it took less than five minutes – seriously impressive improvement.

    Redwood Rhiadra

    August 22, 2015

  • The faster inventory fetching improvement came from Linden lab (Monty Linden). It was part of the Http Pipelining changes.
    That isn’t actually new in 4.7.3, it was part of the 4.7.1 beta, but if you just updated from 4.6.9 then you will notice a huge improvement in inventory fetch time.

    Whirly Fizzle

    August 23, 2015

  • Thanks a lot for 4.7.3.47323!

    Well, but let me rant a bit.
    The “attachment-issue” (BUG 6925), how it’s popularly called, still bothers me (and others).
    Just TP to Blueberry, Collabor etc. to be confronted with a certain percentage of disembodied people.
    BigBird helped to reduce the instances but there’s absolutely no guaranty to “materialise” in one piece.

    I really don’t understand why the lab won’t fix it – or cannot fix it!
    The JIRA (https://jira.secondlife.com/browse/BUG-6925) shows still “unresolved” and that’s literally obvious.

    Sylvia Jeanjacquot

    August 23, 2015

  • There are many different reasons you will see disembodied people (mesh body wearers) at busy events like that.

    The attachments falling off on TP issue that BigBird fixed (https://jira.secondlife.com/browse/BUG-6925) actually was never likely to be one of the reasons.
    When BUG-6925 happened, the attachment wearer would see their own attachments missing after a TP and would likely reattach them.

    There is another old old attachments problem after a TP that BigBird hasn’t fixed – thats the ghosted attachments problem. There *is* some discussion about that on BUG-6925 too, but it’s a different bug and an old bug – See https://jira.secondlife.com/browse/BUG-7761 and https://jira.secondlife.com/browse/BUG-9544 for just 2 recent reports of this and see https://jira.secondlife.com/browse/SVC-7578 (from 2012) for an old report of it.
    This bug has been present for a long time & complained about often.
    It will strike most often when more then one attachment is worn on the same attachment slot & with the popularity of mesh bodies now, where all the bits & pieces generally attach to the same slot, the problem is more likely to strike, plus its very noticeable when someones entire mesh body is missing.
    When the ghosted attachment bug happens, the attachment wearer will still see their attachments on screen, but they have fallen off serverside and thus no observer will see them.
    This bug will very likely need a serverside fix.

    At busy mesh heavy events it is unfortunately really common to see slow loading of mesh bodies (mesh in general) too.
    This has improved somewhat (with the pipelining changes for example) since mesh was first introduced but it’s still a problem.
    A good JIRA issue describing this problem is at https://jira.secondlife.com/browse/BUG-5414
    This problem has nothing to do with the recent BigBird attachment problems.

    Invisible, slow or stalled loading of mesh can also because by other things:

    * All rigged mesh being invisible on AMD systems when hardware skinning is enabled due to the 14.12 AMD driver bug.
    AMD fixed this with the 15.7 Catalyst driver.
    https://jira.secondlife.com/browse/BUG-7653

    * Problems at your local CDN (which would also affect texture loading). Usually transient.

    * Local partial DNS problems affecting connection to the CDN – likely to also affect texture loading.
    Switching to Google DNS usually fixes that case.

    Whirly Fizzle

    August 23, 2015

  • Whirly, thanks a lot for answering in detail.
    I confused 6925 with 7761.

    I’ve voted and I am watching BUG 7761 now, asking every wearer of a mesh body, feet, hands etc. also to do so.
    https://jira.secondlife.com/browse/BUG-7761

    Sylvia Jeanjacquot

    August 23, 2015

  • Congratulations and lots of thanks to the Firestorm Team!
    Great new version, everything works perfect.
    Special thanks for the Linux 64bit version…. works great at my Linux Mint Cinnamon (Intel i5, NVidia GTX 960) with Ultra, view:256, shadows and DOF enabled. Even at crowded sims!
    Love it!

    Tommi Waydelich

    August 23, 2015

  • Piece of crap that only does what the rich donators request.
    The show muted and blacklisted avatars will show the muted and blacklisted avatars where we want it to show or not and if we don’t we are fucked. The mesh now takes forever to rez and often disappears.
    Want to fix? Then fix. But don’t break what was working FINE.

    Lala

    August 23, 2015

  • 1) We dont have any rich donators – or any donators at all…

    2) “The show muted and blacklisted avatars will show the muted and blacklisted avatars where we want it to show or not…”
    Yep – that’s a bug.
    That bug was actually on the 4.7.1 beta too & noone reported it so it went unnoticed.
    Filed & fixed now: http://jira.phoenixviewer.com/browse/FIRE-16760
    Thanks!
    In future, if you see something broken, please file a JIRA issue to report it. If we don’t know something is broken, it wont get fixed – see http://wiki.phoenixviewer.com/file_a_jira

    3) The slow loading/invisible mesh could have many causes.
    Best thing to do there is to file a JIRA issue (see above link) and include your system information & logs so we can look at why you may be having this problem.
    If you don’t report it, we can’t fix it if it’s caused by a viewer bug and if its a local issue support can help you 😉

    Whirly Fizzle

    August 23, 2015

  • Good release, a bit faster than the previous version on my computer with the same settings.

    Mak Munster

    August 24, 2015

  • You guys have worked hard and are trying to provide a Linux 64 bit version, which is great. I hope that one day you actually achieve a workable client and I wish you every luck in getting there.

    Sadly FS is not usable in it’s current state.

    * Mesh HUDS derender during TP (ticket response, don’t wear them)
    * Mesh hair derenders during TP
    * Crashes regularly (Not going to be an easy fix)
    * Photo Freeze Frame is not draggable to compose a photo (bug since 2012 and still a problem?)
    * DOF doesn’t work in Linux 64 Photos

    Back to Singu I go, which is a pity as your sim loading speed is amazing with the 8GB cache making weaing a mesh body a dream rather than a 10 minute wait for your fragments to render, the 768 texture memory meant no more thrashing and flashing textures.

    Maybe next version. I can hope. I really can. But with the 2 blocking level bugs in photo tools especially, nope.

    Good Luck and thanks for all the hard work you do, and are doing trying to get FS working on Linux.

    Jayd

    August 24, 2015

  • 1) Thanks for filing a JIRA issue for the “Mesh HUDS derender during TP”.
    I could reproduce that easily with the example HUD you gave.
    That one isn’t actually Linux specific or even Firestorm specific & it’s not related to the attachment problems in 4.7.1.
    It’s actually really old. Any high render weight *unrigged* worn mesh has a good chance of turning invisible after a teleport until you either right click/edit it, zoom camera out & back or toggle wireframe.
    There is a fix LL have upstream (not in any LL release viewer yet, its lurking in Lion) that may actually fix this once & for all. Their fix is actually for worn mesh (rigged) loading at lower LOD after a teleport, a problem which plagues the noob starter rigged mesh avatars together with a fix for rezzed mesh inworld also only loading at lower LOD at login/after a TP until you right click on it.
    If a mesh has no lower LOD (not unusual for HUDs) then it will be totally invisible).
    For those interested the fixes are at:
    https://bitbucket.org/lindenlab/viewer-lion/commits/e2249ad14486
    https://bitbucket.org/lindenlab/viewer-lion/commits/f3daa7752901
    Those fixes will appear in the next LL Maintenance-RC viewer, Im unsure when that will be.
    The fixes seem to work well though, I built Lion to test them.
    Relevant JIRA issues:
    http://jira.phoenixviewer.com/browse/FIRE-9172 (your JIRA was a duplicate of this one).
    http://jira.phoenixviewer.com/browse/FIRE-15917
    https://jira.secondlife.com/browse/BUG-7239
    https://jira.secondlife.com/browse/BUG-6803
    https://jira.secondlife.com/browse/BUG-8806

    2) Mesh derenders after TP – See (1) above, same bug.

    3) Crashes regularly (Not going to be an easy fix) – we would need a JIRA issue with logs for the crashes to see why it’s happening.

    4) Photo Freeze Frame is not draggable to compose a photo (bug since 2012 and still a problem?)
    Freeze frame has been broken for ages.
    Niran is working on another round of snapshot improvements for LL and freeze frame has been removed and replaced with a freeze world feature which is so much better.
    I’ll be glad to see the back of Freeze Frame myself, it’s never worked well.
    See https://jira.secondlife.com/browse/STORM-2118

    4) DOF doesn’t work in Linux 64 Photos
    Noone has been able to reproduce this on Linux 64bit or Windows or Mac on 4.7.3.
    We would need a JIRA issue with steps to reproduce please.

    Whirly Fizzle

    August 27, 2015

  • I have had firestorm for ages, years! This release, has a weird perspective thing going on, vs the beta release I had been using. Everything looks elongated which makes it challenging to build. Also when zooming around, crashy crashy with no pop up window or anything. I have to go back to the beta version unfortunately.

    Zoz

    August 24, 2015

  • Hmm the “elongated” scene is probably because your camera view has been changed.
    Try doing the following:
    * ESC
    * SHIFT+ESC
    * CTRL+9

    If those don’t help, see http://wiki.phoenixviewer.com/fs_camera for detailed instructions to reset your camera view.

    We would need your logs to see why you are crashing.
    Please file a JIRA issue and see http://wiki.phoenixviewer.com/file_a_jira#how_to_give_us_your_logs for where to find your logs folder.

    Whirly Fizzle

    August 24, 2015

  • Taking a wild guess here – camera view changed & sudden crashing when moving the camera…

    Did you by any chance download the 32bit version of 4.7.3 rather then the 64bit?
    If you were using the 64bit version of the previous viewer and the 32bit version of the new viewer, the 32 & 64bit versions use a seperate settings folder, which would explain the different camera views after update and if you did accidently get the 32bit, you may be suffering out of memory crashes.
    Anyway, a JIRA issue is the best thing to do here so we can get all the details.

    Thanks!

    Whirly Fizzle

    August 24, 2015

  • Does the update fix the problem where after about 20mins of playing or so people and things remain grey because of a texture overload error?

    Lava

    August 24, 2015

  • By “Texture overload error” do you mean that you see text in the bottom right of the viewer saying “# textures discarded due to insufficient memory ” ?
    That isn’t really a bug as such. Whether you suffer from that problem or not depends on your system (especially prevelant on 32bit systems) & viewer settings and the location you are at inworld, even what attachments you are wearing (certain infamous texture heavy HUDs for example).
    Best thing to do is to file a suppot JIRA issue (http://wiki.phoenixviewer.com/file_a_jira) so we can get your system info, settings and logs and have a look whats going wrong.

    Whirly Fizzle

    August 24, 2015

  • About mesh attachments always on same point (right hand by default) it is very easy tio solve that, just make sure you choose to add to a diff attachment, ex: pants choose attach to pelvis, detach and it is all it needs, next time you wear it will go to pelvis.
    Lazy builders should do that before putting their stuff to be sold.
    Shirts should go to chest, pants and skirts to pelvis and so on.
    Most hair creators already did that, no reason for the rest to not do so.
    But is some we can not blame on Firestorm or even the lab (sadly the allow to attach up to 60 on a single attachment point is not a good idea, just a lazy response).

    zzpearlbottom

    August 24, 2015

  • […] has their recent Firestorm Viewer 4.7.3 release out. Now the FS team is looking for stats on the viewer from the Lab. I like the viewer, […]

  • i have a windows 8 , every time i log in i cant move and all i see is my head and shoes . Can someone please help??

    ohNoo

    August 24, 2015

  • if you are still having problems with this, please file a support JIRA issue & support will help you – http://wiki.phoenixviewer.com/file_a_jira

    Whirly Fizzle

    August 26, 2015

  • I tried the work around for the intel and it did not work for me. Maybe I am doing something wrong. Not sure what to do. I do have the HD3000 chipset.

    Noel Zelmanov

    August 24, 2015

  • Noel, if you are still having problems with this, please file a support JIRA issue & support will help you – http://wiki.phoenixviewer.com/file_a_jira

    Whirly Fizzle

    August 26, 2015

  • Well, I’ve been kicking the tires. On the plus side the attachment issue has been solved. Being able to drag the chat tabs around has been nice as well. Unfortunately, the always present memory leak seems to have gotten larger in this version. also even with enough memory, the viewer still goes somewhat unstable as it crosses 3gigs of memory use. This means I have to go back to restarting the viewer after an hour or so, but that’s not that big a deal. At least I can take a quick flight without having to necessarily change viewers (though the LL viewer is still more stable and faster for that.) Overall, good job.

    Crim Mip

    August 25, 2015

  • Tried the new version after a bad experience with the beta and keep getting the same issue. “Failure to load … hair… clothing,,, shoes…” yada yada yada” After a clean install and new ISP. I am at about 100mbps on a Windows 8.1 desktop. I didn’t have this problem on my laptop ( R.I.P last week) and I reverted back to the 14.4 AMD Graphics driver. I have tried several things and wound up going back to an earlier FS version.

    Ambrosia Kamala

    August 25, 2015

  • Thanks for filing a support ticket about that Ambrosia.

    Whirly Fizzle

    August 26, 2015

  • Crip if you sail or fly you should try Ukando instead of LL viewer, the new world map isn answome and its stability is the same.

    zzpearlbottom

    August 25, 2015

  • This time I have to congratulate you, as this release sounds really awesome and I can’t expect to try it out (unlike the previous one)!

    I think it was a wise choice to not just rush out the previous stable version (like it was done with that bad beta with lots of reasons to not upgrade) but instead focus on a really good release. Sometimes quality over quantity is also better and preferred in regard of new features.

    I really hope it runs as good as the release notes sound.

    Though not a feature I use, but I would like to see translations coming back for languages like Spanish and French, since these are some of the most-spoken ones worldwide.

    Lorita Lane

    August 25, 2015

  • I did a clean install of the latest version, and have now been receiving an error message as follows (The transaction with the Marketplace failed with the following error: Reason ‘status_no_connection’). Does anyone know why this might be happening?

    whitefeather macbeth

    August 25, 2015

  • How often is that happening Whitefeather?
    If it happens just very occasionally after a teleport then its nothing to worry about. With VMM the viewer checks with the marketplace at login and after each region change. If something goes wrong there you may see an error like that. It really should only happen very very occasionally though. I’ve only seen it once myself.
    If it’s happening all the time for you then please can you check if the same problem happens on the LL viewer: https://secondlife.com/support/downloads/
    There have been a small number of people getting this error all the time and it was a problem with their marketplace shop & LL can fix that.
    If you have the same problem on the LL viewer, then file a JIRA issue with Linden Lab here: https://jira.secondlife.com/secure/CreateIssue!default.jspa

    If you *only* have this problem on Firestorm, then please file a Firestorm JIRA issue: http://wiki.phoenixviewer.com/file_a_jira
    Note that we cant help you if this is caused by a backend issue, LL will have to fix that. If its a backend issue it will also happen on the LL viewer.

    Whirly Fizzle

    August 26, 2015

  • Uh… that’s a relief. That just started happening to me for a couple of times, right after teleports or login. It only began happening after some sort of rendering crash, brought to me by a ‘Don’t Panic!’ popup. But sorry, I didn’t take note what that was all about, because it was the very first time and maybe it was because my video player was still on pause and a couple of other apps running too. Today, I deleted every single cache file I could find (assets, Inventory, browser profiles), viewer logs, plus the texture_list*.xml files and so far it didn’t happen again.

    Trin Trevellion

    September 15, 2015

  • The new Snapshot window is a bit wonky. Wishing we could change the size of the viewer window ourselves… or of the whole floater, but that is not my problem.

    I chose ‘Save to Disk’ and now cannot figure out what to click to go back to my choices. Sometimes I toggle back and forth between saving to disk and inventory for clients. Now I can’t figure out how to do that. Here is a photo of the floater window: https://gyazo.com/242dfda6bb460a035069d202ad128895
    Where do I click to have that choice again?

    WrenNoir Cerise

    August 25, 2015

  • nevermind!! I found the answer.. Cancel button

    WrenNoir Cerise

    August 25, 2015

  • Yep!

    Whirly Fizzle

    August 26, 2015

  • Oh , hi , Jess x

    U SOOO funny peculiar , darlin 🙂

    Biggest issue wiv Sl is that nobody going there , ain’t it ??

    Tweakin ur resource-heavy viewer ain’t gonna cure that , I doesn’t think , babes ;p

    Wot point in havin sims joined togevva when u ain’t able to cross them at more than walkin-speed , I aks’ ya ???

    Shambles , ain’t it ??

    I luvs u , anywys x .

    Byeeeee . E x x

    Ewanme

    August 26, 2015

  • I am very happy to see a new update however, for some reason, when I would be logged into SL, after a short time, my whole PC system would shut down. As far as I know, I don’t have any of the affected graphic drivers. my pc is only a year old and I also have the NVDIA. Everything on my PC is fully updated, and yes I do have Win 10. I am not getting the msg that is noted on the intel fix page and even tried the fix just for spite to see if it would help, but my system still crashed and restarted once again. So I have had to clean install the previous version once again. The one I have running and have no problems is 4.6.7.42398. Could there be something other causing my whole system to completely crash while using the updated version? I hope you can help me figure this out. Thanks. P.S. Have used FS for years and this is the first time I have ever dealt with something like this.

    Jena

    August 26, 2015

  • Well, I guess no one can help me with this problem. Was hoping to get a little insight maybe as to why my PC System keeps shutting down when I’m using this version, but I guess not. :/

    Jena

    September 7, 2015

  • Jena, best thing to fo is to file a JIRA issue so we can get your system information, logs and your windows dump to see whats causing the system to crash.
    http://wiki.phoenixviewer.com/file_a_jira#how_to_give_us_your_logs
    First thing I would do to try and narrow this down some more is to see if the LL viewer also causes your system to crash. You can download the LL viewer here: https://secondlife.com/support/downloads/
    What antivirus software are you using?
    Some antivirus software takes an extreme dislike to Pipelining & it has been seen to cause the affected systems to BSOD. Known problem antivirus software is Forticlient, Norman Antivirus suite & Panda antivirus.

    Whirly Fizzle

    September 7, 2015

  • Thank You Whirly for the reply. Ok, I downloaded the original SL viewer, and had no problems. So decided to once again install the update to see what would happen, and so far so good! It said something about it changed my graphics to recommended settings because my graphics card changed,,but I couldn’t get that last part. I do have NVIDIA..so whatever the recent upgrade was, it seem to have helped. Thank you again for replying. I do love FS 🙂

    Jena

    September 10, 2015

  • Well, guess I spoke to soon. It full system crashed. :/

    Jena

    September 10, 2015

  • Can you file a JIRA issue?
    (Instructions were given above).

    Whirly Fizzle

    September 11, 2015

  • Hello Whirly, Sorry, I haven’t been able to get back here, to much been going on. I just filed a Jira..hope I did it right. I just did a full factory reset last night for another reason, and thought I would try again, and sure enough..it still happened. 🙁 So yes, I posted it in Jira. I really hope someone can help me..

    Jenadryl

    September 19, 2015

  • Thanks! Yep, you know I saw your JIRA issue 😉

    Whirly Fizzle

    September 19, 2015

  • I was reading a few of these and saw WrenNoir’s post about the new snapshot for the new firestorm, Now he was able to switch from Save to Disk and inventory, I’ve been trying to figure how that is done, anyone know?

    Rash Cat

    August 27, 2015

  • Just click the “Cancel” button to take you back to the save options.

    Whirly Fizzle

    August 27, 2015

  • This is the best, most stable Firestorm release ever. Brilliant. Better performance, no crashes and been using it now since day 1 and have found no bugs or issues. Well done great work,

    Ziggy Starsmith

    August 28, 2015

  • its been 2 weeks now since i cant launch the viewer from chrome. I use windows 10 pro . I go to destination guide click a link to teleport and nothing, been on the forums help chatter its a bug not fixed yet,
    can you fix it asap as it is ruining my second life experience thanks bye

    jjccc Coronet

    September 1, 2015

  • Heya jjccc,

    I don’t see a JIRA isue ot support ticket from you. Launching the viewer from a SLURL should be working correctly but you may not have chrome setup correctly to handle slurls.
    See this wiki page for troubleshooting tips: http://wiki.phoenixviewer.com/slurl
    If you still need help then please file a JIRA issue & support will help you http://wiki.phoenixviewer.com/file_a_jira

    Whirly Fizzle

    September 1, 2015

  • First, let me say I’m not having any problems related to FS or even LL.
    I do have a pretty high-end desk top computer and I suppose I would be called a “low level” user. I don’t have a mesh AVI and the only attachments I wear are some occasional mesh clothing, and a couple of HUDs that have never been an issue. Even most of what I wear is “system” and I only visit a few sims other than my own, and I don’t use RLV so, all-in-all I find the latest version of FS quite usable and stable. Granted, I don’t use every bell or whistle available to be used, but for my needs it works fine.
    Thanks to all at the FS team for allowing me to just plug along at my own slow pace.

    Mewling Moy

    September 2, 2015

  • Hello all
    I installed the last version and it works fine, just a question when I wanna take a snapshot, its on profile, i can’t save it on my computer or inventory. How to change it?

    Eric

    September 3, 2015

  • Click the Cancel button to return to the Save selection.

    Whirly Fizzle

    September 3, 2015

  • […] comentar acerca do que é para muitos um fator que prejudica. Sobre o que temos para hoje leia mais aqui e depois atualize para uma melhor experiência […]

    BBDOLL

    September 7, 2015

  • Why is this hunk of shit viewer locking up on me?

    Anti Goon

    September 10, 2015

  • Please file a JIRA issue with a detailed description of the problem and your system information and logs.
    http://wiki.phoenixviewer.com/file_a_jira

    Whirly Fizzle

    September 11, 2015

  • Wish when you say you fixed the Mesh attachment bug , you actually fix the Mesh attachment bug instead of just lying to us.

    Jesse

    September 13, 2015

  • Okay. So i was only able to save an outfit once with the new version. Since then i have not been able to save any outfits. I have done a clean install and everything. I don’t know what else to do.

    Sara

    September 20, 2015

  • There is likely something you have worn which is “broken” in some way which is stopping the outfit from saving. A lot of people get this problem on 4.7.1 & 4.7.3 & any viewer which uses the new AIS3 inventory system – AIS3 adds a lot of extra checks to all inventory operations and if a check fails when saving an outfit, you will just get an empty outfit folder.
    Open your Inventory and expand the Current Outfit folder (COF).
    Look in the COF folder for anything that isn’t worn (unbolded), anything saying “broken link”, anything saying it’s worn on an invalid attachment point or anything worn on the old “Bridge” attachment point. Take off/delete any suspicious looking items in the COF and try to save the outfit again.
    If you are still having problems, file a JIRA issue (http://wiki.phoenixviewer.com/file_a_jira) and include a screenshot showing all contents of the Current Outfit folder when you are unable to save what you have worn as an outfit and include your viewer logs from that session.
    Quick fix that should work: Go to Avatar -> Avatar Health -> Reset Default female avatar. Then wear all the items again you wish to save as an outfit and attempt to save it. It should work.

    Whirly Fizzle

    September 20, 2015

  • VFS block to a locked file
    VFS block to a locked file
    VFS block to a locked file
    VFS block to a locked file
    VFS block to a locked file
    VFS block to a locked file
    VFS block to a locked file
    VFS block to a locked file
    VFS block to a locked file
    VFS block to a locked file
    VFS block to a locked file
    VFS block to a locked file
    Thank you! Thank you ASSHOLES u left the last version under WinXP with such a lovely bug!
    FUCK YOU VERY MUCH FUCKING ANAL CLOWNS!

    FUCK U ALL

    September 22, 2015

  • You need to update your operating system if you wish to carry on using Second Life.
    There are new compliance regulations coming very soon (before Xmas most likely) which means that all financial transactions on *any* SL viewer will break on XP.
    Then shortly after that, old backend inventory services will be disabled and you will need to be on one of the latest viewers to use your inventory.
    Sorry, but XP is not going to work on any SL viewer much longer.

    Whirly Fizzle

    September 22, 2015

  • Ever since the update my Firestorm will drop to about 3fps after running for awhile and the only way to fix it is to exit and relaunch. Changing the graphic settings from anything to the lowest possible setting has no effect. Clearing the chat logs has no effect. Clearing the cache has no effect. Doing a clean install has no effect. I’ve exhausted every troubleshooting method I can think of to try and fix this issue to no avail. At this point my only option is to try and downgrade to an older version or switch viewers entirely.

    StarServal

    October 2, 2015

  • Star, best thing to do is to file a JIRA issue so we can get your system information & logs & further details & hopefully we can work out what’s going wrong.
    See http://wiki.phoenixviewer.com/file_a_jira

    Whirly Fizzle

    October 9, 2015

  • Is anyone else having issues with Mac El capitain? firestorm crashes quite offten with strange graphics like texture maps on the screen etc…mac book pro..
    worked fine before el capitain update.

    ZiggyRay

    October 8, 2015

  • Do you have Nvidia graphics?
    Lots of people with Nvidia Mac are reporting all SL viewers (even V1 based) crashing frequently when camming or just after a teleport, after updating to El Capitan.
    The crash is in the GeForceGLDriver & it looks like something Apple will have to fix.
    JIRA issues:
    Firestorm: http://jira.phoenixviewer.com/browse/FIRE-16821
    LL: https://jira.secondlife.com/browse/BUG-10302

    Whirly Fizzle

    October 9, 2015

  • Nvidia issues your talking of aren’t EL Capitan based in fact anything the El Capitan fixed a lot of poor performing Nvidia cards that where giving huge hiccups in Yosemite. Most of those issues with EL Capitan are usually due with a poor OS install and can be fixed by doing a clean OS Install. My iMac which runs El Capitan and has a Nvidia card doesn’t have those issues since i got beyond Yosemite.

    Jesse

    October 26, 2015

  • […] November 17th saw the release of Firestorm 4.7.5.47975.  While not as major in terms of LL features and updates as the August […]