DarkSoulsMouseFix

Waypoint Interview – Complete Answers

A few months ago I was interviewed by the gaming website Waypoint about the development of the Dark Souls Mouse Fix (which later evolved into the Dark Souls Input Customizer). As with almost any interview, the answers were cut down to fit the style of the site and the intended flow of the author. I have no idea how many people read the original article or are even interested in this kind, but for the few people who are, here are my complete answers to the questions I was given.

Be wary of wall of text


Can you talk to me a little bit about what you do in real-life, and what kinds of games you’re usually drawn to?

I recently received my master’s degree in computer science and am currently in the process of transitioning out of the lazy life of a student to something more, I guess, grown-up. What that will exactly look like I am not sure about at the moment. As a side job, I have been working as a tutor for a few years now and am currently teaching software development and software engineering at a university.

I am interested in a broad spectrum of games and there really are only a few genres I do not touch at all. But although I play almost anything from RPGs, strategy and adventure games to platformers or weird indie games, I am definitively most drawn to first-person shooters.

Dark Souls shipped with mouse support on PC, but obviously it wasn’t right for everyone. What didn’t work?

As probably most people know by now, the PC version of Dark Souls was a total mess at release and is to this day only properly playable thanks to the fantastic DSFix by Durante. Aside from many technical issues, people also quickly discovered that the mouse and keyboard controls were in a state one could, without exaggeration, only describe as unplayable. Not only showed the default layout of the keybindings a profound lack of understanding of how games are played with that control method, it was also basically impossible to properly control the camera. While there are other games out there which have sub-optimal mouse input, they usually only suffer from unwanted acceleration, sluggish movement or input lag. But the original mouse controls of Dark Souls have a very weird behavior, where the movement is choppy and controlling the camera feels like using a mouse that only updates once a second.

While the keybindings could easily be fixed in the ingame settings, the camera controls were basically broken. Another modder (whose name unfortunately escapes me), very early on came up with a solution that was the way to go when wanting to play the game with the mouse. What he did was writing a controller emulator that feeds the mouse input to the game as movement of the right analog stick, thereby circumventing the original mouse input of the game altogether. This was a good enough solution and made the game finally playable for people who do not have a controller or someone like me who just prefers to use mouse and keyboard.

Although it did a great job in helping many people (including myself) to enjoy the game over the years, it is not an optimal solution, because using an analog stick is very different on a technical level from mouse movement and therefore emulating it with a mouse does not feel like you would expect or want from a PC game. Aside from sluggish movement, the most prominent drawback of that solution is negative acceleration, meaning that the faster you move the mouse, the less camera movement is produced. This had bothered me and other people for years, but we just accepted it, because the only way of this getting fixed was for the game to be patched, which everybody knew would was not going to happen at that point.

It’s hard for me to even imagine playing Dark Souls with a mouse; a gamepad is ingrained into my mind. Is there an advantage to using a mouse, or just preference?

This is something that always comes up when talking about the Souls games. Some people even go so far and claim that those games are impossible to be played with mouse and keyboard. This is of course nonsense. All the games can be played fine with mouse and keyboard from start to finish. It is of course undeniably true that you lose a little control of the movement, because you are trading an analog stick for binary keyboard input, but in practice this actually makes very little difference. The two relevant movement speeds can be specified with a modifier key and using the eight rolling directions the keyboard offers work perfectly well to do anything you need in those games. On the other hand, you gain fine control of the camera with a mouse, which makes some things such as aiming with a bow easier. But I would be the first to admit that this also does not have a major impact to the overall gameplay, unless maybe you are playing a bow-only build.

So for most people it is not about getting an advantage, but rather personal preference. I personally cannot stand using a controller for any game in which I have direct control over a 3D camera. Even though precise input is not necessary from a gameplay stand point, I am just more comfortable with a mouse and keyboard. One of the beautiful aspects of PC Gaming is that everyone can use the control scheme he or she prefers, even though it may deemed to be inferior by other people.

What did you aim to fix with your mod, and what changed as you went about developing it?

The development was actually pretty straight forward, because it was a well defined problem, with which I as devout Dark Souls player was very familiar with. The goal was to iron out all the remaining issues the mouse and keyboard controls had, primarily by making the camera movement feel as you would expect from a proper PC game. Before I started to work on the Dark Souls fix, I had already developed a somewhat similar fix for Dead Space, which also suffers from bad mouse controls. Although these kind of fixes are custom tailored to a specific game and therefore few components can be reused, I was already familiar with the general approach of injecting the raw mouse input directly into a game’s camera functions. However, the Dark Souls fix turned out to be more challenging, because a lot more things had to be taken care of to make it work properly.

