Individual instruction doesn't do much, takes a lot of them for something interesting to happen. Both OllyDbg and 圆4dbg 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. 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. MSDN is the good source when it comes to Windows API. Every program uses some basic services provided by the operating system. It's good to know a bit of C/C++ and some parts of Windows API.

Well, maybe I could explain the individual patches, but every game is different with its own problems and how it does things.

It's not really a simple thing and I probably wouldn't be able to explain it in a way that you'll understand. These patches are the result of analyzing the game's disassembled code by opening its executable file in a debugger like OllyDbg, 圆4dbg. At least I can confirm this if you don't change default install path. 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. It basically prevents the game from running on any other monitor except primary one. The empty display mode list is a bug I fixed in my patch. 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. If anyone has issues, try running The Suffering Settings as ADMIN. Just select the other one that's not highlighted and start the game. In my case, I had 1 video card name as 2 different selections. I was looking under Display MODE (which was blank) instead of Display DRIVER. Seanobi: Don't make the same mistake I did.

Ollydbg tutorial deutsch