No space mouse support in --debug mode #110409

New Issue

Open

opened 2023-07-24 09:22:01 +02:00 by Hanesu · 7 comments

Hanesu commented

2023-07-24 09:22:01 +02:00

System Information
Operating system: macOS 12.6.7
Graphics card: Apple M1 Max GPU

Blender Version
Broken: 3.6.1

Short description of error
Connexion Space Mouse does not work if Blender is launched with --debug.
Normal launch works.
Is this related to #93170 ?

Exact steps for others to reproduce the error
Launch Blender with --debug
Try to use Space Mouse

**System Information** Operating system: macOS 12.6.7 Graphics card: Apple M1 Max GPU **Blender Version** Broken: 3.6.1 **Short description of error** Connexion Space Mouse does not work if Blender is launched with --debug. Normal launch works. Is this related to #93170 ? **Exact steps for others to reproduce the error** Launch Blender with --debug Try to use Space Mouse

Hanesu added the

labels 2023-07-24 09:22:02 +02:00

Iliya Katushenock added the

Platforms, Builds & Tests

labels 2023-07-24 14:27:21 +02:00

Hanesu commented

2023-07-24 15:07:27 +02:00

Author

Ok, now it's getting really weird!
I figured out that the actual issue is if I call blender or Blender in the terminal, it doesn't matter if it is in debug mode or not:

blender --> no space mouse support
Blender --> space mouse support

This is strange because there is only one executable in /Applications/Blender.app/Contents/MacOS/ and that is Blender.

Ok, now it's getting really weird! I figured out that the actual issue is if I call `blender` or `Blender` in the terminal, it doesn't matter if it is in debug mode or not: `blender` --> no space mouse support `Blender` --> space mouse support This is strange because there is only one executable in `/Applications/Blender.app/Contents/MacOS/` and that is `Blender`.

Pratik Borhade commented

2023-07-25 05:28:00 +02:00

Member

Not sure if that's a bug in blender or MacOS configurations

Not sure if that's a bug in blender or MacOS configurations

Pratik Borhade commented

2023-07-27 07:27:53 +02:00

Member

@Sergey hi, can you check? (guess you have Mac + space mouse)

@Sergey hi, can you check? (guess you have Mac + space mouse)

Sergey Sharybin commented

2023-07-27 12:30:26 +02:00

Owner

I can reproduce the issue.

Weirdly enough the axis data in the messages from the 3Dconnexion is all zero when starting Blender as blender.

Changing the RegisterConnexionClient to use winld-card for the client match makes blender to work, but this is not the configuration we want to have (at least from my understanding of the API). It might be some window-matching logic happening on the driver side, although a bit weird that it sends messages, and only some of the fields of them are zero.

Curious if FreeCAD has the same behavior (I don;t have Rosetta configured, and not sure it'll allow driver to work there even).

I can reproduce the issue. Weirdly enough the axis data in the messages from the 3Dconnexion is all zero when starting Blender as `blender`. Changing the `RegisterConnexionClient` to use winld-card for the client match makes `blender ` to work, but this is not the configuration we want to have (at least from my understanding of the API). It might be some window-matching logic happening on the driver side, although a bit weird that it sends messages, and only some of the fields of them are zero. Curious if FreeCAD has the same behavior (I don;t have Rosetta configured, and not sure it'll allow driver to work there even).

Hanesu commented

2023-07-28 06:16:36 +02:00

Author

Just out of curiosity, does the system run a different executable if one calls blender? Or what else could possibly be different?

Just out of curiosity, does the system run a different executable if one calls `blender`? Or what else could possibly be different?

Sergey Sharybin commented

2023-07-28 09:50:42 +02:00

Owner

It is the same executable. The file system by default is case-insensitive.

It is possible that the driver uses executable name for the application/window matching. Depending on how the actual executable name is presented to the appliation runtime, and how it is used later it possible that it makes some things to not find a match.

That is a speculation, as I am not really familiar with the exact rules inside of the driver.

It is the same executable. The file system by default is case-insensitive. It is possible that the driver uses executable name for the application/window matching. Depending on how the actual executable name is presented to the appliation runtime, and how it is used later it possible that it makes some things to not find a match. That is a speculation, as I am not really familiar with the exact rules inside of the driver.

Pratik Borhade commented

2023-07-28 12:05:08 +02:00

Member

I'll confirm then? (even root cause is not clear yet: driver or else)

I'll confirm then? (even root cause is not clear yet: driver or else)

Pratik Borhade added

Platforms, Builds & Tests

and removed

Platforms, Builds & Tests

labels 2023-07-28 12:05:35 +02:00

Brecht Van Lommel added

and removed

labels 2024-02-07 18:04:44 +01:00

Sign in to join this conversation.

No Label

Animation & Rigging

Asset Browser Project Overview

Automated Testing

Blender Asset Bundle

Dependency Graph

Development Management

EEVEE & Viewport

Images & Movies

Motion Tracking

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Render Pipeline

Sculpt, Paint & Texture

Video Sequencer

Virtual Reality

Blender 2.8 Project

Milestone 1: Basic, Local Asset Browser

Good First Issue

Animation & Rigging

Development Management

EEVEE & Viewport

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Sculpt, Paint & Texture

Needs Info from Developers

Needs Information from User

No Milestone

No project

No Assignees

3 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#110409

No description provided.