But I LIKE It!
April 14, 2008In the last post, I detailed my issues with both 1.19.1.4 and 1.20.. and the issue of 1.20 locking up the Mac really sucks, because this awesome little device needs 1.20 to work. This thing rocks.. I used it for a few minutes this afternoon before 1.20 locked up my Mac again, switching between flycam and avatar movement modes, and enjoying it. And I have to say.. if you’ve never used flycam, wow. The camera go go anywhere without having to alt-click to make something your focal point first. Just use the spacenavigator (or joystick if you wanna go back to 2d movements on a 3d canvas) to move the camera anywhere you want. It’s amazing.
So, in theory, someday they’ll resolve this issue, and then my video recording explorations in SL will be even easier and more fun than ever. In the meantime, I opened a jira issue report on 1.20 for doing mean things to the Mac. If you have similar issues, please vote on it. Let them know you’d like it fixed.
From the Mentor mailing list: if you get a mac user
Jane2 | April 15, 2008From the Mentor mailing list:
if you get a mac user with a brand new mac that finds sl freezes after 30 secs and needs a reboot there is a fix that works that i have used..there are other fixes on the wiki which might work if this doesnt.
Find the “user_settings” folder under your Second Life folder that is under yourname/library/Application support/secondLife/user_settings Data. Note also you will have a folder with your Avatar’s name. Don’t change the settings.xml file in that folder - change the one in the user_settings folder.
* once you have found user_settings/settings.xml. You will have to manually add the command to disable Object Occlusion to this file. The lines to add at the end before the “” are:
o
o
* Save the setting.xml file and then try to connect to Second Life.
Yeah, I saw this in the JIRA too.. unfortunately, it
radarmasukami | April 15, 2008Yeah, I saw this in the JIRA too.. unfortunately, it seems to me to be what we call at work “tribal knowledge” when someone’s trying to fix something, they do something, it appears to work, and really it’s not related. I tried this and it had no effect, and I think the problem is there’s a LOT of variables. At first I wasn’t moving around, I was only using the flycam, and I thought it was fixed. Unfortunately, not.
Someone also keeps screaming (as loud as you can scream in the JIRA) that setting texture memory to half the available VRAM instead of 100% of it will stop the beachballs and lockups. While it’s probably a good setting value, this does not eliminate the problems a lot of us are seeing.. certainly not my issues with 1.20. So.. I take all these with a grain of salt. I’m glad they appear to work for certain people in some circumstances, but more often than not they also come back later saying, “Oh. Maybe not.”
Anyway.. thanks for the heads up. I wish this did the trick.
IIRC this person was on a macbook which uses integrated graphics and a whole nother driver and whole other issues than what I’m seeing. And therein lies a lot of the complextity.
If it's any consolation, the RC viewer sucks with a
Jane2 | April 15, 2008If it’s any consolation, the RC viewer sucks with a PC as well. Nothing should be this complicated to view properly IMO.
Yep. I think nvidia cards are having super special issues.
radarmasukami | April 15, 2008Yep. I think nvidia cards are having super special issues. I see there’s a new RC version today, I’ll try it tonight and hope hope hope they fixed the system lockup thing.
I really wanna use my SpaceNavigator. It’s just flat out fun to use.