3 years 8 months ago - 3 years 8 months ago#1by Jimmy C
This is great software and mostly works very well for me. I'm just having issues with a couple of features not working at the moment.
Using the DS4 controller, I set one macro for the guide button to open the Steam overlay in-game. But after saving the macro and switching to the correct profile, the guide button doesn't seem to do anything at all once I'm in-game.
The other feature, which is the one I am most excited to use, is the AutoLaunch function. I assume this is supposed to function by launching a specific profile when a certain game executable is detected by InputMapper. Just as with the macro function though, it doesn't work at all for me right now. I tested it with Dark Souls and Rocket League so far, but in both cases InputMapper just stays on whatever profile it was already on when the game is launched.
Any help would be appreciated. I am using Windows 7 x64 Pro SP1.
You are not separating the press and release commands so the keys are being pressed in sequence rather than simultaneously. Use separate press and release commands and for good measure add a wait for release command in the middle to ensure it goes slow enough to be caught by steam.
3 years 8 months ago - 3 years 8 months ago#5by Jimmy C
Okay I made some progress. The overlay came up correctly in-game, but I ran into a more serious problem where even after completely exiting the InputMapper application, the Ctrl key remained active. So anytime I clicked on anything, my computer registered it as Ctrl+click. I had to do a hard shutdown of my computer to restore normal keyboard usage.
I assume I am still not setting it up correctly, but given that last issue I'm probably just going to skip using the macro function for now.
Regarding the AutoLaunch function - it would be disappointing if we were not able to use it for Steam games. Ideally I would like to use InputMapper as a replacement for Xpadder, which I've been using for a few years and has a similar feature called AutoProfile. But for now I'm happy just being able to use the DS4 as my primary gamepad.
3 years 8 months ago - 3 years 8 months ago#7by Jimmy C
Ah yeah I think I have it now. Thanks for sorting me out.
I've come up with a couple of other questions while working on this: When launching InputMapper, there are two other .exe files loaded along with the main executable: Updater.exe and DeviceDisplayObjectProvider.exe. Are these two files necessary to have InputMapper functioning correctly, or can they be closed?
Updater will close itself after making sure everything is in order. "DeviceDisplayObjectProvider.exe" is not ours, If there is an EXE in the IM program folder named as such I would be suspicious of a possible virus.
Actually the DeviceDisplayObjectProvider.exe isn't in the InputMapper folder so never mind that one. I think it was launched by a different process. Internet says it's part of .NET so I'm not too worried.
Regarding the Updater.exe - I think there's a bug where that executable will not close on its own if the IM program cannot access the servers. At one point I had three separate updater.exe process running simultaneously, because I had restarted IM several times and none of them ever closed automatically even after over an hour. I had to force close all of them.
I would suggest adding a function where if InputMapper does not have an internet connection, those updater.exe process would time out and close anyway, after a minute or so.