Steam Community :: ControlMyJoystick

ControlMyJoystick

All Discussions Screenshots Artwork Broadcasts Videos News Guides Reviews

ControlMyJoystick

3 in Group Chat

Use your voice, joystick, smartphone or optional 3Dconnexion controller to send commands to your game as joystick, keyboard and mouse input. No programming knowledge required!

Visit the Store Page

Most popular community and official content for the past week. (?)

ControlMyJoystick is leaving Steam soon

Jan 7

tl;dr ControlMyJoystick will no longer available for sale on Steam. Users who previously purchased it can still run it in their library without limitations. Non-Steam version is still available on the website and owners of the Steam version can request a non-Steam version product key in Discord. All support will move to Discord. No further development is planned.

ControlMyJoystick Website[tetherscript.com]
ControlMyJoystick Discord Invite[tetherscript.com]

How we got here

CMJ launched back in 2014-ish and was offered on Steam in 2018 in addition to our CMJ website. Not much has changed dev-wise since 2020 or so. A stream-of-consciousness mental dump:

CMJ will be still be available for trial or purchase on the CMJ website.
CMJ requires a re-write from Delphi 32-bit into WinUI/.Net 64-bit so that the display scaling artifacts can be fixed.
CMJ comes with mouse, keyboard and joystick drivers that I created especially for it. These are user-mode drivers, which means that if they have problems or crash, they don't take down your system as a kernel-mode driver would. These drivers are HID-emulation drivers. Kind of old-school but they worked for a long time.
The drivers are the biggest issue going forward. Microsoft is steadily locking down their driver ecosystem, even user-mode drivers. I would expect by Windows 12 they won't allow installation of these drivers at all. Instead, they may require the use of Microsoft's gaming API (DirectX-ish) to emulate HID devices with no drivers required. Unfortunately, game devs could control what kind of emulation to allow in their games. Good for security I suppose, but Yuck.
CMJ drivers were intended to be accepted by games as just regular keyboard, mouse and joystick input and that worked usually well, especially in games where the dev's didn't want that. Elite:Dangerous was incredible with it when using 3dconnexion controllers. And other stuff requiring Z-axis movement.
But as a side-effect of this driver-level emulation, coders were making bots for games. I don't like that, especially since my certificate is used to sign the drivers.
For a brief time, I had a HIDVDK (HID Virtual Developer Kit) where the drivers were available for sale unsigned, so customers would need to get their own certificate. But, no one was interested in that. They wanted signed drivers. So I no longer sell the HIDVDK.
The drivers were coded in VS 2013 and can't be compiled in anything newer. I tried, many times. Microsoft doesn't make the libraries available for newer VS versions.
The 3dconnexion drivers and SDK are brutally bad. They change core calls to their API for no apparent reason, and users have varying versions of their drivers out there. So it's tough to develop CMJ while accessing that API. Right now, it only works with older versions of the 3dconnexion drivers. I'm not going to update the code for the newer drivers.
My lightbulb-moment after some years of dealing with that SDK is that I should not use the SDK. The only thing that it gives you over just reading the HID data stream (SDK not needed) from the device is you can turn on/off the controller lights. And maybe change the text displayed on an Enterprise controller.. That's it. I should have just read the HID stream instead.
But each 3dconnexion controller model puts it's axis and button data into different places in the HID stream. So you would need a smart axis/button calibration util in to figure out exactly what byte does what in the data stream. Doable, for sure. Although this is exactly what is needed to discover and calibrate any other HID device like a joystick. For the time I spent dealing with the SDK, I could have written the best HID controller parser of all time.
Microsoft's voice recognition is in flux, especially with AI agents on the horizon.
No more development is planned for ControlMyJoystick.

The next killer-app for gaming will be AI agents that are explicitly trained on a single game and knows everything about it. It would use the Microsoft API/drivers to send commands directly to games. That would be very, very cool.

When you think about it, there's probably opportunity for gamers to train a game-specific AI Agent and then license it for use in some manner.

