Regression from 3.3: Invalid button mapping on SpaceMouse Enterprise (256f:c633) #109520

New Issue

Mora-Fermi · 2023-06-29T16:42:17+02:00

Mora-Fermi commented

2023-06-29 16:42:17 +02:00

Button mapping on this device is now completely scrambled. For example pressing "Shift" deletes selected object, "Lock rotation" is interpreted as play/pause, "Button 6" rotates camera 90deg CCW and "1" brings up the menu. Other buttons do not seem to register.

Bus 003 Device 013: ID 256f:c633 3Dconnexion SpaceMouse Enterprise

Tested on macOS Ventura and Ubuntu 22.04

In blender 3.3.2 on Linux and macOS, some buttons function correctly:

Shift
Ctrl
Alt
Rotate
Top
Front
Right

Basically all other keys in 3.3.2 bring up the on-screen menu.

Tested versions: 3.4, 3.5 and 3.6.

System Information
Operating system: macOS-14.0-arm64-arm-64bit 64 Bits
Graphics card: Metal API Apple M1 Pro 1.2

Blender Version
Broken: version: 3.6.0, branch: blender-v3.6-release, commit date: 2023-06-27 08:08, hash: c7fc78b81ecb
Worked: 3.3.2

Button mapping on this device is now completely scrambled. For example pressing "Shift" deletes selected object, "Lock rotation" is interpreted as play/pause, "Button 6" rotates camera 90deg CCW and "1" brings up the menu. Other buttons do not seem to register. Bus 003 Device 013: ID 256f:c633 3Dconnexion SpaceMouse Enterprise Tested on macOS Ventura and Ubuntu 22.04 In blender 3.3.2 on Linux and macOS, some buttons function correctly: - Shift - Ctrl - Alt - Rotate - Top - Front - Right Basically all other keys in 3.3.2 bring up the on-screen menu. Tested versions: 3.4, 3.5 and 3.6. **System Information** Operating system: macOS-14.0-arm64-arm-64bit 64 Bits Graphics card: Metal API Apple M1 Pro 1.2 **Blender Version** Broken: version: 3.6.0, branch: blender-v3.6-release, commit date: 2023-06-27 08:08, hash: `c7fc78b81ecb` Worked: 3.3.2

Mora-Fermi added the

labels 2023-06-29 16:42:17 +02:00

YimingWu commented

2023-06-30 05:06:25 +02:00

In Linux you probably could remap buttons pretty easily with xmodmap -e "pointer = 1 2 3 4 5 6 7....." (change to the order you needed), not sure with MacOS, but it probably has dedicated software for mac/win to adjust button shortcut. The description looks like that blender is somehow interpreting it as shortcuts/key combinations, so you might want to check your drivers/configuration software.

3Dconnexion devices are not as common, it would make it somewhat hard for us to test.

In Linux you probably could remap buttons pretty easily with `xmodmap -e "pointer = 1 2 3 4 5 6 7....."` (change to the order you needed), not sure with MacOS, but it probably has dedicated software for mac/win to adjust button shortcut. The description looks like that blender is somehow interpreting it as shortcuts/key combinations, so you might want to check your drivers/configuration software. 3Dconnexion devices are not as common, it would make it somewhat hard for us to test.

YimingWu added

Status

Needs Information from User

and removed

labels 2023-06-30 05:06:45 +02:00

Mora-Fermi commented

2023-06-30 07:46:41 +02:00

Blender is unique in that it talks directly to 3dConnexion hardware and not to the official driver.
On one hand, this is awesome since it means support for basically all USB 6dof devices on all platforms that Blender runs on; on the other, things like button mapping in the official driver are completely ignored. (and that causes massive user confusion)

If somebody points me to the right file(s) I'll happily develop a patch; I just don't have the time and bandwidth to grok through Blender's input stack.

Blender is unique in that it talks directly to 3dConnexion hardware and not to the official driver. On one hand, this is awesome since it means support for basically all USB 6dof devices on all platforms that Blender runs on; on the other, things like button mapping in the *official* driver are completely ignored. (and that causes massive user confusion) If somebody points me to the right file(s) I'll happily develop a patch; I just don't have the time and bandwidth to grok through Blender's input stack.

YimingWu commented

2023-06-30 10:55:51 +02:00

I'm not familiar with MacOS but on linux (Xorg) you could try xinput test <device_id> to check what the actual event that X11 receives when you press those buttons. And xmodmap should be able to remap buttons in different order. I recommend you to report this issue to 3dConnexion and see what they have to say. Have you tested windows? I suspect it reports various media keys and a lot of them doesn't come from regular keyboard and maybe that can cause problem, and we also can't test this thing.

I'm not familiar with MacOS but on linux (Xorg) you could try `xinput test <device_id>` to check what the actual event that X11 receives when you press those buttons. And `xmodmap` should be able to remap buttons in different order. I recommend you to report this issue to 3dConnexion and see what they have to say. Have you tested windows? I suspect it reports various media keys and a lot of them doesn't come from regular keyboard and maybe that can cause problem, and we also can't test this thing.

