• Possible bug-fix for controller re-connection issues after abrupt disconnect https://beta.inputmapper.com/forum/inputmapper-1-7/controller-disconnects-but-remains-connected/
• User avatar fixed
• Ads removed

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.

• Finally added the ViGEm installer into the 1.7 installer, so this package should be all-in-one now. (The ViGEm installer itself is still marked beta so please report installation related bugs)
• Some more translations added, more to come.
• Tweaked the IPC for future communication with StatScreen and possibly other apps.

Download available from https://beta.inputmapper.com/download/inputmapper-1-7-beta/

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.

Parts:
Screen – https://amzn.to/2WyZyKo
HDMI Cable – https://amzn.to/2WI4DF1
USB to Molex – https://amzn.to/2Kh5x4Y
Molex to SATA – https://amzn.to/2JaupZ8
Plastic Dividers – https://amzn.to/2XzqONv

I discuss what I know about the 403 errors, and try to further reiterate that beyond the annoying error warning (which can be disabled), they have zero impact on the use or functionality of InputMapper. I also talk in depth about how pretty much every aspect of the logging, support, ticketing and troubleshooting system are getting major overhauls in an attempt to more easily and quickly provide people with solutions to their issue and to do so in a way that is not reliant on my availability and schedule.

Huy guys, I have seen the uptick in reports of 403 errors over the past week or so. IM 1.6 as you know has not been updated in a couple years now and the production site it gets it’s live info from (https://InputMapper.com) has not had any changes in roughly a year, so in short we have no clue what could have caused this (yet) but are pretty confident it is not from our side. To further investigate, anybody experiencing 403 errors please post at https://beta.inputmapper.com/forum/general-chit-chat/403-errors-data-collection-thread/ your ISP (internet service provider), geographic location (as detailed as you care to provide but please no full addresses), OS (including build # found by typing “winver” into a run or find box), and frequency of error occurrence (every time, nearly every time, rare etc)

As a temporary fix, you can disable error prompts in 1.6 in the settings, or you can log into an account, so far tests indicate this only happens when no login info is provided.

NOTE: 403 errors have absolutely NOTHING to do with the operation of the controller or other issues you may be having, 403 error just means it had issues fetching news, donation data, updates, or user account info from our server.

UPDATE 5/16: Further investigation into this is being suspended indefinately for the following reasons;

• The issue has no bearing on operation of InputMapper
• The dialog generated by the error can be disabled in IM settings
• The issue seems to originate from the CDN due to increased security measures
• The modifications to 1.6 would be pointless with it nearing the end of it’s life and 1.7 not having this error

Working on making IM easier to use for the less savvy users by way of wizardry!

Whats up guys, no video this week for 2 reasons; been busy and running around a lot this week, and the work i’ve been doing on the IM project this week is suuuuper boring. None the less ill let you guys know what is going on.

Sorry for the bad audio in this one, I’ll get all these buttons and knobs figured out one of these days 😉

Plugin loading system has been re-worked to improve start-up performance and reduce chance of errors. New functionality coming to profiles in the form of “state modifiers” that will allow manipulation of multiple complex channels in input output states.