Announcement

Collapse
No announcement yet.

reWASD has stopped working in Fortnite .

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

  • reWASD has stopped working in Fortnite .

    For two days now, rewasd has stopped working in Fortnite. It works perfectly outside of the game, but when I open the game, it doesn't work inside... only outside of the game. The keyboard and mouse aren't mapped to become controllers.

    My rewasd is on 9.1.3.​

  • #2
    Hi! We are aware of the issue and are working on a solution.

    Stay tuned​

    Comment


    • #3
      Just to add to this - it also appears that after closing Fortnite, and even closing rewasd - the actions of rewasd are still active and I can't see anyway to turn off the binds.
      I'm guessing that's potentially what the Emergency Disable Driver function is for?

      Comment


      • #4
        Yes, that’s exactly what the Emergency Disable Driver function is for​.

        Comment


        • #5
          Hi. This issue is directly related to Windows. Please update your Windows, and reWASD will work correctly in Fortnite.

          Comment


          • #6
            Originally Posted by IAmOrion View Post
            Just to add to this - it also appears that after closing Fortnite, and even closing rewasd - the actions of rewasd are still active and I can't see anyway to turn off the binds.
            I'm guessing that's potentially what the Emergency Disable Driver function is for?
            Actually, no. The [Emergency Disable Driver] function allows you to disable our driver instead of uninstalling reWASD when you want to play games that refuse to start because of it.

            To turn remap off, you can use:
            • The [Power Button] at the bottom left corner of reWASD app (selected device).
            • [Turn Remap OFF] command of the Tray Agent (all devices).
            • CTRL+ALT+DEL shortcut (all devices).

            Comment


            • #7
              Originally Posted by strokel View Post
              Hi. This issue is directly related to Windows. Please update your Windows, and reWASD will work correctly in Fortnite.
              In my case no, when I open the game it stops working or gets bugged. And when I close the game it goes back to working normally... They must have updated something in Epic or in Fortnite itself.

              Comment


              • #8
                Originally Posted by Support Agent View Post
                Actually, no. The [Emergency Disable Driver] function allows you to disable our driver instead of uninstalling reWASD when you want to play games that refuse to start because of it.

                To turn remap off, you can use:
                • The [Power Button] at the bottom left corner of reWASD app (selected device).
                • [Turn Remap OFF] command of the Tray Agent (all devices).
                • CTRL+ALT+DEL shortcut (all devices).
                It's quite possible the KB5064081 issue you mentioned was the result of my computers erratic behaviour. Despite turning off and even closing rewasd completely, the rewasd keybinds were still active. It was weird - but then, I had odd behavior trying Fortnite too, so perhaps the KB5064081 you mentioned in different thread fixes the issues. I will check later.
                Thanks again for the info

                Comment


                • #9
                  Originally Posted by Pecene94 View Post
                  In my case no, when I open the game it stops working or gets bugged. And when I close the game it goes back to working normally... They must have updated something in Epic or in Fortnite itself.
                  According to what we know, this issue was "fixed" by Microsoft in the KB5064081 update for Windows 11. We don't know if there is an update that "fixes" this on Windows 10.

                  Comment


                  • #10
                    Originally Posted by Support Agent View Post
                    According to what we know, this issue was "fixed" by Microsoft in the KB5064081 update for Windows 11. We don't know if there is an update that "fixes" this on Windows 10.
                    Well, I an windows update, installed KB5064081 as well as all other updates. It's working 99.99% for me - what is still weird, and not sure where the issue is - the Middle Click (so clicking the mouse scroll wheel) does not get muted and so whatever I had mapped to it doesn't work.

                    I have a Logitech G502 I was able to use the Logitech G-Hub, make the Middle Scroll Wheel Click instead be the # key, and then in rewasd I was able to use the key remap section to alter the behaviour since it was no longer seen as a middle mouse button click. Then it worked fine! So there's something about the middle click on mouse wheel that either Fortnite or Windows has broken that prevents it from muting and not actioning the mapped behaviour.

                    FWIW I've been using it mapped for months if not a couple of years without issue (I've not changed the mapping until today) so whatever the issue, it's new and not directly related to rewasd I don't believe since last week 9.1.2 was working perfectly, then this issue occurred (still on 9.1.2). Still present in 9.1.3 - so again either an Epic Games thing or a Windows 11 thing.

                    Comment


                    • #11
                      Originally Posted by Support Agent View Post
                      According to what we know, this issue was "fixed" by Microsoft in the KB5064081 update for Windows 11. We don't know if there is an update that "fixes" this on Windows 10.
                      I'm on Win 11 and it's not working. It must have been a game update that prevented rewasd from working properly. As soon as I close the game, it works normally.

                      As Kapas said, they're looking for a solution.​

                      Comment


                      • #12
                        Originally Posted by Pecene94 View Post
                        I'm on Win 11 and it's not working.​
                        Do you have the KB5064081 update installed?

                        Comment

                        Working...
                        X