Login

This Months Donations

$504.85
of $500.00 goal
Server, CDN, Network, Licensing
Development Budget
Developers Beer Fund

Number of donations
142
Highest donation
$50.00
Average donation
$3.99

If the spike in donations are any indication, the IM 1.6 launch has been very well received. It has had a few bugs and set backs but as we get into the 1.6.5 patches, things are starting to smooth out and I am turning my attention back to adding features and fulfilling requests.

Trying to find the right balance in the new tool-bar between information overload and too little information has been challenging. I think the majority of people don't mind the more condensed less specific display that omitted things such as latency (which we will discuss further in a minute) and battery percentage. But there was a little bit of push back from people who wanted to know their exact battery percentage and exact latency at all times, even though these numbers are superfluous and even a little fudged. Despite this I think the best thing for the UI of the program is to keep it simple and omit data that isn't necessarily needed to the user.

The latency that people have been focused on lately is something that I half regret ever even implementing because it forces people to focus too much on fractions of a millisecond. The latency that is displayed isn't even a true latency. True "latency" is determines by the amount of time it takes for the controller to register an input and for the software layer to spit it out to the game, well there is no software way to measure most of that info such as the time that the packet spends in the hardware and "in the air". What we do instead is take the time it takes to request a new packet from the controller to the time we receive one and it is processed in IM. the number here is largely affected by factors such as PC load and we try to account for this through some arbitrary math, but its nowhere near perfect. This number was only ever meant to indicate large factor issues that cause large swings in the number, such as slow communication caused by interference or inadequate dongle or driver, the nitpicking over a millisecond here and a millisecond there was never the intention and the margin of error exceeds the 1 or 2 ms concern people have anyway.

2016 09 30 8 36 35The compromise for me was to indicate some sense of latency through the use of the signal strength meter. It gives a rough indication of latency and shows enough info to indicate if there is something wrong or if things are going great. But still there was desire for a actual numeric readout (despite its aforementioned inaccuracy), so a further compromise was reached where there is (or will be in 1.6.6) a balloon pop up when you hover your mouse over the controller that shows "exact" numbers.

The battery level indicator faces many of the same issues is the latency meter in that people put way too much confidence in the number being an exact representation of the battery level. REAL battery level indicators like you would find on your laptop battery take specific hardware and "smart" batteries that just aren't present in the DS4. The DS4 simply guesses the battery level based on its voltage, well the voltage can vary depending on the age of the battery, load placed on it, temperature, humidity, etc etc. Without a "smart" battery the number we use here is just a best guess as well so the desire for specific exact percentages here is pointless. There is a reason why the Play Station 4 only shows a 3 or 4 stage battery indicator. For that reason I again compromised with a less detailed icon to show enough money to give the general idea, but not so much that people nitpick and say things like "my battery only says 80% when I unplug it".

All and all though it seems that the changes have been well received and our donations have definitely seen a spike with this month being the first month in a while where I expect us to break our goal! I thank you for all your support, my liver thanks you, and my local bartenders thank you!

Log in to comment


Wobbles's Avatar
Wobbles replied the topic: #1 5 months 3 weeks ago

John wrote: Sad to say I also had come to rely on the latency graph and even sadder to read it's not coming back.
It was useful when connecting to bluetooth to see what range and angle worked well. Easy to see at a glance if you notice a little delay, to know if it's your controller connection rather than CPU throttle or the likes. Also useful if you have USB ports that sync at different timings.
Recognized it consumed some CPU cycles, always seemed like a worthwhile trade off to me.

Regardless of the theme or visual style, I don't understand removing functionality entirely when it could just be something optional. It's not like it was broken.

I can only agree here and say I really preferred my controller info large and readable at a glance rather than tucked away, almost no reason to have the UI up at all now for me.

I don't mean to be overly negative here, I still like the program I'm just really sad to see functionality removed.


Again.... It was not real latency, it had no bearing on anything, and you can still see the signal strength. I regret ever implementing it because people have completely abused and misunderstood it. For all you guys know it could have just been attached to a number randomizer and you guys would still be upset that I got rid of it. Why is it nobody believe the guy that wrote the thing when he says it was pointless from the get go and did not do what people thought it did...
John's Avatar
John replied the topic: #2 5 months 3 weeks ago
Sad to say I also had come to rely on the latency graph and even sadder to read it's not coming back.
It was useful when connecting to bluetooth to see what range and angle worked well. Easy to see at a glance if you notice a little delay, to know if it's your controller connection rather than CPU throttle or the likes. Also useful if you have USB ports that sync at different timings.
Recognized it consumed some CPU cycles, always seemed like a worthwhile trade off to me.

Regardless of the theme or visual style, I don't understand removing functionality entirely when it could just be something optional. It's not like it was broken.

I can only agree here and say I really preferred my controller info large and readable at a glance rather than tucked away, almost no reason to have the UI up at all now for me.

I don't mean to be overly negative here, I still like the program I'm just really sad to see functionality removed.
Peeensseli's Avatar
Peeensseli replied the topic: #3 5 months 3 weeks ago

Poofu wrote:

Wobbles wrote: The application will still alert you if you are having latency issues. The latency graph simply is NOT coming back, there was zero use to it or the resources it consumed.

ok, but how about a separate tab where the controller info is in a larger more readable and multi controller friendly area.


I kinda miss more info too.


