3Dconnexion Forum

That's the right one.

It's not the SDK that is the limitation, it is the driver. You have to find a driver that works with the old, discontinued serial devices. The SDK will work with anything. You will want to use the C/C++/MFC SDK, not the 3DxInput COM SDK.

If by period, you mean the rate at which the device sends data, you can not change that.

I'd rather fix the underlying problem.

[HKLM\SOFTWARE\3Dconnexion\3DxWare\]
"USBDataRate"="15"

Would set the rate to 15 events per second.

This should work now, but it will no longer work in future drivers.

Weeks.

I understand. This should work in the next major release. Keep on eye on 3DxLabs for a beta opportunity.

What key do you want to have the button press down? And why?

It may be possible to control these scripts with your 3D Mouse if AE has exposed viewing parameters in their scripting API.

2 byte packet 4, 0 turns off the LEDs. 4, 1 turns them on.

The USB SpaceExplorer may still work if your IT dept disabled writing out on the USB ports. That keeps you from writing files onto USB sticks and taking them home--which is what they are trying to prevent. Some things like the LEDs wouldn't work.

No, I'm afraid serial ports went out with the last century (well almost). The SpaceExplorer serial was never supported on Windows, only Unix. You need to try to trade those in for USB devices if you want to run on Windows.

Isn't there a better place to put that code? OnInitDialog or something that gets called after the whole create process is done?

That code looks reasonable. I'd make sure the hwnd you are sending exists. You probably want to make a scg file for your app, but it isn't necessary. Take a look at the driver's log file to see if it is complaining about your connection request. Turn on the log file in the 3DxWare GUI. It is saved i...

Unfortunately, my card is only good for DX9. I may have to upgrade.
All 3Dx software developers follow this forum regularly. I am one of them.