Test My Controls v2.0 Final changelog

If you want to find out whether or not it's time to replace that PSP analog stick, then here's a little application that might help you decide what to do with it. Developer Johnny McKinney has come up with a nifty app which helps test out your analog stick's sensitivity and rates whether or not it may need replacing.

Test My Controls v2.0 basically tests your analog stick's sensitivity and judges whether or not it may need replacing based on the X and Y ratings it receives upon testing.

If the X and Y are not between 120 and 130 then it should be fine. Anything above 140 or below 110, then it may need cleaning. However, if the X and Y coordinates are above 160 or below 190, then you may have to send it to the nearest shop for replacing.

The latest release of Test My Controls v2.0 Final and this is the final version of the program and the developer mentions that he will no longer be updating it unless some bugs pop up that will need handling.

Here's the changelog for Test My Controls v2.0 Final:

• Fixed the display of the image that made it look like a tv in prgressive mode (Thanks to Ziethiec over at psp-hacks for helping me in figuring out I forgot to end my function with a bracket, silly me lol)
• Adjusted the anologs sensitivity.

Constant use is grounds for wear and tear, and that's no exception even for the multi-capable Sony PlayStation Portable. Homebrew developer Johnny McKinney released a homebrew application to diagnose the PSP's controls. Test My Controls version 1.5 - perhaps a C++ rehash of Control Tester v1.0 - allows the user to test the analog stick's response and detection range to gauge the analog control's operational condition.

How does it work? Well, if you've handled joysticks or gamepads in Windows before, Test My Controls v1.5 would be something similar to the gamepad properties' Diagnostics utility. There's a certain threshold your control will accept at both sides of axes X and Y, and if you're pretty close (say 2 integers) to the 127 integer range for both the negative and postive ranges for both axes, your analog control is accurate enough for operation.

But if it hits a certain high, like the developer's suggested threshold of 140, you could be looking at a serious need to replace the analog control - if not attempt to repair the analog control interface yourself. Don't be alarmed by the progressive scan symptoms you'd occasionally catch the program in - its all face value until that little code gremlin's been swatted down.