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.
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.
Ads have been removed from the latest version of 1.7, still working on making a system that will allow for 1.6 to be ad free.
Been spending a lot of time this week going through some of people biggest complaints with IM and coming up with plans to address them, and among the two are the ads (though I honestly don't get the big complaint), and the ease of use. So since ads are gone it's time to focus on the ease of use, and one of the biggest changes to that will be the mapping UI. For strongly typed profiles (meaning it is built for a specific input device type and a specific output device type) gone will be the old "mapping overrides" list where you have to select from drop downs and lists. Instead will be a UI much like what IM and our branch of DS4Windows had in the past where you select a control by clicking it and easily choose what you want it to map to.
InputMapper will be going ad free for everyone in the very near future. No account needed, just no more ads.
I am still working on adding cloud functionality so users can share and download profiles that they create for games. Sharing a profile on the site will be behind the donation barrier, still only $2 and all current donors will have the ability automatically. This is for 2 main reasons; first, donation status is the hands down best bot protection for allowing upload of content to the site. Odds are if you have given the site money, you are not a spam bot. Second, the load on the site from within the application will mostly be for cloud purposes so it seems fitting that the cost associated be tied to the same functionality that creates it. The manual download of profiles from the site will likely be free for everyone since using the site helps generate revenue through the ad's on the site.
1.6 and earlier will not be as easy to remove ads from, but I can make it so that any attempt to log in with even a fake account will be met with a donor status credentials within the application.
This has almost nothing to do with InputMapper, but for those of you that like having a flashy looking PC Case, you may enjoy this!
Been working on an in-case PC stat monitor, the hardware was simple enough and the list of parts I used are at the bottom of the article, but what is more important is the software to make it hands off and hassle free. The most annoying thing that could happen to me with a tiny screen in my case is if windows try to open on it, or if lose track of my mouse on it, or even just going through the trouble of making the hardware look nice just to have a generic copy of NZXT's CAM running on it. So I set out to write my own software, and so far I'm pretty happy with the results.