Can you guys please get together and fix the issue I’m having with my SpacePilots? The need to have the tool I want to map to my buttons on an active toolbar is ridiculous. One of my favorite things in SolidWorks is the fact that I don’t need to clog my graphics area with toolbars. I like having my space! When I got this SpacePilot PRO, I was beside myself with joy. I LOVE new technology and dove right in. Then I got bit. My button mappings wouldn’t work; not even the default mappings. I uninstalled/reinstalled the 3Dconnexion software to no avail. I called 3Dconnexion’s tech support and was told about the whole toolbar thing. I’d forgotten about that tidbit of information when I was having problems with my SpacePilot last fall. The “solution” I was given was to populate a macro toolbar with the commands I wanted to map to my buttons. Seriously? What is it about the coding in SolidWorks that’s preventing me from being able to use the buttons as designed? Where is the disclaimer telling SolidWorks users about this shortcoming? Are any other CAD packages effected this way? Another thing is the whole ‘S’ key thing. That I can get to map to a button, but it won’t stay mapped. Why is that?

Don’t get me wrong, I think the SpacePilot PRO is great. It’d be even better if it worked like it should. With all the software gurus at SolidWorks and 3Dconnexion, you think they’d be able to solve this issue. While I’m at it, can we talk about the default drivers? Is it absolutely necessary to load drivers for every CAD software under the sun by default? I don’t use AutoCAD, Maya or any of the other offerings. It seems to me that, when installing the drivers, you should be given the choice of what to load versus having to go through the custom setup. It just doesn’t make sense, in my humble opinion.

Signed,

A frustrate, yet hopeful user.

</rant>

Be Sociable, Share!

    Related Posts

    Zemanta