Controller movement is ruined after 2.38

[Ayasu]

Good, fix it ASAP please, this is gamebreakig for gamepad users.

Moral of the History: don't fix what ain't broken... >.>

Did you maybe miss the part where they said that they didn't mess with the movement and it was a bug? 'Cause they didn't try to "fix" something that wasn't broken, another bug arose on account of them messing with something else in the code.

This kinda stuff happens with programming.

[Ninjaii]

Did you maybe miss the part where they said that they didn't mess with the movement and it was a bug? 'Cause they didn't try to "fix" something that wasn't broken, another bug arose on account of them messing with something else in the code.

This kinda stuff happens with programming.

Well apparently YOU did miss where the bug has probably resulted from their attempts to try to streamline the Input efficiency of the controllers. So YES they did needless change something that already worked, which created the bug

[Ayasu]

Well apparently YOU did miss where the bug has probably resulted from their attempts to try to streamline the Input efficiency of the controllers. So YES they did needless change something that already worked, which created the bug

Calm down, Sparky. They said they didn't change anything with /movement./ They did try to optimize gamepad controls. But /movement/ coding didn't get touched.

While no movement-related changes were made in patch 2.38, there was history of refactoring* of the pad input processing program, and as a result of this there is a high possibility that a bug was generated. We’ve begun to perform comparative checks by reverting back to the previous state on the development server.

*Revamping of implemented programs and rewriting processes to be quicker and more memory efficient

Whatever they did with the gamepad optimization didn't play nice on a live play environment(which happens), and it resulted in a /gamepad/ related /movement/ bug. They'll fix it. Don't crumple your frompy hat too much.

[Elendil_Voronda]

Did you maybe miss the part where they said that they didn't mess with the movement and it was a bug? 'Cause they didn't try to "fix" something that wasn't broken, another bug arose on account of them messing with something else in the code.

This kinda stuff happens with programming.

Err they specifically said they did change the code for gamepad control (*Revamping of implemented programs and rewriting processes to be quicker and more memory efficient.) So when they modified it to try and be more memory efficient (god knows how many Kb of RAM they saved xD) they introduced the bug.

Hence the "Don't Fix what aint broken" motto, I do programming myself, mostly PLC automation, and am very aware of the dangers that come with changing code.