This mod goes far beyond swapping texture or importing a character model. I have to imagine this was complex. What was its development like?

Yes, even though it might not appear like it, because there are no changes to the visuals or the gameplay, fixes like this actually do take a lot of effort to make. The problem is that these kind of technical issues often cannot be fixed from outside of the game. When it comes to controls, there is only so much you can do by tinkering with configuration files or using external tools, such as AutoHotkey. If they are broken on a fundamental level, like they were with Dark Souls, you actually have to dive deep down into the guts of the game to figure out a way to solve the problem. This is why this approach should only be used as a last resort, when it is pretty clear that all other options have been exhausted and that there is no hope for an official patch to fix the problem.

To do something like this, you have to apply techniques that in computer science are referred to by the term reverse engineering. The same way you can break apart your toaster to find out how it works, you can take a look at the executable file of a piece of software to reveal its inner workings, without having access to the source code. Now, this is easier said than done, because a modern game is of course much more complex than a toaster and you are looking for very specific parts in a program that quite a few people spend years on to develop.

After having found what you were looking for, you are faced with the question of how solve the actual problem. This is a little different from conventional software development, because there are a lot of factors you do not have any control over and you have to find a way to make the game do what you want, all while being very careful not to break something. The whole process can be tedious and time-consuming, but it can also be a lot of fun because it is a challenging problem. It can also be very interesting so see how things are actually implemented in a particular game, which often provides some insight into why a game behaves in the way it does.

How long it will take to do a fix such as this is highly dependent on experience and intuition. People hacked into games forever, and of course I am far from the only person being able to do this. To be honest, I have very limited experience and skills in this kind of thing, especially compared to some other people out there, who in some cases have been doing nothing else for the past 20 years. Unfortunately, more often than not, those people usually end up developing cheats or cracks for games, instead of using their powers for good.

Was there a particular aspect of this mod that was challenging to put together? What took the most time and why?

The development of a fix such as this can broken down into two parts. First, you have the hacking part, in which you are trying to solve the actual problem by dissecting the executable and finding ways to make the game do what you want. Secondly, once you have actually achieved what you wanted, you have to think about how to make the fix usable by other people. Although the first part consumed more time overall, the second one consumed more time than I had anticipated.

What you have to keep in mind, is that you are trying to deploy something that is essentially a hack, to a game without any modding support whatsoever, for a lot of people with vastly different combinations of hardware, tools and other mods they are using with the game.

This is much harder than it may seem, because especially with Dark Souls you cannot assume that people are playing the same way you do. You have to ask yourself things such as: Is the fix easy enough to install or configure, so it can also be used by people who might not be tech-savvy? Are the instructions and the GUI design intuitively to understand? Can players configure the controls the ways they want?

Additionally, there is also the problem of compatibility. People are using all kinds of different mods and tools to customize the game, sometimes resulting in Frankenstanian amalgamations of different programs and DLLs that all interact with the game simultaneously, and you have to take care that at least the most popular ones are working with your fix. Although there was a fair amount of alpha testing before the fix was made public, there were a lot of issues like this that I had not seen coming.

At this point, Dark Souls is several years old, with most of the community having moved on to newer games like Dark Souls 3. Why keep working on Dark Souls?

Even though the sequels were generally well received, the first Dark Souls is already somewhat of a cult-classic and is by many people considered to be the best part in the series. The SteamSpy statistics seem to confirm this, with the first Dark Souls still being roughly on par with Dark Souls 2 in terms of concurrent players. Even Dark Souls 3 has only a little over twice as many, despite being a much younger game. So the first Dark Souls is far from dead and it is also a game many people hold dear and come back to for another playthrough a few years later.

Additionally, even though some games do not age well, great games generally do not suddenly become bad because they are a few years old. And I am of the opinion that good games deserve to be preserved.

How’d you originally discover Dark Souls, and what drew you to it?

As a PC-only gamer, I initially heard of Demons Souls and Dark Souls as one of the great examples of console games that are not available on the PC. And after reading about them I was kind of baffled by the decision, because from the description they struck me as the kind of games that would be very successful on a PC. I then participated in the petition to port the game to the PC, which must have been one of the very rare cases where a petition actually did have an impact on something, and then waited in anticipation for it to come out.

