[BUG-7776] Second Life Viewer will no longer open after latest update. #15450
Comments
Theresa Tennyson commented at 2014-11-11T13:10:32Z There are enough comments on the forum about people having similar issues with the current release viewer that this JIRA shouldn't be considered a support issue. I'll start pointing those people to this JIRA. |
Lindal Kidd commented at 2014-11-11T14:38:48Z Concur with Theresa. Several people are having this issue, although I have not. To add a little info, the version is Second_Life_3_7_20_296094. Here's one of the more active threads in Answers: http://community.secondlife.com/t5/Technical/Second-Life-3-7-20-296094-i686-Setup-is-anyone-else-having-an/qaq-p/2862390 My initial guess is that it has something to do with the new way the viewer handles graphics cards. |
Whirly Fizzle commented at 2014-11-11T19:42:43Z Heya TheBudmanSoR, When a viewer gets stuck on "initialising VFS..." it is usually a problem with the viewer cache or a graphics driver issue. Can you try the following first:
If this does not work, launch the 3.7.20.296094 viewer and let it crash. Thanks! |
TankMaster Finesmith commented at 2014-11-11T23:01:31Z just a note, one of the logs I looked at showed an error that it couldn't load the benchmark shader file. llrender/llshadermgr.cpp(588) : 2014-11-11T17:44:47Z WARNING: LLShaderMgr::loadShaderFile: GLSL Shader file not found: interface/benchmarkF.glsl |
Whirly Fizzle commented at 2014-11-11T23:03:20Z Logs and a stack from this problem are on BUG-7783 |
Beautyqueen4578 commented at 2014-11-12T01:04:45Z Please fix this i am getting frustrated! |
AlucardsSisterCrystal commented at 2014-11-12T03:44:16Z 11-10-2014 09:32 PM I logged into Sl like I normally did, only it asked me to update. It gave me two options 1. update or 2.quite SL. So I updated to Second_Life_3_7_20_296094_i686_Setup. I did a clean installment, cleaned my catch and everything. But the updated viewer still will not launch. so i went to an alternative viewer Second Life Attachments Viewer version 3.7.20.296355, its old and odd but it worked. I am only using this temporary until the bug is fixed for the 3_7_20_296094_i686_Setup update. |
Whirly Fizzle commented at 2014-11-12T03:54:17Z More logs and stack on BUG-7782 |
TheBudmanSoR commented at 2014-11-13T07:45:24Z Greetings, Whirly Fizzle, |
Marissa Linden commented at 2014-11-14T01:10:55Z This is a dupe of BUG-7783. Old Intel gpus seem to be crashing during our gpu benchmark to determine default graphics settings. |
Alexa Linden commented at 2014-11-18T22:02:34Z, updated at 2014-11-18T22:03:50Z Can you try testing the following build http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/oz_maint-4678/rev/296847/index.html and let us know in BUG-7783 if this resolves your issue? |
Steps to Reproduce
After I updated SL, the program closed. When then updated Viewer was finished, I clicked on it, and it got to "Initializing VFS" before crashing. This happened even after deleting and reinstalling the Viewer.
Actual Behavior
After downloading the latest update (sorry, I didn't catch the number), the SL Viewer will no longer work. I'm on Windows 7. The process gets to "Initializing VFS" and then simply stops. Even after removing the Viewer and reinstalling it, I continued to have the exact same problem.
Expected Behavior
I was expecting the Viewer to work. When it did not, even after deleting/ reinstalling, I followed the suggestion of a registered helper on the Q&A and tried downloading the Project Snowstorm alternate viewer, which seems to work (so far).
Other information
When it was clear the Viewer had issues that I couldn't resolve (after several times deleting/ reinstalling it), I followed the suggestion of a registered helper in your Q&A section and downloaded the Project Snowstorm alternate viewer. It seems to work for now, but I'd like to resume using SL with the normal Viewer. However, I believe that something in the most recent update has caused it to stop working until some form of maintenance is performed. Thank you for checking into this problem; it seems like numerous people were experiencing similar issues.
Attachments
Links
Related
Duplicates
Original Jira Fields
The text was updated successfully, but these errors were encountered: