As Kevin puts it “The Steam Overlay, which is required for proper Steam Controller usage, injects itself into the render pipeline of the game, in this case, DosBox.”. The second is that even when switching to an output that Steam can hook into, the overlay is extremely sluggish, with most FPS counters reading 1-2 FPS. This results in the problem where games run through DosBox will use the Desktop Config rather than an application specific config. To start with, what exactly are the two issues that are preventing the use of the Steam Controller with DosBox? The primary issues is that DosBox, by default, doesn’t use a display output that Steam can hook into. As usual with my videos, timestamps are located in the description for those wanting to jump between chapters or topics in the video. I’ll explain at the end why I’m not including a method for getting this to work with Dos games purchased through Steam.
#Make a shortcut for the steam controller editor how to#
While the core information will be identical to the guide, I will be expanding on the source material to explain how to easily set this up for Dos games with their original files as well as Dos games purchased through GOG. A link to the guide can be found in the description for those wanting to peruse through that as well. I discovered this method via a Steam Guide that was written by Kevin Connolly and, with their permission, will be presenting that method in this video. I have discovered a single method that makes the two work perfectly. It doesn’t take many attempts at making them cooperate to come to this conclusion. The Steam Controller does not work very well with DosBox at all.
0 kommentar(er)
