Issue with Input.GetAxis() method in Unity 5.3.5f1

Unity Engine
1

I started making a game with unity 5.3.5f1 long ago. Now that I am more or less satisfied with how it works, I tried to implement InputManager in it, and an strange issue happened.

Long story short, I implemented moving with arrow keys during development. More or less like this:

// I set variables like this, then use them to compute movement
if(Input.GetKey(KeyCode.UpArrow)) {
    upDownInput = 1;
}
if(Input.GetKey(KeyCode.DownArrow)) {
    upDownInput = -1;
}
// Similar for the other two keys, but with a variable called "leftRightInput"

It works fine. And, when I am not inputting any direction, the player (a sphere) keeps it’s inertia no matter if I turn the camera or not (just the way I want it). From there I tried to implement InputManager for the sake of genericity.

However, if I change the “if conditions” like this:

if(Input.GetAxis("Vertical") > 0) {     // <- UpArrow key
    upDownInput = 1;
}
if(Input.GetAxis("Vertical") < 0) {     // <- DownArrow key
    upDownInput = -1;
}
// Similar with horizontal axis

It works well. However, without touching Arrow keys (both Axis == 0), if I turn the camera, the inertia changes depending on direction of camera!

I just don’t understand why this happens. It is too weird!! How is possible that the way I get the input makes such a dramatic change? The rest of the code (which actually controls ball movement) is still the same!

Is there someone that may have any clue why such anomaly happens?

2

Dang!! While opening this thread, after proofreading and making one more test, I noticed:

  • For some reason, leftRight input was getting modified while I turned the camera!

Thinking about it, I checked the Horizontal axis in InputManager and, for some reason (probably my fault for not noticing before) it had alternative keys configured, which matched with the camera controls.

Erasing them, the issue got solved. What an stupid mistake I made! I even opened a thread for nothing… sorry