I felt it from the start. It's that faster (apparently) closing of the viewer. It used to take a good number of seconds to close the viewer. Since the latest release version, it closes almost instantly but clearly (from watching the cache folder) has certainly not finished what it needs to do.
I've been watching this thread and for me, it has been exactly the opposite. Before the update, when the viewer took several seconds to close out, I would all too often log back in with an incomplete inventory. Since using the new viewer which closes instantly, I have not had one instance of a failed inventory load.
Another interesting thing is if I crash, it'll ALWAYS take two attempts to log back in - first attempt I would log in as a perpetual glowing cylinder, and my inventory would fail to load - second attempt would rez normally.
That's a time-consuming process, though, so also in line with hardware the second thing I'd try is something like CPU-Z HWMonitor to see if heat is a problem (which seems unlikely, based on the "40-50fps with no issues" thing, but still something is wrong somewhere).
Firestorm is a community development project headed by The Phoenix Firestorm Project Incorporated as an alternative viewer for Second Life. Our primary goal is to improve the user experience with new features while extending usability, functionality and flexibility of the Viewer 3 code base. Our secondary goal is to lessen the learning curve for users migrating from older V1 viewers, while still being easily accessible to users of Linden Lab's latest viewer offerings. We package contributions from various community developers along with code from Linden Lab and of course ourselves to bring you a quality, feature-rich viewer experience backed up by a large volunteer support team available 24/7 in various languages. More information on support can be found from our website. Documentation here =firestorm and Tutorial Videos here
I'm using the firestorm viewer on the lowest settings but my laptop's fans become 10x louder soon after I launch Second Life with it. Do you think it's a GPU/CPU issue? How would I go about resolving this problem?
Please take a moment to consider if this thread is worth bumping.Recommended PostssyriahhhPosted January 18syriahhhResident
PS: When it said - Installing to /home/cordenne/firestorm I felt it was talking to long to... I guess do anything so I pressed 'Enter'. I don't know if that made a difference but if it does, now you know!
The viewer would freeze for 2 to 15 seconds, the screen would go black for a second then come back with everything working for a few seconds or minutes. Then things would go sideways again and the sequence would repeat. Basically, not usable.
Please take a moment to consider if this thread is worth bumping.Recommended PostsJaide BeckPosted March 9, 2022Jaide BeckResident
I brought on screen keyboard up to see if it was working and it is. Both buttons are working. So I don't understand what is going on? Can someone tell me why it isn't working? Why has firestorm not updated since last June 2021??? I was able to use it before, but I had to reset my pc and since then I can't seem to use advanced. Everything else seems to work in Firestorm.
I'm guessing, when you reset your pc, it took away all the firestorm settings that was made by you. And when you installed Firestorm again, it installed as a clean installation. And hence the tab on your top bar, they're the default ones. Checking the advanced tab might give you access to it.
Please take a moment to consider if this thread is worth bumping.Prev12NextPage 1 of 2 Recommended PostsKitty AeghinPosted April 5Kitty AeghinResident
Standing up and taking a copy of the object I had been editing back to inventory caused 40-seconds maximim CPU activity that sent the resource monitor window white for half the period, and I wasn't able to click back into the Viewer until the end of that 40-second freeze.
Watching the resource monitor for a while longer, doing nothing, there was yet another 40-second freeze period. Resource Monitor clearly indicated it was SecondLife Viewer that wasn't responding. I hadn't done anything, the question is, had either of the other two avatars present being doing anything, and if they had, should they have been able to impact my viewer even when they were well outside draw-distance?
Please take a moment to consider if this thread is worth bumping.Recommended PostsLara AulderPosted August 16, 2018Lara AulderResident
Scroll up to one of Alyona Su post. She does a great job answering the above question. I don't know what the different is between firestorm and Citznip is. What I do know is my user name password did not work. Not sure if Catznip has to have its own or what. Like I've posted before, I had to download Firestorm only to because of RLV having to do so. From there I came across, Catznip. I didn't see a payment option to help pay and support their program. I did enjoy seeing that. Our privatize group is in the process of trying to building a , privatize Second Life viewer. Free is not an option. Seeing all the new many viewers is making easier to understand how too build one.
Please take a moment to consider if this thread is worth bumping.Prev12NextPage 1 of 2 Recommended Postskaleb OrsiniPosted May 5, 2019kaleb OrsiniResident
There are no updated voice libs for linux from Vivox, and none coming. LL support for Linux is dead, firestorm are putting up a good fight to keep their port going though I doubt that can last long term.
if your using firestorm theirs a simple way to run voice under wine. with the native linux client in the debug settings. first unpack firestorm in your home directory i like to make a /bin/firestorm directory to hold it.
to be honest SL voice in native Linux is dead which is why firestorm added that hook to run the windows version in wine and use it threw the native client. to be honest using this hook you don't notice any difference. from the old native version other than it's easier to set up.
Hi, I find version 22.11.2 GPU series 6xxx useless for a second life, firestorm viewer, LL viewer, or any similar software. And that's a big problem when you are a part-time content creator there... I was using rx6600xt together with r5 5600x, and constantly having crash reports, and black screen Radeon wattman errors with bug reports since I did update on that driver version. At first, I was thinking it was my GPU, aldo it is just 9 months old. So I bought a new rx6750rx today. Same problems just less often. Why for crying out loud we don't have GPU drivers support and new drivers for GPU products that we can buy in all stores, in all countries for 3 months now!?!?! I was forced to roll back to 22.11.1 GPU drivers version, I'm in Second Life as I write this here for 2 hours and I don't have any issues so far and I hope it will stay that way while I'm using older, not WHQL version of GPU drivers. AMD you really need to step up for your loyal customers and users. Is anyone else here that is having similar or the same issues, please?
aa06259810