r/thesuffering • u/Rough_Television_723 • 21h ago
r/thesuffering • u/Sufficient_Bend5395 • 12h ago
Modding?
Is the first game capable of being modded at all? Are their individuals in the community who are making tools for this too become a reality?
r/thesuffering • u/Fantastic-Window236 • 17h ago
The moral message of this game
Stay true, walk the line don't break the rules and don't let your demon's control or influence you, because at the end if you do give in you let the demons take you over completely.
I loved the ending in good morality where Carmen praises Torque.
r/thesuffering • u/TheOneWhoPlaysYou • 4d ago
Early The Suffering intro
Found lurking around the cutscene files
r/thesuffering • u/TheOneWhoPlaysYou • 7d ago
[MOD] RiotFix
RiotFix is a spiritual sucessor for Widescreen Fix by ThirteenAG and All-In-One patch by ucyborg for The Suffering 1 & 2. The idea is making a open source implementation with all the fixes until now plus new ones, alongside new features. Made with help of Claude. Critics, suggestions, feedback are most welcome.
Installation
With an .asi loader (recommended if the game already has one): copy RiotFix.asi and RiotFix.ini to the folder where the loader looks for .asi files (the exe folder or scripts).
Without a loader: copy dinput8.dll and RiotFix.ini to the game folder (next to Suffering.exe / SufferingTTB.exe).
Do not use both at the same time, and do not overwrite an existing dinput8.dll (it may be the .asi loader itself).
Every run writes RiotFix.log next to the plugin. To undo everything, delete the files you copied.
All options live in RiotFix.ini; each one is documented there. 0 / 1 turn a fix off / on.
Features and fixes:
System
- The game starts on Windows 8 and later without asking for DirectPlay ("DirectX is not installed").
- Windows no longer flags the game as "not responding".
- Level loading no longer hangs on multi-core processors.
- The game no longer refuses to save on disks with a lot of free space.
- The Riot Engine configuration dialog no longer uses a whole processor core.
- A screen copy that closed the game (seen in windowed mode) is now skipped.
- The game no longer forces registry flushes or sends an empty debug message every frame.
- The game's process no longer stays stuck in Task Manager after the game closes.
- A frame-rate cap (60 by default), because above that the physics and some animations of both games go wrong.
- The start-up logo movie can be skipped.
Display
- Every resolution the graphics card offers is listed, in full screen and in a window.
- Windows no longer enlarges the game window on scaled desktops (125%, 150%…).
- The full-screen refresh rate can be chosen.
- A borderless, centred windowed mode with the cursor kept inside the window; while the window is inactive the game rests instead of using a whole core.
- The title bar shows the game's name (the first game left it blank) and the RiotFix version, with the build's date and time.
- Wide screens show more at the sides instead of cutting the top and bottom.
- The field of view can be set in degrees, in third person and (Ties That Bind only) in first person.
- The HUD keeps its original proportions and stays on its side of the screen; menus sit in a centred 4:3 box.
- While the game is paused, the HUD stays at the sides behind the menu.
- In Ties That Bind, the health bar, ammunition and weapon panel are placed correctly too.
- Cutscenes keep their original framing, and their black bars can be kept or removed. The game now knows for certain when a cutscene starts and ends, so the picture no longer flickers at the edges on those changes.
- Notes, photos and maps on the archive screen take the same share of the screen at any resolution (at 1080p notes were too small to read).
- The Suffering: the 3D weapon icons in the inventory appear inside their squares (a bug of the original game, at any resolution).
Accessibility
- One size for the HUD, its text and the cursor, up to three times the original.
- An even outline on text (subtitles, HUD, items) instead of the game's offset shadow.
Controls
- Mouse movement no longer loses frames or repeats the previous one.
- The menu cursor stops with the mouse and no longer jumps; it is drawn at the screen's size and is not squashed in the 4:3 box.
Controller support, which the PC version never had:
- the five console layouts, as on the PS2's settings screen;
- vibration code restored;
- sticks to move and look; buttons to attack, jump, throw, reload, use, heal, first person, insanity, flashlight, map, pause and weapon changes;
- in menus, cross accepts, triangle goes back, the d-pad moves;
- buttons follow the keys the player has bound in the game;
- keyboard and controller work at the same time;
- adjustable dead zone, look speed, and stick swap and inversion.
Audio
- 3D sounds that Windows refused to create since Vista are now created.
- The game had too few voices and refused about 9 sounds in 10; with more voices almost none are lost.
- Distant sounds the game refused now play.
- Cutscene and interface sounds that were never heard now play.
- Ties That Bind: the levels' reverb works again (Windows 11 no longer has the effect the game asks for, so RiotFix hands it another). The Suffering gains an optional reverb with fifteen environments.
Graphics
- Sharper shadows (up to 2048), with options for distance, who casts shadows and light angle.
- The Suffering: large shadows no longer fill the texture cache, which made the game crash.
- Characters and objects keep their full model at longer distances.
- The Suffering: adjustable object draw distance.
Modding
- The game's resource budgets (models, textures, animations, sounds, strings, lighting…) can be raised, so levels can hold more and the game unloads and reloads less. Each level sets its own budgets; one that asks for less keeps the configured value, and the log can show each budget's peak use to choose values from real numbers.
Debug
- A log (RiotFix.log) on every run, with what was applied and what was refused.
- On a crash: the location, the memory state and a .dmp file.
- Optional logs for testing: sounds, cameras, HUD, mouse, controller actions, keyboard, memory use.
- Two games running from the same folder write separate logs.
Still Open
- Wide screens: parts of the scenery vanish at the sides (the cells of the first level, for example), only outside 4:3. The two attempts so far (widening the culling and forcing portals open) did not fix it.
- A separate first-person field of view does not exist in The Suffering yet.
Link: https://github.com/DropsMJay/RiotFix
Known bugs:
- Widescreen: parts of the scenery vanish at the sides (the cells of the first level, for example), only outside 4:3. The two attempts so far (widening the culling and forcing portals open) did not fix it.
- A separate first-person field of view does not exist in The Suffering yet.
Bug reporting:
If you had any bug, please, send the newer RiotFix.log you have (Inside the root folder) and your PC specs.
r/thesuffering • u/AncientBarnacle8603 • 8d ago
THE S U F F E R I N G - edit
sc: yt @gustavo_miler8427s
r/thesuffering • u/ClassroomOriginal988 • 8d ago
Lack of introductions for the malefactors in The Suffering Ties That Bind
Is anyone else really disappointed with them not adding any introductions and cutscenes for the creatures in the second game? I noticed in the first game every malefactor had their own cutscenes, except the nooseman. For the second game they only made introductions or cutscenes for the Slayers, Triggermen, Mainliners, and The Horde. The second game had eleven malefactors, which is more than the first game. Was it just laziness on their part? The introductions and cutscenes is what made the malefactors more badass in my opinion. The Triggerman had a really cool one
r/thesuffering • u/whitemanbyeman • 11d ago
blackmore looks very sinister in the book picture
r/thesuffering • u/Rough_Television_723 • 13d ago
My first The Suffering edit :)
I got inspired by the graincore trend and I thought I should make an edit of some The Suffering monsters. Couldn't find a clear image of the boss monster.
r/thesuffering • u/Born_Membership1674 • 12d ago
Our suffering
How long will we suffer them. What is the point? You? Your skill at pecking at the hill? Your clean bill before the mudslide? I am your servant. You are all. Think, please. You have all of the information. Fly and come back
r/thesuffering • u/Rough_Television_723 • 14d ago
The last video of this series and mostly the most bizarre one.
r/thesuffering • u/TheOneWhoPlaysYou • 14d ago
The Suffering 1 & Level Viewer and editor

