1 items

File information

Last updated

Original upload

Created by

Ch4nKyy

Uploaded by

Ch4nKyy

Virus scan

Safe to use

About this mod

Explore Rivellon from an immersive Third-Person view and use WASD to move your Heroes. Includes camera tweaks.

Share
Permissions and credits
Changelogs
Donations
WASD Character Movement




Features
  • Directly move your character with the WASD keys (or others)
    • Character movement is bound to the same keys as Camera movement
  • Toggle between Character movement and Camera movement, by default with Caps Lock
    • It automatically toggles on combat start and end
  • Improve mouselook
    • When rotating, the cursor is hidden and stays in place and Interact is disabled
    • Rotate key + Leftclick = Forward
  • Fix input conflicts, when you bind Camera Rotate to the same key as Context Menu and Cancel Action. (Many people bind these 3 to Rightclick.)
  • Auto-move forward, by default with Shift+W
  • Toggle between jogging and walking, by default with Insert
  • Leftclick movement can be blocked in the config if desired
  • Camera tweaks
    • Unlock pitch (By mod default, it is only unlocked to some extent to avoid visual glitches. If you can live with them, you can unlock it completely in the toml file.)
    • Don't reset the camera zoom after dialogs to max
    • Change min zoom, max zoom, dialog zoom, zoom speed, fov, camera movespeed, camera rotation speed, vertical offset, horizontal offset
    • Improve background draw distance

  • Supports the Definitive Edition of both Steam and GOG.
  • (Probably?) Supports multiplayer, even if the other players don't have it
  • Does not affect Savegames or Achievements
  • (Probably?) Does not affect Controller mode or Splitscreen
  • Hotkeys and settings can be configured. Features can be disabled. Edit DOS2WASD.toml with a text editor. Press F11 to hotreload the config ingame, after you saved the toml file.


Installation

From my experience with BG3, I highly recommend to use Fake Fullscreen mode. Fullscreen does not display error messages and does not work well with multi monitor setups.

EITHER Manually

Download the mod, put the zip file in the following location and click "extract here".
C:\Program Files (x86)\Steam\steamapps\common\Divinity Original Sin 2\
  • When Windows prompts whether you want to overwrite the existing files, say yes.
  • The beginning of the path might differ if you installed it on another disk or if you have the GOG version.
  • In the end, the dll should end up in this location:
C:\Program Files (x86)\Steam\steamapps\common\Divinity Original Sin 2\DefEd\bin\NativeMods\DOS2WASD.dll

OR with Vortex

1. Download the mod with Vortex.
2. In Vortex, under the Mods tab, double click the mod, scroll down and set "Mod Type" to "Engine Injector".
3. In the Notifications, click "Deploy".


FAQ, Troubleshooting and Hints

The mod worked before, but stopped working!

Spoiler:  
Show
Maybe the game had an update that overwrote some mod files. Just re-install the mod.


The mod isn't working or displays an error or crashes

Spoiler:  
Show
After you installed it and started the game, see if in \Divinity Original Sin 2\DefEd\bin\NativeMods\ there is a file called DOS2WASD.log.
If you do have a DOS2WASD.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.

If the mod complains about SDL version mismatch, you didn't copy the SDL2.dll correctly.


The mod is not working, although the log file is updating

Spoiler:  
Show
Sometimes, it helps to 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.


I cannot move during combat, camera seems stuck

Spoiler:  
Show
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.


AZERTY keyboards

Spoiler:  
Show
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.


Changing keys or config values

Spoiler:  
Show
You can change some mod settings by editing DOS2WASD.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.


Can I bind Camera movement to other keys than Character movement?

Spoiler:  
Show
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.



Uninstallation

Delete the NativeMods folder.
Delete bink2w64.dll and rename bink2w64_original.dll to bink2w64.dll.
Delete SDL.dll and rename SDL_original.dll to SDL.dll.


Source

GitHub

Contributions are very welcome.


Credits

Ershin for contributions and support
dukethedropkicker for DKUtil and support
kassent for Native Mod Loader
Vectonauta on Freepik for the image
Thank you very much to the donators!