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.

No word on the new version of ViGEm as of yet, so I started testing the beta builds of the installer without it, ViGEm will have to continue to be installed making use of the power shell commands for the plugin to work. Also new Mic is here so audio should be greatly improved.

ViGEm is changing their driver to install from an executable rather than from powershell commands, so I have held off on publishing my installer until ready (should be any day now) and will package that in with with InputMapper’s installer once released.  I have also ordered some better audio gear for VO on the InputMapper tutorials that I am working on.

IM is about ready for help in translating the strings to various languages, more info on how to help will be in a later tutorial video. Starting work on the installer for moving IM 1.7 into the beta stages.