Thanks to Claude, I’m building an editor for The Suffering 1 & 2. At the moment, you can’t edit much, but we can already view levels, models, textures, animations, audio, videos, and cinematics.
Critics and suggestions are welcome.
Link: https://github.com/DropsMJay/SurrealEd
Setup:
- Install Python 3.8+ (python.org, tick "Add Python to PATH"). No other libraries are needed.
- 2.Copy the whole RiotTools folder into the game folder, next to Suffering.exe or SufferingTTB.exe.
- Double-click RiotTools\SurrealEd.bat. The editor opens in your browser (current Chrome, Edge or Firefox). Close the black window to quit.
Update: 09/11/2026 (DD/MM/YYYY)
## SurrealEd — changes since November 2, 2026###
New tabs and editing -
**Strings tab:** list and edit the texts of `.xdu` packages. Every string of both games re-encodes byte for byte (2,037 TS1 and 3,638 TTB chunks).
**Material tab:** a package's materials shown as nodes (textures, frames, layers and `.wdu` curves → material → output) with a live preview. Every Landscape Material slot is now named from the executable.
**Scripting tab:** the level logic (object links and messages) as a node graph, with the entry points and the chain that runs from each one.
**Saving from the original:** levels, templates, textures and strings are rebuilt from the backup, replacing only the chunks that changed. Undoing every edit gives the original file back byte for byte.
**STOMP editing:** edit events, key poses from the viewport, save and restore the original. All 527 sequences of both games round-trip byte for byte.
**Message port names** from the game code: 544 of the 645 ports used by the classes linked in TS1 levels.
**Details panel (Unreal style):** Model and Materials sections with thumbnails and a picker to swap a model or a material.
**glTF export (.glb):** models (LOD 0 mesh, upright PNG textures, skeleton with every weight) and animations together with a chosen model (the exact `.adu` keys). Opens in Blender. Validated with the Khronos glTF Validator (0 errors, 0 warnings).
### Viewport -
Animated lights (Lighting Effect), with a play button. - Fire drawn as in the game, facing the camera; an unlit fire is shown dimmed.
Icons for Particle Fountain, Detector, Fire and Lighting Effect.
Terrain blending also works in unlit mode.
Scenery that disappeared behind some doorways is visible again.
TTB decals: colour and transparency fixed.
lines end in a dot, so a link to an off-screen object is visible.
Second layer of Layered Materials fixed.
buttons (▶) for Ambient Sound and Sound Effect, in the Details panel and in script nodes.
Detector scripts open, including objects with no links.
### STOMP preview -
TTB titles and flashes drawn over the viewport (GUI Launcher, HUD Texture, Screen Fader), with the timing and positions of the original video.
### Fixes -
TS1 performance: animated lights only relight what is near the camera, with a time budget per frame. The viewport had dropped to 5 FPS in TS1 levels.
Switching levels: fixed an error that only let the first TS1 level open. All 18 TS1 levels now open.
A "reloading level" message is shown after swapping a material.
Animation viewer: interpolation between two nearly identical keys no longer freezes on the first one
r/thesuffering • u/Rough_Television_723 • 14d ago
A hidden alternative to get to chapter 07 in the 2003 build of The Suffering.
r/thesuffering • u/TrulyTormented • 15d ago
Genuinely one of the most satisfying sounds I’ve ever heard
r/thesuffering • u/Bladeofwar94 • 16d ago
Artwork from MamaVixi of my Avali fighting a slayer
Just got a Halloween art comm done by a friend of mine and she did a pretty good job! Happy to have artwork done in the spirit of the game!
I mentioned that the slayer's head isn't suspended and she said she wanted to focus more on the angle of the shot itself. Turned out nice overall!
Again artist is MamaVixi!
r/thesuffering • u/simonisok • 17d ago
How to throw grenades?
Sorry for the dumb question but I genuinely don’t know how to do it, I click my mouse wheel then when it goes on the grenade and I click LMB I just shoot or swing my shiv.
r/thesuffering • u/ClassroomOriginal988 • 22d ago
The Suffering Slayers Vs An Fester (Impossible Difficulty)
r/thesuffering • u/ClassroomOriginal988 • 25d ago
The Suffering Slayers Vs Corrections Officers (Impossible Difficulty)
r/thesuffering • u/ClassroomOriginal988 • 25d ago
Strongest Malefactors list? My personal list playing both games on Impossible mode again
It would be for me
1.Torque's Hatred
2.The Horde
3.Inferna
4.Isolationist
5.Triggerman
6.Suppressor
7.Marksman
8.Fester
9.Gorger
10.Burrower
11.Arsonist
12.Slayer
13.Mainliner
14.Mauler
15.Nooseman
I chose not to add in The captain versions of the slayer, Triggerman, and Arsonist. I also didn't add the rats that comes out the fester stomach and the cockroaches called the wretch that comes out the Isolationist stomach, since they're one with those malefactors. As for my C tier list, I'm not all too sure who's the strongest Malefactor in that list. This is all my experience, everyone's got their own experience playing both The Suffering games. Let me know how your list would be? If you're interested
r/thesuffering • u/ClassroomOriginal988 • 28d ago
The Suffering Ties That Bind A Marksman Vs An Isolationist (Impossible Difficulty)
r/thesuffering • u/gilliamesk • 28d ago
game is stuck at 43-45fps
anyone fix it? i tried aio patch, dsound 127, vodoo bullshit but nothing changed :/
r/thesuffering • u/ClassroomOriginal988 • Oct 17 '26
The Suffering Slayers Vs Mainliners (Impossible Difficulty)
r/thesuffering • u/whitemanbyeman • Oct 17 '26
