Krystal Yifu

While I do understand people that view Linux as a great source of frustration and go with the "Windows is just more compatible and so, you should just use that instead" philosophy, I cannot consider this a useful answer. Honestly, if there had been a section in the forums for the Linux Viewer, I guarantee I would have posted there for the sake of engaging with those who *do* use Linux.

I just purchased a SpaceNavigator Mouse from 3D connexion. This was acquired primarily for use in Blender. However, I see people being able to use it for SecondLife as well. Being a Linux user, Im well aware that not everything (that works on Windows or Mac) will work for my Ubuntu install (12.04 -- 64 bit). So far, I have gotten the device working on Blender with full capabilities. However, I cannot get the SecondLife to detect my mouse. The blue LED ring on the mouse is lit up while running SecondLife but the "Joystick Configuration" screen has the "Enable Joystick" checkbox greyed out and reads "no device detected". However, I do see a button on the lower right that reads "SpaceNavigator Defaults". I pressed it and see that it changed yaw/pitch/zoom settings to SpaceNavigator defaults (of course). The "enable joystick" button remained greyed out. I have consulted everything from 3dConnexion's support pages, online documentations and forum posts and even looked at the SecondLife forums to see if someone knows something I dont. So far, I have tried the following: Attempt 1: 3DxWare drivers and spacenavd were installed. This was done while just working on getting Blender to work with my mouse. It was successful with Blender but SL does not see it. Attempt 2: I consulted the following SecondLife wiki page: http://wiki.secondlife.com/wiki/SpaceNavigator#Linux This article suggests that the 3DxWare drivers are not recommended to use in this situation so I uninstalled that but left spacenavd installed. I then made the changes inside /etc/udev/rules.d/ with a file called 91-spacenavigator.rules with the following lines: KERNEL=="event[0-9]*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c603", SYMLINK+="input/spacemouse", GROUP="plugdev", MODE="664" KERNEL=="event[0-9]*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c623", SYMLINK+="input/spacetraveler", GROUP="plugdev", MODE="664" KERNEL=="event[0-9]*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c626", SYMLINK+="input/spacenavigator", GROUP="plugdev", MODE="664" After rebooting, I found that SecondLife and Google Earth still did not detect my device. Attempt 3: I left the above udev rules in there but uninstalled the spacenavd package as well. Upon reboot, the obvious outcome (SpaceNavigator failing to work for anything) was the result. I think I also tried it with 3Dxware installed but spacenavd uninstalled. I did not get any results doing it this way either. I have attempted to contact 3D Connexion's support team and they pretty much linked me to the aforementioned Second Life wiki article. So, at this point, Im getting short on ideas. I can be happy with the fact that it works for Blender but was really hoping I could use it in SecondLife. Any Linux users here with a better outcome concerning 3D Connexion products and SecondLife use? Can anyone suggest other things to try?

I am currently having this issue with the SL Viewer. I am a Linux user so I have expected a certain level of bugs and glitches as support from the Lindens with Linux has always been kind of slow/limted. My problem is not in the snapshot itself. I can open the dialogue and refresh my snapshot necessary. Its when I choose to save it that there is a problem. 1) Save and Save As... - The viewer freezes with the save button still in its hoverstate. I cannot control anything in the viewer or even move my avatar anywhere. I cannot properly quit, using the system monitor to do a hard shut down of second life instead. 2) Send to Profile Feed (this was one suggested method, allowing me to download from my profile as a kludge for #1) - I get a generic error that tells me that my image could not be uploaded to the feed I did take a look at the alternate viewers listed here but all of these viewers result in the same problem.