The current build while still incomplete in many areas, seems stable enough for public build so I released a new alpha. This includes the starting foundation for the keyboard and mouse input device as well as the new on screen keyboard. Both are still under development but I would like to hear feedback on them so far. Be sure to follow our new bug and feature request section for upcoming features and to report bugs and request your own features at https://inputmapper.com/support?view=bugs
Site Login
This Months Donations
$551.19
of $500.00 goal
Server, CDN, Network, Licensing
Development Budget
Developers Beer Fund
Recent:
Karl Scahill
$2.00
Frederick J Hogsett
$5.00
SiesMAN01
$2.00
André Philipi da Silva
$2.00
lookingglassties
$2.00
Number of donations
27Highest donation
$500.00Average donation
$20.61InputMapper 1.7.6277.18816a available for DL and testing
- Details
- Written by Wobbles
- Hits: 5509
Discuss this article
Log in to comment
I can and probibly will make a full KB, but to access those commands I am working on (or am currently white-boarding) an idea to have a separate OSK "page" where users can make their own commands that will be built via the macro interface to open up all the accessibility that the macros have.
Hi wobbles.. I probably missed that step. How do I disable it? Which version worked for you? I'm now back at 1.5 and it works
Update: I went back to the latest 1.5 version and it works fine again. I hope the updated inputmapper also becomes usable again.
Clonazepam wrote: Hi.
Just updated to Windows version 10.0.15063 and inputmapper 1.6.10 would no longer run properly. It basically appeared to run momentarily, as I could see the icon in the taskbar, and just about as quickly as it appeared, it disappeared and shut down.
I decided to download this 1.7.6277.18816 and it appears to be working fine. I did a quick test in Dark Souls 3 and seems well. This version is obviously incomplete and confusing, but so far so good.
How did you get it to work in DarkSouls3? I have 1.7.6277.18816 and my Dualshock4 doesn't work after I updated to creators. It worked fine with 1.6 prior to this windows update.. Now version 1.6 crashes as you described and 1.7 sees my dualshock but the controller doesn't work in game. It stays connected but when I press the buttons there is no response.
What profile settings do you use? What Output Driver/mapping UI template(if that matters)?
Grateful for your help
Same here! Just managed to get it to recognize the ds4 with the latest v1.7 however no matter the settings the controller doesnt work in games. I tried both wired as well as wireless... nothing.
Also v1.7 is much less intuitive compared to v1. 6...like if settings are missing, there is no save profile options button and have to set light bar and other settings again each time I launch the utility as well as other issues
Are there any other alternative apps we can try to make DS4 work while Inputmapper gets updated?
Also v1.7 is much less intuitive compared to v1. 6...like if settings are missing, there is no save profile options button and have to set light bar and other settings again each time I launch the utility as well as other issues
Are there any other alternative apps we can try to make DS4 work while Inputmapper gets updated?
Angelo wrote: Guys has anyone managed to get this to work with the latest Windows 10 creators update that was just released for manual download and will be releasing for auto download on april 11th? I tried all versions and while before the update they worked fine, with creators update it doesn't work anymore.
V 1.6 shuts down few seconds after launch
V 1.7 and 2.0 don't see the controller
V 1.6 crashes within a few seconds here too.
Got this from the crash in Event Viewer, they're identical each time it happens.
.NET Runtime
Application: InputMapper.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Exception
at InputMapper.EntryPoint.Main(System.String[])and
Application Error
Faulting application name: InputMapper.exe, version: 1.6.10.19991, time stamp: 0x57ffa2ee
Faulting module name: KERNELBASE.dll, version: 10.0.15063.0, time stamp: 0x461a0ff5
Exception code: 0xe0434352
Fault offset: 0x0000000000069e08
Faulting process ID: 0x2564
Faulting application start time: 0x01d2ae6ff69b3be7
Faulting application path: C:\Program Files (x86)\DSDCS\InputMapper\InputMapper.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: 501a4fe6-0ddc-42ce-a310-df384fb012e3
Faulting package full name:
Faulting package-relative application ID: Haven't tried v2, but when i tried v1.7 i was able to run it and it found my controller (using the official dongle) and no matter what "device" i chose i couldn't actually get it to be seen as an xinput controller in games.
Guys has anyone managed to get this to work with the latest Windows 10 creators update that was just released for manual download and will be releasing for auto download on april 11th? I tried all versions and while before the update they worked fine, with creators update it doesn't work anymore.
V 1.6 shuts down few seconds after launch
V 1.7 and 2.0 don't see the controller
V 1.6 shuts down few seconds after launch
V 1.7 and 2.0 don't see the controller
?
Hi.
Just updated to Windows version 10.0.15063 and inputmapper 1.6.10 would no longer run properly. It basically appeared to run momentarily, as I could see the icon in the taskbar, and just about as quickly as it appeared, it disappeared and shut down.
I decided to download this 1.7.6277.18816 and it appears to be working fine. I did a quick test in Dark Souls 3 and seems well. This version is obviously incomplete and confusing, but so far so good.
Just updated to Windows version 10.0.15063 and inputmapper 1.6.10 would no longer run properly. It basically appeared to run momentarily, as I could see the icon in the taskbar, and just about as quickly as it appeared, it disappeared and shut down.
I decided to download this 1.7.6277.18816 and it appears to be working fine. I did a quick test in Dark Souls 3 and seems well. This version is obviously incomplete and confusing, but so far so good.
Well I don't understand 1.7 I tried it I didnt really get it 
. But seriously thank you Wobbles and the rest of you (if there are any others) for such a great application as this. Had this not been a thing, I probably would not be able to play my Xbox One. My last actual XB1 controller died and now I have to use my PS4 controller through my PC using Inputmapper and use the Xbox App to stream my Xbox in order to play it at all. So thank you for enabling my Xbox One to still be used 
. But seriously thank you Wobbles and the rest of you (if there are any others) for such a great application as this. Had this not been a thing, I probably would not be able to play my Xbox One. My last actual XB1 controller died and now I have to use my PS4 controller through my PC using Inputmapper and use the Xbox App to stream my Xbox in order to play it at all. So thank you for enabling my Xbox One to still be used
So... A while back, I posted about me having issues with the lightbar just being blue in InputMapper 1.7, while still working fine in InputMapper 1.6 and 2.0. It turns out that the lightbar profiles were just set for me to be based on a value, but without a set control to monitor the value from, so it had nothing to set the lightbar to. After figuring that out and fixing it to take the value from the battery level, it works just fine again. Just thought I should probably mention that.
Previous post seemed to not go through. It seems that the installer won't run on my end over here, but the current 1.6.10 download is still fine. It gives the error
"Error Opening installation log file. Verify that the specified log file location exists and that you can write to it."
Something I'm missing?
"Error Opening installation log file. Verify that the specified log file location exists and that you can write to it."
Something I'm missing?