Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.

Warning for game developers: PCGamingWiki staff members will only ever reach out to you using the official press@pcgamingwiki.com mail address.
Be aware of scammers claiming to be representatives or affiliates of PCGamingWiki who promise a PCGW page for a game key.

Topic on User talk:Mrtnptrs

This is a permanent link to the first version of this post. You can view later versions on the post history page.

I write a shortened summary, and someone thinks it is too short and not exhaustive enough in its breakdown of the testing performed. I write a longer breakdown of the actual testing performed, and someone else calls it an "opinionated blog post"... šŸ¤£

> It's absurd to say something like "despite the devs saying they removed it, it was never there to being with."

Mate, this happens quite frequently if you're aware enough to notice disrepancies between random PC gamers claims, the reality of the situation, and clueless developer's responses (which contrary to popular belief are mistaken quite frequently).

In this case, from PCGW's perspective, the "opinionated blog post" as well as the testing performed (and confirmed by the same user that even added the misleading claim to the page to begin wtih), resolved around clarifying the fact that mouse smoothing is not the same as mouse acceleration and a parameter to disable mouse smoothing have no impact on mouse acceleration (and so also didn't even have an impact on user's experiences in this game either).

From a developer's perspective, they see claims of X among their players, and that Y parameter solves it. They implement Y as claimed by players that should fix it, and then they claim X was fixed. Easy peasy lemon squeezy. Developers are happy, players are happy, and everyone's happy!

Except for the ones that actually understands the terminology and parameters involved and have performed testing to confirm the obvious hypothesis (that smoothing parameter does not affect acceleration, and that UE4 doesn't even use mouse acceleration by default). No, no, our contributions are questioned in favor of developers -- even if those same developers have a questionable history.

Like, forcing UE4 to apply mouse acceleration?! You have to go out of your way to do that -- who does that?! What does that say about the competence level of those same developers even if that were the case? "UE4 has this fully appropriate input method scheme that uses raw input data and doesn't apply acceleration, but we'll go out of our way to force acceleration anyway!"

TL;DR: Now this is an opiniated blog postĀ :)