**KNOWN AW ISSUE**
Please be aware, there is a known issue with Saga badging when observing the AW map.
The team have found the source of the issue and will be updating with our next build.
We apologize for the inconvenience.
**KNOWN BG ISSUE**
We are aware of an issue with the seeding for the beginning of the BG season.
We are adding rewards to higher progression brackets to offset the additional grind.
More information here.
**Arcade is being extra tricky with his Murder Box...**
It appears Arcade has been non-cooperative in his approach to this month's side quest and presented his clues in a nonsensical order. Lucky you, Summoners, we have our best and brightest on the case and those clues should now be a lot more straightforward. While messing around in Arcade's files we came across a phrase, highlighted and bolded, with sparkles and pointy arrows: "the abode for the dead" ... Maybe that will help you along the way!
Options

Disable input system beta?

Before 38.1.1 update, I was able to disable Input System Beta option from the Settings menu.
But, now I can't see that option anymore.
For me (on Android), old input system was working better with more prdictable controls & champion movements.

Comments

  • Options
    PikoluPikolu Posts: 6,975 Guardian
    Kabam wants to fix the inputs but not having everyone on the same platform would make it twice as difficult to fix things because you have to try and fix them on both. I've been using the new input system (android) pretty much since its release. It is just a reconditioning your muscle memory.

    With everyone on the same input system, I imagine kabam has completely removed the old one from the build and we might start seeing some headway in input issues being resolved.
  • Options
    FurrymoosenFurrymoosen Posts: 2,225 ★★★★★
    Pikolu said:

    Kabam wants to fix the inputs but not having everyone on the same platform would make it twice as difficult to fix things because you have to try and fix them on both. I've been using the new input system (android) pretty much since its release. It is just a reconditioning your muscle memory.

    With everyone on the same input system, I imagine kabam has completely removed the old one from the build and we might start seeing some headway in input issues being resolved.

    Agreed. Hopefully this will help them to better identify if a) issues are actually still occurring and b) specifically what and where those issues are. I will say I have been playing two accounts on the same device for a long time, one with the beta opted in and the other not (though it obviously doesn’t matter now) and had no noticeable difference between the two.
  • Options
    bumble-beebumble-bee Posts: 137 ★★
    Oh man, game is unplayable on new input system on my galaxy s22 ultra.
    Champions jumping, defender stuttering, dex resulting in parry, and parry resulting in getting hit in face.
    Sometimes the input is dropping and sometimes delay in registering input.
    Sometimes attacker moves only half distance than usual while dashing back and sometimes dash back doesn't work at all (especially when defender is launching sp1 or sp2).
  • Options
    ItsDamienItsDamien Posts: 5,626 ★★★★★
    Pikolu said:

    Kabam wants to fix the inputs but not having everyone on the same platform would make it twice as difficult to fix things because you have to try and fix them on both. I've been using the new input system (android) pretty much since its release. It is just a reconditioning your muscle memory.

    With everyone on the same input system, I imagine kabam has completely removed the old one from the build and we might start seeing some headway in input issues being resolved.

    The problem is that instead of having a smaller proportion of the playerbase having issues with the two input systems they’ve now created a monster where a much larger population now has input issues. When developing on different platforms, you can’t simply have an androgynous system where one size fits all. If the old system was working for some, and the new system was working for others, they could have easily continued to develop the new system in the background and leave the old one untouched like they had for months and months. If it ain’t broke don’t fix it. The old system wasn’t broken or being changed, so why remove the option and create more issues. It’s reductive.
Sign In or Register to comment.