What's new
By:

Request for Full 3Dconnexion Support in Alibre Design (Beyond Basic Navigation)

clexpert

clexpert

Member
I would like to raise a broader and more detailed request regarding 3Dconnexion device support in Alibre Design, specifically for advanced devices such as SpaceMouse Enterprise.

This request is not about whether a SpaceMouse works at all.
It clearly does.
The issue is how limited the current integration actually is compared to what the hardware and SDK are capable of.

1. Current Situation in Alibre Design​

Today, Alibre Design provides basic navigation support for 3Dconnexion devices:
  • Rotate
  • Pan
  • Zoom
  • Fit
  • ISO view switching
This confirms that:
  • 6DOF input is recognized
  • Camera navigation works reliably
Many users describe this as “working great”, which is reflected in existing forum discussions.

2. Existing Forum Feedback (Important Context)​

For example, in the thread “3D Connection Mouse” (Aug 12, 2025), users state:

“Works great with my Alibre Expert. I've been using it since ver 8 or 9 and find it hard to model without it.”
Click to expand...

“I definitely wouldn’t do without it.”
Click to expand...

“Super bit of kit but rather expensive.”
Click to expand...

These comments are valid and understandable.
They clearly confirm that basic navigation is useful and appreciated.

However, what is important to note is what is not mentioned in that thread:
  • No mention of context-sensitive commands
  • No mention of environment-specific command sets
  • No mention of SpaceMouse Enterprise LCD display
  • No mention of command feedback or state awareness
  • No mention of SDK-level integration
In other words, the discussion confirms that navigation works, but it does not describe professional-level integration.

3. The Core Problem: Navigation ≠ Integration​

At the moment, 3Dconnexion support in Alibre appears to be limited to generic driver-level camera control.

This means:
  • The SpaceMouse behaves essentially as a high-quality navigation controller
  • Advanced hardware features remain unused
  • The device does not interact with Alibre’s internal command system
For lower-end devices, this may be acceptable.
For SpaceMouse Enterprise, this results in a severe underutilization of the hardware.

4. What Is Missing Today​


❌ No context-sensitive command mapping​


The SpaceMouse does not know whether the user is:
  • Sketching
  • Modeling features
  • Working in an assembly
  • Editing drawings
The same static behavior applies everywhere.

❌ No dynamic command sets​


Commands do not change automatically based on:
  • Active environment
  • Active tool
  • Application state
This defeats one of the main productivity advantages of 3Dconnexion devices.

❌ No support for SpaceMouse Enterprise display and soft keys​

  • LCD display remains unused
  • No visual feedback
  • No command labels
  • No state indication
As a result, the Enterprise device is effectively reduced to basic navigation hardware, despite its premium feature set.

❌ No visible SDK-level integration​


Without proper SDK integration:
  • Commands cannot be bound meaningfully
  • Context switching is not possible
  • Device feedback is not possible
Hotkeys and macros cannot replace this functionality.

5. Why Hotkeys and Macros Are Not a Solution​


While keyboard shortcuts can be assigned:
  • They are global
  • They are context-blind
  • They do not reflect Alibre’s internal state
Professional CAD workflows rely on context awareness, not static key emulation.

6. Industry Comparison​


Other professional CAD systems have supported full 3Dconnexion integration for many years, including:
  • Context-sensitive command sets
  • Automatic environment switching
  • Device displays and soft buttons
  • Deep SDK integration
In those systems:
  • The SpaceMouse becomes a central workflow tool
  • Keyboard usage is significantly reduced
  • Productivity and ergonomics are improved
In Alibre:
  • Navigation is supported
  • Workflow integration is not
This creates a clear competitive disadvantage, especially for users who invest in professional hardware.

7. User Perspective​


As a SpaceMouse Enterprise user:
  • I can rotate, pan and zoom
  • I can switch views
  • And that is essentially all
For a high-end professional device, this level of support is not sufficient and does not match industry expectations.

8. What Is Being Requested​


This is not a request for experimental or exotic features.

