problems of SpaceMouse Pro *Wireless with Modo

[Aaronsam]

Hi guys, I have a problem with my new stuff "SMP Pro" and modo. If anybody who has same problem or methods, please let your comments here! thx!

1. If I directly press the “menu” button on SMP that will call the “3D Mouse Settings” out in modo. That means I can't custom shortcuts in my SMP driver.

2. So I made modo in half-window and I clicked out of modo program then press "menu" on SMP that called the "3dconnexion menu" out. And I click back to modo and the driver recognized modo that means I can custom with it.

3. All going well in the beginning. I set “1” button of SMP in a custom radial menus. And then I put four macros in this radial menus. I test that in modo that did works, but when I rolling the rocker of SMP I found the navigation mode was changed... I realized the “navigation style” programming is binding with“1” button of SMP that means even if I set the custom functions with “1” button,it will calling two commands together at the same time...I love the stuffs of 3d mouse settings in modo with speed edits?axes edits,but I really want to lock the other function bindings with my SMP that I can DIY my own workflow in modo with my SMP device happily!

If you know how to solve these,please comment here thxxxxxxxxxxxx!!

[UtaSH]

Hello Aaronsam,

Luxology has integrated the support for the 3D mouse without making use of our SDK. This means the navigation with the 3D mouse would work even with no driver.

From your description it sounds as if you did everything correctly. But Modo is reading the data directly from the device and seem to have their own functions on the buttons. You need to address this with Luxology.

[odd_enough]

This is an issue with Modo that drives me absolutely bonkers. There is a fix to this, but it requires manual editing of config files and some guesswork. I am strongly considering writing a script to make this easier since you need to repeat the process with each new version of Modo.

First off, don't even try to use the SMP drivers to assign custom button commands. As you've found out, this will result in the drivers issuing a cmd over top of the one Modo is determined to execute no matter what. This fix works for Windows 10.

In order to change the key commands, Modo can't be running. So close it if it's open and then open this file (or appropriate version) in a text editor: "C:\Users\<username>\AppData\Roaming\Luxology\MODO11.0.CFG" (I put a shortcut to it on my desktop if I need to open it to change things).

Copy and paste this at the end of that file but before "</configuration>":

Code: Select all

<atom type="3DMouse">
    <hash type="Button" key="1">cmd </hash>
    <hash type="Button" key="2">cmd </hash>
    <hash type="Button" key="3">cmd </hash>
    <hash type="Button" key="4">cmd </hash>
    <hash type="Button" key="5">cmd </hash>
    <hash type="Button" key="6">cmd </hash>
    <hash type="Button" key="7">cmd </hash>
    <hash type="Button" key="8">cmd </hash>
    <hash type="Button" key="9">cmd </hash>
    <hash type="Button" key="10">cmd </hash>
    <hash type="Button" key="11">cmd </hash>
    <hash type="Button" key="12">cmd </hash>
    <hash type="Button" key="13">cmd </hash>
    <hash type="Button" key="15">cmd </hash>
    <hash type="Button" key="14">cmd </hash>
    <hash type="Button" key="16">cmd </hash>
    <hash type="Button" key="17">cmd </hash>
    <hash type="Button" key="18">cmd </hash>
    <hash type="Button" key="19">cmd </hash>
    <hash type="Button" key="20">cmd </hash>
    <hash type="Button" key="21">cmd </hash>
    <hash type="Button" key="22">cmd </hash>
    <hash type="Button" key="23">cmd </hash>
    <hash type="Button" key="24">cmd </hash>
    <hash type="Button" key="25">cmd </hash>
    <hash type="Button" key="26">cmd </hash>
    <hash type="Button" key="27">cmd </hash>
    <hash type="Button" key="28">cmd </hash>
    <hash type="Button" key="29">cmd </hash>
    <hash type="Button" key="30">cmd </hash>
    <hash type="Button" key="31">cmd </hash>
    <hash type="Button" key="32">cmd </hash>
  </atom>