The thing I find most intriguing about Dark Souls is the world design and how it is connected to the gameplay. While other fantasy settings often present a peaceful world under attack by evil, the world of Dark Souls is a bleak place full of misery and despair, while at the same time being quite beautiful and appealing in its own way. The atmosphere the game creates with its art design and music immediately makes it clear that you should not expect any help to progress in the game and are supposed to figure things out on your own.

I think it is unfortunate that the Souls games are mostly known for their supposed difficulty, when a much better word to describe them would be tough. Although they are certainly not easy and may appear to be unfair at times, they are mostly about being thoughtful and observant of the environment, and will punish you if you are careless.

Do you have a history with modding, and do you tinker with things in real-life, too?

I am a long time PC gamer and came first into contact with the concept of modding around 1995, when building levels for the Star Wars game Dark Forces, together with my father and brother. Not only was it amazing to see how much work people put in custom campaigns, it was also an interesting experience to exchange levels online at a point in time where most people around you had not even heard about the internet.

While I was dabbling around with an editor to create a custom map for the original Counter Strike, I quickly realized that I lacked the creativity and dedication to contribute anything valuable for other people and I just kept enjoying modding as a player instead of a developer.

Some time ago I ran into a notorious problem in one of my all-time favorite shooters named F.E.A.R, which on many modern systems slows the performance of the game down to an unplayable degree and can only be fixed by a tedious workaround. I took a deeper look into the problem and was able to determine the cause and develop a fix for it. After I released it I was amazed by the reception and it made me realize that I could contribute to the PC community in ways that did not require any creative talent.

That is why I do not consider myself a modder in the traditional sense of the word. Up to this point, I did not create anything that changes the gameplay or visuals of a game, but rather help people to better utilize their hardware and to allow them to play a game in the way they like. There are many other great people doing stuff like this, such as Durante or the developers behind tools such as Flawless Widescreen.

Unfortunately, I have two left hands when it comes to fixing things in real-life that have nothing to do with computers. But I have an unspoken agreement with a long-time friend of mine, who works as a craftsman. I will fix any problems he has with his PC, and he will help me with any handiwork around my apartment. Which is also an idealized way I like to think about the PC gaming community as a whole.

When I saw this mod posted to reddit, the outcry of support was huge. People seemed to really appreciate it. What was that like?

It is always great to see that something you have created is helping people to enjoy a game more. Aside from the few expected naysayers claiming that the game should not even be played with mouse and keyboard in the first place, the reception was pretty good and I am very grateful for the acknowledgement I got. Although I was fully aware that the vast majority of players prefer to play the game with a controller, I did anticipate that there would be at least a few people who would be happy with a fix like this. What I did not see coming was the coverage the fix got on many, mostly PC-centric, gaming websites. This was a very pleasant surprise.

Another thing that took me by surprise was the interest in the fix by people who do not even want to play the game with mouse and keyboard. As it turned out, the changes to the mouse movement improve the camera controls with the Steam Controller, when mapping the mouse movement to one of the trackpads. This resulted in the experimental Steam Controller support, which was introduced to the Dark Souls Mouse Fix in version 1.3.

Any plans for future mods? What’s next for Methanhydrat?

I am definitely planning to continue working on something in the future. What that will be I am currently not sure about. The Dark Souls fix needs some additional work, as there are still some minor bugs to fix and also additional features that I would like to add. Aside from Dark Souls, I also have a few other games in mind that would benefit from some fixing. I am also always open for suggestions. I originally developed the fix to remove the mouse acceleration in Mass Effect for just one person. So if you have an idea, get in touch with me, make a good case for it, and we will see what will happen.

However, due to the ongoing changes in my work life, it is currently hard to say how much time there will be in the future for stuff like this.

Dark Souls Mouse Fix – Update to Beta 1.4

I did have some free time on my hands again and took the opportunity to tackle some of the bigger remaining issues of the mouse fix for Dark Souls. This is a major update and should remedy many gripes and problems some people had with the previous version. It has gotten a fairly well reception and I am pretty confident that from this point forward there are no issues left that could be considered major. You can find the latest version on Nexus here or on PC Gaming Wiki here.

Instead of just posting the change log as I normally do, I will summarize them in reasonable sections.

New Binding System:

This is a big one. The old binding system was very clunky and restrictive, because users had to manually select the key they wanted to bind from a predefined list of keys out of a dropdown menu. I was not a big fan of that system in the first place, but it was the only thing feasible I could do at that point in time. To keep that list manageable, I only included the most common keys. This was a problem because people are using a wide variety of keyboard layouts and languages, which sometimes prevented them from binding the keys they wanted. Another issue was that the old system did not properly support modifier keys, which had to be added manually for each option. This was overall one of the most requested features.