I just updated to the newest version 1.6.9 and I got back this annoying thing when shutting down/restarting my PC. I get this message saying: "This app is preventing shutdown." and the app is InputMapper.
I once had it with earlier versions of 1.6 but it got fixed on newer versions.
It doesn't appear when I don't have InputMapper running, only when I have it running and trying to shutdown/restart.
Wobbles's Avatar
Wobbles replied the topic: #4 5 months 3 weeks ago
My focus right now is on the macro UI. I'm not ruling anything out, but I think the UI is going to continue in the direction it is now. I got far more complaints during IM 1.5 about how the UI didn't conform to the look and feel of other windows apps than I have from people who miss the latency graph.

I simply cannot please anybody, and its absurd for any developer to try. I'm sorry you end up on the disappointed side of this see-saw as I recognize you as one of our long tem users from back when we started, but the benefits of the new look far outweigh the things that were lost.
Poofu's Avatar
Poofu replied the topic: #5 5 months 3 weeks ago

Wobbles wrote: The application will still alert you if you are having latency issues. The latency graph simply is NOT coming back, there was zero use to it or the resources it consumed.

ok, but how about a separate tab where the controller info is in a larger more readable and multi controller friendly area.
Wobbles's Avatar
Wobbles replied the topic: #6 5 months 3 weeks ago
The application will still alert you if you are having latency issues. The latency graph simply is NOT coming back, there was zero use to it or the resources it consumed.
Poofu's Avatar
Poofu replied the topic: #7 5 months 3 weeks ago
Both me and my friends who updated all think that this new condensed look is rubbish compared to the old look. I get it some people like it but could you have a toggle, i like to see if i'm having latency issues.
Bruno's Avatar
Bruno replied the topic: #8 5 months 3 weeks ago
hello Wobbles please could convert the taskbar icon for a dark color on win 7? sorry for my English
Wobbles's Avatar
Wobbles replied the topic: #9 5 months 3 weeks ago
Working on the new "Macro Studio" that will be part of IM 1.6, developing it as a independent library so it can easily be brought into IM 2.0 as well.
Full drag and drop support, Finally a record option that will not only record keystrokes but mouse and controller movement and inputs. hopefully what you all will agree is a much cleaner UI
Marcus's Avatar
Marcus replied the topic: #10 5 months 3 weeks ago
I can wait. :)
Wobbles's Avatar
Wobbles replied the topic: #11 5 months 3 weeks ago
customization options like that are on the list, but they aren't that high on it right now. right now I need to focus on redoing the macros.
Marcus's Avatar
Marcus replied the topic: #12 5 months 3 weeks ago
I saw that, but an on-the-fly implementation (presumably with color inversion depending on hidden pool vs taskbar) would not be helpful to me. Your worst case scenario, a custom option, is my best case scenario. ;)
Wobbles's Avatar
Wobbles replied the topic: #13 5 months 3 weeks ago

Wobbles wrote: Ill have to look into that, I don't know if an application can detect if its icon is in the hidden section and give it a different icon based on the background color. Worst case scenario it may have to be a user selectable thing.

Marcus's Avatar
Marcus replied the topic: #14 5 months 3 weeks ago
Can you consider a custom icon option like I mentioned? IMO it doesn't look good in Windows 10 either...
Wobbles's Avatar
Wobbles replied the topic: #15 5 months 3 weeks ago
It was switched with windows 8/10 in mind
Marcus's Avatar
Marcus replied the topic: #16 5 months 3 weeks ago
Here is my tray icon in Windows 7:



It makes me want to revert to 1.5. Please allow the program to scan the program dir at run time so that if it finds a valid custom tray.ico it will use it instead. This is really ugly.
Chase's Avatar
Chase replied the topic: #17 5 months 3 weeks ago
So, before when clicking on the input mapper icon in my toolbar, it brought up the interface and i could use it from there. Is this no longer an option? Do i have to use the icon in the tray now? If so i dont really have a use for the app in my toolbar. Love the 1.6 tho!! Keep up the good work.
Khronikos's Avatar
Khronikos replied the topic: #18 5 months 3 weeks ago
Yeah, it is not a big deal at all.
Wobbles's Avatar
Wobbles replied the topic: #19 5 months 3 weeks ago
Ill have to look into that, I don't know if an application can detect if its icon is in the hidden section and give it a different icon based on the background color. Worst case scenario it may have to be a user selectable thing.
Khronikos's Avatar
Khronikos replied the topic: #20 5 months 3 weeks ago


Yes, your icon in the tray is white, and I can drag that to the taskbar notification area. But I don't use the white icon. I use your app black controller icon on the taskbar so I can click on and off when I want to. Your icon in the tray is white, and the tray is white too.
Wobbles's Avatar
Wobbles replied the topic: #21 5 months 3 weeks ago

Khronikos wrote: Just a normal aero custom theme with slideshow is all. Nothing really all that crazy.

My notification area after clicking on the arrow on the right side has always been white. Even when I switch to classic mode or any other theme it is white. I can hover over IM but not see it in the tray.


Can you post a SS so I can get an idea, this is what I am used to Win7 looking like:
Khronikos's Avatar
Khronikos replied the topic: #22 5 months 3 weeks ago
BTW the new look is great!
Khronikos's Avatar
Khronikos replied the topic: #23 5 months 3 weeks ago
Just a normal aero custom theme with slideshow is all. Nothing really all that crazy.

My notification area after clicking on the arrow on the right side has always been white. Even when I switch to classic mode or any other theme it is white. I can hover over IM but not see it in the tray.
Wobbles's Avatar
Wobbles replied the topic: #24 5 months 3 weeks ago
I thought even windows 7 had reverted to white icons, are you using a custom theme?
Khronikos's Avatar
Khronikos replied the topic: #25 5 months 3 weeks ago
Taskbar icon is dark grey and okay. The tray icon is totally white and the tray is white as well in Win 7.