It is a request for:
  • Proper 3Dconnexion SDK integration
  • Context-sensitive command mapping
  • Environment-specific command sets
  • Support for SpaceMouse Enterprise display and buttons
  • Command feedback and application state awareness
In short:
Parity with standard professional CAD workflows.

9. Why This Matters for Alibre​


Improved 3Dconnexion support would:
  • Significantly improve daily productivity
  • Reduce reliance on keyboard shortcuts
  • Improve ergonomics
  • Make better use of professional hardware
  • Increase Alibre’s attractiveness for advanced users
Basic navigation support is no longer sufficient.

10. Conclusion​


Alibre Design already recognizes 3Dconnexion devices.
The next step is to use them properly.

This request is not about adding something new.
It is about fully implementing what the hardware and SDK already offer.

Thank you for taking the time to consider this request.
 
clexpert said:

10. Conclusion​


Alibre Design already recognizes 3Dconnexion devices.
The next step is to use them properly.

This request is not about adding something new.
It is about fully implementing what the hardware and SDK already offer.

Thank you for taking the time to consider this request.
Click to expand...
Wow, this is a pretty thorough "request", now all you have to do is copy all of it into an actual Feature Request on the support page. I think that would get more attention than a post in the forum.

feature request 3dconnexion.jpg
 
HaroldL said:
Wow, this is a pretty thorough "request", now all you have to do is copy all of it into an actual Feature Request on the support page. I think that would get more attention than a post in the forum.

View attachment 46105
Click to expand...
Thank you for the suggestion.

I’ve now submitted this as an official Feature Request through the Alibre support system, including a link to this forum discussion and the full technical description.

Hopefully this will give it better visibility on the product side. Thanks for pointing me in the right direction.
 
I don't think you're the first person to request enhanced functionality for the Space Mouse. Either Alibre or 3dconnexion needs to step up and do some developing with the SDK.
 
HaroldL said:
I don't think you're the first person to request enhanced functionality for the Space Mouse. Either Alibre or 3dconnexion needs to step up and do some developing with the SDK.
Click to expand...
I agree. This has likely been requested before in one form or another.

The main issue seems to be that without proper SDK-level integration on the Alibre side, the SpaceMouse is limited to generic navigation only. The hardware and SDK capabilities already exist — they’re just not being utilized.

Hopefully raising this again, with a more detailed technical breakdown, helps move it forward.
 
Thanks for bringing this to attention of the Alibre Team. Very detailed and clean language.
 
tyc said:
Thanks for bringing this to attention of the Alibre Team. Very detailed and clean language.
Click to expand...
Thank you for taking the time to review it and for the feedback.

I appreciate that the Alibre Team has taken notice. I’m happy to provide any additional technical details if needed.
 
One possible issue here is that there may not be very many users who have the SpaceMouse Enterprise. So potentially this might soak up development resources and only be of benefit to a small number of users, yet takes resource away from other developments that could benefit many.

SO - let's hear if there are lots of people out there who already have the SpaceMouse Enterprise, or who would definitely buy one if there was full integration. It's also important to know whether your SpaceMouse Enterprise works with the current generation of 3DxWare - we know that some older 3DC devices stopped working when we followed 3DC advice to update how Alibre interacts with 3DxWare.
 
DavidJ said:
One possible issue here is that there may not be very many users who have the SpaceMouse Enterprise. So potentially this might soak up development resources and only be of benefit to a small number of users, yet takes resource away from other developments that could benefit many.

SO - let's hear if there are lots of people out there who already have the SpaceMouse Enterprise, or who would definitely buy one if there was full integration. It's also important to know whether your SpaceMouse Enterprise works with the current generation of 3DxWare - we know that some older 3DC devices stopped working when we followed 3DC advice to update how Alibre interacts with 3DxWare.
Click to expand...
Thank you for the detailed response — that’s a fair concern, and I appreciate you raising it explicitly.

I obviously don’t have visibility into how many Alibre users currently own a SpaceMouse Enterprise, or how many might consider purchasing one. That kind of usage data is something only Alibre or 3Dconnexion could realistically have.