From here, you can now add in the custom commands. Like for instance, I have "<hash type="Button" key="2">cmd tool.snapState ?</hash>" which toggles snaps on and off. The easiest way to find a cmd to use is with the Command History window in Modo. Must make sure every button assignment is preceded with "cmd ". Save the file with Modo closed (or else it won't take), and restart Modo.

Hope this helps!

[zoomer]

The Enterprise Settings are in the Modo.cfg !?

I thought I had Enterprise initially running for Modo for a few weeks
(Can't remember anymore which Modo version)
by just setting the 3DS Con driver.

At some point, my Macros stopped working.
Like "SHIFT+A" to Zoom Selected went to "A" Zoom All.
Only the letters worked, no more extra Keys.


I don't quite get what your edits are doing or how the driver config files work.
But could be that I would need the same for Bricscad.
Looks like there (depending on which Version) Enterprises Button "Menu" and "Fit"
also are hardcoded to the default behavior of a standard 3D Navigators 2 Buttons
(3D Mode Options + Fit View)

So If I would now what I am doing, I could enter Bricscad hidden Config file too.

[odd_enough]

I can't speak for BricsCAD. Modo is the only program that I've used that supports 3D Mouse but still has issues with it. What works for Modo might not work for BricsCAD.

I do know that the 3Dconnexion drivers custom button assignments USED TO work with Modo a very long time ago. But those days are long gone.

[zoomer]

Yes, but it stopped at one day for all Versions at once.
Even my beloved 701

Didn't try if Short Cut Macros work again on Display Buttons in 11.02
But Enterprise doesn't work that bad, including all function and view
navigation keys on Mac.

And BTW,
I'm a Mac user.
Just for fun I installed the Windows Drivers on my Parallels VM Windows 10
and connected the Enterprise. I see Icons for the first time on my screen.
And Bricscad is perfectly integrated there.
That way that device makes sense.

Really pity what rests of functionality Mac users got for their drivers and
Enterprise device.

[odd_enough]

I wish I could edit my first reply, but after digging around, I found a way to assign buttons through the 3Dconnexion drivers AND stop Modo from executing its own will over top.

Similar procedure from what I mentioned before. Insert that block of text in the .cfg file, but instead of adding commands there, simply make all of the buttons be blank. Here's the fixed block of text again for easy pasting (can add more buttons if you are using the Enterprise model):

Code: Select all

  <atom type="3DMouse">
    <hash type="Button" key="1"></hash>
    <hash type="Button" key="2"></hash>
    <hash type="Button" key="3"></hash>
    <hash type="Button" key="4"></hash>
    <hash type="Button" key="5"></hash>
    <hash type="Button" key="6"></hash>
    <hash type="Button" key="7"></hash>
    <hash type="Button" key="8"></hash>
    <hash type="Button" key="9"></hash>
    <hash type="Button" key="10"></hash>
    <hash type="Button" key="11"></hash>
    <hash type="Button" key="12"></hash>
    <hash type="Button" key="13"></hash>
    <hash type="Button" key="15"></hash>
    <hash type="Button" key="14"></hash>
    <hash type="Button" key="16"></hash>
    <hash type="Button" key="17"></hash>
    <hash type="Button" key="18"></hash>
    <hash type="Button" key="19"></hash>
    <hash type="Button" key="20"></hash>
    <hash type="Button" key="21"></hash>
    <hash type="Button" key="22"></hash>
    <hash type="Button" key="23"></hash>
    <hash type="Button" key="24"></hash>
    <hash type="Button" key="25"></hash>
    <hash type="Button" key="26"></hash>
    <hash type="Button" key="27"></hash>
    <hash type="Button" key="28"></hash>
    <hash type="Button" key="29"></hash>
    <hash type="Button" key="30"></hash>
    <hash type="Button" key="31"></hash>
    <hash type="Button" key="32"></hash>
  </atom>

And doing so will stop Modo from being a keymapping bully. Should be free to use the drivers to map again.

[zoomer]

I wonder if that button ignorance of Modo is Space Pilot or
Windows only, as I never had problems assigning different
functions by driver.
Maybe just the two lowest keys that seem to resemble the
original two buttons of old navigator, menu and fit view.
As it seems to happen in Bricscad for Mac.

But I am a silly Mac User.
In the past I looked at some of the XML files of the driver and
found similar button numbers but never the functions or macros
that I assigned to my Apps like in your first example for Modo
Config.

And as assignment of buttons in the driver inteface is very tedious
and inconvenient anyway, I would even prefer to edit the XMLs
directly.
So I could assign buttons alternatively in Modo Config which is
a nice option.

Have to look at them again.

[odd_enough]

If you need help figuring out which key number refers to which button on the 3D mouse, I made a list from sifting through the 3dx XML file's HID numbers.

From 1-31:

Menu
Fit
Top
Left
Right
Front
Bottom
Back
Roll_CW
Roll_CCW
ISO1
ISO2
1
2
3
4
5
6
7
8
9
10
Esc
Alt
Shift
Ctrl
Rotate
Panzoom
Dominant
Plus
Minus

I only have 15 of those on my SpacePilot Pro, but the ID's do match up. I don't think that ordering is Modo specific, since it's based off of HID numbers, so might work in other programs if you can figure it out.

[zoomer]

Interesting,
that's about the order the button assignments are displayed in my driver.
Yes, I have 12 vs 10 and and some more at the end.
But it looks like a plan.

I will look into Modo Config and Drivers Config files again over the weekend.
I think the 3DCon Part in Modo Config could be extracted, saved as partial CFG
file, to work for all Modo versions and installations, especially future ones.