any way to change this? It's especially annoying as my secondary monitor is an old 4:3 ratio that I use for my chat while gaming. Also can't seem to fix it as it let me push the game to my main montior reolution to where it can't show now.

Choose the correct monitor from the game's launcher (Riot Engine Configuration), it's under Display Driver.

Don't make the same mistake I did. I was looking under Display MODE (which was blank) instead of Display DRIVER. In my case, I had 1 video card name as 2 different selections. Just select the other one that's not highlighted and start the game. Then you should be good to go.

If anyone has issues, try running The Suffering Settings as ADMIN. That's what I did.

You will have multiple selections with the same name with multiple monitor because Direct3D 9 doesn't give any other information except the name of graphics driver's user mode DLL and the graphics card's name as seen in Device Manager.

The empty display mode list is a bug I fixed in my patch. It basically prevents the game from running on any other monitor except primary one.

https://www.gog.com/forum/the_suffering_series/the_suffering_series_aio_unofficial_patch

Running as admin is not required neither with this patch as long as regular users have write access to game install directory, which is the case by default with GOG version. At least I can confirm this if you don't change default install path.

Dude, thank you! I wish I could make things like this. I'm wanting to learn. Did you do this with scripting or did you do actual coding/programming? I'm curious. If you have answers for this, feel free to shoot me a message! Thanks again!

These patches are the result of analyzing the game's disassembled code by opening its executable file in a debugger like OllyDbg, x64dbg, ... It's not really a simple thing and I probably wouldn't be able to explain it in a way that you'll understand. Well, maybe I could explain the individual patches, but every game is different with its own problems and how it does things.

Yes, it does involve programming. It's good to know a bit of C/C++ and some parts of Windows API. Every program uses some basic services provided by the operating system. MSDN is the good source when it comes to Windows API. But the most important part is learning x86 assembly instructions, something you don't need to deal with when working with games that come with source code. Most of them don't. Both OllyDbg and x64dbg come with the description of individual instructions, but the tricky part no tutorial will be able to explain in general is what the game is trying to achieve by executing sequence of those instructions. Individual instruction doesn't do much, takes a lot of them for something interesting to happen.

I wouldn't consider myself a guru when it comes to these things, there are just certain small pieces of the puzzle I was able to put together and the result are the patches I've made.

I don't see anything that says Riot Engine Configuration anywhere.