3Dconnexion Forum

Hi kit, 3DxInput (TDxInput) is a COM server. There are no headers. The best thing to look at is the example you already downloaded, and the "Windows COM SDK Documentation" from the same download page where you got the example. Essentially, you connect to the COM server, sign up for events,...

Hi kit, 3DxInput (TDxInput) is a COM server. There are no headers. The best thing to look at is the example you already downloaded, and the "Windows COM SDK Documentation" from the same download page where you got the example. Essentially, you connect to the COM server, sign up for events,...

Before you make any of the Si* calls, you can check whether the 3DxWare driver is running by looking for its window:

FindWindow("SpaceWare Driver Class", NULL);

If this returns NULL, the driver isn't running. Don't call any Si* functions.

Just to be clear, these "old" demos show a different way of interfacing to the driver than the 3DxInput COM API shown in the "current" SDK (on the web site). These demos show how to use a 3Dx proprietary API that works well with Win32 and MFC programs. Still the old API works and...

This topic refers to some Java work being done.

Oh, the format is definitely going to change. In the next major release in fact.

In the mean time, you can copy your .scg file into the profiles/default directory. You can find the 3DxWare install dir from the registry (HKLM...3DxWare/Home Directory)

Hello kari, The "Button 1-6" strings come from the config file. To change them, create a config file for your application, find the strings and change them with notepad. You can make a copy of any.scg in (by default) c:/program files/3dconnexion/3dconnexion 3dxsoftware/3dxware/en_us/profil...

Hi waiwai128bebe,

Do you have any error messages listed in your 3DxWare.log file? It should be written to %appdata%/3dconnexion/3dxware.

Jim
3Dx Software Development

In the short run, you may be able to use the driver mentioned in this thread: http://www.3dconnexion.com/forum/viewtopic.php?t=336 It is NOT in any way supported by 3Dconnexion, but some people have been able to use it successfully. It can be quite a task to get it to work. The best approach is to c...

???

It appears that you are interfering with some unwritten protocol that UG expects. Perhaps you can try forwarding all the events you receive to the UG window.

You need to break into the input loop. Capture the events as they arrive, before they are thrown away by the existing event loop.

You have a couple of directions depending on the structure of the app. If the app makes use of COM, it may be easiest to use our 3DxInput COM API. If it is a Win32 or MFC app, you can use our "old SDK" (from the download...archive section of the web page). If it is a game, you may find tha...

Your best bet is to use the old SDK (or one of the MS APIs like DirectInput, RawInput, HID).

The old SDK mechanisms will always be supported. All new devices will be supported with it.

Not that I know of.

The data is not encoded from the device. It must be the OSX device driver that is encoding it. See if they have a raw data mode.