Announcement

Collapse
No announcement yet.

Important notice for EA players (and more)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Important notice for EA players (and more)

    We’re aware of the recent compatibility issue that prevents reWASD from working properly in certain games.
    Our team is already on it, and we’re preparing a fix that will be rolled out in the upcoming update.

    We know how frustrating it is when you can’t fully enjoy your favorite games, and we’re truly sorry for the inconvenience. Thank you for your patience and understanding — it means a lot to us.

    Stay tuned and get ready to update reWASD soon.​

  • #2
    Any ETA ? :P

    Comment


    • #3
      We don’t have an exact ETA to share yet, but the fix is already in progress and will be included in the upcoming update.

      Comment


      • #4
        Hi, first of all thanks for communicating on the subject. But this isn’t really a recent issue — EA officially addressed it 2 years ago.

        I play Apex Legends periodically, and there have been alternating periods where reWASD could be used without issue, and periods where it couldn’t even be installed. It seems we’re back in the latter situation now.

        I’m not here to criticize, just to share my point of view.

        There was a time when I couldn’t fathom why anyone would cheat in a game where improvement is possible. Now I understand: one of the strongest human drives is the need to belong, and some will sacrifice anything to be part of a group.

        Cheaters are just an example of what this group dependency can create. When combined with economic incentives, competitive environments, and the pursuit of fame, breaking rules becomes a way to gain status. Anyone managing such systems knows that the fight against rule-breakers is endless.

        EA is clearly trying to provide a better environment for players, but in the case of reWASD, this has created a shadow economy: cheaters selling bypasses and showcasing their exploits online. They were already finding ways to break the game, and they will continue to do so regardless of the ban on reWASD. Meanwhile, legitimate users are the ones being punished.

        Perhaps organizing an open dialogue between all parties — developers, software creators, and the community — could lead to some solutions. Yet I also know my message will likely be ignored, as financial concerns will almost always take priority.

        Peace out anyway

        Comment


        • #5
          Hi Hazental

          This issue was not resolved by EA 2 years ago. That was simply the first incident after which we're open to starting a dialogue with EA to find a solution, but unfortunately, they simply ignored us.
          At the same time, EA games have a much more significant problem with cheating compared to remapping software that allows keyboard and mouse to controller remapping, yet this receives less attention. That's why, at least for me, this fight against remap software that makes players' lives easier looks a bit ironic.​

          Just a week ago, reWASD was working fine in all games, and this time we'll also fix this issue for the convenience of our users. Have a great day!

          Comment


          • #6
            Interesting! I'm going to assume Epic Games (Fortnite in this instance) has potentially updated something too this week! I've been away for like a week, went to play Fortnite tonight and binds just don't work properly - more so, it appears the "mute" function in rewasd isn't working. Can't exactly figure out wth is going on but seems likely Epic Games has done something :/

            Comment


            • #7
              IAmOrion As far as we know, this issue is somehow related to the Windows 11 system, and was already "fixed" by Microsoft in the KB5064081 update.

              We don't have any information on the situation with Windows 10.

              Comment


              • #8
                Originally Posted by Support Agent View Post
                IAmOrion As far as we know, this issue is somehow related to the Windows 11 system, and was already "fixed" by Microsoft in the KB5064081 update.

                We don't have any information on the situation with Windows 10.
                oooh interesting! I am indeed on Windows 11 - so it's possible Windows Update had not yet installed KB5064081 despite auto-updates being on. I shall check.
                Thank you for the info

                Comment

                Working...
                X