I played around with the Max Shooter a little bit over the weekend. In its default config it works really well once you adjust the X/Y sensitivity via the wheels on the device. The problem is when you try to do a custom config. For example, in COD4 I tired mapping L1/R1 to mouse2/mouse1, and the PS button got mapped along with it, so every time I hit the mouse1 the PS button was hit. Supposedly you can erase the config by holding the program button for 5 sec, but the behavior didnt go away. There were other cases where keys I mapped also mapped the PS button as well.
The good thing was that in COD4 you can switch fire and aim to L2/R2, so I went back to the default config and it worked pretty well, much better than using the R stick to aim. If I had to do it all over again, I probably would go with the XIM, as you can have profiles for different games, and not have to reprogram for each FPS you play. I had to write down a chart to keep the mappings straight. I could see putting stickers on the keyboard to make it easier to remember what is what. But then again it just takes some time to learn the keys just like when you first play a game.
It was nice playing with KB+M again, but the frustration of the custom config killed most of the enthusiasm I had to actually play the game.
The good thing was that in COD4 you can switch fire and aim to L2/R2, so I went back to the default config and it worked pretty well, much better than using the R stick to aim. If I had to do it all over again, I probably would go with the XIM, as you can have profiles for different games, and not have to reprogram for each FPS you play. I had to write down a chart to keep the mappings straight. I could see putting stickers on the keyboard to make it easier to remember what is what. But then again it just takes some time to learn the keys just like when you first play a game.
It was nice playing with KB+M again, but the frustration of the custom config killed most of the enthusiasm I had to actually play the game.
Facebook
Twitter