Realizing the implications to competitive play, I quickly set about working on a method to fix this horrendous oversight in the game's coding. It turned out that they didn't get processed for up to two frames after the input was read by the game.
Project m turbo mode pikachu vs mewtwo code#
This Engine Optimization is a fix for Controller Input Delay.ĭuring my work on updating the code that adds analog shoulder buttons and C-stick inputs to the game, I discovered that the button press function mapped to the C-stick isn't processed immediately as one might expect, resulting in up-smashes out of shield with the new code when pressing up on the C-stick to jump using its analog input (the C-stick analog jump input was going through before the C-stick button smash).
But with release right around the corner, the time has come to reveal one of the most important discoveries in the history of Project M.
Project m turbo mode pikachu vs mewtwo update#
We've been saving this update for a while to keep you from getting worked up over it. But even casual players will immediately recognize the difference it has on gameplay, so we're going to spend just a little bit of time giving a brief overview of what this code is, how we found it, and what it means for you, the players. The PMBR is rather excited about this code, due to its vital contribution to competitive play. Magus here with another engine optimization announcement for Demo 2.5! This is a pretty big one, as you all will very quickly see come release day, though many people may not realize exactly what the big deal is.
0 kommentar(er)
