![]() ![]() The next release of Firestorm is good to go, but again awaiting the GPU-related fixes from Linden Lab.The team have been working with LL with these bugs, and a version of Firestorm would be pushed to the Beta group to assist with further testing on the working being undertaken to fix things.This issues are Linden Lab issues, and as such, Phoenix is being held pending a fix or fixes from the Lab. Which phoenix viewer code#The current graphic issues being experienced with the Firestorm Mesh Beta (and other mesh-capable Viewers) will be in the code for mesh rendering in Phoenix Jessica estimated that around 50% of people using mesh-enabled Viewers are caught with the issue (basic shaders causing Viewer crashes).The mesh rendering code, supplied by Henri Beauchamp, is in the Phoenix code repository.Overall, not a lot has changed since my last report on The Phoenix Hour – the team are really waiting on LL to resolve issues their end before making any further releases of either Phoenix or Firestorm. To kick things off, however, Jessica ran though the latest status for both Phoenix and Firestorm before going on to pass comment on the new LL Viewer UI – which, at the time of her comments, was about to be merged with the Development Viewer code but had not actually been released for anyone to see. Ed actually heads-up the Viewer support side of the Phoenix / Firestorm group, and both he and Lette provide classes in using Firestorm. This week’s Phoenix Hour saw a couple of guests sharing the sofa with Jessica: Ed Merryman and Lette Ponnier, who would be joining Jessica and Phaylen in a discussion on matters relating to Viewer support. Which phoenix viewer download#In the meantime, and if you haven’t already, you can grab Phoenix 1.6.0 1591 directly, or go to the Phoenix home page and use the Quick Download links. Which phoenix viewer update#In the release blog, Jessica suggest that those wishing to update to the latest RLVa implementations should give either Firestorm or Catznip a try. Removal of the Google chat translation API options from PreferencesĪ signficant element not updated was that of RLVa – it was decided that Kitty’s time and focus is better spent on the numerous projects with which she is already fully engaged: her own Viewer (Catznip, reviewed here), working on bringing the spell checker to Viewer 3.x, her continuing support of RLVa for other V2/V3 TPVs, and so on).The Firestorm 3.2 log-in / splash screen options.While it may not be a popular move, one can hardly blame Jessica and the team for taking this position: maintaining an aging code base which itself is built on something LL no longer maintain (Snowglobe) is liable to become harder and harder as time goes on, and for a Viewer to remain functional and relevant, it needs to keep pace with the evolution of the grid and as the Phoenix / Firestorm project has made the step of producing a V2/V3 hybrid, it makes sense for them to focus on that work in order to do so, rather than splitting efforts (and doubling the workload) to try and maintain two sets of code.Īs well as mesh rendering, this release also brings with it: ![]() As time passes we will determine if another release is absolutely necessary and/or sensible and make a decision then on whether another update is mandatory in order to keep our promise to you.” I will not commit to saying this is the last Phoenix Viewer Release, but I will also not commit to saying it isn’t the last either. ![]() “Any future releases of Phoenix will be sparse and only if needed. But ‘we’ are no longer actively developing Phoenix on our own steam. When necessary we will continue to keep it up to date with advances/fixes from other third-party viewers and provide them the credit they deserve for that work. As you can see, we are not walking away from that promise, but it is important to understand that Phoenix is no longer our top priority. “We stated some time ago our active development commitment is now focused on the Firestorm viewer and that continues today. We still feel strongly that the end of V1 functionality is an inevitability, so it is more important to develop an alternative viewer for our users they will enjoy for when that time comes than to spend our efforts on a dying viewer and then leave our users with no alternative once it’s gone. However, we also promised we would try to keep the phoenix viewer alive for you until it is no longer feasible to do so. However, the release announcement from Jessica Lyon is liable to make difficult reading for some: This means that the majority of users in SL are able to see mesh objects rendered correctly in-world, if not import them. Version 1.6.0 1591 brings with it the ability to render mesh objects. Yesterday, the much-anticipated release of Phoenix was made. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |