Ultimate space simulation software

 
Snaffy
Observer
Observer
Topic Author
Posts: 4
Joined: 14 Jan 2017

3DConnexion SpaceNavigator - All wrong ?

14 Jan 2017 04:02

Hi, This is my first posting, so please be gentle with me :)
And apologies if this is a well known issue. I did a search here in this area and did not find anything to help, hence this post.

A little background:
I did try Space Engine quite some time ago, and will admit to being a little frustrated with the controls, however after some chat to others and seeing recent screenshots I decided I've give it a second try :)

Downloaded the latest version and the HD and Ultra add-on packs, and all looks gorgeous (if I can keep anything in view)  ;)

My biggest problem, is the same problem I had last time, in that, my 3DConnexion SpaceNavigator controller seems completely unusable and all over the place inside "Space Engine"

I can use this 3D controller in Photoshop, some 3D modelling apps, Second Life to pan about in 3D, also Google Earth.
However in Space Engine, it's just all over the place.

I can see it's supported, so I am guessing, there is some config I need to sort out, or settings I need to put in place?

Moving the 3D controller in various directions when running "Space Engine" just gives very weird results that make it totally unusuable.

Can anyone perhaps what I'm doing wrong, or what I need to do, or what I need to change, so that I can get this working as using a 3D controller such as this in a 3D environment is an utter joy, when it's working right, and as expected.

Many many thanks in advance :)
 
Snaffy
Observer
Observer
Topic Author
Posts: 4
Joined: 14 Jan 2017

3DConnexion SpaceNavigator - All wrong ?

15 Jan 2017 03:38

No one using the Space Navigator?
Or are many using it, but it's working perfect?

Perhaps I need a follow up post and write here what happens on screen when I use it, as the movement of the controller is not linked correctly to the effect it has "on-screen"

Which is a shame as it's lovely to use, when it's working right.
 
User avatar
Mosfet
Star Engineer
Star Engineer
Posts: 1525
Joined: 24 Oct 2016
Location: Italy
Contact:

3DConnexion SpaceNavigator - All wrong ?

15 Jan 2017 06:05

Snaffy wrote:
Source of the post No one using the Space Navigator?

The only one I know of is SpaceEngineer, but I'd wait more than 24 hours for answers ;)
"Time is illusion. Lunchtime doubly so". Douglas N. Adams
| My mods: http://forum.spaceengine.org/viewtopic.php?f=3&t=80 | My specs: Asus x555ub - cpu i5-6200u, ram 12gb, gpu nvidia geforce 940m 2gb vram |
 
Snaffy
Observer
Observer
Topic Author
Posts: 4
Joined: 14 Jan 2017

3DConnexion SpaceNavigator - All wrong ?

15 Jan 2017 07:05

Mosfet wrote:
Snaffy wrote:
Source of the post No one using the Space Navigator?

The only one I know of is SpaceEngineer, but I'd wait more than 24 hours for answers ;)

Thanks for the reply, as I'm new to these forums, I'm not used to the general speed/activity here.
Hopefully I can get this working with the help of some kind others who can tell me what I'm doing wrong, or probably what changes I need to make to get the 3D controller working as expected :)
 
User avatar
Mosfet
Star Engineer
Star Engineer
Posts: 1525
Joined: 24 Oct 2016
Location: Italy
Contact:

3DConnexion SpaceNavigator - All wrong ?

15 Jan 2017 07:53

In the meantime, see these results from the old forum, they refer to an older version but maybe some answer can lead to partial solutions:
http://en.spaceengine.org/search/?q=space+navigator
"Time is illusion. Lunchtime doubly so". Douglas N. Adams
| My mods: http://forum.spaceengine.org/viewtopic.php?f=3&t=80 | My specs: Asus x555ub - cpu i5-6200u, ram 12gb, gpu nvidia geforce 940m 2gb vram |
 
User avatar
SpaceEngineer
Author of SpaceEngine
Author of SpaceEngine
Posts: 1108
Joined: 17 May 2016
Location: Saint-Petersburg
Contact:

3DConnexion SpaceNavigator - All wrong ?

16 Jan 2017 06:47

Maybe this is because default settings in SE for this input device does not correspond to the axes names (changes in drivers?), or maybe because of conflict with their "joystick emulator", which detected by SE as a joystick. Just open settings menu and configure Space Navigator axes. I recommend to you to clear out all actions for Space Navigator first, because movements of a stick must be very gently. And clear out that 3D connection joystick emulator to prevent conflicts (SE works with all joysticks in the system simultaneously). Also, clear bindings of a buttons, and assign them to the SE speed presets [Ctrl] + [Numpad +] and [Ctrl] + [Numpad -] in the Space Navigator settings app. I also increased a "sensitivity" of the Space Navigator to make turns more faster (scroll the window down, there will be a sliders).

I ended up with these settings for a free camera:

scr00186.jpg


And these for a ship:

scr00187.jpg


Configuring axes in-game is very tricky, so here is the config file. Put it into config directory. If your device name differs from mine, rename the file.

joy_SpaceNavigator.cfg
(8.95 KiB) Downloaded 425 times
 
Snaffy
Observer
Observer
Topic Author
Posts: 4
Joined: 14 Jan 2017

3DConnexion SpaceNavigator - All wrong ?

16 Jan 2017 14:36

Thank you very much for the advice and screen shots.
I shall spend some time following these and see how I get on.
I'll report back either way :)
 
User avatar
keerah
Observer
Observer
Posts: 3
Joined: 18 Feb 2018
Contact:

3DConnexion SpaceNavigator - All wrong ?

18 Feb 2018 20:01

Hi I use SpaceNavigator too. And it was very glitchy to set the controls, it detects axis wrong like 90% of times. 
But I've finally managed to set things up by editing the config text file. I've also had to disable all controls for the Spaceengine 
in 3dconnexion configurator cause the up/down axis works as mouse wheel by default and changes velocity as you navigate.
Though controlling with Space Navigator is quite difficult sometimes because of infinite inertia
 
lightbulbjim
Observer
Observer
Posts: 1
Joined: 30 Jun 2020

3DConnexion SpaceNavigator - All wrong ?

01 Jul 2020 00:16

A bit of an old topic, but I just got this working with my SpaceMouse Compact and thought I would document the process. As others have mentioned native integration is wonky so it's necessary to use joystick emulation. It's not possible to do joystick emulation via the 3Dconnexion GUI, so you'll need to create a hand-rolled config file.

Here are the steps since it's not immediately obvious how to do it:

1. Find any existing 3Dconnexion config files for Space Engine and delete them. You should find SpaceEngine.xml in one or both of the following locations:

  • C:\Users\<user>\AppData\Roaming\3Dconnexion\3DxWare\Cfg\
  • C:\ProgramData\3Dconnexion\3DxWare\Cfg\

2. Create a new config file in one of the above locations. I named mine SpaceEngineJoy.xml to make it easy to distinguish from any auto generated files. It should contain the following:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!--
(c) Copyright 3Dconnexion. All rights reserved.
$Revision: 16358 $
-->
<AppCfg Default="true" xmlns="" CfgFormatVersion="1.3" ThisFileVersion="1.6">
  <CfgProperties>
    <ID>ID_STR_3_JOYSTICK_TEMPLATE</ID>
    <Name>SpaceEngine</Name>
    <InheritsFromID>ID_Base_Cfg</InheritsFromID>
  </CfgProperties>
  <AuthorInfo>
    <DriverVersion>17.6.1</DriverVersion>
    <Created>
      <Tool>3DxService.exe</Tool>
      <Version>17.5.5</Version>
      <Date>2017:11:2:28:10:58:11:745</Date>
      <User>3DxCfgAdmin</User>
    </Created>
    <LastChange>
      <Tool>XMLCfgEditor.exe</Tool>
      <Version>17.6.1</Version>
      <Date>6/27/2019 10:04:51 AM UTC</Date>
      <User>jwick</User>
    </LastChange>
  </AuthorInfo>
  <AppInfo>
    <Signature>
      <Name>STR_3_JOYSTICK_TEMPLATE</Name>
      <ExecutableName>SpaceEngine.exe</ExecutableName>
      <Transport>KMJ</Transport>
    </Signature>
    <Options>
      <IgnoreMouseWheelInertia>true</IgnoreMouseWheelInertia>
    </Options>
  </AppInfo>
  <Settings>
    <ResponseCurve>1.00</ResponseCurve>
  </Settings>
  <ButtonActions>
    <!-- App Handled Actions -->
    <ButtonAction Type="App">
      <ID>App_ResetYourView</ID>
      <Name>STR_APP_RESETYOURVIEW</Name>
    </ButtonAction>
    <!-- Keyboard Functions -->
    <ButtonAction Type="Joystick">
      <ID>HIDJoystick_1</ID>
      <Name>STR_JOYSTICK_1</Name>
    </ButtonAction>
    <ButtonAction Type="Joystick">
      <ID>HIDJoystick_2</ID>
      <Name>STR_JOYSTICK_2</Name>
    </ButtonAction>
    <ButtonAction Type="Joystick">
      <ID>HIDJoystick_3</ID>
      <Name>STR_JOYSTICK_3</Name>
    </ButtonAction>
    <ButtonAction Type="Joystick">
      <ID>HIDJoystick_4</ID>
      <Name>STR_JOYSTICK_4</Name>
    </ButtonAction>
    <ButtonAction Type="Joystick">
      <ID>HIDJoystick_Hat_N</ID>
      <Name>STR_JOYSTICK_HAT_N</Name>
    </ButtonAction>
    <ButtonAction Type="Joystick">
      <ID>HIDJoystick_Hat_E</ID>
      <Name>STR_JOYSTICK_HAT_E</Name>
    </ButtonAction>
    <ButtonAction Type="Joystick">
      <ID>HIDJoystick_Hat_S</ID>
      <Name>STR_JOYSTICK_HAT_S</Name>
    </ButtonAction>
    <ButtonAction Type="Joystick">
      <ID>HIDJoystick_Hat_W</ID>
      <Name>STR_JOYSTICK_HAT_W</Name>
    </ButtonAction>
  </ButtonActions>
  <Devices>
    <Device>
      <Name>Standard 3D Mouse</Name>
      <ID>ID_Standard_3D_Mouse</ID>
      <AxisFilter>None</AxisFilter>
      <CurrentButtonBank>Default</CurrentButtonBank>
      <CurrentAxisBank>Default</CurrentAxisBank>
      <AxisBank Default="true">
        <Name>STR_DEFAULT_BANK</Name>
        <ID>Default</ID>
        <Axis>
          <Enabled>true</Enabled>
          <Input>
            <ActionID>HIDMultiAxis_X</ActionID>
            <Min>-512</Min>
            <Max>511</Max>
          </Input>
          <Output>
            <ActionID>HIDJoystick_X</ActionID>
          </Output>
        </Axis>
        <Axis>
          <Enabled>true</Enabled>
          <Input>
            <ActionID>HIDMultiAxis_Y</ActionID>
            <Min>-512</Min>
            <Max>511</Max>
          </Input>
          <Output>
            <ActionID>HIDJoystick_Y</ActionID>
          </Output>
        </Axis>
        <Axis>
          <Enabled>true</Enabled>
          <Input>
            <ActionID>HIDMultiAxis_Z</ActionID>
            <Min>-512</Min>
            <Max>511</Max>
          </Input>
          <Output>
            <ActionID>HIDJoystick_Z</ActionID>
          </Output>
        </Axis>
        <Axis>
          <Enabled>true</Enabled>
          <Input>
            <ActionID>HIDMultiAxis_Rx</ActionID>
            <Min>-512</Min>
            <Max>511</Max>
          </Input>
          <Output>
            <ActionID>HIDJoystick_Rx</ActionID>
          </Output>
        </Axis>
        <Axis>
          <Enabled>true</Enabled>
          <Input>
            <ActionID>HIDMultiAxis_Ry</ActionID>
            <Min>-512</Min>
            <Max>511</Max>
          </Input>
          <Output>
            <ActionID>HIDJoystick_Ry</ActionID>
          </Output>
        </Axis>
        <Axis>
          <Enabled>true</Enabled>
          <Input>
            <ActionID>HIDMultiAxis_Rz</ActionID>
            <Min>-512</Min>
            <Max>511</Max>
          </Input>
          <Output>
            <ActionID>HIDJoystick_Rz</ActionID>
          </Output>
        </Axis>
      </AxisBank>
      <ButtonBank Default="true">
        <Name>STR_DEFAULT_BUTTONBANK</Name>
        <ID>Default</ID>
        <Button>
          <Input>
            <ActionID>V3DK_MENU</ActionID>
          </Input>
          <Output>
            <ActionID>Driver_ShowDriverGUI</ActionID>
          </Output>
        </Button>
        <Button>
          <Input>
            <ActionID>V3DK_FIT</ActionID>
          </Input>
          <Output>
            <ActionID>Driver_ShowDriverGUI</ActionID>
          </Output>
        </Button>
        <Button>
          <Input>
            <ActionID>V3DK_TOP</ActionID>
          </Input>
          <Output>
            <ActionID>HIDJoystick_Hat_N</ActionID>
          </Output>
        </Button>
        <Button>
          <Input>
            <ActionID>V3DK_LEFT</ActionID>
          </Input>
          <Output>
            <ActionID>HIDJoystick_Hat_W</ActionID>
          </Output>
        </Button>
        <Button>
          <Input>
            <ActionID>V3DK_RIGHT</ActionID>
          </Input>
          <Output>
            <ActionID>HIDJoystick_Hat_E</ActionID>
          </Output>
        </Button>
        <Button>
          <Input>
            <ActionID>V3DK_FRONT</ActionID>
          </Input>
          <Output>
            <ActionID>HIDJoystick_Hat_S</ActionID>
          </Output>
        </Button>
        <Button>
          <Input>
            <ActionID>V3DK_1</ActionID>
          </Input>
          <Output>
            <ActionID>Driver_Toggle_3DxNumPad</ActionID>
          </Output>
        </Button>
        <Button>
          <Input>
            <ActionID>V3DK_2</ActionID>
          </Input>
          <Output>
            <ActionID>HIDJoystick_2</ActionID>
          </Output>
        </Button>
        <Button>
          <Input>
            <ActionID>V3DK_3</ActionID>
          </Input>
          <Output>
            <ActionID>HIDJoystick_3</ActionID>
          </Output>
        </Button>
        <Button>
          <Input>
            <ActionID>V3DK_4</ActionID>
          </Input>
          <Output>
            <ActionID>HIDJoystick_4</ActionID>
          </Output>
        </Button>
        <Button>
          <Input>
            <ActionID>V3DK_ESC</ActionID>
          </Input>
          <Output>
            <ActionID>KB_Esc</ActionID>
          </Output>
        </Button>
        <Button>
          <Input>
            <ActionID>V3DK_ALT</ActionID>
          </Input>
          <Output>
            <ActionID>KB_Alt</ActionID>
          </Output>
        </Button>
        <Button>
          <Input>
            <ActionID>V3DK_SHIFT</ActionID>
          </Input>
          <Output>
            <ActionID>KB_Shift</ActionID>
          </Output>
        </Button>
        <Button>
          <Input>
            <ActionID>V3DK_CTRL</ActionID>
          </Input>
          <Output>
            <ActionID>KB_Ctrl</ActionID>
          </Output>
        </Button>
        <Button>
          <Input>
            <ActionID>V3DK_ROTATE</ActionID>
          </Input>
          <Output>
            <ActionID>Driver_ToggleTranslations</ActionID>
          </Output>
        </Button>
        <Button>
          <Input>
            <ActionID>V3DK_DOMINANT</ActionID>
          </Input>
          <Output>
            <ActionID>Driver_ToggleDominantFilter</ActionID>
          </Output>
        </Button>
        <Button>
          <Input>
            <ActionID>V3DK_PLUS</ActionID>
          </Input>
          <Output>
            <ActionID>Driver_IncreaseAppScale</ActionID>
          </Output>
        </Button>
        <Button>
          <Input>
            <ActionID>V3DK_MINUS</ActionID>
          </Input>
          <Output>
            <ActionID>Driver_DecreaseAppScale</ActionID>
          </Output>
        </Button>
        <Button>
          <Input>
            <ActionID>V3DK_USER</ActionID>
          </Input>
          <Output>
            <ActionID>Driver_ToggleRotations</ActionID>
          </Output>
        </Button>
      </ButtonBank>
    </Device>
    <Device>
      <Name>SpaceMouse Wireless</Name>
      <ID>ID_ProductID_C62E</ID>
      <CurrentButtonBank>Default</CurrentButtonBank>
      <ButtonBank Default="true">
        <Name>STR_DEFAULT_BUTTONBANK</Name>
        <ID>Default</ID>
        <Button>
          <Input>
            <ActionID>HIDButton_1</ActionID>
          </Input>
          <Output>
            <ActionID>HIDJoystick_1</ActionID>
          </Output>
        </Button>
        <Button>
          <Input>
            <ActionID>HIDButton_2</ActionID>
          </Input>
          <Output>
            <ActionID>HIDJoystick_2</ActionID>
          </Output>
        </Button>
      </ButtonBank>
    </Device>
  </Devices>
</AppCfg>


3. Launch the 3Dconnexion GUI (double click on the tray icon).

4. Launch Space Engine.

5. Alt+Tab to the 3Dconnexion GUI and hover your mouse over the tray icon. The tooltip should say that it's using the SpaceEngineJoy.xml profile.

6. Switch back to Space Engine and go to the control preferences. Clear out every axis and button binding in every section for both the SpaceMouse and SpaceMouse KMJ Emulation controllers. This is a bit tedious as you need to click each binding and then the "clear" button, but it makes things less confusing later.

7. Now bind the axes in the camera section using the SpaceMouse KMJ Emulation controller. I bound all of my axes reversed to the direction the camera moves so that the SpaceMouse acts as a pseudo direct-manipulation controller, but this is up to you.

8. To bind the buttons you need to use the SpaceMouse controller (the KMJ emulator only controls analog axes). I bound my buttons to prev/next velocity, but again, up to you.

9. Done!

Who is online

Users browsing this forum: No registered users and 1 guest