After I had thought about the problem for a while, I came up with a solution I am quite happy with. The new binding system allows you to bind any action to an arbitrary combination of keyboard keys, mouse buttons or the mouse wheel. Have you ever wanted to switch your magic spell with Space+W+~+MouseWheelUp? Now you can. Instead of manually selecting a key from a limited set of predefined keys, the new system works reactively. To bind an action, double left click the corresponding box. When the box turns green, press the combination of keys you would like to assign. The combination is set once any pressed keys are released.

You should be able to use almost any keyboard key, independent of the keyboard type or layout. The key names are dependent on the layout currently set in Windows. If you are using an English layout, the key names will be in English, while an AZERTY layout will lead to French names.

Bear in mind that the names the keys are getting in the GUI are sometimes not entirely correct. For example, both the left and the right control keys can be referred to by the same identifier, while keys like Page Up might refer to the corresponding key on the numpad. This is because the key names are generated dynamically by using a Windows function, which does not distinguish between certain keys and does not always lead to pleasant display names. However, this is entirely a cosmetic issue and the keys will get recognized in the game as they are pressed in the GUI.

A few additional notes on the binding system:

  • Each key pressed before another acts as a modifier for the next one
  • Any key can be used as a modifier key, not just ALT, CTRL or SHIFT
  • There is no limit to how many keys can participate in a combination. You can set a combination involving half a dozen keys if you want to
  • The order you are pressing the keys in is only important during the binding process to differentiate between bindings that involve the same modifier keys
  • To unbind an action double right click the corresponding box

There are some videos out there that show how the binding works in practice. For example this one.

Manual Targeting Option:

It is now possible to enable the switching of targets by flicking the mouse. After the keybindings, this was the second most requested feature. I honestly did not anticipate that so many people would prefer to switch targets by using the mouse instead of a dedicated binding.

Manual targeting can either be always enabled or specified by a hold or a toggle binding. Additionally, one of the things that always prevented me from using this kind of target switching was how easy it was to unintentionally switch targets. For this reason, I also added a Targting Threshold option, which determines how far you have to move the mouse for a target switch to occur. Take a look into the GUI tooltips for more information.

Non-Standard Bindings:

Added a set of non-standard bindings. It is now possible to bind Leap Attack, Kick, Dash Only, Roll Only and Auto Run actions to further enhance the customization of the controls. See the corresponding GUI tooltips for details.

There has been some considerable amount of thinking and discussion about whether to include non-standard bindings at all in the fix. I actually started a discussion about this in the main reddit thread when the mouse fix first came out, but it did not really gain much traction. The question was at which point something ceases to be a matter of controls and begins to just make the game easier. Especially with the Kick and Leap Attack, one might argue that being able to execute them well is part of the learning process of the game.

In the end, I decided to include them because they do not allow you to do anything that cannot also be done manually. Additionally, the actions are not that difficult to execute in the first place and most of the bindings could also be easily replicated without the fix, by using external tools such as AutoHotkey. I am personally also not a fan of context-sensitive bindings and it is nice to see that there are also other people out there who prefer to have dedicated bindings for rolling and dashing.

However, if you are a purist, feel free not to use them. PC Gaming is all about choice after all.

Miscellaneous:

  • Added a custom mouse cursor that should be more suitable for the game. The cursor is enabled by default but can be disabled in the GUI
  • Added audio feedback for certain status changes, such as loading of the mouse fix, reloading the config or changing the input mode
  • Multiple changes to the usability of the GUI, including a revision of the labels and tooltips
  • Added a complete initial default config that should be decently intuitive for most players that are not familiar with the game

These are just some little quality of life features to improve the overall experience. They should be pretty self-explanatory. The custom cursor is called Das Black and was created by a user named aroche. If you want to know how it looks, you can find pictures of it on his Devian Art page.

Major Bugfixes:

  • The GUI no longer loads a local d3d3.dll to prevent conflicts with certain mods/injectors, such as DSPW or SweetFX/ReShade (thanks to SeanPesce for his feedback and research on the issue)
  • The Auto Cursor will no longer enable the cursor and lock the camera when UI elements are shown that cannot be controlled with the mouse, such as subtitles or certain floating messages
  • Fixed a bug that caused the Auto Cursor to not recapture the cursor correctly after having switched out of the game

I am very happy that I got these fixed.

