For more info on fixing the first and finding the other two, see the support-related blog post here: Lette's Trivia and Trivial Stuff: Frequently Asked S...

Cannot be replurked enough...

::Plurk Frontpage Promotion::

Just wanted to let you guys know that we LOVE the new viewer sooo much. My partners bad pc is running it so much better than the last. Thank you!

IveyDeschanel: Consider the thank you delivered to the team.

awesome! Great work, we're really happy with it

Lette - I just downloaded and I have noticed no difference whatsoever, other than the camming seems to be a little smoother. Should something be blatant?

Performance tends to be individualized. There might be patterns (we've been hearing a lot of comments about performance improvements this time), but it won't apply the same to everyone.

This version performs pretty much the same for me as previous ones do. But I'm glad to hear it's running even better for a lot of people.

If you're interested in what has objectively changed, have a look at the change log: wiki.phoenixviewer.com/f...

my new fave thing is the custom quick menu and the new tabs

It runs very well for me.

This version runs so well for me!!! I love it! Keep up the good work Firestorm Team <3

LettePonnier: It is wonderful as usual, my only problem is I seem to have lost my height offset, we tend to use this a lot blogging and what not, so if it is in another spot now, could you let me know where

Sasypants: That's explained in the blog post linked above. The one to my blog, not the main one (unless you want to take a detour).

My question is...why release with bugs?

ASimpleGuy: As a former QA engineer, I can assure you there is no way to make an application bug-free. Not every scenario/combination of hardware/drivers can be tested for.

I should amend. It's within possibility, but you have to stop adding new features, keep it relatively simple, and keep up with the changes as quickly as possible.

With something as complex as Firestorm, it won't be bug-free. Ever.

lysana: an as someone who has tested software as well....obvious bugs like this should have been seen quite early.

Firestorm was perfectly when I updated it, even went in a took some photos. I logged out and now I'm trying to get back in, as soon I click to open FS I get an immediate send crash report.

I even uninstalled and did a clean install.

HybridAnsar: Did your reinstall include a settings clear? And if so, did you change any settings again from the login screen before you tried logging back in?

And do you have an error message?

I changed some settings the first time I logged in and was able to log in and take some photos. They were mostly graphic settings, nothing major though. Turned off some lights etc. It was when I logged out and

tried to log back in that I started getting the message. I do not have the error message.

ASimpleGuy: And when not everyone's run into it, clearly it's not a scenario that was easily caught in QA cycles.

Within literal hours people were complaining of these scenarios. Thats an indicator that there wasn't enough testing.

just want to add that now I can't even log into any of the other viewers. this is strange.

uninstalling everything, report back later

ASimpleGuy: IT's also volunteer labor. Asking why there are bugs in free software is like asking why hand-sewn clothing doesn't have clean selvage.

Excuse me. I just realized I'm currently channeling other issues into this discussion. If I have seemed curt, I apologize. I shall step away so I don't do it further.

Had to do a complete system restore to like 3 days ago, still crashing when I try to open. So, that's pretty awesome.

HybridAnsar: Is it just Firestorm now or all viewers? If you shares your crash logs by making a JIRA and attaching them, we can look to see if they give any clues as to the cause of the crash.

Instructions for that are at wiki.phoenixviewer.com/f...

LettePonnier: I totally missed that i saw Firestorm and opened the plurk and got distracted thank you for responding even though I was a goof

just read it, and wow that they have made it so hard, I have height adjust in my VR Studio, so I am good, it's only ever been navigating a tree root or something that it was handy, going into ap/mode will take

you out of the pose and mess up alignment and then have to start over again lol thank you for giving it to use until now, at least we had it for a while

You can disable the edit appearance animation in Prefs > Move & View > Movement (uncheck "Appearance"), and you won't be taken out of the pose.

However, I've been told there are other oddities when doing that, like a system clothing layer item being removed from you when save it if you edit it at that time, but I haven't tested it, don't know details.

Lette, it's all viewers, I've done a clean install 3 times and restored my comp 3 times to earlier dates, nothing is working.

You can still submit the logs, assuming the launch gets far enough to produce them. Even though the problem isn't Firestorm-specific, we can still see if we can get any info out of them.

The idea is, logs can sometimes (though not always) show what the viewer was trying to do when something got blocked or went wrong. This can provide clues as to how to fix the issue, even if the problem isn't

rooted in the viewer itself.

Which it probably isn't, since it's affecting all of them.

I'd also look at what other software you have running while you're trying to launch the viewer. Try closing out everything, no matter how unrelated you think it is, and then try.

What operating system is it?

windows 8

but everything seems to install just fine, it's when I go to open the program it gets to "detecting hardware" and then boom I get this

'k, then the crash reports will be getting sent to our crash-fixing dev, who keeps an eye on whether there are crash patterns and fixes the causes for the next release.

If you want crash reports examined to fix your specific problem, which is probably necessary in this case, then the process is different, as in the link from earlier: wiki.phoenixviewer.com/f...

If you want to troubleshoot the issue a different way, by all means go ahead. I just wanted to present this option, since it's how we normally go about it when we're helping someone with a login problem.

word, no I appreciate all the ideas and suggestions I can get.

Ok

If you file it as a SUP ticket, then it won't be visible to the general public. It would probably get moved into that section anyway.

gotcha

I think it's been fixed. I had to go into SL shortcut and add --noprobe to bypass hardware detection at login. the official viewer is running for me now.

I don't crash.... it just seems to be a lot laggier now, like when i move I used to have fluid movement, now it's jerky and freezes and such... also textures keep rezzing then blurry then rez over and over

Okay I'm installing it now.