Currently the most widely used version of InputMapper considered feature complete, however is being phased out in favor of InputMapper 1.7 which is more modern and stable and has less issues with Windows 10 and exclusive mode.
A pretty serious memory leak bug has been discovered in IM 1.7. More accurately it's a buffer overflow issue where some mid- range or heavily taxed systems are generating output device reports faster than the output driver can process them. This in itself isn't an issue as devices do this all the time and is why DPC, interrupts and buffers exist. But the issue is that the output buffer isnt being corrected when it starts to back up which over time can become noticeable in the form of lag and audio glitches or other hardware device stuttering. This is a top priority right now as I modify the plugin to handle clearing a buffer when it starts to overflow.
The plugin system is getting some tweaks in the way that InputMapper manages the plugin instances themselves. Currently they are uncontained and pretty much after initialization IM has no real control or interaction with them whatsoever. I am going to start to tweak this and have the plugins exist within wrappers so they can have better access to settings and be more easily managed as-well as enabled or disabled as needed.
The Dualshock 4 plugin has been renamed to the Playstation 4 controller plugin and has settings to add 3rd party PS4 controllers to the detection list.
Documentation is going to get a bump soon as I focus on including documentation into the application itself as well as creating tutorials for common issues and setups.
Updates to the installer and the website have been among this weeks top accomplishments. Many bugs have been removed from the installer to make it more streamlined especially with upgrading. The site has a new downloads section that is still in progress that will keep a running change-log as well as ability to download older versions.
InputMapper now has the ability to notify users of newer versions, so make sure to update to that so you dont miss any important changes.
First connected devices will now get a popup wizard to walk through the basics of getting the profile created and a output driver selected.
Apparently something broke during the upgrade and everything is past the point of no return. The hosting company "escalated the issue to a higher tier", so I'm sure their top janitor is on the case....— 🎮 InputMapper (@InputMapper) November 1, 2019
We did finally get things sorted and are now running smoothly and on a up-to-date CentOS install again. There are also some font end changes coming to the site, mostly focused at the downloads section. I am in the middle of writing a downloads plugin that will allow version histories so if a important feature breaks users can roll back to a previous version.
It's been teased for a couple weeks, but I think it is ready for release now, the new UI is now available for testing.
More things have been updated such as adding the option to switch between the advanced mapping view and the mapping UI (on properly configured devices). I have also swapped the data rate graph out for a less CPU intensive one. many other various performance changes have been made as well as some bug fixes for the Dualshock 4.
I have been spending a LOT of time on polishing as many rough edges as possible. There is still work to be done for sure, but the effort is already easily visible.
One of the toughest things people had a hard time coming to grips with in InputMapper 1.7 vs previous versions and even DS4Windows, was the way the mappings looked as a result of the generic nature of devices in IM 1.6 due to the wide variety of devices supported. The idea of using "overrides" in place of a straightforward this-to-that approach made people apprehensive. Some because they didn't understand the reasons behind doing it this way, others because it was different; and different is bad. Well I am happy to say that after much blood, sweat, tears and booze; I have finally developed a way to bring the UI point and click style of mapping back to InputMapper 1.7, and it's better than ever.
Among other things that have been polished are the settings themselves. Fonts and layouts have been made more appealing and descriptions have been added to most settings to help those that are unfamiliar. The profiles tab has been re-worked to move the profile list into the tab header making for a more open main window (helpful for the new UI based mapping). And a new setting that hides advanced settings from those just looking for a basic experience has been added.