The first one was not only quite annoying, but also confusing to the user. Although not many people seem to use SweetFX with Dark Souls, Dark Souls PvP Watch Dog (DSPW) is a popular tool and I got many reports of people who had no idea why starting the GUI caused an error box of DSPW, which lead them to believe the mouse fix was incompatible with the it.

The Auto Cursor problem was probably the most severe ingame bug, as it could potentially lock you out from controlling your character in situations where that could actually cause you to die. Aside from some very rare situations involving keys opened by doors (see Known Issues), the Auto Cursor should now work correctly in all situations.

That is it for now. Aside from potential hotfixes, it will probably take a while before the mod is updated again. But as always, do not hesitate to provide feedback or suggestions. I will keep them in mind. Also, if more people are suggesting a feature, it is more likely that it will get implemented.

Have fun.

Dark Souls Mouse Fix – Update to Beta 1.3 – Preliminary Modifiers, Experimental Steam Controller Support

Although I really should do other things right now, I invested some more time into the mouse fix to add some often requested features and fix some annoying bugs.

Beta 1.3 change log:

  • Added preliminary modifier bindings that turn left and right attacks into heavy attacks (see Configuration for details)
  • Made all modifier bindings non-blocking so they can also be used as a modifier in the ingame settings where applicable (see Configuration for details)
  • Added proper Input Mode setting to the config that allows easy switching between mouse and controller input (see Configuration for details)
  • Added experimental Steam Controller support (see Configuration for details)
  • Replaced Toggle Mouse Fix binding with Toggle Input Mode
  • Fixed bug that prevented the number keys from getting bound correctly
  • Fixed bug in the GUI that prevented an action from getting unbound correctly when there was a default binding for it

From the documentation:

Modifier Bindings

Modifiers change the behavior of a binding when they are down. The current implementation is preliminary and has some shortcomings:

  • Modifiers are currently only available for movement as well as left and right attack. The implementation will be overhauled in the future to allow all actions to be bound with a modifier
  • Any key or mouse button can be set as a modifier
  • While a mouse wheel direction can be set as a modifier, it will not work properly, because rolling the mouse wheel cannot be hold down
  • A key or button used as a modifier will not be blocked in the game to make it also usable as a modifier with the ingame keybindings. This also means that it may be necessary to unbind some ingame keybindings to make everything work properly

As you can see there are some drawbacks to the modifiers. Although I am really not happy with the way the modifier keys are implemented right now, I figured it would be better to have them for at least those bindings which seem to be most important to people, rather than not having them at all. But to be honest, I cannot wait to have some free time again to do modifiers and bindings in general properly.

Again from the documentation:

Input Mode:

The input mode specifies the behavior of the fix:

  • Mouse: Enables raw mouse camera and keyboard standard action bindings, deactivates controller input and vibrations
  • Gamepad: Standard controller behavior, disables raw mouse camera and keyboard standard action bindings
  • Steam Controller (experimental): Standard controller behavior with the exception that the raw mouse camera is enabled and the right analog stick is disabled

This point might be surprising to some people, but I had an unanticipated amount of requests to make the fix usable with the Steam Controller. Apparently the new mouse movement is a big improvement to the usual analog controls of the gamepad. I had actually posted an experimental version a few days back in the Steam Controller reddit, which now got fully incorporated into the fix alongside a few bugfixes.

I also took the opportunity to implement a proper input mode, because there previously was no clear divide in the code that specified when which components of the fix should be active or not. As you can see, it is now properly supported to have the fix installed alongside a controller and to switch between the input modes, even on-the-fly, without having to fiddle around with the setup.

This is all I can do for the moment. Although there are still things left to do and also a lot of room for improvements in other areas, most of those things either require a considerable update of the software or another deep look into the engine of the game, both of which I unfortunately currently do not have time for.

As always, let me know if you encounter any problems.

Dark Souls Mouse Fix – Update to Beta 1.2

I just updated the fix to a new version:

Beta 1.2 change log:

  • Added option to bind movement to the config. These differ on a technical level from those in the ingame settings (see Configuration for details)
  • Disabled hardware acceleration for the GUI to avoid conflicts with post-processing injectors such as ReShade or SweetFX
  • It is now possible to resize the GUI in vertical direction to use it with low-resolution displays
  • The GUI now groups options by category

Although I’m sure some people were hoping for something more impressive, the GUI changes were necessary to help people who previously could not really use the fix at all in the intended way.

