The BRAWL² Tournament Challenge has been announced!
It starts May 12, and ends Sept 12. Let's see what you got!
https://polycount.com/discussion/237047/the-brawl²-tournament
It starts May 12, and ends Sept 12. Let's see what you got!
https://polycount.com/discussion/237047/the-brawl²-tournament
What is the consensus on 3DConnexion hardware?
Hello!
I've scoured for what others think of these devices, but most of the threads are quite old (10+ years), or they are focused on CAD. I have been having hand pains, and I have tried a variety of devices (vertical mouse, cadmouse, wacom, so many trackballs, etc.) and with many of them various pains come up. Wacom has been by far the most comfortable, but clicking the mmb on the wacom pens get pretty uncomfortable after a while (I tend to work in 3d for 10+ hrs a day).
I was thinking of binding one of my keyboard buttons to mmb, but I recently came across the Spacemouse from 3DConnexion. It seems quite interesting since you can navigate the viewport so quickly and easily, but I am wondering if it will not be useful in the long run? I use my keyboard a lot, and I tend to jump between software (Blender, UE5, Unity, Painter, Zbrush, PS, Designer, Toolbag). Having my left hand jump between keyboard and the small spacemouse seems like it will slow me down, and the enterprise is interesting, but it seems cumbersome to lug to and from the office and I also have read that the buttons are a bit difficult to press when using them a lot. On top of this, I have concerns that getting used to a unique way of navigation and getting used to a ton of macros set up on a non-keyboard device can hurt me in the long run when going between workstations or between jobs, or if god forbid the spacemouse breaks or the company goes under. Plus, half of the software I use uses the keyboard all of the time, like Designer, UE, or Unity.
The latter half of the paragraph sounds really disparaging towards the spacemouse but these are just concerns of having such a radical change in hardware for my setup, but I do need to figure something out to fix my RSI issues. What do you all think of these devices? Are my fears of being too hardware/macro dependent something that actually warrants such concern? I'm a Junior, so my career is just beginning and I would like for it to be a long one.
The latter half of the paragraph sounds really disparaging towards the spacemouse but these are just concerns of having such a radical change in hardware for my setup, but I do need to figure something out to fix my RSI issues. What do you all think of these devices? Are my fears of being too hardware/macro dependent something that actually warrants such concern? I'm a Junior, so my career is just beginning and I would like for it to be a long one.
Thank you,
Max 
Replies
I really like them and if you use software that has driver support and you do something that takes advantage of the hardware (not modelling imo) they are absolutely a useful thing to have.
But
There is zero effective support outside of their proprietary drivers - there are a couple of open source efforts to make them useful but they aren't complete or very usable (the only one I could get to respond at all recently was on Linux and would have required me to write a layer on top of the basic drivers
To fix your actual problem...
Get (or build) a keyboard or macropad that's compatible with vial or zmk.
That will allow you to program macros, layouts etc as well as special behaviour when you hold keys, double tap them and so on .
You can set up mousekeys as well-including moving the pointer.
Vial has the best support through a web browser ui - zmk is pretty close though. Via and qmk are the more popular options but hide access to the clever features.
These things store the layout on the device so you don't need special drivers or shitty razer malware and when you move to a different computer the layout remains
Don't worry about getting attached to macros etc.
Its usually less painful to remap a device to an applications default shortcuts than it is to change the application shortcuts - and you'll remember the defaults if you work somewhere you don't take your special hardware.
RSI is serious business - thinking about it when you're young is very sensible .
Wacom plus macropad is probably your best option for doing art workflows but you need to mix it up - the R in RSI stands for repetitive
Blender has a very clever legacy input scheme (quite unusual for people not familiar with oldschool command-centric CAD) revolving around tapping a key to initiate a command like Move, followed by moving the mouse to perform the action (without any button being held down), and then confirming or cancelling the action with another tap of a button. This coupled with the fact that such a Move action doesn't have to start anywhere near the element being moved but is instead performed relatively to wherever the mouse cursor was located when the action is triggered makes it way easier on the hands than having to precisely grab, hold and drag a manipulator like Maya or Max require, and it's also objectively faster since it involves less mouse travel. Once you try it there's really no coming back, it's just that much more pleasant, streamlined and easier on the hands.
This could probably be applied to navigation too, but I think that using this kind of lightweight input scheme for object manipulation alone could already be a significant improvement for your hand pain.
I appreciate the well written response, and it’s definitely a good idea to get a QMK board or something similar so I don’t have to mess with drivers.
On navigation : honestly this video showing the spacemouse/spacenavigator in action is a reminder that even though these devices definitely have some uses for presentation and can be a decent input device for people not used to Maya-style KB and mouse, it really isn't a time saver at all. I find it a bit painful to watch actually (and yes I do have one too ... sitting in a box next to other spare computer stuff).
I am actually quite sensitive to bad camera implementations in games and software (in the sense that I often feel uneasy if a game camera has too much unexpected ease-in/ease-out, or if a camera does weird things on its own as is often seen in current third person games) ; yet the above paradigm of framing to the position 3D Cursor feels extremely natural and snappy and doesn't bring any discomfort. And of course this saves on mouse inputs as well.
Thank you!
I never enjoyed them for actually modelling where I want to be focused around a specific object - cos that's not what you get. There's no reason the device can't do it but the software always seemed to actively work against you - even if there were settings that claimed to focus your object.
combine that with the fact you lose access to shortcut keys (or replace them with buttons that are worse to press) and it just knackers any productivity.
there were some 'unofficial' windows drivers that emulated a standard HID device back in the Vista days - i got it working with zbrush on a cintiq and it wasn't a bad setup - zbrush has a weird paradigm that kinda suited the device
- i assume those have been lost to time now (and frankly there's no way I'd be installing a windows device driver I got off the internet these days)
fwiw - i struggle to enjoy all camera navigation setups that aren't identical to max's 'orbit selected subobject' tool so I may not be the best measure
Like I said, try to find one with VIAL support - or at least VIA.
QMK is the underpinning for these but is much more work to set up key maps (as in you have to modify files and reflash the thing every time) vs having a web interface that does it.