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 Public Beta and Win64 Alpha releases!

translation services

Firestorm Public Beta 4.5.1.38838 (for all supported Windows, Mac and Linux operating systems)

We had hoped to be able to have all the latest Linden Lab bug fixes and service improvements in our next release, but it looks like it’ll be another month or two before that code is ready from LL. But we also wanted to get a release out before 2014 with the latest (released) code from LL and the latest Firestorm development work. This includes new features like Content Import/Export and Collada Export, plus new features from LL like Materials, ribbon particles, etc. Click for the completeChange LogandKnown Issues. Unfortunately we only have a small window of time to get a release out before 2014 due to the coming holidays, so we haven’t had time to polish it up to our normal quality standards; thus we are calling this a BETA. This means it should be considered a fully supported release, but expect it to have some quirky bugs here and there. Upgrading to it is recommended but not mandatory. You can grab the Public Beta release from our Downloads page. CLEAN INSTALL RECOMMENDED!

 

Firestorm Public “Experimental Alpha” (Windows 64bit) 4.5.1.38838

This release, regarded as separate from the Beta announced above, is a 64bit Firestorm Viewer for 64bit Windows operating systems. This build has had very little testing, and we expect it to have bugs we don’t know about and don’t know how to help you with. Thus it is ALPHA and experimental. Also note that not all of our support or developers can run it. Please consider it unsupported and please do not come to support asking questions that have already been answered on THIS PAGE. If you do, they will send you back to that page. This is an experiment and should be considered pioneer territory for those of you who are adventurous-minded! If you are looking for something stable that has been tested and is supported… please use the normal download mentioned above.

FEEDBACK
Viewers for 64bit Windows have been requested for years, but it’s never been done until just recently. We do not know if it will have tangible notable benefits or not, so we throw it out to you in hopes of receiving in return your thoughts, feelings and findings! If you are adventurous, please feel free to try it; after you’ve been using it for about a week, we’d be interested in your findings. To provide your feedback please email jessica.lyon@phoenixviewer.com; subject should be “x64 feedback”. Click the following link to download the 64bit alpha and read information about it like known issues, whether it will work on your computer, etc. http://wiki.phoenixviewer.com/fs_firestorm-64-bit

LETS REVIEW!
Who should use the Alpha: Adventurous people who have 64bit Windows operating systems.
Who should not use it: Folks without 64bit Windows operating systems and/or folks who prefer something stable, tested and supported. If this is you, please refer back to the Beta described at the top.
Have questions about it? Read: http://wiki.phoenixviewer.com/fs_firestorm-64-bit
Where to download it: http://wiki.phoenixviewer.com/fs_firestorm-64-bit

We hope to have Linux 64bit Alpha before too long and possibly even Mac 64bit Alpha, so stay tuned.

 

Firestorm Q&A video and transcript

This past Saturday we held another Question and Answer meeting with our users. Many questions were asked and answered regarding the x64bit and this Public Beta release. We recommend you watch the video and/or read the transcript from Inara Pey’s Blog here.

 

Blocking of all versions below 4.4.0

We have given ample notice already and are now giving final notice. There are still a lot of people on old versions of Firestorm out there, versions that not only cannot see avatar textures correctly anymore but in some cases also don’t see mesh. We will be blocking all Firestorm versions below 4.4.0 on the 15th of November. Please update now!

 

