Vapor Dosh
Published
The game is perfectly playable out of the box, but there are very minor visual glitches in the menus that don't hinder gameplay. Turning D9VK on makes those go away and the game runs absolutely flawlessly.
Worthy of whitelisting IMO
D9VK is enabled by default in the latest Proton version, so it works perfectly out of the box now.
Works great, the only thing is that the process remains when you leave the game.
Need to kill the processes manually after closing the game.
Appears to work the same as in Windows with the d3dxof Winetricks workaround.
Works excellent in almost every aspect.
I have Logitech F310. The game doesn't detect the controller when it's set to Xinput, but it just works when I switch it to DirectInput.
I used Winetricks to enable a virtual desktop in winecfg.
Normally enabling fullscreen was glitchy and made it impossible to interact with the game properly, while disabling it afterwards crashed the game. Enabling virtual desktop and enabling fullscreen in-game allows for playing in a larger window as a workaround; manually resizing the window (without the fullscreen setting in-game) crashes the game whether the virtual desktop is enabled or not.
Like for others below, the game only shows black screen with version number in bottom left and music in the background. I read somewhere that it probably has something to do with .wmv playback, so I attempted a workaround described here: https://github.com/doitsujin/dxvk/issues/728#issuecomment-459839962 but that makes the game not even show up the black screen.
Remove the line "StartupMovies = "Movies/loading.mp4"" from cm3.ini or the game won't progress past a black window.
The game crashes several seconds after launching. This seems to be caused by game connecting to the Steam Workshop, since I did manage to get past that after switching Steam to offline mode. Unfortunately, the game still crashes on the first level right as you are about to be given control.
Just works out of the box now.
I checked the older versions of Proton just to make sure the improvements didn't result from my hardware upgrade. While it doesn't crash in both new and older versions anymore, current Proton version doesn't require you to modify the ini file.
Works without a hitch as far as I can tell
The game's servers are down as of writing this report, so I couldn't test multiplayer. I might make a new report when they're back up again and I feel like checking out PVP.
I used DSFix, which I had in Windows anyway as well.
The intro cinematic doesn't play. I would use Proton GE to fix that, but the game crashes when launched with this, so I had to use vanilla Proton.
I didn't notice anything out of the ordinary after completing the entire game.
I made it to the final boss just fine. I recommend checking the mouse and avoiding the controller.
The game suffers from stutter when moving with a controller that isn't there when playing with mouse (with proper polling rate), I don't know how to fix that one.
The mouse's polling rate has to be set to 125Hz to be playable, otherwise the image locks up when rotating with mouse. Like other report said, framerate also needs to be set to above 60FPS (or I'm guessing above your monitor's refresh rate, but I didn't test it with any other monitor) for it to be smooth. Setting it to "max" made the game crash, but 120FPS worked great.
Works fine without tinkering (unless you count the Bethesda account skip, which is something to consider in Windows too)
RADV_PERFTEST=rt gamemoderun %command% +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1
For some reason the game doesn't respond to Tab key (needed for the in-game menu with maps and other things) until I switch to the windowed mode and back to fullscreen with Alt+Enter.
"RADV_PERFTEST=rt" is needed to get raytracing on an AMD card; it actually runs pretty nicely on my relatively low end GPU, but the effect is subtle enough that you may as well skip it. Gamemode helps a bit, but you probably won't need it with raytracing disabled.
This part isn't exclusive to Proton and to my knowledge is a thing in Windows as well, but I really didn't want to make the Bethesda account, and skipping it without some workarounds is not an option. I'm still a bit too technologically inept to set a firewall, so the workaround I used is much simpler: switch Steam to offline mode, start the game, make it to the main menu, switch Steam back to online. That way you still get tracked playtime, achievements, and cloud saves.
thcrap_proton -e "%command%"
I used this to make the translation work: https://github.com/tactikauan/thcrap-steam-proton-wrapper
I have given up trying to understand what's going up with performance in this game. I started it and was quite pleased with how it ran on high settings, until one day I loaded it and had my framerate basically halved. I switched to Proton GE, which did help, but then the problem reappeared. I saw someone in the forum suggest running the game in offline mode, which did appear to have an effect too, but it was temporary and the framerate went down again after a few minutes. I thought I figured it out when I noticed it performs better once more if I run the game right after launching Steam, but that stopped working the next day too. The game never turned unplayable, but in the end I just gave up and lowered the settings a bit. I suspect Denuvo is messing with it, but I'd probably need the GOG version or something to test this hypothesis.
The only reason I'm listing the game in Tinker category instead of SteamPlay is because of a small problem that may have just been unique to me. The game refused to progress past the black window even after disabling DXVK like others recommended. Turned out the reason was that the game refused to launch when Daifukkatsu.ini file in the game folder was missing. Making a blank file with that name allowed the game to start and be configured.
It's playable over all, but freaks out when changing between fullscreen and windowed mode - it either gets really glitchy, or outright crashes. Luckily, it remembers which setting you picked when you start it again and runs well afterwards. Other than that, some fonts look a bit off.
Eggscellent out of the egg carton, no extra steps required
I think the only complaint I have is that it makes my hardware a bit toasty, but that can work well for you if you prefer your eggs hard boiled.
Shows a black window unless PROTON_USE_WINED3D is set.
If the game is set to fullscreen, there is still border from the compositor and the aspect ratio isn't kept. You have to "unmaximize" the window manually when switching from fullscreen to windowed mode, otherwise the window will only show the top left corner of the game area. Other than that, the game is perfectly playable in windowed mode, although I wish there was an option for higher scaling.
I had to enable "D-pad only" option in the config to prevent constant "Up" input with a controller.
Playable, but runs properly only in fullscreen.
Performance issues I mention below only happen outside fullscreen mode.
The game runs at full speed only in fullscreen. Running it in the window makes it considerably slower, it feels like it runs at half the speed.
The game crashes if the resolution set in-game is the same height as my native resolution.
Barring shutting the game down, works as well as the first game
The game freezes when trying to close it from the main menu, has to be closed with e.g. Alt+F4
Black screen for a short moment, then closes itself.
Enabling WineD3D makes the black screen stay slightly longer, but the end result is the same. Messing with esync, fsync and seccomp does nothing.
Still just a black screen.
If you consider black screen staying long enough for the Steam overlay messages to appear an improvement, you could say there's progress, but it's still just not working. WineD3D actually gives a worse result than default now and the game crashes almost instantly with that option. Disabling Esync with nothing else on makes it stay the longest, it's probably your best bet if you can actually make the game run like the other reports say.
Same thing with another GPU
I reanimated my other GPU and wanted to check if the game works. It still doesn't, both Nvidia and AMD don't handle it.
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
Disabling esync and fsync is necessary to make the game run properly. It launches without that, but softlocks on the character creation screen. It also seems to reduce loading times.
I'm making the report after getting my new PC, so I don't know how much difference this makes. I don't think either of my GPUs were a problem, but my old CPU met the minimum requirements, so I'm not confident it was to blame either.
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 gamemoderun %command%
The framerate can get very low without gamemode. Enabling gamemode significantly improves it, but there is still a bit of slowdown during combat when action picks up. There's also the mail menu that's very choppy regardless of the settings, but that one can be tolerated.
Repeating from the previous report: Disabling esync and fsync is necessary to make the game run properly. It launches without that, but softlocks on the character creation screen. It also seems to reduce loading times. Proton GE is necessary to make the FMVs play. For some reason they don't with GE version 7-39, but 7-24 has no problem. Like stated before, in my opinion gamemode is necessary to make the game run acceptably: https://wiki.archlinux.org/title/Gamemode
Managed to beat the game fine with no special settings.
Taking screenshots doesn't work for some reason, even though the overlay does.
5.11-GE-3-MF GloriousEggroll
There's a black window in vanilla Proton; I didn't bother with customizing it, simply using the GE version is enough.
There is working sound and the game appears to receive input correctly, but shows only a black screen.
ddr=gdi and enabling DirectD3D is required to make the game display properly.
There are slowdowns, but not bad enough to make the game unbearable.
It does have the same slowdown problem as Teleportals and Maytroid, but it doesn't hinder the experience as much as in those two. Maybe it's because of the type of the game, but I don't have the means to "scientifically" measure the difference, so I'm just going with my subjective feeling.
It's not game-breaking, but I think the sound bug is annoying enough to prevent me from giving this one thumbs up.
Music and character voices work as they should, but all other sound effects are missing.
To fix the sound bug, use: protontricks 282900 xact
ddr=gdi and enabling DirectD3D is required to make the game display properly.
Like with the other games by this developer, there is noticeable slowdown when played in Proton, but this is a type of game where the gameplay isn't hindered by it like in platformers.
Normally crashes on startup, and only shows an error in older versions of Proton, specifically about audio initiation. I was able to launch it with a workaround I found on WineDB: use Winetricks to install xact, then make sure that in Winecfg the xaudio2_4 override is set to use the built in libraries before the native ones. After that, the performance is perfect.
Playable and almost perfect without touching anything, nothing to complain about with WineD3D.
PROTON_USE_WINED3D=1 %command%
Animation looks a bit choppy OOTB. It becomes perfect when the game runs with the WineD3D renderer instead of DXVK.
Still doesn't start on the newest version.
It's odd it doesn't work considering Phantom Pain is quite playable.
5.9-GE-3-ST
I still don't understand how vanilla Proton doesn't handle it, but there's hope now that GE can do it.
Runs excellent with keyboard, but you may want to unplug the controller first.
Controller calibration that happens when the game first starts progressed only when I Alt-Tabbed after each input, then it would detect Up being pressed all the time. Unplugging the controller while the game ran gave me "Error Happened" on repeat.
On launch, only a Chromium window running nw.js shows up; game itself doesn't load at all.
It displays properly (with tinkering) now, but I can't give it thumbs up with the framerate drops.
ddr=gdi and enabling DirectD3D is required to make the game display properly.
It doesn't detect controller by default, but setting "Steam Input Per-Game Setting" to "Forced Off" fixes it.
Normally the performance is pretty good, but framerate tanks hard in the rooms with snow or rain.
Doesn't work, period.
I used to have the diagonal glitch screen problem when I was on my previous GPU. Now the game doesn't do even that, just a silent black screen for a few seconds and then a crash.
Still doesn't launch at all with Proton 6.3-2.
I also tried 6.5-GE-2, same result.
Disregard my previous report, it works fine. :P
No FMVs in normal Proton; I didn't manage to make the game run with newer versions of Proton GE, but it's not the problem with the game itself because other games also don't launch with 6.4-GE and 6.5-GE either for some reason.
The initial installation is required to make the game launch. If you deleted the contents of the Steamworks Shared folder, just verify integrity of game's files and it will download what it needs.
If Wine D3D is not used, the whole collection seems to be locked to 45FPS for some reason and the games run at 3/4th of normal speed. Ironically, this makes MMX4 run worse unlike the previous three games and it gains a few frames with DXVK, but still doesn't reach 60FPS.
protontricks 743890 wmp11 - required to make MMX4 run at all
MMX1-3 ran at regular speeds, but had occasional framedrop for some reason. MMX4 refused to run at full speed no matter what.
Part of it might be because I'm technically a bit below minimum requirements, but I'm bummed I couldn't get X4 to run at full speed. Tweaking the config.ini didn't really help and I don't know what else to try in Linux.
GE is needed to make the FMVs play, haven't noticed other problems.
I tried several Proton versions, none of them worked.
6.5-GE-2 was the most successful, letting me see a "Checking system data" message before getting stuck on the black screen - controller does nothing, and pressing Enter crashes it. 4.11-13 shows an "Unable to initialize steam libraries" error. Other versions I tried either show a black screen for a moment and crash, or just crash right away.
I reached the ending credits, it's playable as long as long as you switch to WineD3D to fix fonts.
WineD3D fixes the broken fonts.
Alt-tabbing crashes the game in fullscreen, but works fine in windowed mode.
As an aside, this is not a problem with Proton, but the game doesn't support multiple resolutions, all you get is 800x600 window or fullscreen with at least aspect ratio kept. You'll probably get better experience if you can figure out how to make the game run in a bigger window in Linux.
Controller support is broken, directional buttons behave odd even when using keyboard while gamepad is plugged in. There is an option in the menu for disabling D-pad/analog stick, which makes the game run with keyboard with no issue and lets you use something like AntiMicro. Rest of the game runs flawlessly as far as I can tell.
If you're fine with how the game looks out of the box, no need for tinkering. However, I recommend using the LodMod.
WINEDLLOVERRIDES="dinput8=n,b" gamemoderun %command%
I found the way the game handles level of detail jarring, so I downloaded a visual mod.
https://github.com/emoose/NieRAutomata-LodMod
The mod initially refused to work for me until I renamed xinput1_4.dll to dinput8.dll; you might not need to rename it, so adjust the launch option accordingly.
Anti-aliasing settings impact the performance to a greater extent with LodMod enabled - MSAA 8x makes it practically unplayable. I ended up using SMAA for most of my playthrough. Also I followed the suggestion from other reports to enable gamemode, but I didn't notice much difference with it, your mileage may vary.
(Report based on the demo version) Everything seems to be in order when it comes to graphics and sound, but controls ruin it.
The crystal necessary for progress often stops responding to mouse input and can't be moved until the window is fiddled with automatic grabbing onto it or edge of the screen.
The crystal's position also happens to be ignored at times, appears to be the same as when it can't be moved with mouse.
My desktop environment is KDE Plasma. I haven't tested the game in other environments, so I'm not sure if e.g. XFCE would handle it better.
With scaling set to pillarbox there are some visual glitches, like sprites showing on top of objects that cover them or some strange artifacts. Scaling set to stretch fixes these glitches, but that option cannot be used in windowed mode and it automatically makes the game go fullscreen, so you can't play in window without those glitches.
I used autoexec.cfg from this guide: https://steamcommunity.com/sharedfiles/filedetails/?id=1813176155
The screen is completely black and unresponsive with only the menu theme playing if the game's resolution doesn't match the system's native resolution; that's easily solvable with the guide I linked. It can be a problem if you have a very weak hardware and don't want to turn other settings down too much.
Game only has sound in safe mode and the graphics are rather blurry. I also had problems with my controller. While it was plugged in, the character kept walking upwards and the game didn't let me reconfigure the controller settings; the configuration first asks to press up on the D-pad, but it ignored any input from the joypad. Rest of the game seemed to run fine when I unplugged the pad.
Doesn't start, Steam just shows it as running for a few seconds and then nothing.
WINEDLLOVERRIDES="ddraw.dll=n,b" %command%
I did what other reports did and used Protontricks to install mfc42.dll.
I have Logitech F310, which has a switch that allows it to use either XInput or DirectInput. The game detects neither.
I beat the single player mode with no tinkering.
I didn't get a friend to play co-op with me yet, but it's local only and I don't think Remote Play should cause any issues.
Button prompts for controller don't show up properly, so for example "Press A to retry, Press B to go back to menu" becomes "Press to retry, Press to go back to menu"
6.20-GE-1
Character voices don't play in regular Proton, which is fixed by using the GE version. What isn't fixed is the things I mentioned in the performance part.
From what I've seen in the forum, it seems to be a problem with the port itself rather than how Proton handles it, but Shenmue I is a CPU resource hog. I admittedly have a rather weak CPU below the official requirements, but there were some Windows users with much more powerful CPUs that complained about it too. There are a few cutscenes and one place (part of Dobuita) where large CPU load makes the audio sound really choppy, which wouldn't be a huge problem otherwise, but that place has to be visited very often throughout the game. It didn't help me since my CPU is plain too weak, but for someone with a stronger CPU it might help to mess with the CPU governor. It at least doesn't seem to affect framerates much, so it's just annoying rather than unplayable. Shenmue II, on the other hand, ran without those problems.
I tried playing with bots and a match online - just works.
Game starts out fine out of the box, but shuts down with no error message after about a minute. Disabling Esync fixes it, and I didn't notice other issues after reaching the credits.
Just like others, I needed msvcirt.dll to make the game run, then it's almost perfect. I did have problems with mouse, but according to the forum this happens on Windows as well; I solved that by lowering my mouse polling rate way down to 125 Hz, anything higher than that felt unplayable.
Unfortunately, Proton 5.0-1 doesn't help, the game still doesn't work.
Goes as far as the splash screen and shows the game's custom cursor, but only ends up with a black screen.
The game works now, but in the current state it's only playable with keyboard and mouse.
The game technically detects the controller, but it only works in menus. The control scheme only shows KB+M, and the character and camera ignore controller input.
Shows only a black screen. There is working sound and it seems to accept input, but it's impossible to play when there's nothing visible.
I tried the ddr=gdi workaround with Protontricks that someone else suggested, but it didn't change anything at all.
ddr=gdi workaround combined with enabling WineD3D is required to make the game run.
Some of the levels play really slow, while others are very smooth. The first level is one of those with slowdown, while the next few work excellent.
I no longer have the black screen after additional modifications, and it's technically possible to play now, but the slowdown prevents me from giving it thumbs up.
ddr=gdi workaround works if you switch to DirectD3D rendering.
Some levels work excellent, while others suffer from significant slowdown. The first level for example has poor framerate, while the next few are very smooth.
It more or less works, but I can't give the game thumbs up with the slowdowns I experienced.
FMVs don't work, and the game softlocked for me at the end of the airship section at the beginning, where an FMV would play. If movie playback is disabled in the configuration program, then the performance is basically perfect.
Throws "Cannot load library nw_elf.dll" error and doesn't load.
Something that may give a clue to someone better with getting things to work: I tried what this Steam post said ( https://steamcommunity.com/app/594950/discussions/0/1733217528128966631/#c1639790664942624210 ) and loaded nw.exe using the game's WINEPREFIX and Proton's executable. The game still didn't start, nw.exe was just a black window itself, but it did delay the error message until after I killed the nw.exe process.
Finished the VN fine.
The window and the game process don't go away when exiting the game, it has to be either stopped through Steam or get the process killed manually.
thcrap_proton -- %command%
The window is always in focus so you can't Alt-Tab normally, you have to minimize it instead.
This doesn't happen in the unmodified game, only with the translation tool: the thcrap process still runs after exiting the game, so you have to manually shut the game down in Steam or kill the process.
I used this to make thcrap work: https://github.com/tactikauan/thcrap-steam-proton-wrapper
The game works perfectly fine out of the box in Japanese. Getting it to work with the English patch is a bit trickier.
Custom translation tool: https://www.thpatch.net/wiki/Touhou_Patch_Center:Main_page
While the game itself is handled with no problems, the thcrap translation patch proves to be annoying. The normal version of the program doesn't work, so I had to download the standalone version, rename "th17 custom (thpatch-en).exe" to "custom.exe" (backing up the original custom.exe first), and run the game by picking "Launch Configuration Tool". If it does work, I recommend deleting the thcrap_update.dll file inside the thcrap subfolder.
Normally throws error "can't create Direct3D device." and closes. Using PROTON_USE_WINED3D=1 launch option fixes that and makes the game run perfectly fine.
Normally throws error "can't create Direct3D device." and closes. Using PROTON_USE_WINED3D=1 launch option fixes that and makes the game run perfectly fine.
Normally throws error "can't create Direct3D device." and closes. Using PROTON_USE_WINED3D=1 launch option fixes that and makes the game run perfectly fine.
-game Unofficial_Patch
Used Protontricks to install the unofficial patch like other reports suggest.
Can crash when loading a new area. Most of the crashes happened to me early in the game and it seemed to stabilize after the first story act, but I still got some close to the end.
3.16-9 was the only Proton version that ran the game normally for me. I wanted to see if I can run it with DXVK (since 3.16-9 predates inclusion of D9VK and it's a DX9 game), but to no avail. I did try briefly running it in 9.0-2 with the WineD3D renderer, but I saw no benefit to it and it also broke the overlay.
Occasionally softlocks in fullscreen, but it doesn't have this problem in windowed mode.
Media Foundation is required, otherwise it gets stuck on a black screen.
FMVs don't play, but it's easy to skip them. Text doesn't show properly, all the characters are replaced with closing square brackets. There are very long loading times and the game is overall sluggish and not very responsive - loading a save takes a solid minute, and the game can take seconds processing actions in battles and menus that would normally be instant. VN sections seem to run fine other than the glitched text.
6.1-GE-2
It's not as bad as I remember from the last time I tested this game, but general sluggishness still makes it a bad experience. PROTON_USE_WINED3D=1 %command% seems to improve it further a tiny bit, but not enough to make it playable. Loading times are significantly better this time, but still longer than they should be.
FMVs play only if Proton GE is used with PROTON_USE_WINED3D=1 %command% in the launch options; no FMVs at all with vanilla Proton, and there's only sound during the video in Proton GE without the launch option.
At the very least the text is now readable OOTB in both normal Proton and GE, so the only thing that holds it back is the performance.
Nothing out of the ordinary except strangely poor framerate, but according to the forums it happens natively too.
Framerate, controls and sound work pretty well, but I wouldn't try going through the whole game with graphics this glitchy.
Tried making a 32-bit prefix, game refuses to launch with it at all.
Textures don't show up normally, some are missing and a lot of them are just random colors and gradients. On my machine it looks just like in someone else's old report: https://github.com/ValveSoftware/Proton/issues/1688
I think one of the errors I got in the log file could hint at what's wrong: "fixme:d3d8:d3d8_vertex_shader_init Usage 0x10 not implemented." Something to do with how Wine/Proton handles DX8, but I have no idea what to do about it.
The graphical glitches are now fixed, the game is now actually playable.
I have Logitech F310, which supports both XInput and DirectInput. If set to XInput mode, the camera keeps spinning to the right, but it works fine with DirectInput. I didn't have that problem last time I tested the game, and I don't know why.
It's working way better than the last time I tried, except a bug with the controls. (see above) It should still be perfect if you play with DInput controller or KB+M.
5.9-GE-3-ST GloriousEggroll
The text only appeared properly when I switched to Proton GE and deleted the file "lang/en/system/font.bin" in the game folder; for some reason I couldn't see any text in regular Proton, while without removing that file in Proton GE there are boxes instead of normal letters.
Rarely the background in the starting menu is completely black, but other elements remain and the menu is completely navigable.
I could not get FMVs to play. I tried tweaks suggested for other Ys games and Trails series, but they didn't work in this one.
5.9-GE-3-ST GloriousEggroll
I had to switch to Proton GE as well as remove the "lang/en/system/font.bin" file from the installation folder to make the text appear properly. In regular Proton the text didn't appear at all, while in Proton GE it showed boxes instead of normal character if the file remained.
Rarely the background in the starting menu is completely black, but other elements remain and the menu is completely navigable.
I could not get FMVs to play. I tried tweaks suggested for other Ys games and Trails series, but they didn't work in this one.
I'm reuploading the report because the customization got completely overwritten by Proton GE data. In case it gets overwritten again, here's what it says: I had to switch to Proton GE as well as remove the "lang/en/system/font.bin" file from the installation folder to make the text appear properly. In regular Proton the text didn't appear at all, while in Proton GE it showed boxes instead of normal character if the file remained.
Game itself doesn't start, only goes as far as the settings window.
The game is already a pain to get working on modern Windows setups, doesn't look like it will be easy on Linux either.
Proton-5.8-GE-2-MF GloriousEggroll
Proton-5.8-GE-2-MF; the game still crashes with non-GE Proton.
Shadows outside battles look off on higher settings, it's more passable if the shadows setting is set to lower. For comparison: https://steamcommunity.com/sharedfiles/filedetails/?id=2108681501 https://steamcommunity.com/sharedfiles/filedetails/?id=2108681666
The framerate drops from time to time, usually when entering new areas. It becomes smooth 60FPS after a moment.
I tried PROTON_USE_SECCOMP=1 suggested in another report, but the game works about the same to me with and without this launch option.
I did try using dgVoodoo2 before, but didn't succeed until I saw another user's report, now it's perfect.
Download dgVoodoo2, extract needed files as QuickGuide.html says, and put this in the launch options:
WINEDLLOVERRIDES="ddraw.dll,d3dimm.dll,d3d8.dll,d3d9.dll=n,b" %command%
I recommend also putting dgVoodoo.conf in the folder and adjusting it to get rid of the watermark and get some better visuals.
I wish I figured this out myself, since I was using dgVoodoo2 to get the game to work properly on Windows.
Played from start to finish (didn't reach the secret stage though)
Game itself works great out of the box with no extra tinkering. I also managed to make the fan translation work.
You can optionally use "LANG=ja_JP.utf8 PROTON_USE_D9VK=1 %command%" as launch options, the former to make Japanese text appear properly in configuration menus, the latter may make your game run better, but it could also make no difference.
As for translation, I had to specifically download standalone patch for this particular game, unpack it into the game's folder, then rename "th16 custom (thpatch-en).exe" to "custom.exe" (rename original custom.exe to something else beforehand), and run the game by picking "Launch Configuration Tool". If thcrap updates break the patch to you, disable updates by going to thcrap subfolder and removing/renaming thcrap_update.dll.