In Elite:Dangerous it would be fantastic to say 'Hey AIAgentName, I'm going to watch Netflix for a bit, so find a good planet, enter orbit land at an interesting point of interest and launch the rover. And then remind me to saddle up." OMG.

Hmmm...maybe I could make that.

Russ
Developer of ControlMyJoystick

ControlMyJoystick

If using 3dconnexxion devices, use this driver version

Use the older version of the DxWare 64-bit drivers at https://3dconnexion.com/us/archived-drivers/?fwp_drivers_os=windows-10-64bit Drivers from 10.6.4 up to 10.6.8 work, but newer drivers don't because 3dconnexion made major changes to the SDK without letting anyone know about it. In the next version of ControlMyJoystick, we'll just bypass the drivers entirely and read the HID values directly....

RussDev

Nov 16, 2023 @ 9:00am

General Discussions

5.3.45.89 Released

Jan 7, 2020

5.3.45.89 Final January 6, 2020

Release Notes

1) Fixed crash you get when you press a joystick button if you don't have a 3dConnexion device installed.
2) Now when you click on the Curve Presets button, it no longer resets the curve.
3) Now the keyboard driver is reset on CMJ startup.
4) Updated support for most recent 3dconnexion devices.
5) Added extra delay on CMJ shutdown so that it has more time to release HID devices and speech recognition interfaces.
6) Fixed crash encountered if you click on the registration splash screen Close button.
7) Binding an output axis when a voice prefix has been set now works.

ControlMyJoystick

Version 5.1.65.80 Released!

May 18, 2019

5.1.65.80 Final April 12, 2019

This is by far the largest feature update since ControlMyJoystick was launched around five years ago. Where to start?

IMPORTANT
- Make sure you export your profiles as .cmj files from your earlier version of ControlMyJoystick. In more recent versions, this was done automatically on shutdown. You should find them at: C:\Users\YourName\Documents\ControlMyJoystick. You will need to import these into ControlMyJoystick.
- Update your 3DxWare10 version to 10.5.5 or higher if you are using a DxWare device.

LOTS OF NEW FEATURES
- You can now accept input from one or more physical joystick devices and apply the usual smoothing and curves. This is in addition to the existing DxWare device input.
- You can now map the various buttons and axis from physical joystick and DxWare inputs to the output virtual joystick driver axis and buttons.
- Added a VIRTUAL KEYBOARD DRIVER, which is way more reliable then the old SendInput method. You can still use SendInput, but after you use the driver, you won't want to. This emulates a physical keyboard and it can do tons of stuff. Note: We don't read keystrokes from the keyboard driver. We only send data to the driver so that it can appear as physical keystrokes.
- Added a VIRTUAL MOUSE DRIVER, which is also more reliable than the old SendInput methods.
- Refined how you bind output axis and made it more likely to be 'seen' by games.
- Greatly reduced CPU usage.

Note: For most output to be received by a target app(like a game), you need to set a profile target and enable it. Right-click on the profile picklist for this option.
Note: There is an import function to import older .cmj profiles. If you are using .cmjson files, these will upgraded automatically when you first select them in the profile picklist.
Note: We'll be updating the knowledge base soon.