Enjoy the release!
The Phoenix Firestorm Project Team.

  • inb4blogtrolls

    Cinder Roxley

    October 30, 2013

  • Hue

    October 31, 2013

  • The 64bit installation instructions are confusing. If you get the missing MSVCP100.dll error go to this page and download the 64bit. I get presented with 3 files on that microsoft page which one is the one i need?

    Also the 32bit beta seems to have a lot of known issues. Even glow is broken?

    Bea

    October 30, 2013

  • Try this: Microsoft Visual C++ 2010 Redistributable Package (x64). It’s what I (re)installed; Running fine now.

    JD Llewellyn

    October 30, 2013

  • do i need to download this 451 ver. of firestorm (64bit) ?

    Because, my WINXP is 32bit only.

    Ms. Cristina

    October 31, 2013

  • no, for 32 bit windows only use 32 bit software. For 64 bit windows, use either.

    Iala

    November 10, 2013

  • […] via Firestorm Public Beta and Win64 Alpha releases! « Firestorm Viewer – The Phoenix Firestorm Projec…. […]

  • I’ll pass on both. Boy you guys are really starting to slag behind the official releases. I am starting to wonder if you are getting to far behind to ever “catch up” even somewhat?

    TheMizANG

    October 30, 2013

  • This brings Firestorm up to date with everything LL has officially released. Slagging behind on what then exactly?

    Jessica Lyon

    October 30, 2013

  • guess he’s complaining about the lack of materials support, which is of course in no official GA release of the official SL viewer.

    Iala

    October 31, 2013

  • Not sure about you but Materials is officially released since several versions and when i download the latest official Release Version i DO have materials and its menu’s in the tools floater.

    http://community.secondlife.com/t5/Featured-News/Get-the-New-Materials-Viewer-Today/ba-p/2051927

    This was from 2 months ago. I think it was 3.6.6 or something like that, maybe even sooner…

    NiranV

    October 31, 2013

  • This beta has Materials (if everyone reads the blog you will see what is included)

    Starlight

    October 31, 2013

  • Is…is this what christmas feels like?

    Gk

    October 30, 2013

  • Did a clean install per the instructions and now getting bad flickering and rainbow colors around windows/edges. Is this normal?

    Alicia Parrish

    October 30, 2013

  • You may need to make sure that Firestorm is properly detecting your graphic card, and that your driver is updated.

    For an ATI/AMD card, see http://wiki.phoenixviewer.com/ati

    For an Nvidia card, see http://www.nvidia.com/Download/Find.aspx?lang=en-us

    And for Intel, see http://downloadcenter.intel.com/default.aspx?iid=gg_support-EN_01+home_downloadctr

    If you still have issues, by all means contact us in Firestorm Support English, or even create a support ticket on our JIRA. http://wiki.phoenixviewer.com/file_a_jira can walk you through that process.

    Mister Acacia

    October 31, 2013

  • Had the same on one machine, turns out it had 2 video cards and FS was trying to use the wrong one.
    Used the AMD/ATI config tool to force that card to be used with FS, problem solved.

    Iala

    October 31, 2013

  • I know nothing when it comes to cpu. How do I use the AMD/ATI config tool to force that card to be used with FS step by step please?
    Im using Windows 8.1/ 64bit

    xhale24

    January 6, 2014

  • You’ll prolly want this one: Microsoft Visual C++ 2010 Redistributable Package (x64)

    I had the same error and that solved my issues. And my hats off to the DEVS .. I love how SL looks and acts with 64 bit! I can finally use my 8gigs of ram! YAY!!

    JD Llewellyn

    October 30, 2013

  • thank you for your help.. I was able to download the right file with it and am now previewing the 64bit version on-line.

    Bea

    October 30, 2013

  • Thank you so very very much ^_^

    Mystery Keeper

    October 30, 2013

  • okay this update totally make it 100percent unusable for my 8 core 2.66ghz 16gig ram macpro… There is 5 second or more lag win moving windows around and bring up other windows and just doing anything. i have to force quit the program everytime. Its totally useless…

    michael

    October 30, 2013

  • I had this the 2nd day i went to use the x64 version, but done a clean install and it worked fine for the week of testing.

    prokofy whatever

    October 31, 2013

  • Mac Pro 3,1 (early 2008) 8-core, RAM 13 Gigs, SSD boot drive, Mac OS X 10.9 Mavericks. No lag, no more crashes than on full releases, (which means very few).

    Raymond Martinek

    November 10, 2013

  • I have a MacPro 1,1 Mac x 10.8.5. my comp wont allow a mavericks update unless i redo the whole chameleon boot which i am on at the moment with 10.8.5. 16 gig RAM and ATI 5770 card. 8 core machine. did clean install and nothing still works on the 64bit version it literally just freezes.

    michael

    November 18, 2013

  • When I set a normal map or specular map texture, then close the edit window, the object just reverts back and doesn’t keep the new normal/specular textures. I’ve tried this dozens of times on multiple objects Am I doing something wrong? Am I supposed to press a confirm button somewhere after setting the textures?

    Fire

    October 30, 2013

  • @Bea That is because during the testing, we found that those files are what is needed. And are not sure which one is needed as some of us self compile and have one or all three versions of the redistribute package. And is along the same lines of the app fix that was required for the old V1 Phoenix and Firestorm Viewers. And was given all three, in case if one did not work or was not enough the others might be. the X86 redistribute package maybe all you need, as it is often used to make a 32 bit program compile for use on a 64 bit system.

    animorf Kawadias

    October 31, 2013

  • You write: ‘Unfortunately we only have a small window of time to get a release out before 2014 due to the coming holidays, so we haven’t had time to polish it up to our normal quality standards; thus we are calling this a BETA. This means it should be considered a fully supported release, but expect it to have some quirky bugs here and there. Upgrading to it is recommended but not mandatory.’ Why on earth is upgrading to an unpolished, substandard version of the viewer ‘recommended’? And all the tedium of a clean install? What is the point of this ‘upgrade’ exactly?

    Rufus Attis

    October 31, 2013

  • Bingo!

    TheMizANG

    October 31, 2013

  • ‘Unfortunately we only have a small window of time to get a release out before 2014 due to the coming holidays, so we haven’t had time to polish it up to our normal quality standards; thus we are calling this a BETA. This means it should be considered a fully supported release, but expect it to have some quirky bugs here and there. Upgrading to it is recommended but not mandatory.’ Unpolished? Substandard? Quirky bugs? Recommended? Right!

    Rufus Attis

    October 31, 2013

  • Nobody forced or forces you to use the viewer. If you don’t like it, then don’t use it – or maybe help with doing it better. It’s really that simple!

    Ansariel Hiller

    October 31, 2013

  • Hard to understand how you can so spectacularly miss my point. I’m currently using 4.4.2. I love it. It works fine. I’d recommend it to anyone and have done so. Launching and recommending an ‘unpolished’ and flawed ‘upgrade’ seems (to me, at least) a rather strange thing to do. Hence my question. Care to answer it, instead of putting up a smoke-screen?

    Rufus Attis

    October 31, 2013

  • As I replied in an earlier comment…

    We wouldn’t recommend everyone update to it if we didn’t feel it was very stable and worthy of mass consumption. And I think we would be the best to judge whether it is or not since we are the ones who have done months worth of testing on it. It is very stable and perfectly safe for the masses. Bugs some might find will be little UI quirks. like a button overlapping another slightly.. but not unusable. No release, even full out release.. is without bugs.

    Jessica Lyon

    October 31, 2013

  • omg, yaaaay!!! The 64-bit alpha is perfect, and I can finally get the user experience I’ve been missing out of it!!! Thank you so much, devs!!! Jessica, you can expect a progress email from me in a week ^_^

    Caitlin Mirabella

    October 31, 2013

  • I’m not really sure yet what the big deal is with this 64bit version. I see NOTHING better or worse about it. Nothings improved…I might as well be using the Beta. Maybe it would help if I knew what the point of using a 64bit viewer IS?? I’m just not seeing it. I *do* have more than 4gb RAM…I have 8….So I can use all 8gigs…yay? Again I’m not seeing any improvement compared to the standard viewers. Good for you though? I wish I could be as thrilled, really do lol

    Ailasa

    October 31, 2013

  • “64-bit” is not about memory, it’s about CPU registers which now are 64 bits wide instead of 32 bits. 64 can be very helpful when you do double precision math for a hadron collider, or weather prediction for next 10 years, or genome decoding. Some specific tasks (like data compression) can be speeded up too. But FS hardly uses these features a lot. As a trade-off, a 64-bit data in a CPU register can also be a memory address, thus enabling direct access to “more than 4 Gb RAM”. Though, 32-bit with PAE also can address “more than 4 Gb” (actually, 64Gb, although in MS Windows it’s programmaly limited to 4Gb because of “licensing policy”, etc, etc). Anyway, even at full speed, FS hardly uses more than 2Gb of RAM. With 128Gb RAM on Win8 you only can easier have several apps running side by side (and this will bring other types of issues, heh).
    What is good about 64-bit MS Windows is that it requires you to have a newer CPU which usually has advanced features like SIMD instructions or hyper-trading. Unfortunately, you probably can’t use the most of them if you don’t compile and tweak your FS yourself. But with 64-bit MS Win you have at least SSE2 by default. In some cases multi-trading may be helpfull too.
    If you ever profiled FS, you would see (on Linux, at least) that the most of work is done by GPU driver (with little except for j2k decoding). Practically it means, the better GPU and corresponding CPU you get — the faster your FS will probably be, regardless to how much RAM above 2-3Gb you have.
    So, it’s quite normal, that you don’t see any “improvements” with 64-bit FS on the same hardware (some could even see “drawbacks”), 64-bit is not a “magic bullet”. But if you already have a 64-bit OS on your PC — it’s more natural to run 64-bit apps on it.

    Allex Alcove

    November 1, 2013

  • *”multy-trading” = “multithreading”, my typo, sorry.

    Allex Alcove

    November 1, 2013

  • Annnnd I have been enlightened. Thanks, Allex =D

    Ailasa

    November 4, 2013

  • I broke my hadron collider.
    Any news on the Linux 64bit FS?
    Anyone got an ETA?

    Rez

    November 16, 2013

  • I’ve installed the 64 bit alpha on my hard drive. I’m running Windows 8.1 x64, fully patched. I installed the Microsoft Visual C++ 2010 Redistributable Package (x64). I still get an error message upon starting up FS and I get the identical error messages upon logging in. I click the messages off. I’m able to run the alpha just fine. Just a heads up to the developers. It’s probably because I’m running Windows 8.1 x64.

    Steve

    October 31, 2013

  • I normally like FS, however, why was this even released ? I looked at your known issues page before downloading and this isnt a beta its an alpha. I wont consider it as it is, with the issues it has. Materials and 64bit just isnt worth all the (now) broken bits.

    This is why Jessica/Team usually make us wait guys. This was pushed and people are gonna be sorry it was. Have some patience with updates so they can get them done right. I feel sorry for the help chat, I have a feeling theyre gonna be flooded.

    This is gonna make users unwilling testers for FS/LL code. I dont think its fair to them. You guys dropped the ball badly on this one.

    YaItsMe

    October 31, 2013

  • Maybe you should try the official viewer for a change. You will be surprised what kind of bugs will be in their so called “release” versions!

    Ansariel Hiller

    October 31, 2013

  • Please don’t block the Firestorm below 44. I can’t use the newest, I can still only use the OLDEST phoenix viewer because of my computer. I can’t do anything about it and I am saving up. But I definitely am not able to afford computer or better of anything. If everything will be blocked, I can no longer play SL 🙁 I tried everything this past year, but my computer does not work. 🙁

    Tris

    October 31, 2013

  • Try one of the non-graphical viewers like Radegast( http://radegast.org/wp/ ) or metabolt( http://www.metabolt.net/ ) then, considering if you’re using a viewer that old you can’t see anything right to begin with, I don’t think a non-graphical viewer will be too much of a hindrance… and radegast actually does have a 3D Viewer window if you need it, but I don’t know how well it will work on your machine.

    Luna

    November 3, 2013

  • Rather it’s broken or not i’d like to test a linux 64 build please?
    Gettin tired of having to use singularity to view flash media… 🙂

    Wolfee Darkfang

    October 31, 2013

  • This update is very nice, fixes a lot of issues.

    But how do you get rid of the blue bar at the top? I like everything grey.

    Randompersonwithquestion

    October 31, 2013

  • The 64-bit download page says there is no point in 64-bit Windows if you only have 4GB of RAM.

    This is mistaken. Your video card memory on a 32-bit system has to fit in the same address space. That;s no problem with 2GB of RAM, but a big chunk of RAM lost on a 4GB system. And it depends on your video card. There are ways of getting round this, and using the lost RAM for something such as a RAMdisk, but going 64-bit works better.

    An upgrade to 64-bit Windows is not a smooth easy path. But it does make a big difference to a 4GB machine, starting with reducing the need to page to virtual memory. How much you notice depends on what you are doing.

    Wolf Baginski

    October 31, 2013

  • This helps me understand the point of 64bit a little better. Gahh somebody throw me a wiki lol

    Ailasa

    October 31, 2013

  • >This is mistaken. Your video card memory on a 32-bit system has to fit in the same address space. That;s no problem with 2GB of RAM, but a big chunk of RAM lost on a 4GB system. And it depends on your video card.

    Either I couldn’t understand what you meant, or I must doubt your saying, sorry…
    Oversimplifying, CPU doesn’t address a dedicated GPU’s _internal_ RAM directly. CPU reserves (maps) a bit of “general” RAM and uses it to exchange data with GPU (i.e. like a mailbox or the like). On 32-bit, address of this “mailbox” must be below 4Gb and it perfectly fits in address space. There’s no difference between 1Gb, 2Gb or 4Gb, “mailboxed” RAM is “lost” only in the sense that CPU can’t use it for other apps.
    In case of 32-bit with PAE things are a bit more complicated, more on this: http://msdn.microsoft.com/en-us/library/aa366778%28v=vs.85%29.aspx#how_graphics_cards_and_other_devices_affect_memory_limits

    “Note that memory on our graphics cards DOES NOT COUNT towards the physical memory limit because it does not occupy address space as seen by the CPU. However, hardware mappings do. A graphics card with 2GB of memory on it will probably not have more than 256MB of mappings if the BIOS has memory remapping disabled (which it should for a 32-bit OS). That’s why the physical memory limit is typically around 3.5GB, even if you have a graphics card with 1GB — hardware mappings seldom exceed 768MB.”

    Allex Alcove

    November 1, 2013

  • Fullscreen don’t work on OS X 10.9 and have some graphics issues.

    SImon

    October 31, 2013

  • Never mind, it turns out the latest stable OpenSim release (0.7.6) has broken materials. If you use the latest OSgrid version instead (0.8.0) materials work perfectly in Firestorm. Keep up the great work!

    Fire

    October 31, 2013

  • The Mac version has a small issue. Because the app is from an unidentified developer, you will need to do the follow steps instead of double clicking the app icon:

    1) In the Finder, locate the app you want to open. Most apps can be found in the Applications folder.
    2) Press the Control-key, then click the app icon.
    3) Choose Open from the shortcut menu.
    4) Click Open.

    Andy L

    October 31, 2013

  • Thank you Andy! I was able to help another user with your information and we’ll be adding this to our Wiki. Cheers!

    Willow

    October 31, 2013

  • […] Firestorm team announced that you can now download the public beta version of release 4.5.1.38838 of their very popular […]

  • Thanks for getting to my question in the Q&A.
    Hugz!

    Virtualban Alex

    October 31, 2013

  • Can you clarify if 4.5.1 OS Beta includes the fix for the “4096 Bug” in OpenSim?

    If so it would be helpful to include mention of this in the “OpenSim New Features and Improvements” section of the release change log at
    http://wiki.phoenixviewer.com/firestorm_beta_release_4.5.1.38838_change_log

    Ai Austin

    October 31, 2013

  • Yes it does!
    I should have that list complete later on today. Ive been pushed for time these past few days 🙁

    Whirly Fizzle

    October 31, 2013

  • I see from the “OpenSim New Features and Improvements” section that new icons are in place for the OpenSim build but they don’t show on the installer .exe file for Windows or the desktop icon to run the OS version (though they might be under the bottom left short cut overlaid arrow in that case?). If someone can confirm they really are meant to be showing in various places I will make a JIRA entry with snapshots.

    Ai Austin

    October 31, 2013

  • Yes it does.. actually release notes are still being written. Takes a long time to write them up.

    Jessica Lyon

    October 31, 2013

  • Thanks Jessica… all the efforts of the Firestorm team are very much appreciated, and the OpenSim capabilities are welcome.

    Ai Austin

    October 31, 2013

  • Not really happy about the Public Beta being pushed via the main channels, making that notice in the Firestorm log in page about a new version being available… It’s not ready for mass consumption, and I would recommend not upgrading to this until they release a final stable non-beta version of Firestorm 4.5.xxxxx…

    Gibby Gibletz

    October 31, 2013

  • We wouldn’t recommend everyone update to it if we didn’t feel it was very stable and worthy of mass consumption. And I think we would be the best to judge whether it is or not since we are the ones who have done months worth of testing on it. It is very stable and perfectly safe for the masses. Bugs some might find will be little UI quirks. like a button overlapping another slightly.. but not unusable. No release, even full out release.. is without bugs.

    Jessica Lyon

    October 31, 2013

  • What??? So the “masses” run out of memory every other fifteen minutes and this is “safe”? Do you read your crash reports?

    (Faints)

    Vivienne Schell

    November 1, 2013

  • Agreed

    TheMizANG

    October 31, 2013

  • Beautiful. I’ve been running FS all night so far nd no crashes or glitches in evidence so far. Good job! It is SO GOOD that I no longer have to switch Viewers to work on materials surfaces!

    Motoko Henusaki

    October 31, 2013

  • Niran, your viewer, as Kokua, Cool Sl viewer, Rlv, UKanDO, ragedast, Lumylia, Exodus and some others even else known, does not belong to the Major league of Tpv’s where Firestorm is leading (Singularity, Catznip, old Phoenix being the others!).
    Therefore jessica can’t remember all the features that those same viewers have already for months!
    (Wonder if the inv prim fix when using Alm is on this release!).

    zzpearlbottom

    October 31, 2013

  • Go home ZZ, you’re drunk.

    Singu and Catznip are not leading anything. They are just real sparkly diamonds in a collection of mass-production fake gems.

    NiranV

    October 31, 2013

  • You are just pissy because Niran does not make his viewer to please your every little need. I have read your complaints on his blog many times. Over the dumbest crap. It is always something with you. I don’t know why its so hard to get through your head that his viewer is for his needs not yours. You either like it or you don’t and move on. Just like any other viewer. One other thing…you have seriously bumped your head to line up his viewer to Cool Viewer…really!? Both Black Dragon AND Firestorm are top dogs in my book. Niran offers features it takes Firestorm months to come out with, and though he may not be willing to have many of the lil quirks and nifty tools Firestorm gives us..his graphics features are out of this world, AND he is just one person, not a team. So give him some credit.

    Ailasa

    October 31, 2013

  • LOL

    TheMizANG

    October 31, 2013

  • […] Firestorm public beta and Win64 alpha releases! – Firestorm […]

  • Win64 version is missing a lot of the windlights from the 4.4.2.34167 version.

    Diamond

    October 31, 2013

  • We just checked the windlights. On 4.4.2 release there are 683 skies. On both the 32 bit beta and 64bit windows alpha there are 725 skies.
    Which windlights are you seeing missing?

    Whirly Fizzle

    October 31, 2013

  • Just compared they are not missing in the 64 bit version. 42 new sky settings were added this release and the 64 bit has 42 more than the last release.

    Starlight

    October 31, 2013

  • I thought y’all said some time back that 4.4.2 was the beginning of not having to do the clean install anymore, yet this 4.5.1 requires it?

    Demina

    October 31, 2013

  • Backup settings, do the full clean install, restore settings. Done.

    Crim Mip

    November 1, 2013

  • Blog and instructions very confusing and hard to tell which is which download.
    When downloaded logo’s are the same and Name for x64 is incomplete.

    June

    October 31, 2013

  • Thanks bunches for the x64 Firestorm. I’m running it in Windows 8.1 and so far it’s been a success (only one day but hey it works and no error messages). Of course it’s always entertaining to come into the blog and see the usual flamers and fans – hi y’all! Onward and upward!

    Cincia Singh

    October 31, 2013

  • x64 version tested on Win7 Prof 64 8 GB AMD system … no improvement over 32-bit version 4.4.2 noticeable, possibly even slower; texture memory hard limited to 512 MB in debug console, for this reason even worse results in visual values ​​(again blurry textures in the field of view).

    Conclusion: At the moment an update is not recommended if 4.4.2 is stable.

    =)

    12345

    October 31, 2013

  • in x64 the radar is very poor

    Ito Hotaru

    October 31, 2013

  • Hey guys, Just thought you should know that hiding legacy/usernames Is broken in the new beta/alpha as the names in the chat box still show it like this for example. Kitsune (Foxi.Kitsune) But in the 4.4.2 34167 it doesnt do that, it stays like it should which is “Kitsune” and that’s it. I’d like to use the new betas but this issue is annoying and no one in the support group knows how to sort that out. so i figured i should let you know to fix it. Thanks so much.

    Kitsune

    October 31, 2013

  • The Beta runs great, I didn’t see anything unexpected at all. Bugs inherited from LL for the most part – and fully expected.

    Today I installed the 64 Bit Alpha. The installation went perfectly, no hiccups. Once up and running, several things got my attention immediately.

    My frame rate went from ~185fps with the Beta, to ~240fps with the 64bit application. (in a simple scene)

    For some reason, both lowered graphics from what I normally run, and disabled Advanced Lighting on install/import of settings via Backup. My card is an NVIDIA branded GTX660ti .

    The other notable difference between 32 and 64 bit is that when I open the group chat for a large group on the 64 bit, the participants list populated very quickly – as opposed to “Loading….” and never doing anything more.

    For a long time, I have had issues loading profiles. Very slow, if it works at all. So far, the 64 bit is working beautifully.

    Both versions seem quite stable, meaning try as I might, I have yet to be able to crash either one. Nothing that I normally do, is broken. :-))

    Gryphon

    November 1, 2013

  • In other words, no difference whatsoever in your actual graphic display of SL since the most it will feed is 45fps. Rendering more copies of the same frames doersn’t make the graphics better.

    Crim Mip

    November 1, 2013

  • It shows an increase in performance, and is stable. Unless you want to argue that as well.

    In that setting, no real difference. In a busy place, when frame rate might have dropped to less than 45fps, it stays above 45fps.

    Since a “busy location” is hardly a constant of any description, I didn’t bother citing that. I think a ~30% increase in performance is something worth mentioning. And logic dictates that if there is that type of an increase in a stable and simple scene, tehre will be an increase in a more complex scene.

    Of course, you may not see it that way. Depends on your agenda.

    Gryphon

    November 2, 2013

  • I’m saying that the absolute best frame rate the SL servers will send your viewer under ideal conditions is 45. Under less than ideal it is less. You can’t get a real frame rate higher than the frame data being sent to render said frames. Any extra that is being reported are just repeated frames rendered with the same data while the viewer waits for the data for the next frame to be sent. I have no agenda, I’m just pointing out that if your rendered frame rate never goes below 45 it makes absolutely no difference what the number is as far as what you see in the viewer window. Somebody getting 50 fps will see exactly the same level of quality as somebody getting 150 fps does.

    Crim Mip

    November 3, 2013

  • I am using the Beta on a MacBook Pro and it seems nice but two things nag at me, The favorites dont show on the login screen and the nice new multi line input bar is like type in molasses.

    alisroma

    November 1, 2013

  • Unfortunately accounts with ‘Resident’ do not show the favorites on the log in screen. It’s a bug that the devs are looking into.

    Starlight

    November 1, 2013

  • Woot!!! No more lag!! This is an awesome update, I like the special functions and I didnt need to clean install. It did automatic 😀

    Matsui

    November 1, 2013

  • spend more time change viewers, and crash to stay in game not good play time with all these updates last year game was fine now u update so much folk complain less fun try stay in game

    marilynlove

    November 1, 2013

  • Installed 64bit version on Win 7, 8GB Ram. I have two avatars in SL. When logging into one, everything works fine. Logging out and logging in with the other, I experience temp freezes every 15-30 seconds until I clear cache and restart FS.

    Robert

    November 1, 2013

  • firestorm beta 4.5.1.38838
    I cannot find the volume controls or the search bar. It’s really rather annoying to have to mute sound through cntrl+P

    Aileen Brashe

    November 1, 2013

  • Aileen R click the top bar and select search bar – this will show the search bar :). Volume controls are top right of your screen and also in prefs > sound & media

    Starlight

    November 1, 2013

  • Prefs => Interface => Show media controls in top menu. This is turned off by default in Phoenix Mode, because Phoenix Viewer didn’t have them in this place.

    Chakat Northspring

    November 2, 2013

  • This beta version crashes way faster for me as soon as i enter Bondage Ranch. On the previous version i usually lasted 10 mins before i got that “textures discarded due to….” bug. With this one i last just a few min, it don’t give me that error just a small popup with a OK button i can click. No crash report is being sent either 🙁

    Also i wonder if someone has made a tuturial for Photoshop how to create the materials textures, i’ve just found one for Gimp 🙁

    Vanity

    November 1, 2013

  • Vanity – if you are on a Windows 64 bit OS and have more than 4 gig RAM, try the alpha 64 bit version as this should eliminate the out of memory crashes.

    Starlight

    November 1, 2013

  • sadly i’m on 32bit Starlight, but maxed out memeory on motherboard and vga card

    Vanity

    November 1, 2013

  • So you wanna tell us, that the 64bit version is only reeased because the Firestorm team is not able to make the software run on an average 32bit OS? Right? Btw. , the annoying memory allocation bug is not fixed in the 64bit version, it only lets Firestorm stay alive for a lil bit longer due to the higher amount of available RAM on 64 bit OS. But it´s still there. Honestly, if the team isn´t able to make this happen on the hardware and OS which apr. 80 percent of the SL users happen to use, then the team should consider to retire as No 1 viewer provider. Really.

    Vivienne Schell

    November 1, 2013

  • So, 80%? Wow. Where exactly does one find a statistic such as that?

    We’ve had 64 bit processors for how long now? 13 years or so? Microsoft put out a 64 bit version of XP in what, 2001?

    SL is outpacing the obsolete gear. No surprise there.

    Gryphon

    November 2, 2013

  • 1) From where you’ve tugged out this “80 percent”? Did you have done some survey?
    2) Majority of Firestorm users, in general, received the newest beta/alpha rather positively. When you make a sedan car, you can’t make happy users, who wants/owns cabriolets or combis.

    Chakat Northspring

    November 2, 2013

  • http://stats.unity3d.com/web/os.html

    That´s pretty up to date. And pretty reliable. Even if there is made no difference made between 64 and 32 bit, anyone with a lil bit of insight into the PC market can read the numbers.

    The Firestorm team outpaces no one but themsellves by releasing two superbuggy pieces of alpha software which ruin the SL experience for a majority of people, anyway. And if you were member of some of the more mportant power user groups in SL you´d know that I am by far not the only one who shares this opinion.

    Vivienne Schell

    November 3, 2013

  • Okay, so when I try to log in with the 4.5.1.38838 beta I get the following message:

    Login failed.
    Despite our best efforts, something unexpected has gone wrong.

    Please check status.secondlifegrid.net to see if there is a known problem with the service.
    If youcontinue to experience problems, please check your network and firewall setup.

    If I sit long enough on the login screen, the screen turns light pink and has the message “Socket operation timed out”.

    I installed the beta on my dual boot Win 8 install and it worked fine, but on win 7 its not connecting, singularity and the offical viewer are both connecting, any ideas whats going on?

    (Normally I don’t have to do any special port shit or proxies).

    Windows 7 64x and I did also try a clean install.

    Any ideas?

    Thanks.

    The Deer

    November 1, 2013

  • Sorry Jessica for playing with some remarks, obviously some just didn’t catch them, lol!

    zzpearlbottom

    November 1, 2013

  • Ran out of memory within 5 minutes, client lag, client lag, client lag…installed, deleted, trash can.

    Vivienne Schell

    November 1, 2013

  • Has anything been done about the “textures discarded to insufficient memory” bug? My understanding is that this bug is due to something that LL did/broke when they brought in SSA/SSB and not specifically a Firestorm bug. However, it has ruined my SL experience to the point whereby i seldom log in anymore. I have tried every so-called fix and work-around going and nothing makes a jot of difference.

    Many MANY users are affected by this bug. Do you know when something will be done about it, please? Until it’s addressed i feel very “meh” about trying out any Viewer update, Beta or otherwise.

    Thanks.

    Squashy

    November 1, 2013

  • As far as I can tell, this bug is a Firestrom only bug. Didn´t happen to me with any other viewer out there, and I tried them all. So, LL is innocent.

    Vivienne Schell

    November 1, 2013

  • It may be so; i don’t really understand what’s causing it. All the more confusing since it happened to me on Cool Viewer as well, but not on Niran’s.

    Squashy

    November 2, 2013

  • Squashy – if you are on a 64 bit windows OS and have 4 or more gig of RAM – try the alpha win 64 bit version of FS – should stop the out of memory crashes

    Starlight

    November 2, 2013

  • Thanks, Starlight. I can’t use the 64-bit version on my pc. However, i downloaded the latest Niran’s viewer and no crashes! I don’t by any means have a high-end machine, but so far so good. 🙂

    Squashy

    November 2, 2013

  • Looking at the change log, Firestirm 4.5.1 beta incorporates LL viewer changes up to 3.6.7. I ask as I think thw reallya nnotig problem of prims like floors and walls not showing until you click on them seems to be a new issue in the latest FS beta, whereas it was fixed (I think, at least reduced) in recent LL viewers. S yonee lae seeing this in FS 4.5.1 beta?

    Ai Austin

    November 1, 2013

  • OMG yes! Collada export!

    MoonWhisper

    November 1, 2013

  • Macbook pro (r) MountainLion Issues:
    1- When Alt-Click on an avi sometimes the Cam madly turns to an unexpected direction then stops and after that you can cam around normally (occasionally happens not every time same like in the latest LL Viewer)
    2- Random Crashes on Log Out
    3- When using “Local Textures” the Viewer freezes as soon as you select the texture
    4- FullScreen option not working properly as in the Official LL viewer
    Review:
    The overall performance on a Mac is much better than 4.4.2 in terms of rendering and graphics, but for creators the issues with caming and broken local textures does not help at all. I have reverted to 4.4.2 at the moment and I hope those issues are fixed on the next official release.

    Karlos

    November 2, 2013

  • Word on the street is both of these releases are “junk” its going around SL in the groups i’m in. People are uninstalling and reinstalling the previous version. I am holding off of either one of them based on this. Try at your own risk, have that old version ready to reinstall….

    TheMizANG

    November 2, 2013

  • I discovered a bug in the 32bit Beta…if you create a classified ad, the text saying you don’t have any doesn’t go away, and the ad editor is broken after you publish it.

    Marie Resch

    November 2, 2013

  • I appreciate the upgrade.. I have noticed some change in things.. I dont seem to have the lag i previously had .. but I do see multiple problems..
    1. logging in even after a clean install is a problem .. crash every time and not once maybe twice or more.
    2. once i do finally get in .. i still get the flash to black screen as it is processing something.. never occurred when i was on 4.4..
    3. I have been getting logged out lately with the view chat window..
    4. Trying to maneuver through my inventory sucks as you do a search you cant collapse folders you dont need.
    5. I have always crashed on log out.. It have never logged out properly on this version or the 4.4 version.
    6. When i do log in i am a cloud for like 30 minutes or more.
    7. teleporting is crap.. get stuck constantly in teleporting window to go nowhere at all.
    To me the new viewer is a bit unstable. I hope the later version addresses some or all the issues. I have had to stop using the view cause of its instability for me.. i spend more time logging in and out then actually being in SL.

    Destynee

    November 2, 2013

  • It’s FREE. Quit whining.

    Nicholas Melchior

    November 2, 2013

  • Any other viewer is free, too. But if the structure of SL would be based on “free” and not -as it is- on commercial purpose, there would not be any SL I remember times when TPV folks actually not only improved Linden Code but fixed it, as the grandfathers of all TPV developers did with the notorious 1.19 Linden release. Obviously Linden Lab gave up on using the paying customer as alpha/beta tester guinea pig, while the later Phoenix Team adopts the former Linden Lab role – which included releases of more or less instable stuff, just because the kids wanted to have fun with presenting their latest toys to the public. This former LL attitude almost killed Second Life, beacuse it might work in a truly free environment, but never can work in a commercial one. Being No. 1 provider of SL client software – in this sense – includes responsibility for the user experience and the commercial environment, and excludes the childish attitude of “I WANNA SHOW OFF MY NEW TOYS AND BE “CUTTING EDGE”!” Second Life as a commercial construct is cutting edge and fragile anyway, and it does not need anything of significance which is not cutting edge, but over the edge – as this particular release (especially the almost meinstream incompatible 32bit version) is.

    I strongly suggest the team to remove AT LEAST the “update your viewer” button on the viewr startup screen and make this release less noticed until some of the major bugs (memory and the like) are fixed. SL as a whole cannot afford to annoy the percentage of users this viewer release – from a known as reliable Np. 1 provider – certainly annoys.

    Vivienne Schell

    November 3, 2013

  • Since you are so dissatisfied with the Firestorm viewer and the alleged practices of the team, I have asked Jessica to refund to you all the money you’ve paid the team to download and use Firestorm.

    You should be able to apply that cost toward the purchase of a viewer that better suits you.

    Mister Acacia

    November 3, 2013

  • If a viewer consuming – by default- more than the double amount of RAM as any other viewer on the planet and runs helplessly out of memory with an inventory containing about 80-90 k items (quite normal for a power user) suits you well, ok. Your choice. Thanks for the fish! And btw, you did´t get anything.

    Vivienne Schell

    November 4, 2013

  • Hey kid, the issues your rig has with Firestorm are YOUR issues. Each and every machine is different.

    And newsflash for you kid – Linden Lab still uses its user base as alpha/beta testers for their software, now expanded a few years back to include server software.

    Your facts: Get them straight before spouting off.

    Dark Wolf

    November 6, 2013

  • Hello. I download new (4.5.1.38838) 64bit version and doing slowly as the previous version (4.4.2.34167) example at my home 4.4.2.34167 have 70-80FPS, 4.5.1.38838 have 50-60FPS in other places also see a big difference in the quality of work…

    4.5.1.38838 and 4.5.1.38838 works at working on the same settings… Maybe anyone know why such a difference?

    Thanks for help and sorry for my English!

    Nicol Putzo

    November 3, 2013

  • ANOTHER FUCKING UPDATE WITH TONS OF BUGS !!!
    INSTABLE AND VERY SLOW ON A i7 HASWELL/16GO RAM/NVIDIA 660 GTX 2go on WIN 7 PRO and WIN 8.1 PRO. I SPEND MY TIME WITH FIRESTORM ONE MORE TIME !!

    DON T MAKE ADVISE FOR A BETA VERSION IN THE FUTURE. SHAME ON YOU.

    Nova

    November 3, 2013

  • Download a fixed version here: http://secondlife.com/support/downloads/

    Ansariel Hiller

    November 4, 2013

  • Bwahahaha I love what you did there 😉

    cincia singh

    November 6, 2013

  • this new update its preatty awesome less lagg and crash huraaay but i have one problem when i have attached this:#Firestorm LSL Bridge v2.5 I can’t move at all i tried recreate the bridge but still can’t move x3 what should i do,(sorry for my bad english)

    bridge

    November 3, 2013

  • Bridge – check that you haven’t inadvertently enabled Move Lock. It’s in the Avatar Menu – Movement or use Ctrl Alt P

    Willow

    November 4, 2013

  • Installed 64bit and restored my settings without any problems so far. Still the only viewer that supports my card too (displays shadows). Win 8.1 – i7 3770k – geforce titan – 16gb ram (4gb dataram ramdisk)

    I love you so much firestorm guy.

    00stevey

    November 3, 2013

  • Beta version 32bit works fine for me…. we can see materials features now!
    Only one question: is it possible to switch off all toasts (not only IM and group)… I don’t need the puplic chat toasts (nor console) too.

    Tommi Waydelich

    November 3, 2013

  • Tommi – See the options in Preferences – Chat – Notifications

    Willow

    November 4, 2013

  • This so far is the only V3 style viewer I’ve ever been able to log into and say I like, granted I’m using the V1 layout. My ONE and ONLY request, is a small check box that says “Chat Bar ALWAYS has focus”. This is something that 1.23 TPV’s do, and it’s very handy for macro keyboards. If you can add this, you’ll have a switch.

    Hokusai Otsuka

    November 3, 2013

  • Love it. The x64 Alpha installed just fine and everything is great… as has been the case for every other previous release – not sure why so many think the FS team are responsible for fixing the kludges on their machines – maybe the usual crowd of whingers should try building their own viewer. As for me, framerate doubled and none of the occasional out of memory issues i was getting previously, so hats off to the team, and thank you.

    Serendipidy Haven

    November 3, 2013

  • 4 days on with the x64 alpha and I have to say I’m happily surprised at how well it runs. No, it doesn’t double my fps (no one should believe those claims anyway) and no, it doesn’t make SL look like GTA (it never will) but it does start reliably, it’s stable (no crashes so far), it’s got all the bells and whistles and updates from a fairly recent LL code base, and it didn’t eat a baby or kick a puppy! If you’re collecting votes count mine in favor of continuing with building the x64 version. Also, please talk LL into updating to x64.

    cincia singh

    November 3, 2013

  • Having camera issues. Actually, had them before even on stable releases.

    1) Camming (Alt+click) sometimes “misfires” and gets me focused on a wrong object and turns my camera the wrong direction. Might be a matter of perception, but it seems to happen more often in x64 version.

    2) I always have “Disable camera constraints” on. But even with my draw distance set to 1km I can’t “hook to” and get camera focused on clearly seen, but distant object. It is even harder to hook it to the terrain.

    Mystery Keeper

    November 3, 2013

  • trippy fall

    November 26, 2013

  • Im with cincia on wishing LL will do a 64b dedicated version soon!

    zzpearlbottom

    November 4, 2013

  • Reading all the comments I can see a huge variety of results and reactions.

    In my case FS works beautifully in Linux, 32 Bit version (hoping to see a 64 version for it soon as I would -love- to be able to play streams directly from the viewer), materials are cute and the new features makes this release really attractive.

    I’m not on SL, of course. I use the Open Sim version. I had less crashes than before, alas there’s always some crash. No biggie, I just click on the icon and launch it again.

    The restore preferences button worked very well, but since I use the Firestorm mode + Firestorm skin I had to restore the preferences a couple of times until everything was in place. Again, flex a finger muscle to perform a click won’t bother me at all.

    In Linux do a clean install is as simple as delete a folder and reinstall. But did I mention I have the last version running on Mac too? You know, it’s even more stable.

    Thanks Firestorm team for all the hard work. I’m enjoying this beta.

    Here’s a silly question: will we have a collada export for the avatar itself? or an OBJ export? In my personal case I don’t need to export things out, as 90% of what I do is produced outside the grid and then imported (meshies), but export the avatar is something I can do only in Phoenix 1.5.x and have the avatar in blender it’s a useful tool to create wearable things, like clothes.

    Regardless I’m very happy with this release, thank you again for all the hard work guys.

    Aaack Aardvark

    November 4, 2013

  • Personally, if you’re going to edit on the avatar, I recommend the Avastar plug-in for Blender. Well worth the $22 – because it gives you an avatar mesh already rigged and ready to edit and upload. Works with all current viewers, as well.

    Tonya Souther

    November 4, 2013

  • Tonya, agreed, Avastar does a nice rig with custom bones, auto rig and it’s easy to animate for more than one character, feature I love.

    However I would love to know if export the shape is planned, that will make me decide if buy Avastar or not lol.

    Thanks much for the answer!

    Aaack Aardvark

    November 5, 2013

  • To the best of my knowledge, nobody has any plans to export the avatar mesh as .OBJ or anything else.

    Tonya Souther

    November 5, 2013

  • Beta versions!!

    For those of you who aren’t aware of this betas are releaed so that more bugs can be found. You can’t find all the bugs in a small sample group. These things need to be released to the public so that the larger pool of users with a vast array of configurations can report bugs so they can be worked on. If you don’t like that don’t download a beta.

    You might look at it this way: Running beta software and reporting problems through the channels is supporting FS and all the other users, a public service for the more civic minded. If you are just in it for you, stick with what works and stay safe.

    As for me I am whipping my 64 bit alpha screaming “Go on crash now, lose my build. I WILL report you!”

    Drinking at my KB,

    Georgie

    George E. Tungsten

    November 4, 2013

  • I agree with Georgie, but I think that the announcement “Upgrading to it is recommended” should be reworded. This beta is stable enough to me, but (besides the good stability) it shows a number of new annoying bugs and some further bug can be discovered. This can be unacceptable for some users. So maybe I’d recommend it to whom wants to help the FS team, and/or to whom wants to try out the last features, aware of the issues and that this is not a finished release. The “Know Issues” page is meant to be read. Else I’d recommend to wait for the final release instead. Since anyone has his or hers needs and interests, IMHO the recommendations depend on them. But in this case maybe there is an extra reason: to not delay materials for further months, as they have been released months ago. As you can figure out, this is impacting on the creators too, because Firestorm is the most used viewer around, and If it doesn’t support materials, a lot less people can see the materials in your creations (even if their hardware is capable) and so the adoption is slowed down.
    Anyway I wish to thank the team for letting us to test the beta and the alpha and for the cool features.

    MoonWhisper

    November 5, 2013

  • I just not clear on which to use as they all have problems, so maybe you could tell me which as the least problems?
    I do not understand why no improvements made since the official FS came out, all my years in SL I have had updates to download at intervals and always advised to use the current viewer if I wanted to avoid Beta, alpha etc. bugs.

    June

    November 6, 2013

  • Honestly … if you have to ask this question it’s probably better that you don’t update yet. These are “beta” and “alpha” versions that are not as stable and refined as a regular viewer release.

    cincia singh

    November 6, 2013

  • In theory I agree with you but 2 things make for the confusion the big yellow announcement on login screen making them seem to be the official ones to use and the fact the FS version which is the so called official as had not corrections to it for a long, long time.

    June

    November 8, 2013

  • this is beta…and it makes single Life worse??????

    jim

    November 6, 2013

  • Yeah, cause it took me about 1 hour of my precious time for downloading, performing a clean install, setting up all the settings, loggging in, crashing, logging in again, crashing again, crashing one more time, not crashing but textures got “discarded due to a lack of memory”, going hysterical, deleteing the crap, reinstalling the previous version (clean), setting up all the settings…and it probably cost you one minute of your precious time to read this.

    Vivienne Schell

    November 7, 2013

  • Going to wait for the Official Final Release I think 🙂

    Looking forward to it Firestorm Guys 😉

    Mapoo Little

    November 6, 2013

  • ivn prim fix when using ALM already in place?
    At least several Tpv’s had it!
    Is on Firestorm plans to integrate it?
    Can Firestorm team at least tell users that there is some called “Add” and that there are several packs of full perm alpha layers available, so any can hide the inv prims (If not being able to delete them from the object) with alphas, therefore making all look much better for the unlucky oens that can use shadows at all times!

    zzpearlbottom

    November 7, 2013

  • Several TPVs = Niran’s? Honestly: No. We do not plan to integrate that so called “fix” that causes new issues in return.

    Ansariel Hiller

    November 8, 2013

  • I don’t remember having the Invisible prims fix included since it still happens for me quite alot.

    NiranV

    November 15, 2013

  • This version has the pink/purple bug back, I see all items that has alpha textures pink’ish before they rez…. most of the time on mesh and sculpt objects.

    Vanity

    November 7, 2013

  • You know for all you people out there who, whine and cry about things I got this to say. Do you want some cheese with that Whine of yours.

    As I have said it before, I will say it again. If you do not like the viewer do not use it, of you can apply to be a Firestorm Beta tester and will find out just how much better the viewer is when you all get it. And I dare all of you who complain, to step up on board and to apply to become a Firestorm Beta Tester. As god knows we could use more people, to test all of the versions especially MAC and Linux OS versions.

    The more people we have helping test the viewer, the better it will be for you guys who are not happy with it.

    animorf Kawadias

    November 8, 2013

  • Works good so far. I’m a 64 bit computer, but using 32bit because ‘alpha’ is a scary word for programs to me.
    It’s been pretty good, except in some sims I will get random lag / freezes, mostly freezes for …5 to 20ish seconds? Just guessing. So yeah aside from slowly murdering my computer it works pretty well. Materials are pretty in the rare times I see them, ribbon particles are fascinating, and collada export is amazing.
    Also getting a weird ‘wasd and numpad now control my camera instead of my walking’ glitch, but that could be something unrelated.

    Horse

    November 10, 2013

  • The walking thing never happened again, but my computer really was dying. Luckily I had 4.4.2’s installer or whatever the last one was still handy. Beta is beta, not really safe for general use yet. Really neat though, and Firestorm is still the best~! (Just keep old versions handy before beta testing, everyone.)

    Horse

    November 13, 2013

  • The changes you did to the build->texture part sucks, now I can get – numbers on the repeat scale… wtf would I need that… why not keep it as it was when the numbers could just be adjusted down to zero and we could flip the texture without seeing the confusing – values.

    Vanity

    November 10, 2013

  • Okay. Is there anyway to remove the ‘Update Me” message or prevent it from showing everytime I launch the “STABLE VIEWER”. I mean come on… I tried both “beta” versions and they are bug ridden so I went back to the previous version. I don’t want to be reminded that there is a “unstable” version out there each time I start the viewer…. It’s one thing to put the half baked viewers out there for public consumption but to remind people every time they is just crazy now…. And no i’m not complaining or “whining” as some would say. Wow, what is this “Fight Club”??? First rule of Firestorm is don’t talk about Firestorm? It’s called constructive critisism and feedback. It can’t be all good all the time you know. If you ask your general user base to participate in a Beta then you are opening yourself for the comments both GOOD and BAD. ’nuff said.

    TheMizANG

    November 10, 2013

  • The only way I have found to block the login page (because that’s where the nag msg are) is to block that url through your PC’s host file (located in C:\Windows\System32\drivers\etc).

    I totally agree with you, people that don’t follow the FS blog or are not that technical would follow that msg and install the beta or alpha ,and get a buggy SL.

    That “Update me” msg should just show when a new FINISHED release is out.

    Vanity

    November 10, 2013

  • Do you know what URL I would need to add to my hosts file?

    TheMizANG

    November 13, 2013

  • NM I found it. No more nag screens. Great tip!

    TheMizANG

    November 13, 2013

  • I also think that the “Update me” message should only be shown for the “Stable” releases. I think honestly what happened here and it has been said by others is that the team was “falling behind”. At one point it was said a new release wouldn’t be out until 2014. The team wanted to take a well deserved break. Other viewers were getting things out that the FS team still hadn’t been able to. And the gap between the official LL viewer and the FS viewer was getting to be bigger and bigger by the day. I think the team made a decision to get “something” out before the end of the year. Knowing they wanted to take a break they decided to put out a public beta so that they could look “good” before the end of the year. The problem is, and like I mentioned before when you release a beta to your general user base (half of whom or more Im guessing) dont follow this blog and have no idea what “beta” or “alpha” mean. They see the “shiny and new” and install it. As a project manager for a large team I think the “betas” should be released to the beta group. These people willingly sign up to test software and want to provide the feedback. Again, this is my opinion of what happened here and its not just mine its been said through other outlets and by others as well. I look forward to the next release and will upgrade when the next final version comes out.

    TheMizANG

    November 14, 2013

  • In the 32 bit beta, in the chatbar in the “Nearby Chat” conversation tab, if I type to emote /me, it is rearranged to /em.

    Problem does not occur on the regular “Nearby Chat” chatbar. I do not have autocorrect enabled.

    Astoria

    November 11, 2013

  • Where’s the Linux 64 bit build? It’s actually easier to build for 64 bit Linux than for 64 bit Windows. Come on already, let us have it!

    seriouslytho

    November 12, 2013

  • It may well be easier but is it productive? What percentage of users would benefit from the devs using their time to do a 64 bit Linux build.

    “Come on already” as if you are annoyed that people are not using their expertise and free time to make things better for you?

    If this is so important why haven’t you done anything to further it? Take some classes, read up, practice and learn so you can donate your time and expertise to your particular area of interest.

    You sound too much like Veruca Salt (The spoiled little girl not the group).

    Tsk tsk tsking,

    Georgie

    Georgie Tungsten

    November 15, 2013

  • Actually, Linux devs already use their time for, so to say, Linux… And all 64-bit linux users would benefit from 64-bit linux FS. The difference between 32 and 64 builds is mainly not in the code itself, but in compiler flags. An ordinary user can’t help much here besides recruiting oneself as a beta-tester…
    Anyway, real men write their own drivers! It’s relatively easy to build FS yourself. The only serious drowback here is lack of 64-bit KDU for self-compilers, because it’s a proprietary lib (and costs US$250 for an ordinary user).

    Allex Alcove

    November 17, 2013

  • Not using Niran since old version was discontinued!
    Rlv (btw raising steadily on the tpv chart), UKanDo as far as i know are the only ones (perhaps Cool sl viewer as well!) that use it!
    The fact is that it works and i would like to know about the bugs you say it gives?

    zzpearlbottom

    November 12, 2013

  • ZZ, the thing is the following:
    Lately LL is pushing alot major overhauls of everything: CHUI, Materials, AISv3, SAB etc etc, some or many of these overhauls touch large amounts of code that RLVa also touches which makes it break if you don’t fix it properly. Since RLVa is not my cup of tea i don’t actually work or fix it, hell i try to avoid doing anything with it as good as possible since its not mine, i don’t have any idea how it works internally and i’m not willing to put time into learning and understanding it, all it has to do is work and thats where it fails if you update your Viewer with all the new fancy overhauls LL throws out lately. As someone pointed out way above already, i’m not a Team full of coders nor do i have anyone helping me out except those i ask from time to time (if at all). You always seem to forget that i’m not a coder at all, i don’t have any coding skills, i’m not even willing to learn them the traditional way -> school, books, tutorials etc. I’m just trying to learn it by doing, by trying. You can’t expect me to create a new wonder. You should take a look at the LL repository, download the source, compile it and start working on your own Viewer with nothing more than the LL Wikipedia to help you understanding how you can compile your Viewer, i want to see you creating a better Viewer with no knowledge, toss me a link when you’re done and i will critically investigate your Viewer, especially the UI and i can asure you i will flame you with things like “the button is 2px too far on the left” , “that text field is misaligned by 1px” , “those buttons arn’t…” and so on. I’m not even listing the usual stuff like bug, crash and other misbehaviors.

    NiranV

    November 15, 2013

  • I have had more people asking me for help with their phoenix viewer since the release of this beta version (4.5.1) than ever before with problems ranging from inability to view textures, avatars failing to rez in (including their own), inventory failing to load, and the list goes on.

    Part of the issue is how this was pushed through the main update channel, it should never have been done that way. While these issues may not result in crashes they are still issues that make the viewer unusable for many. I cannot count the number of people I have had to provide a link back to the 4.4.2.34167 version ( http://downloads.phoenixviewer.com/windows/Phoenix_Firestorm-Release_4-4-2-34167_SetupSL.exe ) just to alleviate their issues.

    Your users are not all fit to be testing beta version software, and a beta version of the software that has not been put through it’s paces should not be pushed for mass consumption. I understand you wanted a release before the holidays and before the turn of the year, but honestly this was a bad idea.

    In most cases I have been supportive of the actions of you and your team, but in this instance I cannot. This move to release a beta version through the main release channel has caused myself and my friends plenty of frustration, and it could all have been avoided by simply keeping this beta off the main release channel. Would have been fine to tell people about it, just the way it was done has caused some issues for some. In the future could we keep beta software out of the main update channel? That is all I ask.

    Certified Lunasea

    November 17, 2013

  • I am loving this update so much! Only issue I’ve had is mesh hair seems chopping, and the alpha around the hair seems more pronounced than usual. I am hoping this gets fixed soon :D. Other than that, I can run shadows most of the time with the same fps that I used to get in the old viewer without shadows.

    Savvy Warden

    November 19, 2013

  • I would like to know why Meshmaxconcurrentrequests is now capped at 64 😛

    Cat

    November 19, 2013

  • CAT, that is LL decision and a decent one! More then that stresses servers!
    Of course all now sems reduced to this = All stresses LL servers!
    Truth is that LL does not invest on new servers, keeps staking more and more sims over old ones and thats the reality will have to deal with!
    Niran, i don’t need to compile a viewer to my taste when a developer already listens and makes a viewer with all i need! (UKanDO!).
    And the my question, why the inv prim fix that some viewers adopted is considered by Firestorm team as more warm full, remains!
    To end, I can use Alm, shadows and look at the feet of the avatars that still use the inv prims!
    Can any using the firestorm do that without seeing them all screwed?

    zzpearlbottom

    November 20, 2013

  • I have been suddenly experiencing an issue since updating with Firestorm 4.2.2 and the beta version. It will not save my user name or password. This is the error message I get. How can I resolve this issue?

    “We were unable to decode the file storing your saved login credentials. At this point saving or deleting credentials will erase all those that were previously stored.

    This may happen when you change network setup. Restarting the viewer with previous network configuration may help recovering your saved login credentials.”

    Ravyen

    November 20, 2013

  • I asked for help with this issue. I removed both viewers from my computer. I did a clean install. I deleted all Firestorm files from my computer. I followed the instructions how to make a back up file, delete individual account files. Removed the viewers again, did another clean install, removed all Firestorm programs, files off my computer. The message did not come up until I logged in, made my settings, logged back out and again the message returned that it could not decode the file storing saved login credentials. I think this must be a ‘BUG’ with Firestorm itself. I didn’t notice this problem until I installed the Beta version, then both the 4.2.2 Viewer and the Beta Viewer began doing this 3 days ago.

    I hope you can get this issue resolved soon because I am out of ideas how to fix this so I can have my user name and passwords saved.

    Ravyen

    November 20, 2013

  • Ravyen, as a workaround you can edit the shortcut on your Start Menu or Desktop (right click > Properties) and add this at the end of the command for starting Firestorm…
    –login yourusername yourpasword
    That bypasses the login screen and is a fast and easy way to start FS. It doesn’t depend on FS remembering your password.
    If you prefer, you could make it a copy of the shortcut, named Firestorm Login maybe, so you can still choose to start the normal way instead.

    Aimee

    November 20, 2013

  • The beta is great.. Haven’t had any freezes since . Quite stable but seems a bit more slow.. not sure yet.

    Great job FS team

    Monica

    December 4, 2013

  • Yes 64 Firestorm is a vast improvement for me! I am getting about 180 to 200 fps with graphics set to ultra with shadows turned off! About 280 or more fps in mouselook!

    VolmarrGoth Vollmar

    December 8, 2013

  • This beta is in my opinion nothing but sh*t, it takes forever for my Avatar to rez, and when it rezzes the skin, clothes, alphas, and other pieces never attach, I want the other viewer back. I’m sorry, but to me, the public who wants to go waste 24 hours doing w/e on SL, are not the people who should be playing around on beta’s that’s what a production teams job and purpose are, so all the stuff can be patched BEFORE it is released to the public.

    Matthwe Gallant

    January 19, 2014

  • When is Linux 64bit due at last? I know there’s the possibility to grab the source code and build etc. but i don’t have a powerful computer for compiling (thus it would take ages for the compilation to finish). Firestorm 4.5.1.38838 is the version that works perfectly on my computer and thus the version i would love to see in Linux x64 version!!!! Or, at least, if anyone has compiled this version on linux 64-bit, it would be a good idea if he/she could send me an email… 😀

    Alex Shuri

    March 6, 2014

  • […] regards to the latter, this means CtrlAltStudio now includes all updates found in the  Firestorm 4.5.1 and 4.6.1 releases, including a number of significant LL-driven viewer updates, such […]

  • Forgive me if this is seen as little more than a complaining gripe, but was the change to the Edit>Texture tab REALLY necessary? The other individual way above me, who posted on the uselessness of the number charts, I am highly in agreement with. Add to the fact that now, instead of having ease of accessibility through all values being seen on a single screen, now we have to use a small drop down menu to switch between Texture, Bumpiness and Shininess. This does nothing for those who were already so well-acclimated to the previous setup. Opinion only, a useless change.

    Rohennightlover

    April 9, 2014

  • Yes… It was… Due to the introduction of Materials. Take it up with LL as it was not our change.

    Jessica Lyon

    April 10, 2014

  • […] per Firestorm 4.5.1 (materials, CHUI updates, new particle effects, […]

  • I deleted the old version and now I can’t install this: “Phoenix-FirestormOS-Releasex64-4-6-7-42398_Setup”
    on my Win 7 64 bit. Get this error message: “A newer version of Microsoft Visual C++ 2010 Redistributable has been detected on the machine.”

    JD

    September 1, 2014