Tag Archives: PVw

Calling all Phoenix users

PhoenixJessica Lyon has announced she and the Phoenix  / Firestorm team will be holding an Office Hour meeting, and all users are invited. Jessica is particularly keen to have users on Phoenix attend the meeting, commenting:

Everyone is invited and encouraged to attend but I especially want to see Phoenix Viewer users in attendance as the primary topic will be about Phoenix and its future. I also would like to see all you angry people who have been flaming and hating on us in our blog comments. I’d like to address your complaints so please at least be on the stream if you can. 

Because the lack of Phoenix Viewer development and in fact the future of the Phoenix Viewer itself needs to be discussed and your questions/concerns need to be addressed.

Firestorm users are also obviously welcome.

Event Details

Those wishing to attend / join the stream are advised to turn up around 30 minutes ahead of the meeting. As there are limited slots for both the in-world event and the stream, it would be advisable if those attending the event don’t also run the stream, as this could prevent others who are unable to get in-world from watching and listening on-line.

The event will be recorded for future playback.

Phoenix gets set for Direct Delivery

Phoenix 1.6.1.1691 has been released today. This has been expected since the recent updates to the TPV Policy required the removal of the on-line truth status from the profile floater.

More importantly, the update prepares Phoenix for the forthcoming roll-out of Direct Delivery, scheduled for this Wednesday, the 21st March. As such, it is very important for Phoenix users to upgrade to this release if they wish to be able to use the SL Marketplace to receive items once Direct Delivery is launched and merchants switch over to it. Additionally, the Viewer includes the V2 inventory fetch system.

Other updates include:

  • RLV updates (Kitty Barnett)
  • Optional support group viewer version identification (Zi Ree, Kadah Koba)
  • GPU table updates (TankMaster Finesmith)
  • Added CHOP, MAINT, EXP, SINV, PATHBUG, and DOC to jira parser (TankMaster Finesmith)
  • Option to show script time in either ms or µSeconds (Kadah Coba)
  • Allow /me’ when using viewer prefix (Inusaito Kanya)
  • Support for CreateInventoryCategory capability (Henri Beauchamp)
  • Backport of V3 inventory loading at login (Henri Beauchamp & Singularity Viewer)
  • Additional fast timers from V3 (Henri Beauchamp)

It is recommended that a clean install is performed for this release.

Related Links

Phoenix / Firestorm Q and A – The Video

Note:  I’ve closed comments on this article as the most recent have turned to commentary on features and presentation within Firestorm. This blog is not the place for such commentary because matters on the internal working / presentation of Firestorm (be they general enquiries or potential feature requests) need to be posted via the Firestorm blog and JIRA, where they can be seen and responded to by the Firestorm team.

On Saturday December 17th, a Phoenix / Firestorm Q&A was held at the Rockcliffe University regions, where Jessica took questions on both Viewers from the audience and which had been posted beforehand either to her directly, or via the Phoenix blog.

Jessica and host Nigma Sterling at the Q & A session

The event, hosted by Nigma Sterling, was recorded for those who could not attend, and the video has now been released on YouTube. The video is some 2hrs 30 mins long, and covers a lot of ground.

This is an honest and open response to the many criticisms the team have faced from their user community, and for those that have concerns about Phoenix and / or Firestorm it is a worthwhile spending time watching it.

I’ve not been privy to much of the situation that is alluded to in the video – the heated discussions regarding Phoenix and the perceptions that the team are somehow “abandoning” their users in “forcing” them into the V3 world through Firestorm – and i’m not about to embroil myself in it.

However, I do emphasise very much with Jessica and the team – indeed with all TPV developers in that they all face a difficult hill to climb, whether they are attempting to stay current and work within the constraints of the new Viewer code base or whether they are trying to work within the constraints of a code base (Viewer 1) that has been effectively frozen by LL for a year now, and which LL have themselves indicated is only going to get more and more broken as time goes on.

It’s a thankless task, however you look at it, and one that is never going to please everyone, be it for genuine technical issues or simply because of people’s unwillingness to take the time to work with a new UI. This being the case, I’m going to take a moment and lift a metaphorical glass of mulled wine to all TPV developers and say “thank you” for all of your efforts over the years.

Sadly, I cannot embed the Phoenix / Firestorm Q&A, as it is locked from doing so. However, you can see it here.

Phoenix / Firestorm Q&A

I’ve been asked to pass on the following – and while only too happy to do so, I’m closing the item to comments as it is important anyone who has questions and who can’t attend the event, post their question to the official Phoenix Firestorm blog.

The Phoenix / Firestorm team are holding a public Q&A session this coming Saturday to answer questions and concerns relating to both the Phoenix and Firestorm Viewers.

The meeting will take place at 13:00 SLT at the 4-region auditorium at Rockcliffe University and will be hosted by Nigma Sterling of Rockcliffe University.

Those wishing to attend are advised to arrive early, and using the following SLurls according to the first initial of your FIRST name:

A – I:http://maps.secondlife.com/secondlife/Rockcliffe%20I/2/32/29
J – R:http://maps.secondlife.com/secondlife/Rockcliffe%20Library/227/5/30
S – Z:http://maps.secondlife.com/secondlife/Agile%203D/227/250/31

The event will be recorded and made available online after the fact (no live streaming planned at this point).

Note that the focus of the event is to discuss genuine concerns relating to either Viewer and their future development, and to answer questions and address specific critiques.

You can read the entire post from Jessica here.