Hi,
After having too many frustrations with the Beta 10 drivers, I've reverted back to the 3.14.2 version and I'm seeing a problem I wasn't seeing before. I'm using 3dsMax 2011, and when orbiting or panning in the viewports, upon releasing the navigator knob the viewport continues to pan or orbit as though I were still applying force to the navigator. I then apply new force to the knob to stop the motion. This is occuring now about 50% of the time. Last week, it wasn't quite this bad. I tried a simple calibration but that didn't work. Should I reinstall the driver? Blow some air inside? Any other suggestions??
Thanks!
"Sticky Motion" problem with SpacePilot
Moderator: Moderators
-
digitalx3d
- Posts: 19
- Joined: Fri Oct 15, 2010 12:49 pm
When you removed and installed the 3.14.2 driver did you remember to remove previous button mappings?
Computer/OS(C)/Users/your profile/AppData/Local/Roaming
There are 3Dconnexion folder files these contain past button mappings.
Uninstall the driver remove the 3Dconnexion folders in the above path.
Install the 3.14.2 driver.
Open the 3DControl panel
Make sure nothing is touching the cap
Click Calibrate and close
Calibrate works in the background you wont see anything on the screen.
You can also try a miscalibrate to the oposite direction of the spin
Twist knob in oposite direction hit calibrate and release.
Now recalibrate one more time this time not touching the device and see if this works.
Computer/OS(C)/Users/your profile/AppData/Local/Roaming
There are 3Dconnexion folder files these contain past button mappings.
Uninstall the driver remove the 3Dconnexion folders in the above path.
Install the 3.14.2 driver.
Open the 3DControl panel
Make sure nothing is touching the cap
Click Calibrate and close
Calibrate works in the background you wont see anything on the screen.
You can also try a miscalibrate to the oposite direction of the spin
Twist knob in oposite direction hit calibrate and release.
Now recalibrate one more time this time not touching the device and see if this works.
-
digitalx3d
- Posts: 19
- Joined: Fri Oct 15, 2010 12:49 pm
Thanks for the quick reply Fred. I will try this but I have a few questions first. In the ".../local" folder there is no "Roaming" subdirectory. Did you mean for me to look in both the "local" and "roaming" folders (within AppData)? and then in the "3DConnexion" folder in each of those? Do you know the specific filename of those button mappings? I see "user.config" files, .scg file, and various XML files.
Also, in regards to your suggestion for "opposite calibration"- you're suggesting to twist the knob in the "opposite direction". I just want to clarify that in my situation, the viewport motion continues in whatever direction I was last moving (kinda like a momentum/inertia effect). I don't have the random spinning issue like another user here was having. So I'm not sure if this "miscalibrate" will work for me??
Thanks!
Also, in regards to your suggestion for "opposite calibration"- you're suggesting to twist the knob in the "opposite direction". I just want to clarify that in my situation, the viewport motion continues in whatever direction I was last moving (kinda like a momentum/inertia effect). I don't have the random spinning issue like another user here was having. So I'm not sure if this "miscalibrate" will work for me??
Thanks!
Hello digitalx3d -
The reason Fred suggested intentionally mis-calibrating first is that a small mis-calibration can be more difficult to resolve than a more obvious one.When the calibrate function is either not correcting a problem with drifting or is correcting it only briefly, this additional step can be helpful.
The direction of the drifting or whether the model is drifting or spinning is not important - both come from data being sent to the application when you are no longer touching the device. While it is normal to rest your hand on the cap when you are not actively moving the model, it is sometimes possible for hand pressure to cause the device to keep trying to re-center once the cap is released. The small stream of data sent to the application as the cap tries to return to center can cause unwanted movement onscreen. By re-zeroing, the calibrate function stops the data being sent to the application.
Typing %appdata% in the Win7 Search box or XP's Run command will bring up the Application Data [XP] or App Data|Roaming [Win7] folder. That will contain the 3Dconnexion folder where the profiles are stored.The profiles from the released driver are .scg files. The .xml files are profiles from the beta driver.The entire 3Dconnexion folder should be removed for a clean install. When you re-install the software new default profiles will be created.
----------
Barbara
The reason Fred suggested intentionally mis-calibrating first is that a small mis-calibration can be more difficult to resolve than a more obvious one.When the calibrate function is either not correcting a problem with drifting or is correcting it only briefly, this additional step can be helpful.
The direction of the drifting or whether the model is drifting or spinning is not important - both come from data being sent to the application when you are no longer touching the device. While it is normal to rest your hand on the cap when you are not actively moving the model, it is sometimes possible for hand pressure to cause the device to keep trying to re-center once the cap is released. The small stream of data sent to the application as the cap tries to return to center can cause unwanted movement onscreen. By re-zeroing, the calibrate function stops the data being sent to the application.
Typing %appdata% in the Win7 Search box or XP's Run command will bring up the Application Data [XP] or App Data|Roaming [Win7] folder. That will contain the 3Dconnexion folder where the profiles are stored.The profiles from the released driver are .scg files. The .xml files are profiles from the beta driver.The entire 3Dconnexion folder should be removed for a clean install. When you re-install the software new default profiles will be created.
----------
Barbara