|
3D Connexion Space Navigator controller feedback
|
|
| alfski | Date: Tuesday, 06.01.2015, 06:19 | Message # 1 |
|
Observer
Group: Users
Australia
Messages: 18
Status: Offline
| Hi, let me know if this topic should be elsewhere.
Some initial feedback on using the Space Navigator controller with SE0.972
1. Rotating around an axis is much slower than translation along axis.
Let me explain, in normal camera control mode them amount of force you need to fwd/reverse/up/down/left/right is okay, but turning and rotating (yaw/tilt/roll) is slow relative to the amount of effort you put in. This makes it easy to fly forward at speed by hard to turn left or right!
Some scaling of the rotation or translation sensitivity is needed. Maybe something in the Control GUI to set the sensitivity of each axis? This can also be done with the 3D Connexion Control Panel tool, so I'll probably concentrate on that.
Google Earth is a good reference for how the translation/rotations are calibrated for 'even' camera control with Space Navigator.
2. Am randomly getting "teleported" back to "Go to" position when flying around with Space Nav.
When zooming towards and around planets with the SpaceNav sometimes the camera position is suddenly teleported back to the "Go to" position (or close by?), but facing in some weird direction! Pressing 'g' brings the object back into view and then off we go again.
3. It's too easy to 'crash' into a planet, as camera acceleration/speed is not adjusted based on distance from an object.
Maybe there's a setting that I've missed? The relative speed of the camera should change depending on distance from objects. Google Earth does this very well. Whether you are at 10m or 100,000m altitude the camera movement is very natural. There's no 'speed setting' in Earth, it's all automatic. This should work for navigation around large bodies (moons/planets/stars), but other objects eg. spacecraft would also need to be considered.
Andrew
|
| |
| |
| HarbingerDawn | Date: Tuesday, 06.01.2015, 07:28 | Message # 2 |
 Cosmic Curator
Group: Administrators
United States
Messages: 8717
Status: Offline
| Quote alfski (  ) The relative speed of the camera should change depending on distance from objects.
This makes sense in a program like GE, but not in SE. It would also not be simple to implement. What would happen if you wanted to fly quickly through interstellar space? You would have a certain speed limit, which would decrease as star density increased, and your speed would be constantly fluctuating as you passed stars at various distances. If you happened to pass particularly close to a star, your journey would be brought to a near-standstill until you passed it! It's just not practical in a program like this. In any case, asking the user to determine their own velocity is not unreasonable, and it gives the user the most possible freedom.
All forum users, please read this!
My SE mods and addons
Phenom II X6 1090T 3.2 GHz, 16 GB DDR3 RAM, GTX 970 3584 MB VRAM
|
| |
| |
| SpaceEngineer | Date: Tuesday, 06.01.2015, 20:51 | Message # 3 |
 Author of Space Engine
Group: Administrators
Russian Federation
Messages: 4800
Status: Offline
| Quote alfski ( ) Let me explain, in normal camera control mode them amount of force you need to fwd/reverse/up/down/left/right is okay, but turning and rotating (yaw/tilt/roll) is slow relative to the amount of effort you put in. This makes it easy to fly forward at speed by hard to turn left or right!
"Scaling of the translation speed" is a mouse wheel or + and - keyboard buttons. You may bind them to the SpaceNav buttons aswell. You should adjust your speed manually, as Harb have said. This will solve your issue with rotation/movement speed.
Also, there is a sensitivity control. Open the "Camera controls" tab and scroll it down.
|
| |
| |
| alfski | Date: Wednesday, 07.01.2015, 09:43 | Message # 4 |
|
Observer
Group: Users
Australia
Messages: 18
Status: Offline
| Thanks for your replies.
re: Issue 1. Increasing the "Sensitivity of SpaceNavigator" has helped a lot as far as rotating (yaw/pitch/roll) is concerned. Thanks!
re: Issue 3 "free flight speed control"
I understand automatic acceleration setting for free-flight is a tough problem.
Setting aside galaxy-scale navigation for the moment, perhaps automatic-speed-scaling for trips between planets and moons is more solvable?
Imagine a trip starting at ground level on Earth, pulling away from the surface. Then turning to face the Moon, selecting it with mouse click and then start flying towards the Moon and land at Tranquillity Base. All without having to mouse wheel the speed setting.
Alternatively, perhaps a "Google Earth-style" flight mode that became active in close range of a planet/object, and when it was selected 'g'. Sorry, I know I'm really trying to emphasise the Google Earth Space Nav thing. It is by far the most fluid and natural xyz controller on the market.
Also new problem...
4. Pressing and holding Space Nav Left Button (Button 1) interferes with rotation/translation of controller when looking at objects.
This occurs whether or not the Left Button (But 1) is assigned to do something in SE.
I assigned Velocity+ to Right Button(2) and Velocity- to Left Button(1). Holding Right Button performs as expected, everything get's progressively faster. The Left Button decreases speed as expected, however it also reverses the rotation axis and stops movement along an axis while the button is being pressed.
The best way to see this behaviour - find a planet, hit g to bring it into view. Rotate Left/Right with Space Nav and no buttons pressed. Now hold down Left Button and turn left/right. Do the same with the Right Button pressed. The behaviour is different for each button.
Edited by alfski - Wednesday, 07.01.2015, 09:53 |
| |
| |
| SpaceEngineer | Date: Wednesday, 07.01.2015, 18:02 | Message # 5 |
|
Author of Space Engine
Group: Administrators
Russian Federation
Messages: 4800
Status: Offline
| Quote alfski ( ) 4. Pressing and holding Space Nav Left Button (Button 1) interferes with rotation/translation of controller when looking at objects.
This occurs whether or not the Left Button (But 1) is assigned to do something in SE.
This is because it is also bound to the "orbit object" action. Make sure there only one bindings for the controller's buttons. Check the first and the second tab of the controls menu.
|
| |
| |
| alfski | Date: Saturday, 10.01.2015, 06:08 | Message # 6 |
|
Observer
Group: Users
Australia
Messages: 18
Status: Offline
| Thankyou! I assumed the SpaceNav was only being used for Camera control.
|
| |
| |
ENG
New site
Australia 
United States 
Russian Federation