Gabby Pixelbottom Posted September 2, 2011 Share Posted September 2, 2011 Hi,I am desperately trying to get Viewer 3 to work on at least one of my machines but so far have been completely unable to. On my Windows machine I can perhaps run it for a minute or two sometimes but it always crashes with an OpenGL error, I have made sure everything is updated, I uninstalled and reinstalled my nVidia drivers (many times) but nothing I do seems to help. On my Linux machine I am able to log in and run the client but I can only seem to do anything on my mainland region where my home is, in fact, I can not even see any of the adjacent regions (just water) and I can not walk into them, also my friends list will not load (at least it hasn't after more than 45 minutes of standing at my home now) and I can not tp anywhere without crashing (well that is not entirely true, I can TP to places in the region I am already in but that does not do me much good.)Both machines have nVidia GTX460 video cards and both machines can run the Phoenix viewer with no problems, I have also had no problems running Viewer 2 versions in the past on either machine. The Windows machine runs Windows 7 64-bit with 6gb of memory and a Core2 Duo 3.0ghz processor, the Linux machine is also 64-bit with 32-bit compatibility libraries installed and has 4gb of memory and an AMD 2.8ghz triple core Phenom II processor. I know these are not the most up to date processors but they are well within the listed requirements for the client. Both machines are connected to a gigabit ethernet switch, I am not running wireless which I know can cause problems.Over the years I have had my fair share of issues with SecondLife but nothing as frustrating as this, especially running what is listed as the "Stable" version (I know, the Linux client is beta technically but the Windows version is listed as stable and it seems no where near it to me.Can anyone give me any guidance on what might need to happen to get 3.0 working?Thanks in advance. Link to comment Share on other sites More sharing options...
Phillip Wasp Posted September 3, 2011 Share Posted September 3, 2011 I can only tell you about my case...and it may not help! But...I have used most viewers from before 1.23 up to 3.0, and several 3rd party wiewers--I tried 1.0, went back to Phoenix, tried 2.0, went back to Phoenix, and the 3.0? It pegs my processors out! Down to 5 f.p.m. with water, clouds, and particles turned off! And it takes forever to log on, so I find myself doing other things now besides SL. I don't know if it doesn't run good on multi-cores or not; or 64-bit or not--but there is a problem! I downed the Firestorem beta viewer and the difference is remarkable..and I can only hope they are designing a viewer to accept mesh, otherwise SL is going to be a distant memory for me... Link to comment Share on other sites More sharing options...
Gabby Pixelbottom Posted September 3, 2011 Author Share Posted September 3, 2011 Just an update, I did not realize there was a 3.0.3 Beta version which I just downloaded and tried on Linux, using a fresh .secondlife folder. I am experiencing the same issues with my friends list not loading and only being able to see the mainland region I logged in to. I will test the new version on Windows too but that will have to be later. Oh also, apparently this viewer thinks my land is for sale! At least the "Buy this land" icon is dipslayed in the address bar of the viewer (clicking on it does bring up a box that says the land is not for sale at least.) Link to comment Share on other sites More sharing options...
Baloo Uriza Posted September 3, 2011 Share Posted September 3, 2011 First of all, I need to thank you for providing detailed information on what you're seeing; I really wish more people asked for help like you did. Some things that would help me get a better grip on what's going on (and feel free to use Pastebin if the output is huge for any of these): While you're in Linux, open a terminal. Type glxinfo and hit enter. What's it say? Same for lsmod. What's the complete output in "About Phoenix" under the help menu in your viewer? Does the amd64 flavor of Imprudence perform differently for you? I'm suspecting that in Linux, you're using software rendering and/or don't have the correct modules inserted; the output from the above will help me figure out what to try next. Link to comment Share on other sites More sharing options...
Tristizia Demonista Posted September 3, 2011 Share Posted September 3, 2011 Looking at your post, it seems you have a driver issue. The newest drivers do NOT support some OpenGL functions anymore, so you need to DOWNGRADE your NVIDIA-Driver! I think v 260.99 was the last which supported all necessary functions. ps.: No, i do not have an idea why Link to comment Share on other sites More sharing options...
Gabby Pixelbottom Posted September 3, 2011 Author Share Posted September 3, 2011 Hi Baloo, Thank you so much for your willingness to look at this, here is the information you asked for... About phoenix viewer: http://pastebin.com/FjnukXWv glxinfo results: http://pastebin.com/cEH3nCJ6 lsmod results: http://pastebin.com/f7m9MEVb I do not have Imprudence installed but will do so and get back on that. I have installed the 64-bit version of Imprudence (1.3.2-Linux-x86_64). It is behaving strangely too, for instance, about 2 out of every 3 login attempts it gives me dns errors and fails to log in entirely, but I can do a nslookup on the address it is trying to connect to and that works fine. Plus Phoenix continues to work and if there were dns issues it certainly would not work either. When it does let me log in I had some of the same problems as viewer 3, especially in regards to neighboring regions. From my home I was able to see one of my next door regions but none of the others, when I tried fly into the neighboring region I could see I crashed. I was able to tp to another region I have some land in (Sabre) and made it there ok, but again, none of the neighboring regions were visible and I crashed when trying to tp home. Thanks again for your help! Link to comment Share on other sites More sharing options...
Gabby Pixelbottom Posted September 3, 2011 Author Share Posted September 3, 2011 Thanks, I may try that in this machine too, it seems strange though as the drivers I am using on this machine worked with viewer 2, it is hard to imagine that viewer 3 requires an older version of the drivers than viewer 2 did. Link to comment Share on other sites More sharing options...
Baloo Uriza Posted September 3, 2011 Share Posted September 3, 2011 Tristizia Demonista wrote: ps.: No, i do not have an idea why Features removed were deprecated in the OpenGL spec, and nobody should have been using them anymore at this point anyway. So...SL FAIL. Link to comment Share on other sites More sharing options...
Gabby Pixelbottom Posted September 4, 2011 Author Share Posted September 4, 2011 Well, Portage did not have 260.99 in it but it did have 260.19.44 and I downgraded to that (this on my Linux machine, have not messed with my Windows box yet). Unfortunately both Second Life 3.0 and 3.03 are still exhibiting exactly the same thing. None of the adjacent regions to the mainland region my home is in are visible and the friend's list does not load. Thanks for the idea though. Link to comment Share on other sites More sharing options...
Tristizia Demonista Posted September 4, 2011 Share Posted September 4, 2011 Hmm, you don't have by any chance another Viewer installed too ? If so, it could be that 2 Viewers share the same cache, which is bad! (Clearing the cache is a good thing anyway, btw) The only other thing that would come to mind is, that you check your connection. Else, running out of ideas Link to comment Share on other sites More sharing options...
Gabby Pixelbottom Posted September 4, 2011 Author Share Posted September 4, 2011 Whenever I test a new viewer like this I always rename my .secondlife folder to .secondlife.bak and then run the new client which creates a brand new empty .secondlife folder for itself, so that is definitely not the problem. It was a good idea though. Thanks for posting it. Link to comment Share on other sites More sharing options...
Baloo Uriza Posted October 2, 2011 Share Posted October 2, 2011 I've been trying to sort this for weeks now and I'm just thoroughly stumped. I'm legitimately curious what the solution to this turns out to be. Link to comment Share on other sites More sharing options...
leliel Mirihi Posted October 2, 2011 Share Posted October 2, 2011 Baloo Uriza wrote: Tristizia Demonista wrote: ps.: No, i do not have an idea why Features removed were deprecated in the OpenGL spec, and nobody should have been using them anymore at this point anyway. So...SL FAIL. 30% of the people that log into SL have GPUs that don't support modern OpenGL so what exactly is LL supposed to do? Not that it matter tho since everyone who has the problem with nVidia's latest drivers reports being able to login with basic shaders disabled which means the viewer is exclusively using these depreciated functions. If the driver didn't support them anymore then people shouldn't be able to log in at all no matter what their graphics settings. Oh and did I mention that nVidia as repeatedly stated that they have no intention of dropping support for the OpenGL fixed function API? People are barking up the wrong tree on this one. The viewer is doing something that's causing the latest drivers to take a really long time to crunch through the data, sometimes it gets reset by Windows, some times it crashes. Either way it's the driver that changed, not the viewer, SL isn't the only OpenGL program that's having problems with this new driver. Link to comment Share on other sites More sharing options...
Facebook
Instagram
Twitter
YouTube
Flickr
Recommended Posts
Please take a moment to consider if this thread is worth bumping.
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now