However, the first point might be more interesting than it seems. There is an issue with the keyboard controls that has been in the game since launch. If the player runs diagonally and does not move the camera at the same time, the character might sometimes not roll in that direction, although the input is correctly performed. Although this problem can be mitigated by moving the camera, it can sometimes happen by accident, when you are not thinking about it. Now, the new keybindings to move the character differ on a technical level from those you can bind ingame and I could not reproduce the rolling problem with them, which was reliably possible with the standard controls. Some people also reported that the new bindings fix the problem of sometimes moving without input after exiting lock-on mode. They might also improve other things regarding the input.

However, further testing is needed before I can say that those problems are indeed gone and that there are no unwanted side-effects. If you try them out I would appreciate the feedback.

Dark Souls Mouse Fix – Initial Reception and Update To Beta 1.1.2

The first release of version Beta 1.0 of the Dark Souls Mouse Fix had kind of a slow start on /r/pcgaming, and at first I was a little bit worried that it might get lost in the stream of news about Ryzen, GDC and Mass Effect: Andromeda. But after a few hours it really gained some traction, also thanks to some additional help from other people who spread the news around. Aside from the expected few people who expressed their disdain to even think about playing the Souls games with mouse and keyboard, the initial reaction was quite positive and it is always nice to see that you’ve helped people to enjoy a game more.

There also was valuable feedback for some problems that were not discovered during alpha testing. I did my best over the course the day to fix the ones that were most severe and updated the fix several times accordingly.

Updates:

Beta 1.0

  • Initial public release

Beta 1.1

  • It is no longer possible to accidentally flip the camera and invert the input by looking too far up or too far down
  • The camera no longer suddenly jumps when exiting lock-on/focus mode
  • The mouse wheel can now correctly be bound to any standard action

Beta 1.1.1 – Hotfix

  • Reverts changes regarding the mouse wheel in the previous update, which introduced a bug that caused buttons and keys to not be usable as a hold

Beta 1.1.2 – Hotfix

  • The mouse wheel can now correctly be bound again to any standard action

This should bring the fix to a level on which it should be comfortable to play for most people.

I’ll definitively continue to work on it, as there are a ton of things that can be improved upon, especially regarding the GUI and implementing additional features, such as truly customizable keybindings, including modifier keys. I was also surprised to see people asking for Steam Controller support, because apparently the mouse fix improves the camera movement with it.

However, I cannot say how much time I can put into it in the next few weeks, because I have to take care of a few other pressing things first.

I’ll maybe write another update on unresolved issues and upcoming features, if people are interested.

Dark Souls Mouse Fix

What is this?

This fix makes Dark Souls use raw mouse input without any additional smoothing or acceleration. It offers a flexible binding system, automatic cursor support for the UI, improved targeting and an easy configuration using a GUI.

Overview

Description

Important: This is a beta version. Although it underwent some thorough testing before the first public release, there might still be some issues that need to be addressed. If you encounter any problems see the Contact And Support section on how to get in touch with me

Although there already is a mouse fix for Dark Souls, which did a great job in helping many people (including me) to play the game with mouse and keyboard over the years, it is not an optimal solution. Because it emulates a controller, there are still some issues with sensitivity, apparent negative acceleration and overall sluggish movement. Using the cursor in the UI is also a hassle, because it has to be manually enabled and disabled via keybindings.

Instead of emulating a controller, this fix injects raw mouse input directly into the game’s camera functions, thereby avoiding any additional transformations. It also provides an auto cursor feature which automatically manages the visibility and capture settings of the cursor depending on the current situation.

Features

  • True raw mouse input without controller emulation
  • No additional smoothing or acceleration
  • Flexible options such as individual horizontal and vertical sensitivities for camera movement and bow aiming
  • Allows any action to be bound to any combination of mouse buttons, the mouse wheel or keyboard keys
  • UI Auto Cursor mode that enables and disables the cursor when in a menu or when switching out of the game
  • Improved target switching
  • Includes a GUI for easy configuration
  • Steam Controller support
  • Compatible with DSFix

Instructions

Supported Versions

This fix only works with the latest, fully patched Steam version.

Important: The fix relies on the layout of the executable. Older versions or ones that otherwise have been tempered with probably won’t work. This also means that if the game were to be patched — which is very unlikely at this point — it might break the fix and require it to be updated.

Install

