Mods overwrite and add game files. Game updates often reset these files. So often, all you have to do is re-install the mod AND the mod loader! During Vortex installation, don't forget Engine Injector mod type.

The mod CAN break after game updates and might need an update to work again!

After you installed it and started the game, see if in \Baldurs Gate 3\bin\NativeMods\ there is a file called BG3WASD.log.
If you do have a BG3WASD.log, look for warnings in this file. It can be opened with a text editor. See that the timestamps in there are up to date!
If the file does not exist or the timestamps do not match the system time, then you probably didn't install the mod or the mod launcher correctly.
Sometimes, the mod also displays an error or warning message on launch that can help.

It is possible that Windows blocked the zip or dll files, because it mistakes it for a virus. This is common, since the mod injects code to the game and listens to keypresses.
Rightclick the file, click Properties and see if, at the bottom of the General tab, it says something about unblocking the file.

The Game Speed Mod by livelylion has a colliding hotkey! Capslock. So change it in either their mod config or mine.

Sometimes, it helps to reset or re-bind the Camera movement hotkeys, especially if Shift+W works, but WASD doesn't.
Go to the game menu and bind Camera Left/Right/Forward/Backward. Character movement will be the same keys. Toggle between Camera and Character with Capslock.
When you clear both keys from a command in the game menu, the game sometimes binds the default values to the command without displaying them in the menu! This can lead to confusing hotkey conflicts.

Sometimes just restarting the game or the computer once can help.

See if you have any input scripts or tools running like AutoHotKey that might manipulate keypresses.

If you cannot move the camera during combat, read the section "I cannot move during combat" below.

If you cannot move the camera during combat or turn-based mode with WASD, press Capslock once.

That happens when the mod does not detect the combat state correctly and remains in Character movement mode.
So you have to toggle manually to Camera movement mode.

And no, character movement with WASD during combat is not possible.

Maybe you use the ScriptExtender version from March 29. This has an issue that makes it incompatible with the Native Mod Loader, causing the game to not start.
Make sure to kill all bg3 processes in the task manager, download the most recent ScriptExtender version, and try again.

Speedhack Mod: Also uses Capslock for something. The result is that you press Capslock to toggle between WASD and Camera movement mode, but then you also trigger some Speedhack Mod behaviour that will freeze the camera or something. The solution is to change the Capslock hotkey in either the Speedhack or the WASD Mod.

Works out of the box. One thing to note though:
The hotkeys you set ingame will adapt to your layout. So W will still be Forward. But the mod hotkeys you can set in the toml file, do not adapt.
So you probably want to rebind ToggleAutorun to shift+key:z.

This is not a bug of the mod, but a BG3 bug.
It happens, when you drag an object, while you move your character.
To prevent it, wait a short delay and let the animation finish after you drag objects.
To fix it, just drag an object without moving the character! If it doesn't work, save and load.

You can change some mod settings by editing BG3WASD.toml with a text editor.
If you edit the file while the game is running, you can press F11 to hot reload the config.

If you want to change the movement keys, bind Camera Left/Right/Backward/Forward in the ingame menu. Character movement is automatically bound to the same keys. You can manually toggle between Camera and Character movement with Capslock.

Vortex users can find this file by going to the Games tab, opening the games Game Folder and then navigating to \bin\NativeMods\.

If you don't want Game Updates to break all your mods, you can disable them for BG3.
In Steam, rightclick Baldur's Gate 3 and click Properties. Go to the Updates tab and set Automatic Updates to Only Update This Game When I Launch It.
Then, when an update arrives and you want to play the game, you will see that it has an update. Don't download it, but let Steam go into Offline Mode.
Then, you can launch the game without updating.

Apparently, there is also a way to downgrade games on Steam, but it is complicated, so I won't explain or support it. Please google it yourself.

No, it doesn't. The game engine is just poorly optimized for the low camera angle that you have, when using WASD and Native Camera Tweaks. So what is causing the decreased FPS is the way you play with the mod, not the mod itself.

If your machine is struggling, there is a FPS mod that sets the process priority to high. You can also do that in the task manager. Maybe this helps a bit.

No. The intended way is to use one set of keys and toggling between Character and Camera movement.
It also has a technical reason. Allowing it would make development harder.

The game has a auto-rotate feature so the camera always follows your characters orientation. However, this option is only visible in the game options, when you are in the Controller UI mode!

Unfortunately not. The ingame mod manager only supports pak mods, not dll mods.

This is part of Native Camera Tweaks. Make sure to keep this mod up to date.

This is only relevant for older mod versions before 1.9.6.
If you get this error, it means that you did not copy the SDL2.dll that comes with the mod to the correct location.
You must overwrite the existing SDL2.dll in BG3/bin folder!
In 1.9.6 and newer, you don't need to copy this file anymore.

Yes, yes, yes and yes.