USER INTERFACE
- You will notice new Input and Output tabs. In the Input tabs you set which DxWare or physical joystick devices you will accept input from. In the Output tab, you will map those inputs to the output virtual joystick driver.
- Axis and button gauges for input devices now show curve alignment and the raw and curved values.
- Added a statusbar at the bottom of the screen to show whether or not profile targeting is enabled, the delay, and the target.
- Now if you add the three characters [!] at the end of a macro name, only one instance of this macro can run concurrently. This is useful for longer macros that you don't want to accidentally trigger again before it has finished running.
- Added keyboard driver editor dialog buttons ('Edit...') to the curve digital joystick dialog so now it easier to compose scroll commands.
- Added on profile targets enabled switch to the statusbar so you no longer have to go to the menu to enable/disable targeting. Removed the ability to enabled/disable this from the menus. It is not profile-specific, so it didn't really belong in the profile menu. This setting is used for all profiles.
- You can now toggle the enabled/disabled state of macros, triggers and scripts by selecting a row in the grid and pressing the spacebar on the keyboard.
- Tweaked the profile target functionality so now you can set the delay that occurs immediately after the target app is activated. This delay is set in the profile target edit window, and is used to give the target window enough time to become active. A small and simple window like Notepad may only take 10ms, but a larger running game window may take 50ms or more before it is ready to accept commands from CMJ.
- Now if you hold down the keyboard shift key when starting ControlMyJoystick, it will launch with profile targets, voice and DxWare disabled as well as reset the layout to 1024x720 on the main monitor.

TRIGGERS
- You can now have cross-device button combinations as a trigger. Think pressing button one on this joystick, button two on that joystick, and the Fit button on a DxWare controller to trigger a macro. We're sure someone will find a good use for this.
- You can now receive triggers from physical joystick devices as well as DxWare devices. It is very customizable - you can literally do a device button combo by pressing buttons across different input devices if you wanted to.

SCRIPTS
- Added a 'Reset Drivers' item.
- Nested scripts now work properly.
- In the new Keyboard (Driver) option, all DOWN_UP, DOWN and UP keystrokes are done in the same dialog. You can also enter text and press the 'Test' button to send it to the targeted app.

CURVES
- You can now apply smoothing and curves to input joysticks.
- In the Digital Joystick option, you can now specify one or more keystrokes, so it should be possible to do something like CTRL-F7 or something like that instead of a single key. To experiment with the keystrokes needed for your game, try launching the keystroke editor from the Output/Keyboard tab and experiment there.
- You can now use the Prev and Next buttons to change the current axis instead of having to close the curve dialog.
- There is now the concept of curve alignment when editing a joystick curve. Axis curves that spring back to center should be set to Center alignment. Use Left or right alignment for joystick slider and dials. Yes, you can now curve a throttle axis!
- There are now more curve presets to choose from.
- You can now run a script triggered by axis movement. It's kind of like Digital WASD, but with macros. See the new 'Tutorial 16 - Digital Controller Axis Triggers' for a demo.

SECURITY
- We never have and never will use 'hooks' to read mouse and keyboard output. We don't monitor your keyboard. Period.
- Our drivers or fully cross-signed, legitimate drivers that we have developed in-house for use with ControlMyJoystick. No reduction of Windows security is required to install these drivers.
- Because the keyboard driver is so flexible, be careful when running scripts that you gotten from someone else. You can literally launch a command line or web browser and type stuff in and do pretty well anything you can do with a physical keyboard. So, never run an unknown without reviewing it first.

WHAT IT DOESN'T HAVE
- ControlMyJoystick does not have a way to read memory or screen pixels, or relay axis and button data from a third party app to the ControlMyJoystick virtual drivers. This kind of functionality is typically used by cheat-bots and we do not condone this use, or provide a way to do so.

VIRTUAL JOYSTICK DRIVER
- You can view the driver output in the Output/Joystick tab.
- Dial, Slider, Wheel and Hat Switches are now supported.
- You can now map input axis and buttons to the output joystick driver axis and buttons. By default it is mapped to DxWare, but if you double-click on an axis you can remap it to something else.

VIRTUAL MOUSE DRIVER
- You can set absolute desktop cursor positions. Try this in the Output/Mouse tab. You can enter the coordinates and see where the mouse goes. You can also use a voice command to dump the current x,y coordinates to the mouse log so that you can use the coords later in a script (think navigating menus).
- You can no longer set relative mouse positions. You must use absolute. Relative really wasn't too useful as you could never set where to start the relative movement.
- This driver is far more reliable than the old SendInput message we used in previous versions.

