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 4.6.9.42974 Hotfix now available.

translation services

After releasing 4.6.9.42969 we discovered a few bugs that affect just enough users to warrant a hotfix update. However, if none of the issues addressed in this hotfix affect you personally there is no need for you to update to it.

The issues are listed below.

We have replaced the 42969 links with the new version 42974 on our download pages.

I apologize for any inconvenience this may have caused.

Jessica Lyon
Project Manager
The Phoenix Firestorm Project, Inc

  • Awesome!

    Will you release in the future a 64 bit version for Linux?

    Thank you for this release people, you’re great.

    Aaack Aardvark

    December 12, 2014

  • Replying to myself, when I saw Whirly didn’t answer me I guessed this was answered 458765328 times in the original release.

    I was right:

    Whirly Fizzle
    December 11, 2014
    YT, a Linux 64bit build is being worked on.

    So now you know if you’re wondering the same =D

    Aaack Aardvark

    December 13, 2014

  • Does this require another clean install, or can we just install on top of what we already have?

    RichD

    December 12, 2014

  • RichD, you should be fine for this hotfix release without doing a clean install if you already did a clean install for the 4.6.9.42969 release.

    Whirly Fizzle

    December 12, 2014

  • As always Firestorm is right there when you need them!! Best viewer out there! Thank you Whirly and Jessica (and Ed) for helping out yesterday with this voice issue!!

    Walter Balazic

    December 12, 2014

  • […] Quelle: Firestorm 4.6.9.42974 Hotfix now available […]

  • i AM NOT SEEING MESH PROPERLY

    Jenny M

    December 12, 2014

  • Jenny, if all rigged mesh is invisible and you are using the new AMD Omega 14.12 Catalyst drivers then this is a known bug in those drivers – see these 2 blog posts by Inara Pey for details:
    https://modemworld.wordpress.com/2014/12/09/latest-amd-catalyst14-12-drivers-continue-sl-rigged-mesh-woes/
    https://modemworld.wordpress.com/2014/12/13/amd-catalyst-drivers-additional-windows-workaround/

    If your mesh problem is different then we need more information to know whats wrong.
    Please file a JIRA issue so it can be investigated – http://wiki.phoenixviewer.com/file_a_jira

    Whirly Fizzle

    December 13, 2014

  • Oh…now you tell us, Whirly! Inworld support were adamant a clean install was needed, so I did! Still, it is so easy now it really wasn’t a Big Deal, but really with a Beta tester roster like the FS one this ought not to have happened!

    Ayesha Askham

    December 12, 2014

  • […] blog post on the fixes reads in […]

  • I still need a fix for the invisible rigged mesh bug here! >_<

    Kernyx

    December 12, 2014

  • Kernyx, if you mean the bug with the latest AMD Catalyst 14.12 Omega drivers causing all rigged mesh to be invisible unless hardware skinning is disabled, this fix will have to come from AMD.

    You can file bug reports with AMD here: http://www.amd.com/betareport

    For further details see these 2 blog posts by Inara Pey:
    https://modemworld.wordpress.com/2014/12/09/latest-amd-catalyst14-12-drivers-continue-sl-rigged-mesh-woes/
    https://modemworld.wordpress.com/2014/12/13/amd-catalyst-drivers-additional-windows-workaround/

    For now you can either untick Hardware skinning under Preferences -> Graphics -> general or roll back your driver to the 14.4 or 14.9 release versions.
    Inaras blog posts also tells you how to force the viewer to use older AMD driver dlls but keep the 14.12 driver on your system.

    Whirly Fizzle

    December 13, 2014

  • ive download this fix, and still cant make work AOS, cant hold my prim baby (it doesnt work, by the way), could you please tell me WHAT HAPPENS NOW???????

    Thanks a lot

    Sissigarcia

    December 12, 2014

  • Sissigarcia, I have no idea why you cannot hold your prim baby.
    Please can you file a JIRA issue (http://wiki.phoenixviewer.com/file_a_jira) giving as much detail as you can about the problem and support will help you.

    Whirly Fizzle

    December 13, 2014

  • +1 for some Linux love on the 64bit version.

    Supa Shang

    December 12, 2014

  • Was hoping this hotfix would solve my issue with SLPlugin not working on Linux 64Bit KDE but it didn’t. Have tried copy/pasta from SL latest release and older FS installs but alas that didn’t work either.
    Despite that, everything else is working fine and I am liking all the new bits!
    Can someone explain for Aaack, me and other Linux 64Bit users what the cryptic “library problems” refers to and if this will be resolved any time soon?
    Hugs,
    Charlie.

    Charlie

    December 12, 2014

  • Charlie, does the information on this JIRA issue fix your slplugin problem? http://jira.phoenixviewer.com/browse/FIRE-15168

    Whirly Fizzle

    December 13, 2014

  • Awesome!!
    FS FanGirl 001 is back in business!
    Adding libqtwebkit4:i386 was all it took.
    Terminal command is;
    sudo apt-get install libqtwebkit4:i386
    (It wasn’t showing up in the GUI “Muon Software Centre”.)
    Confirming this works on Kubuntu 14.04 64Bit.
    Thanks to Samandra & Whirly for quickly resolving this.
    More Hugs,
    ςhãrlîє

    ςhãrlîє

    December 15, 2014

  • \o/

    Whirly Fizzle

    December 15, 2014

  • Today I installed 4.6.9.42974, Windows 64-bit. I never installed 4.6.9.42969. I just went directly to 4.6.9.42974.

    I backed up my settings for each account to a folder on my desktop, uninstalled Firestorm and found and deleted the data files in AppData, installed 4.6.9.42974, launched Firestorm, and restored my backups, one account at a time.

    Performance is much worse than the prior version. Things don’t load (even with draw distance 32). It freezes every few minutes, especially if there are many other avatars close by.

    The prior version ran great. I had no problems at all. I want to go back to it.

    Kammie Zong

    December 12, 2014

  • Kammie, older downloads are available here: http://wiki.phoenixviewer.com/fs_older_downloads

    If you decide not to roll back and need help troubleshooting the poor performance issues on 4.6.9, please file a JIRA issue and support will help you – see http://wiki.phoenixviewer.com/file_a_jira for instructions.
    Thanks!

    Whirly Fizzle

    December 13, 2014

  • Kammie, are you using Webroot antivirus?

    Whirly Fizzle

    December 14, 2014

  • Same by as by you. I go back to my older download cause it worked all fine. At first I install after cleaninstall (make this 5 years) the new Release and all was ok. Then comes new Update cause many Bugfixes .. I delete and cleaninstall again and now runs nothing. I can not install one of the 2 newest Version but the Installation breaks after some seconds and a Data would be missing *rolls her eyes …
    So now – I clean all a g a i n and use my latest old Version and all is fine. I never did this again if a release come out. Is better to wait some weeks *hehe
    Good luck to all
    Happy Holidays

    Caren Jewell

    December 13, 2014

  • Is it possible that there’s a bug in .42969 that prevents one from logging into SL? Or is it blocked?

    Thanks,

    Sean

    ScotHighland

    December 12, 2014

  • Can you login okay now?
    Logins were disabled for some accounts at the time you posted this – LL were doing maintenance.
    http://status.secondlifegrid.net/2014/12/12/post2435/

    Whirly Fizzle

    December 13, 2014

  • Loading bar is stuck on “Logging In” …on every alt.

    What’s going on??

    Ashley

    December 13, 2014

  • Can you login okay now?
    Logins were disabled for some accounts at the time you posted this – LL were doing maintenance.
    http://status.secondlifegrid.net/2014/12/12/post2435/

    Whirly Fizzle

    December 13, 2014

  • Ty for the hotfix!

    Well, somehow the fonts seems to be a bit blurry now. I’ve changed the size etc. but to no avail.

    CPU: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (3300.06 MHz)
    Memory: 16362 MB
    OS Version: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601)
    Graphics Card Vendor: NVIDIA Corporation
    Graphics Card: GeForce GTX 560 Ti/PCIe/SSE2

    Windows Graphics Driver Version: 9.18.0013.4475
    OpenGL Version: 4.4.0 NVIDIA 344.75

    RestrainedLove API: (disabled)
    libcurl Version: libcurl/7.24.0 OpenSSL/1.0.1i zlib/1.2.6 c-ares/1.10.0
    J2C Decoder Version: KDU v7.5
    Audio Driver Version: FMOD Ex 4.44.41
    Qt Webkit Version: 4.7.1 (version number hard-coded)
    Voice Server Version: Not Connected
    Settings mode: Firestorm
    Viewer Skin: Firestorm (Grey)
    Font Used: Liberation (96)
    Draw distance: 200
    Bandwidth: 500
    LOD factor: 15
    Render quality: Ultra (7/7)
    Advanced Lighting Model: No
    Texture memory: 512 MB (1)
    VFS (cache) creation time (UTC): unknown
    Built with MSVC version 1600
    Packets Lost: 0/4,992 (0.0%)

    Sinead McMillan

    December 13, 2014

  • edit:

    Also enabling AML reduces fps dramatically.

    Sinead McMillan

    December 13, 2014

  • Enabling ALM will often reduce performance yes – this is to be expected, same as enabling shadows and other more intensive graphics settings 😉
    The performance hit from ALM can vary from scene to scene and depend on what exactly is in camera view at the time (lots of alpha tends to be the usual culpret).
    The performance drop from enabling ALM should not be any different on this release from 4.6.7 though.
    If you think you are seeing a bug there and have a certain location where we can reproduce this problem, please file a JIRA issue with details – http://wiki.phoenixviewer.com/file_a_jira

    Whirly Fizzle

    December 13, 2014

  • Fonts shouldnt be blurry.
    What setting do you have for Antialiasing (AA) under Preferences -> Graphics -> Hardware settings?
    Setting AA too high for your card can make the UI text look bad (blurry and distorted).
    Set AA to 8x or lower and see if this fixes the problem (you may need to relog after changing the AA setting).

    Whirly Fizzle

    December 13, 2014

  • *ALM, sorry

    Sinead McMillan

    December 13, 2014

  • sowas nennt man dann wohl einen “Schnellschuß”, was ihr da abgeliefert hatten was ?! hahahahahahahaha
    Und das, wo ihr doch vor allem bugs fixen wolltet ROFL Und dann merkt ihr nicht einmal, dass man toolbar buttons im mouselook sehen kann XDDDDDDDDD …. klasse

    Das macht ja Mut für die hot fix version … 😛

    *kichernde Grüße* von Frau Ito
    😉

    Ito Hotaru

    December 13, 2014

  • Mwuahahaha! Vielleicht einfach mal selber als Beta-Tester melden. Dann kannst du gerne beweisen, ob du mehr als nur Sprüche klopfen kannst!

    Ansariel Hiller

    December 13, 2014

  • So where is this hotfix? Or do I have to download the program again, blow away the old one, and reinstall? I only downloaded and installed the version I’m using (42398) this past week.

    Chris Yost

    December 13, 2014

  • The hotfix downloads are available here: http://www.firestormviewer.org/downloads/

    Whirly Fizzle

    December 13, 2014

  • my bro said he had an issue with Object view, funny thing, is I never use it, lol. he will be happy, that it is fixed.

    North Reisende

    December 13, 2014

  • OK, just to be sure, so there’s *nothing* that needs to be deleted or cache cleared, etc. Just install?

    Skye McLeod Fairywren

    December 13, 2014

  • You *should* be okay just uninstalling the old 4.6.9 version and installing the hotfix version.
    I’m probably going to get in trouble for saying that though 😉
    If you have ANY problems though, please do a full clean install – http://wiki.phoenixviewer.com/fs_clean_reinstall

    Whirly Fizzle

    December 13, 2014

  • Some prims and unrigged meshes not rendering at all, specially flooring etc in built up skyboxes & cityscapes. Going back to 4.6.5. Sigh.

    Kylie Remsen

    December 13, 2014

  • I have the same problems with 4.6.7 and 4.6.9. Occasionally certain things that have been rezzed fine will just up and vanish – a chunk of rock, a boat, etc. Usually after I’ve been camming around. I’ll come back and it’s just gone, no way to get it back. Only way is a relog. 4.6.5 never had that issue. I’m on an Nvidia card with up to date drivers and not running Webroot.

    Cassandra Kestrel

    December 26, 2014

  • 4.6.7.42398 is back on my Computer now and runs. After tons of cleaninstall works the Hotfix version for me not without Problems
    Win7 64Bit
    And had never in all the years this problem sorry, so I think I can try tons of cleanInstall again and brings nothing 🙂

    Caren Jewell

    December 13, 2014

  • I am experiencing poor performance on the Mac 64-bit viewer opensim version (there is no 32-bit to test for OS). It is fast for about two minutes, then it dives down to 3-4 fps with shadows turned on. The Kokua viewer runs at 17-20 fps in the same area.

    I see a number of technical issues with the 64-bit version. On inspecting the libraries it use, some are compiled 64-bit, some are a mix of 32 and 64 bit and some even have 32-bit intel + PowerPC (a processor unseen since 2005), but no 64 bit code. – meaning the operating system will struggle as it does not run in clean 64-bit mode.

    Further the only system Framework it opens is the old Carbon library which is pure 32-bit and compiled with the GCC compiler, which also this version of FS is compiled with. GCC was discontinued in OS X support by Apple in OS X 10.8 which is now 3 major system versions ago.

    When running under OS X 10.10.1 FS returns it is running under OS X 10.9.1 and it is calling on an old JavaAppletPlugin that has the wrong architecture, so it does load at all.

    My recommendation to the FS developer team is for now to produce 32-bit versions of the Mac viewer as it has a much smaller vector for failure, and then as the Singularity team has done, make it compile with Clang in newer versions of Xcode before attempting to port it to a modern 64-bit version.

    Linden Lab should take the bulk of the flack for this as it should have been completely rewritten for OS X a long time ago.

    Finally, thanks to both the FS development team and other TPV developers for your great effort on your viewers! 😉

    Gavin Hird

    December 14, 2014

  • I too went back to the old version, the new one ran so slowwwww on my machine I could barely move. My computer was nearly freezing. I ended up doing a rollback and much better now on the last version.

    Pookie

    December 14, 2014

  • Pookie, are you using Webroot antivirus?

    Whirly Fizzle

    December 14, 2014

  • with this version i don’t load nothing 🙁

    ophelia kira

    December 14, 2014

  • Is everything okay now Ophelia?
    When you posted this there was maintenance going on and anyone using Google DNS was failing to load any textures or mesh – see http://status.secondlifegrid.net/2014/12/14/post2436/ and http://community.secondlife.com/t5/General-Discussion-Forum/Nothing-loading-in-world-and-gray-textures/td-p/2875679

    Whirly Fizzle

    December 14, 2014

  • awesome thanks for the hotfix !!!

    Bradley

    December 14, 2014

  • Hi Whirly, is there any progress regarding the notorious “Mennory Alllocation for Vertex Data Failed” bug which hits all 32bit systems and accounts with an inventory containing more than a few objects so hard? I know it´s not a Firestorm bug, but neverttheless…

    🙂

    Vivienne

    December 15, 2014

  • Not really I’m afraid 🙁
    If you crash with that error message usually (not always) it’s an out of memory crash, which 32 bit operating systems are especially prone to with SL viewers. Add to that a very large inventory (which takes up extra memory) and you are even more likely to get an out of memory crash.

    Whirly Fizzle

    December 15, 2014

  • Why you don’t offer and update and not all the core. It’s hardly download everytime your app for make critical updates.

    Isidro A. López G.

    December 15, 2014

  • My partner downloaded the initial update and his Norton Antivirus alerted him of a virus. That’s the first I’ve ever heard of that happening with a firestorm or any viewer update download since I’ve been an SL resident.

    Miyushu Babii

    December 15, 2014

  • well I just happened to notice an older post about this happening because of SLVoice…so I’m going to assume this is why he got the warning. Correct me if I’m wrong.

    Miyushu Babii

    December 15, 2014

  • It happens every single release Miyushu 😉
    It happens with all SL viewers.
    As long as you downloaded the viewer from the official download link, you have nothing to worry about.
    If the file Norton was complaining about was slplugin, then you must tell Norton to whitelist that file or you will have broken inworld media, web profiles and web search – see https://jira.secondlife.com/browse/BUG-2745

    Whirly Fizzle

    December 15, 2014

  • with this version of 4.6.9.42974 … m textures dont rezz properly. they get distorted and start flashing. any suggestions on how to fix this ?

    retodd

    December 15, 2014

  • Retodd, no idea what could be causing that I’m afraid.
    If you have Intel graphics, make sure the driver is up to date – some older intel drivers can cause textures to “flash”.
    If that doesn’t help, please File a JIRA issue (http://wiki.phoenixviewer.com/file_a_jira#how_to_give_us_your_logs) and give a full paste of your system information from help -> About Firestorm and also your logs files. That wiki page tells you what to do and where to find your logs.

    Whirly Fizzle

    December 16, 2014

  • worked good before

    but today i cant rez, talk in open chat, talk IM’s change clothes, i can not tp without getting disconnected. . Even with older versions as with the hotfix is the same.

    How can i fix that
    or
    What can you do?

    pat ayres

    December 16, 2014

  • Pat, that sounds like a connection issue.
    It could be a poorly region – try logging direcetly into a different region & see if everything is normal again. If your problem only happens on one particular region then this region needs a restart (probably caps fail).
    If you have this problem no matter which region you login to, power off your router/cable modem for a few minutes and for good measure also reboot your computer.
    If this doesnt help file a JIRA issue (http://wiki.phoenixviewer.com/file_a_jira#how_to_give_us_your_logs) and support can help you troubleshoot the problem.

    Whirly Fizzle

    December 16, 2014

  • Thank you for fixing my object view tool. It was driving me absolutely bonkers. I downloaded the hotfix in hopes that had been fixed so I didn’t need to bug you all.. and it was *sighs happily*

    Aternia

    December 16, 2014

  • I did again a clean and cant download it stops doesnt install

    Jolie Wonder

    December 16, 2014

  • Jolie, do you mean that the download fails to complete? Or is it the installer thats not working for you? Need more details please.
    Best to file a JIRA issue (http://wiki.phoenixviewer.com/file_a_jira#how_to_give_us_your_logs) and support will help you.

    Whirly Fizzle

    December 16, 2014

  • I am having a mesh issue also with the new hotfix, I did a clean install and afterward loading into sl can never load people with mesh bodies , or mesh anything for that matter, I don’t wear a mesh body, I do however wear mesh hair and feet wich wont appear.
    anthing mesh isn’t working anymore. what do I do ?

    ValeskaRAiN

    December 17, 2014

  • Valeska, I presume you have an AMD graphics card and you updated to the new 14.12 Omega drivers.
    This driver version is buggy and will not render any rigged mesh unless hardware skinning is disabled.
    For details see:

    1) https://modemworld.wordpress.com/2014/12/09/latest-amd-catalyst14-12-drivers-continue-sl-rigged-mesh-woes/
    2) https://modemworld.wordpress.com/2014/12/13/amd-catalyst-drivers-additional-windows-workaround/

    Whirly Fizzle

    December 17, 2014

  • When I got last update, I found that sometimes I’m unable to open groups. I need to and eventually can join them through other ways, but cannot open group profiles. I’m downloading this hotfix now to hope it fixes, but if not I hope someone reads this and would know why that happens.

    Orb

    December 19, 2014

  • Disregard, I think Ive figured it out. Feel free to delete.

    Orb

    December 19, 2014

  • I can’t seem to open the web-based profiles in world. Once I click to view it gives me 2 different links, the avatar name appears after a few seconds and nothing else. It worked on/off on the previous version. I did a clean install, then updated to the latest. Is there anything I can try? I’m using Windows 7 if that helps. Thanks.

    Frankie

    December 24, 2014

  • I was running the 64bit for SL and OS and the more people that were around, the more RAM it used, to the point where I had to shut down all other processes just to keep FS running. This didn’t happen with previous versions. I am going to try the 32bit for SL and see if I have the same problem.

    Marie Resch

    December 25, 2014

  • Switching to 32bit for SL did not change the behavior. I have had to roll back to the previous version.

    Marie Resch

    December 25, 2014

  • After reading through the comments here, I see that others also are having the same issues that I am having with freezing up every few minutes. This is happening to me on two different computers, and this issue is locking up not only SL but the entire computer as well. The freezing lasts approximately 30-60 seconds every time, and is ending with a black screen then finally flashes back to the picture where everything runs again. It seems to me that if multiple people are having this same issue, it’s something that deserves looked at, rather than saying “file a Jira”. I’m not asking for feedback, simply I wanted to put in my two cents and say hey this problem is bigger than you guys think.

    Melisande Whitesong

    January 2, 2015

  • Are you using Webroot antivirus?
    Most people who reported the freezing problems were using Webroot & their problem was fixed after white listing the viewer install folder, cache folder & settings folder with Webroot.
    We ask you to file a JIRA issue because we need to get more information from those on affected systems. If no one can reproduce the problem in-house then it cannot be fixed. If the problem is solely down to Webroot then that cannot be fixed anyway apart from white listing the viewer or removing Webroot from the affected system.

    Whirly Fizzle

    January 2, 2015

  • I’m having the same problem on 64-bit Linux, with the freezing.

    Bob Larson

    January 3, 2015

  • Bob, which Firestorm version are you using? There is no Linux 64bit release of 4.6.9, only 32 bit. Are you on the 4.6.7 Linux 64bit release?
    On Linux there is a known bug which will cause the viewer to freeze if the music URL changes – so if you are at a music event where the DJ’s change the music stream often, this can be a real problem.
    I’m only guessing what the problem could be because it’s impossible to know without seeing your viewer logs after a session where you had one of these freezes.
    Please can you file a JIRA issue (http://wiki.phoenixviewer.com/file_a_jira) and give your full system information & log files.

    Whirly Fizzle

    January 3, 2015

  • Yes, I’m on 4.6.7 on Linux x64. I am hoping that 4.6.9 will soon be available for Linux x64 because I wanted to give it a try. I will keep an eye on the freezing; do you know if it still happens even if you don’t have the stream playing? I am getting freezing even when I haven’t allowed permissions for the radio stream to be played.

    Bob Larson

    January 3, 2015

  • No it shouldn’t happen if the stream isn’t playing. It sounds like you are having a different problem.

    We need more information to have any idea what could be wrong – a JIRA issue really is the best way to do this.
    For starters we need to know:
    1. Your full system information from Help -> About Firestorm.
    2. Your viewer logs after a session where you reproduce the freezing problem.
    3. To know whether the freezing still happens on default out of the box settings (this can be done by renaming the settings folder or a clean install).
    4. More details on how/when the viewer is freezing – eg – is the viewer only freezing when you do certain actions, like opening preferences or turning your camera or teleporting? How is the viewer exactly freezing? Is it short micro freezes that happen constantly or does the viewer freeze hard and never recovers forcing you to force quit?

    Whirly Fizzle

    January 4, 2015

  • I’m using openSUSE 13.2 x64 with the open source radeon driver on an ATI 6750. FPS drops significantly when going to a club with 15-20+ people, even with all graphics settings turned to low, anisotropic filtering off, and anti-aliasing off. The viewer performs great when on a barron land with no other avatars. The freezing happens when going to a populated parcel, and avatars are halfway rendered, not rendered at all, and may be rendered but not dancing (even though they are supposed to be). Pretty much it’s unplayable unless I go to a parcel with no or very few avatars. The freezing happens intermittently when on a parcel with other avatars in view, and will freeze for 5+ seconds at a time. It would be nice if there were a forum here where people could post and communicate, rather than in the comments section. Thanks

    Bob Larson

    January 4, 2015

  • For a problem like this, that “forum” is the JIRA (http://jira.phoenixviewer.com/).
    We really can’t do support or investigate potential bugs in the blog comments. It needs a JIRA issue to be properly investigated by support or the developers.

    Whirly Fizzle

    January 4, 2015

  • What happened with the Linux 64-bit library? I am using Linux and would like to use the latest version. Thank you

    Bob Larson

    January 2, 2015

  • I did a clean install of the new update … I am still crashing when ever I try to TP … what to do? Please help!

    Zelda

    January 3, 2015

  • Zelda, is the viewer actually crashing after teleport or are you being disconnected? Actually crashing because of a teleport is really rare.
    If you get a message like “You have been disconnected from Second Life, View IM/Quit” after teleporting then this is a disconnection not a crash.
    If you only have this problem when teleporting out of or into a certain region then this is likely to be a poorly region problem and a region restart should fix it. Many regions are in a bad state at the moment because there have been no weekly rolling restarts for a while. If a region has broken capabilities then anyone trying to teleport out of that reguion will get disconnected.
    If you have this problem with most or all teleports and it happens no matter which region you are teleporting out of or into then it is most likely to be a connection problem at your end – most likely with your Firewall/antivirus software settings or your router settings.
    If you havn’t done so since this problem started, power off your router/cable modem for a few minutes (and reboot the computer too for good measure).
    If this does not help, then see: http://wiki.phoenixviewer.com/fs_tp_fail
    If you still need help then please file a JIRA issue (http://wiki.phoenixviewer.com/file_a_jira) giving your system information and log files after a session where you crashed/disconnected after a teleport.

    Whirly Fizzle

    January 3, 2015

  • I turned off Webroot and ran McAfee instead, and all of my problems disappeared. Thank you.

    Kammie Zong

    January 4, 2015

  • Awesome!

    Whirly Fizzle

    January 4, 2015

  • i updated to the new firestorm but quickly went back to 4.6.5. I have no voice and did everything firestorm support said to do but I cannot get my voice to work. So until this is addressed I am staying at 4.6.5

    BleuEyedAngel

    January 21, 2015

  • would like to know if this problem gets addressed so I can update my viewer…

    BleuEyedAngel

    January 29, 2015

  • If voice works on 4.6.5 but not on 4.6.9, I suspect that your Firewall is blocking slvoice from the 4.6.9 install.
    Make sure that you have allowed slvoice access through your Firewall and if you are still having problems with voice on 4.6.9, file a support JIRA and support can help you – see http://wiki.phoenixviewer.com/file_a_jira

    Whirly Fizzle

    February 11, 2015

  • the past two days I haven’t been able to see mesh bodies I can see their clothes and their hair but not their bodies I installed the do you wear

    tiffianie richardson

    February 8, 2015

  • I suspect you have an AMD graphics card and you are using the latest 14.12 catalyst omega driver.
    This driver has a bug which makes all rigged mesh invisible unless you disable hardware skinning.
    Roll back your driver version to the 14.4 or 14.9 Catalyst version.
    Also see these 2 blog posts from Inara Pey:

    https://modemworld.wordpress.com/2014/12/09/latest-amd-catalyst14-12-drivers-continue-sl-rigged-mesh-woes/
    https://modemworld.wordpress.com/2014/12/13/amd-catalyst-drivers-additional-windows-workaround/

    Whirly Fizzle

    February 11, 2015

  • for the past two days I haven’t been able to see mesh bodies I can see close and hair but not body I uninstalled the viewer and reinstalled it and cleared my chat and still not working and I asked one of my friends that’s on the same viewer as I am and he can’t see him either

    tiffianie richardson

    February 8, 2015

  • See my comment above.

    Whirly Fizzle

    February 11, 2015

  • you broke it (and I can’t find this on the jira ) the fact that firestorm crashes with certain meshes. (AMD intel or nvidia card doesn’t matter)

    brian

    February 23, 2015

  • Brian, is this happening on the 4.6.9 release or are you using an older version?
    I can only guess what the problem is without more information – The viewer (any viewer) will crash when right clicking certain meshes if you have an older AMD card (4000 series using drivers later then catalyst 12.1) and you have selection outlines enabled. This isnt a new crash though and it only affects older AMD cards and affects all viewers.
    There are a few mesh graphics crashers floating around which will crash your graphics driver – these objects are specifically made to do this & are often found in “combat” HUDs. This is not a new thing though & those meshes basically use the same method as the older sculpty graphics crashers. They will pretty much crash anyone on any viewer.
    If you are using an old pre-materials viewer, some normal meshes will cause a crash as soon as you render them. This particular crash was fixed in with the materials code changes.

    If your problem doesnt match any of those above it would be great if you could file a JIRA issue (http://wiki.phoenixviewer.com/file_a_jira) giving your system information and log files after a crash and if possible details on where to get hold of one of the meshes that is causing you to crash.
    Thanks!

    Whirly Fizzle

    February 24, 2015

  • A few problems I’m having with my viewer at this time. I have added firestorm to my antivirus and my firewall as suggested.

    1. Since a corrupted file that prevented me from logging in forced me to update the latest version, I am crashing. It isn’t telling me I logged out, it is a hard viewer crash. It happens while I am camming and when I teleport making both these things very difficult to do.

    2. http://grabilla.com/05304-66417842-2ac6-4f15-9c96-a3cea3612546.png I don’t know what this is at all but it flickers across my screen routinely enough to give me headaches. And it does it everywhere in no particular pattern.

    I don’t know how to fix this but I would very much like to.

    Thank you.

    Eden

    March 3, 2015

  • The image looks like a sculpty or mesh blowing up.
    Eden, we need your full system information & viewer logs after a crash.
    Best thing to do is file a JIRA issue – see http://wiki.phoenixviewer.com/file_a_jira
    That wiki link tells you where to find your system information and logs.
    I can only take a guess at what the problem is without getting this information but if you are usually crashing when camming or right after a teleport, I suspect you are blowing memory – if you have intel graphics and you are using an older driver version, update to the latest driver – some of the older intel drivers have a bad memory leak.
    An out of date driver version could also trigger exploding mesh.
    If you are just about to blow memory though, you will often see explaoding objects as shown on your attached image just before you crash.
    Please file a JIRA issue & I’m sure we can help you 🙂

    Whirly Fizzle

    March 4, 2015