The fix does not make any permanent changes to the system, the game or the configuration of the game and can easily be removed (see below).

  1. Install Durante’s DSFix if you haven’t already
  2. Extract the contents of the DarkSoulsMouseFix.zip to the same folder. For example: "C:\Program Files (x86)\Steam\steamapps\common\Dark Souls Prepare to Die Edition\DATA"
  3. Look for the dinput8dllWrapper line in DSFix.ini and set it to dinput8dllWrapper DarkSoulsMouseFix.dll. No additional configuration of DSFix is necessary
  4. Start DarkSoulsMouseFixGUI.exe to set mouse setting and keybindings as desired
  5. Start the game normally, for example directly through Steam. If you want to change the settings while in the game, see the Configuration section below on how to do that

A few additional notes on the installation:

  • You should hear a Mouse fix loaded message on game launch when the fix is installed correctly
  • If you currently have DSMFix installed, it is not necessary to remove it. Just replace the dinput8dllWrapper dsmfix.dll entry in DSFix.ini with dinput8dllWrapper DarkSoulsMouseFix.dll
  • It is not necessary to unplug the controller if you have one. You can even enable the controller on-the-fly by using the Input Mode Toggle binding (see Configuration)
  • The GUI requires the Microsoft .NET Framework 4.6.1, which should already be installed on most systems. If you are having problems starting the GUI, you can download the required version here
  • I would recommend increasing the FPS limit to 60 in DSFix for the complete smooth experience. Keep in mind that there are some problems with unlocking the FPS though. You can find more information about that on PC Gaming Wiki here

Uninstall

  1. Set the dinput8dllWrapper setting in DSFix.ini to none and delete the files of the fix

Configuration

Although the configuration using the GUI should be easy and straight-forward, there are some things to note:

  • You can change settings while in the game by using the Reload Config binding, which is per default set to the '-' key on the numpad. Just change the settings in the GUI as necessary, press save and then use the binding to reload the config ingame. You should hear a Mouse Fix Reloaded sound message when the reloading was successful
  • You may also want to enable borderlessFullscreen in DSFix for easier switching between the GUI and the game
  • Although it is not necessary to bind a standard action when you are happy with the ingame setting, it is strongly recommended to exclusively use the bindings in the GUI of the fix
  • It is not necessary to unbind a key or button in the ingame settings to use it with the fix
  • The GUI also provides tooltips with additional information about a setting

Binding System

The new binding system allows you to bind any action to an arbitrary combination of keyboard keys, mouse buttons or the mouse wheel. Instead of manually selecting a key from a limited set of predefined keys, the new system works reactively. To bind an action, double left click the corresponding box. When the box turns green, press the combination of keys you would like to assign. The combination is set once any pressed keys are released.

You should be able to use almost any keyboard key, independent of the keyboard type or layout. The key names are dependent on the layout currently set in Windows. If you are using an English layout, the key names will be in English, while an AZERTY layout will lead to French names. Bear in mind that the key names are automatically determined by using a Windows function and not all keys have pleasant display names.

A few additional notes on the binding system:

  • Each key pressed before another acts as a modifier for the next one
  • Any key can be used as a modifier key, not just ALT, CTRL or SHIFT
  • There is no limit to how many keys can participate in a combination. You can set a combination involving half a dozen keys if you want to
  • The order you are pressing the keys in is only important during the binding process to differentiate between bindings that involve the same modifier keys
  • To unbind an action double right click the corresponding box

Auto Cursor Mode

The Auto Cursor mode automatically manages the state of the cursor behavior depending on the current situation:

  • It captures and hides the cursor when ingame and not in a menu
  • It releases and shows the cursor when in the main menu, in a system menu or when the window goes into background, e.g. when using alt-tab
  • It overrides all cursor settings in DSFix

Non-Standard Bindings

Non-standard bindings perform actions that usually have to be performed by using a context-sensitive key or a combination of keys. They are provided for convenience as they could also be implemented by using external tools, such as Auto Hotkey. Although they do not allow anything that cannot also be done manually, purists of the game might not want to use them.

Movement Bindings

The keybindings to move the character differ on a technical level from those you can bind ingame. They should fix the problem of sometimes not being able roll when running diagonally and not moving the camera at the same time, which existed in the game since launch.

Input Mode

The input mode specifies the behavior of the fix:

  • Mouse and Keyboard: Enables raw mouse camera and keyboard bindings, deactivates controller input and vibrations
  • Gamepad: Standard controller behavior, disables raw mouse camera and keyboard bindings
  • Steam Controller: Standard controller behavior with the exception that the raw mouse camera is enabled and the right analog stick is disabled

Note that:

  • The Auto Cursor setting is independent of the input mode. For example, it is possible to play with a controller and only use the mouse for menu navigation if you want to
  • The input mode can be toggled with the Input Mode Toggle binding. The toggle order is the following: Mouse -> Gamepad -> Steam Controller -> Mouse -> …
  • You should hear a corresponding sound message when the input mode is changed by using the binding

