Site Login

This Months Donations

$137.98
of $500.00 goal
Server, CDN, Network, Licensing
Development Budget
Developers Beer Fund
Recent:
John Lee
$2.00
Thank you!!
jhonatan felipe
$2.00
Frederick J Hogsett
$5.00
Karl Scahill
$2.00
SiesMAN01
$2.00
Number of donations
37
Highest donation
$30.00
Average donation
$4.19

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 occurance (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. Any controller or program issues you are having that affect the devices operation should be reported as if the 403 error does not exist because it has nothing to do with it.

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.