Mora-Fermi commented

2023-06-30 14:31:49 +02:00

This is NOT a pointing device despite having "mouse" in the name.

On Linux, NDOF devices do not use XInput system at all; they are handled by a utility called spacenavd through /var/run/spnav.sock

See https://projects.blender.org/blender/blender/src/branch/main/intern/ghost/intern/GHOST_NDOFManagerUnix.cc

On macOS and Windows, Blender is about the only NDOF capable ~~device~~ program that doesn't use official 3dxWare libraries and completely ignores the rich configuration that this driver supports.

The problem is that the mapping in https://projects.blender.org/blender/blender/src/branch/main/intern/ghost/intern/GHOST_NDOFManager.cc is not exactly correct.

This is NOT a pointing device despite having "mouse" in the name. On Linux, NDOF devices do not use XInput system at all; they are handled by a utility called `spacenavd` through `/var/run/spnav.sock` See https://projects.blender.org/blender/blender/src/branch/main/intern/ghost/intern/GHOST_NDOFManagerUnix.cc On macOS and Windows, Blender is about the only NDOF capable ~~device~~ program that doesn't use official 3dxWare libraries and completely ignores the rich configuration that this driver supports. The problem is that the mapping in https://projects.blender.org/blender/blender/src/branch/main/intern/ghost/intern/GHOST_NDOFManager.cc is not exactly correct.

YimingWu commented

2023-07-02 17:07:19 +02:00

Ah well then. Great info! I wasn't aware it's not a standard "button/axis" kind of device. We don't have such a device here, if you could would you like to provide us a fixed mapping based on what your testing result is?

Jesse Yurkovich commented

2023-07-04 01:44:31 +02:00

Perhaps the same as #107926. I think @ideasman42 has a Space Mouse; maybe he can take a look on Linux at least.

Campbell Barton referenced a pull request that will close this issue

2023-07-04 07:31:33 +02:00

WIP: Test partial revert of ecda118be407163096641db36b6ee8bf1d88ee55 #109681

Campbell Barton commented

2023-07-04 07:33:40 +02:00

There are two possible causes.

The fix for #101866 added the SpaceMouseEnterprise_HID_map button map.
The version of libspnav on Linux was updated (which was meant to fix support for "SpaceMouse Enterprise").

This is a build to check if a partial revert of ecda118be4 resolves this issue. See: !109681

There are two possible causes. - The fix for #101866 added the `SpaceMouseEnterprise_HID_map` button map. - The version of libspnav on Linux was updated (which was meant to fix support for "SpaceMouse Enterprise"). This is a build to check if a partial revert of ecda118be407163096641db36b6ee8bf1d88ee55 resolves this issue. See: !109681

👍 1

Campbell Barton commented

2023-07-05 04:49:45 +02:00

@Mora-Fermi could you please test the patched build?
https://builder.blender.org/download/patch/PR109681/

@Mora-Fermi could you please test the patched build? https://builder.blender.org/download/patch/PR109681/

Mora-Fermi commented

2023-07-22 14:07:15 +02:00

Hello,

Sorry for the long delay.

I investigated this a little bit further and realised that this situation is quite a bit more complex.

On Windows with latest 3DxWare, the existing button mapping in Blender 3.6 is perfect.
On Linux with spacenavd >= 1.0, the existing button mapping in Blender 3.6 is perfect.

BUT:
On macOS, even with the latest 3DxWare ( 10.8-1 at this time), the button mapping is completely different to what windows driver does.
on Linux with spacenavd <= 1.0, the button mapping is again different.

I created a new mapping for macOS; I tested it on several macOS devices and OS versions, making sure to do clean install every time to avoid potential configuration carry-over in 3DxWare. I have not yet tested on Ubuntu 22.04, since my build host have bitten the bullet.

/* Values mapped from SpaceMouse Enterprise running firmware 4.42, 3DxWare version 10.8.1 on macOS Sonoma, all buttons mapped to "default" dn the driver.*/
static const NDOF_ButtonT ndof_HID_map_SpaceMouseEnterprise[] = {
    NDOF_BUTTON_MENU,    /* (0). */
    NDOF_BUTTON_FIT,     /* (1). */
    NDOF_BUTTON_TOP,     /* (2). */
    NDOF_BUTTON_ENTER,   /* Labeled "Enter" (3). */
    NDOF_BUTTON_RIGHT,   /* (4). */
    NDOF_BUTTON_FRONT,   /* (5). */
    NDOF_BUTTON_DELETE,  /* (6). */
    NDOF_BUTTON_B,       /* Labeled "11" (7). */
    NDOF_BUTTON_ROLL_CW, /* (8). */
    NDOF_BUTTON_C,       /* Labeled "12" (9). */
    NDOF_BUTTON_ISO1,    /* Labeled "ISO1" (10). */
    NDOF_BUTTON_TAB,     /* (11). */
    NDOF_BUTTON_1,       /* Labeled "1" (12). */
    NDOF_BUTTON_2,       /* Labeled "2" (13). */
    NDOF_BUTTON_3,       /* Labeled "3" (14). */
    NDOF_BUTTON_4,       /* Labeled "4" (15). */
    NDOF_BUTTON_5,       /* Labeled "5" (16). */
    NDOF_BUTTON_6,       /* Labeled "6" (17). */
    NDOF_BUTTON_7,       /* Labeled "7" (18). */
    NDOF_BUTTON_8,       /* Labeled "8" (19). */
    NDOF_BUTTON_9,       /* Labeled "9" (20). */
    NDOF_BUTTON_A,       /* Labeled "10" (21). */
    NDOF_BUTTON_ESC,     /* (22). */
    NDOF_BUTTON_ALT,     /* (23). */
    NDOF_BUTTON_SHIFT,   /* (24). */
    NDOF_BUTTON_CTRL,    /* (25). */
    NDOF_BUTTON_ROTATE,  /* Labeled "Lock Rotate" (26). */
    NDOF_BUTTON_V1,      /* Labeled "V1" (27). */
    NDOF_BUTTON_V2,      /* Labeled "V2" (28). */
    NDOF_BUTTON_V3,      /* Labeled "V3" (29). */
    NDOF_BUTTON_SPACE,   /* (30). */

};

Hello, Sorry for the long delay. I investigated this a little bit further and realised that this situation is quite a bit more complex. On Windows with latest 3DxWare, the existing button mapping in Blender 3.6 is *perfect*. On Linux with spacenavd >= 1.0, the existing button mapping in Blender 3.6 is perfect. BUT: On macOS, even with the latest 3DxWare ( 10.8-1 at this time), the button mapping is completely different to what windows driver does. on Linux with spacenavd <= 1.0, the button mapping is again different. I created a new mapping for macOS; I tested it on several macOS devices and OS versions, making sure to do clean install every time to avoid potential configuration carry-over in 3DxWare. I have not yet tested on Ubuntu 22.04, since my build host have bitten the bullet. ``` /* Values mapped from SpaceMouse Enterprise running firmware 4.42, 3DxWare version 10.8.1 on macOS Sonoma, all buttons mapped to "default" dn the driver.*/ static const NDOF_ButtonT ndof_HID_map_SpaceMouseEnterprise[] = { NDOF_BUTTON_MENU, /* (0). */ NDOF_BUTTON_FIT, /* (1). */ NDOF_BUTTON_TOP, /* (2). */ NDOF_BUTTON_ENTER, /* Labeled "Enter" (3). */ NDOF_BUTTON_RIGHT, /* (4). */ NDOF_BUTTON_FRONT, /* (5). */ NDOF_BUTTON_DELETE, /* (6). */ NDOF_BUTTON_B, /* Labeled "11" (7). */ NDOF_BUTTON_ROLL_CW, /* (8). */ NDOF_BUTTON_C, /* Labeled "12" (9). */ NDOF_BUTTON_ISO1, /* Labeled "ISO1" (10). */ NDOF_BUTTON_TAB, /* (11). */ NDOF_BUTTON_1, /* Labeled "1" (12). */ NDOF_BUTTON_2, /* Labeled "2" (13). */ NDOF_BUTTON_3, /* Labeled "3" (14). */ NDOF_BUTTON_4, /* Labeled "4" (15). */ NDOF_BUTTON_5, /* Labeled "5" (16). */ NDOF_BUTTON_6, /* Labeled "6" (17). */ NDOF_BUTTON_7, /* Labeled "7" (18). */ NDOF_BUTTON_8, /* Labeled "8" (19). */ NDOF_BUTTON_9, /* Labeled "9" (20). */ NDOF_BUTTON_A, /* Labeled "10" (21). */ NDOF_BUTTON_ESC, /* (22). */ NDOF_BUTTON_ALT, /* (23). */ NDOF_BUTTON_SHIFT, /* (24). */ NDOF_BUTTON_CTRL, /* (25). */ NDOF_BUTTON_ROTATE, /* Labeled "Lock Rotate" (26). */ NDOF_BUTTON_V1, /* Labeled "V1" (27). */ NDOF_BUTTON_V2, /* Labeled "V2" (28). */ NDOF_BUTTON_V3, /* Labeled "V3" (29). */ NDOF_BUTTON_SPACE, /* (30). */ }; ```

👍 1

YimingWu commented

2023-07-24 10:13:30 +02:00

Thanks for the investigation. @ideasman42 Any idea how we solve this? Apparently the driver seems to report different values on different versions. Maybe @Mora-Fermi you could also report this issue to 3Dconnexion?

Pratik Borhade added

Status

Needs Triage

and removed

Status

Needs Information from User

labels 2023-09-01 07:05:23 +02:00

Brecht Van Lommel added the

Module

Platforms, Builds & Tests

label 2024-02-07 18:10:53 +01:00

Pratik Borhade referenced this issue