VIRTUAL KEYBOARD DRIVER
- This driver is far more reliable than the old SendInput message we used in previous versions. We still haven't seen it fail to press a key in an app that could be pressed with a physical keyboard. SendInput failed quite often, depending on how the game devs restricted external inputs.
- If you send a key DN (down) to the driver, you better follow it up with an UP for the same key. If you don't, the key will remain stuck, just like someone is still pressing the key on a physical keyboard. You can kill this stuck key by shutting down ControlMyJoystick. Best to review your Alt-Tab and Alt-F4 skills for killing ControlMyJoystick should this happen. Wear it as a badge of experimental honor.

JOYSTICK BUTTONS
- There used to be a list of output joystick buttons that you assigned names to. This has been removed as it is no longer required.

BUG FIXES
- Removed the particular theme that could cause a crash when selected.
- Now when you double-click on the upper-right-hand corner 'x' to shut down the app, it doesn't crash.
- Nested scripts now work.
- Fixed bug when some dialogs would appear underneath the main window when Stay On Top was enabled, making it look like the app had crashed.
- Fixed odd placement and scaling of dialogs.
- Reduced the number of words stored in the speech recognition dictionary, which will make recognition a bit more accurate.
- Fixed bug that could occur when bringing up the Profile Target dialog if there was an app running with a title of greater than 256 chars in length.
- Removed duplicates from Profile Target dialog.
- Fixed bug that could prevent a script commands MACRO_SYNC and MACRO_ASYNC from running properly.
- Fixed a bug where a keystrokes could be sent to CMJ if the target app is not available.
- Fixed a bug where sometimes macro's would appear in the macros activity list even if they were no longer running.
- Fixed a bug where if you duplicated a macro, it would not select the newly duplicated macro.
- Reduced the likelyhood of a crash due to switching themes too fast.
- Increased the volume of the beep.wav file.
- Fixed duplicate cmjson file created when renaming a profile then editing and saving profile notes.
- Tweaked how mouse movements and button presses works in scripts. See the new 'Tutorial 15 - Draw an X in Microsoft Paint' for a demo.
- Many other small fixes. A bunch, really.

ControlMyJoystick

CMJ missing system voice commands? Input curves not saving or mirroring? v5.5.78.50

Title says it all, but I've run through the tutorials and they show a host of system voice commands my version does not seem to have: https://i.imgur.com/mXOMSu4.png And on top of that, the output curves aren't saving when I change them (though editing the JSON file directly seems to work), and the mirror function doesn't work at all, it does nothing. Is there an issue with the latest build? Or what's the problem with mine? Edit: I managed to do what I want without CMJ. What was necessary was logging ...

no fun

Jan 7, 2024 @ 6:41am

General Discussions

Spacemouse WASD setup

I am trying to setup my spacemouse for WASD keys and i am running into issues. If i push a direction on the spacemouse, it should press a key and release it when the joystick returns to center, but for some reason, mine keeps repeating and wont stop until i kill the program. Anybody have any experience or knowledge on this? Thanks in advance!...

ockert.john

Jul 5, 2021 @ 10:02pm

General Discussions

Some of the examples aren't working for me.

I'd like to have my Space Mouse work as the WASD keys, but the example given in the CMJ software doesn't work. More info gladly given if needed.

Gamyr

Jan 21, 2022 @ 8:42am

General Discussions

Curve groups for 3dconnexion

I am trying to setup CMJ with my SpaceMouse Enterprise. For my live I cannot get the app to bring up the right click menu when I right click a curve group with 3dconnexion selected as an input device. This behavior has be conirmed on two computers. Right clicking on curve groups when other input devices are selected shows the right click menu. I guess I could work directly with the xml files but I'd prefer to be able to copy curve groups directly in the app. What am doing wrong?...

DNACHIP

Jun 22, 2024 @ 3:46am

General Discussions

See More Content

No more content. So sad.

You can help: share a screenshot, make a video, or start a new discussion!

Returning to where you were last on this page...

Cancel