Additional Information

What You Should Know

Since the fix consists of an executable DLL-File, I could have put any harmful shenanigans in there. You just have to trust me that the file is clean.

If you don’t — and why should you — feel free to use a meta online virus scanner like VirusTotal to verify the file. Be aware however, that because the fix uses “hacking techniques” such as injection and hooking, it could trigger anti-virus software without being harmful.

Known Issues

The Auto Cursor currently briefly activates the cursor when opening certain doors with keys. This is not easily fixable but should only be a minor issue, due to the short duration and small number of situations where this problem occurs.

Apparently the dialog that pops up when summoning a co-op partner can currently not be controlled with the mouse cursor (unconfirmed).

Acknowledgments

I would like to thank Kaibz for his extensive testing, detailed feedback and valuable suggestions during the development of the alpha versions of the fix. Without him, creating the fix would have taken even longer than it already did.

Additionally, I would also like to give a shout-out to the author of the original DSMFix for Dark Souls, which allowed me to enjoy several playthroughs of the game over the years.

Finally, I would like to thank Durante, author of DSFix, who made the game playable in the first place. Without his work, everything I’ve done would not be worth much.

Contact And Support

If you like this mod and want to support the development or show your appreciation, you can find more information on my website. There you can also find out more about other fixes that I have done and means to contact me if you have a question, want to provide feedback, bug reports or suggestions.

Version History

Beta 1.4.1 – Hotfix:

  • The GUI no longer loads a local dxgi.dll to prevent conflicts with SweetFX

Beta 1.4:

  • Replaced the binding system with an entirely new one, which allows the binding of arbitrary key combination with almost any key on any keyboard (see Binding System section for details)
  • Added Manual Targeting options that allow the switching of targets by flicking the mouse instead of using a binding (also available in Steam Controller input mode)
  • Added non-standard bindings for Kick, Leap Attack, Dash Only, Roll Only and Auto Run actions (see the corresponding tooltips or the Non-Standard Bindings section for details)
  • Added a custom mouse cursor that should be more suitable for the game. The cursor is enabled by default but can be disabled in the GUI
  • Added audio feedback for certain status changes, such as loading of the mouse fix, reloading the config or changing the input mode
  • Multiple changes to the usability of the GUI, including a revision of the labels and tooltips
  • The GUI no longer loads a local d3d3.dll to prevent conflicts with certain mods/injectors, such as DSPW or SweetFX/ReShade (thanks to SeanPesce for his feedback and research on the issue)
  • The Auto Cursor will no longer enable the cursor and lock the camera when UI elements are shown that cannot be controlled with the mouse, such as subtitles or certain floating messages
  • Fixed a bug that caused the Auto Cursor to not recapture the cursor correctly after having switched out of the game
  • Added a complete initial default config that should be decently intuitive for most player that are not familiar with the game

Beta 1.3:

  • Added preliminary modifier bindings that turn left and right attacks into heavy attacks (see Configuration for details)
  • Made all modifier bindings non-blocking so they can also be used as a modifier in the ingame settings where applicable (see Configuration for details)
  • Added proper Input Mode setting to the config that allows easy switching between mouse and controller input (see Configuration for details)
  • Added experimental Steam Controller support (see Configuration for details)
  • Replaced Toggle Mouse Fix binding with Toggle Input Mode
  • Fixed bug that prevented the number keys from getting bound correctly
  • Fixed bug in the GUI that prevented an action from getting unbound correctly when there was a default binding for it

Beta 1.2:

  • Added option to bind movement to the config. These differ on a technical level from those in the ingame settings (see Configuration for details)
  • Disabled hardware acceleration for the GUI to avoid conflicts with post-processing injectors such as ReShade or SweetFX
  • It is now possible to resize the GUI in vertical direction to use it with low-resolution displays
  • The GUI now groups options by category

Beta 1.1.2 – Hotfix:

  • The mouse wheel can now correctly be bound again to any standard action

Beta 1.1.1 – Hotfix:

  • Reverts changes regarding the mouse wheel in the previous update, which introduced a bug that caused buttons and keys to not be usable as a hold

Beta 1.1:

  • It is no longer possible to accidentally flip the camera and invert the input by looking too far up or too far down
  • The camera no longer suddenly jumps when exiting lock-on/focus mode
  • ~~The mouse wheel can now correctly be bound to any standard action~~

Beta 1.0:

  • Initial public release