While The IM project has been far from dormant, the IM 1.5 branch has been. Not having seen an update in over a year, IM 1.5 will see a new set of updates in the coming weeks.
The reason IM 1.5 has remained untouched is because it was largely considered stable and there was no real need for it, thus allowing me to focus my efforts on IM 2.0. During development of IM 2, I have fine tuned many things that may be beneficial to IM 1.5 and until I have IM2 in a state where I am comfortable releasing it as a replacement for previous versions I might as well implement some of the newer code into the legacy app.
Things that the update will cover:
An entirely new hardware middle layer that should be more resource friendly and account for pesky Win10AU issues.
New user account control code to take advantage of the new communications path that IM2 is using. More stable and less bandwidth intensive (server side)
Better incorporation with our website including a tab to display news and updates.
Add some more macro features that are in the code, but not accessible in the UI.
These updates will be fairly time consuming so dont expect it in the next couple days. Once it is released and seems stable, I will give a few days for people to update then I will disable the legacy IM->website communication and move forward using only the new code. At this point users MUST be on the new version to be able to log into their premium accounts. The old way is just getting to resource intensive with all the users we now have.
An input protocol developed by microsoft in the mid 90's designed to attempt to standardise communication between input devices and games. Direct input has been mostly replaced by XInput for most gaming devices, but Direct input remains fully supported by Microsoft due to the fact that complex devices such as flight sticks and wheels require it due to the more complex and higher number of inputs.
The latest name of the controller mapping development project.
☐ Remove references to System.Threading, adapt to System.Windows.Threading
☐ Remove all uses of System.Windows.Forms
☑ Update Singleton/Mutex signature
☑ Remove interop calls that are causing false positives where IM is recognized as a game.
☑ Incorporate Windows UI Toast notifications (remove old popup window)
☑ Remove lingering bit of game detect API
☐ Update active app recognition
☑ Integrate website updates and feed into a page in the app
☑ Tweak currently connected controllers display
☐ Obliterate uses of Thread.Sleep()
☐ Use WMI for device notifications
☑ 3 stage connection process with redundancy for Windows 10 AU
☐ Non MAC reliant hardware interaction library
☐ UAC using IM 1.1 Cloud interface
☐ Missing macro functions added to UI
☑ Stick dead zones bug
☑ Fix profile save error when in use NEW!
Lighter, faster, smaller. Initial tests of some new code indicate that the same features are running with a noticeably smaller footprint. With a single controller connected IM is down from 1.2% CPU and 53mb Ram, to .4% CPU and 33mb Ram!
And thats just the start. IM 1.5.32 will feature some of the same tricks I use in IM 2 to minimize pooling to further reduce overhead!