What I’d like to emphasize is that this request isn’t really about SpaceMouse Enterprise specifically, but about proper SDK-level 3Dconnexion integration in general. Enterprise simply makes the limitations most visible because its advanced features (display, soft keys, command sets) cannot be utilized at all with the current level of support.

Proper SDK integration would benefit a much broader range of 3Dconnexion devices — not just Enterprise — by enabling context-sensitive commands and environment-aware workflows across Sketch, Part, Assembly and Drawing. From that perspective, this is less about serving a small niche and more about aligning Alibre with what has become a common baseline in professional CAD software.

Regarding compatibility concerns: my SpaceMouse Enterprise works reliably with the current generation of 3DxWare drivers. Basic navigation is stable and consistent. The limitation is clearly on the application side rather than the hardware or driver layer.

For additional practical context, I also occasionally use Autodesk Fusion 360, where full 3Dconnexion SDK integration works extremely well, including context-sensitive commands and device-specific features. This isn’t meant as a criticism of Alibre, but simply to illustrate that for many users this level of integration has become a normal and expected part of modern CAD workflows.

I agree that community input is important here. My hope is that improving SDK-level integration would not only better serve existing SpaceMouse users, but also remove a barrier for users who currently avoid investing in 3Dconnexion hardware because of Alibre’s limited support.
 
We have no way of knowing whether Alibre users have 3DC devices, unless they tell us - hence my question above to hopefully get some feedback.
 
I understand that — and that’s fair. As an end user, I obviously don’t have visibility into how many Alibre users own 3Dconnexion devices, nor is that something I can reasonably measure or prove.

My point isn’t really about providing usage statistics, but about the fact that 3Dconnexion support has effectively become a baseline expectation in professional CAD software. Most users who rely on it already have the hardware, and others decide whether to buy it based on how well it’s supported in their primary CAD tool.

From that perspective, limited integration can actually suppress adoption — users don’t report having a SpaceMouse because they know it won’t be fully utilized in Alibre.

That’s why I believe SDK-level integration is less about serving an existing, visible group of users, and more about removing a barrier and aligning Alibre with established industry standards.
 
I sold mine when I retired from reality, and no longer wished to sacrifice my life-savings to the likes of Dassault Systèmes, to continue on with Alibre, with all of its glorious, inexpensive, shortcomings.
 
DeadKahunaFL said:
I sold mine when I retired from reality, and no longer wished to sacrifice my life-savings to the likes of Dassault Systèmes, to continue on with Alibre, with all of its glorious, inexpensive, shortcomings.
Click to expand...
I understand that perspective.

My goal here isn’t to turn Alibre into an expensive enterprise CAD, but to improve everyday workflow and ergonomics for users who actively model for hours a day.

Better 3Dconnexion support wouldn’t change Alibre’s positioning — it would simply make an already efficient tool more comfortable and competitive for those who rely on it professionally.
 
Petr - you don't need to labour the point quite so much. I understand that full integration would be good. Was just trying to gather some more data that might help inform prioritisation when items are being chosen for any future version of Alibre.
 
DavidJ said:
Petr - you don't need to labour the point quite so much. I understand that full integration would be good. Was just trying to gather some more data that might help inform prioritisation when items are being chosen for any future version of Alibre.
Click to expand...
Understood — thanks for the clarification.

I appreciate you taking the time to look into it and to gather additional input. I’ll leave it there and look forward to seeing how it fits into future planning.
 
NateH said:
I have a spacemouse enterprise and the biggest thing I would like to see is the ability to rotate around the object thats in the center of the screen insteadof the orgin.
Click to expand...
That’s a great example of the kind of workflow limitation many SpaceMouse users run into.

Rotating around the object under the cursor or the current view center — rather than the global origin — is exactly the type of behavior that typically comes from deeper SDK-level integration and application-side context awareness.

It’s also a good illustration that this isn’t about “extra buttons” or luxury features, but about making everyday navigation behave in a way that feels natural when working on real geometry.
 
I have Spacemouse (Compact) + keyboard + trackball. Know some people who use a Wacom tablet as sole input device. Don't know anything about Spacemouse Enterprise.
 
You must log in or register to reply here.
Back
Top