Original Post — Direct link

With the plan of epic removing legacy aim assist in a few days, and months of me complaining about the same issue highlighted in this post. And many other linear/expo aim assist bugs posted under my username, and sending multiple feedbacks in-game, with no word on anything is very frustrating.

So again, I'm going to say linear/exponential aim assist doesn't work on the Nintendo Switch, it's been like this ever since Chapter 2, Season 1 was introduced. When the new settings were introduced in Season X, they worked as intended, so I switched to Exponential (motion controls enabled), but with the new chapter introduced it wasn't working as it was before. Thus resulting my decision to going back to Legacy, as even with motion controls enabled and an abysmal frame rate, I still had it aid me tracking an enemy. I never "L2" spammed anyone.

Linear/Exponential aim assist on switch isn't the same as on what it is on console/pc, it seems like its more reliant on fps more than legacy, please fix this, I'm honestly begging at this point. I've highlighting these bugs for months. The random frame drops from 30fps to 13fps don't help the situation either.

Side Note: I only use motion controls for editing and building.

External link →
over 4 years ago - /u/FreightTrainUSA - Direct link

Originally posted by piddythebat

u/FreightTrainUSA with the removal of Legacy aim assist in less than 5 days, I would like to report a major bug regarding exponential/linear aim assist, on Nintendo Switch. When motion controls are enabled, aim assist disables itself/works inconsistently, it's difficult to describe in words.

There's no aid when tracking the enemy, even when I'm definitely just using the look control stick, it only works when motion controls are not enabled in the settings.

This bug started with the introduction of Chapter 2 Season 1, and wasn't present when the new settings were added during Season X. I was using the exponential look input curve with motion controls enabled, which worked perfectly fine.

But I had to go back to using Legacy when the bug appeared, and is the only reason why I went back, even with motion enabled the aim assist was still present helping me.

The only instances where I use motion controls, is for building and editing. Which is a great feature that I don't want to abandoned.

Ever since Chapter 2 Season 1 started, I've been making multiple reports in-game and on this subreddit, with no word if the devs are looking into this or not, via the trello board.

Which is a huge reason why I mentioned you in this thread, and hopefully give them word of this bug. Thank you.

Thanks for the report, I will pass this along.