Return of Reckoning

Hey guys

I keep crashing on dx12 when changing zones, did anyone had this problem? Is there any workaround?

I crash with that issue on Vulcan, I don't think there's a work around unfortunately..

Scottx125 wrote: Wed Apr 02, 2025 4:44 pm I crash with that issue on Vulcan, I don't think there's a work around unfortunately..

The 3d9 dll included in Sildur's pack isn't the most optimal.

Use this one here: https://gitlab.com/Ph42oN/dxvk-gplasync ... type=heads.

Pulptenks wrote: Sat May 10, 2025 2:08 am

Scottx125 wrote: Wed Apr 02, 2025 4:44 pm I crash with that issue on Vulcan, I don't think there's a work around unfortunately..

The 3d9 dll included in Sildur's pack isn't the most optimal.

Use this one here: https://gitlab.com/Ph42oN/dxvk-gplasync ... type=heads.

Thanks I'll give it a try!

Rydiak wrote: Sun Oct 06, 2024 6:29 pm A heads-up to any player with a modern AMD gpu, driver 24.9.1 added driver-level frame generation with AFMF2. Using Sildur's addon with a modern API (dx11, dx12, vulkan) will allow you to run AFMF2 (enabled when using the "HYPR-RX" graphics preset in the AMD Adrenaline software) in RoR and achieve 200 fps. Definitely noticeably smoother gameplay in areas that would otherwise have caused visual slowdowns.

Landuin85 wrote: Sun Nov 24, 2024 8:53 pm

Rydiak wrote: Sun Oct 06, 2024 6:29 pm How did you get the function to work with the game? In my case it shows the error message (AMD Adrenalin) that the GPI does not match.

I installed the Vulkan hook in the game folder, directed AMD Adrenalin to the 32-bit exe, set the game in Adrenalin to HYPR-RX, and enabled AFMF2. Works flawlessly.

@Rydiak Thank you!
I was previously using OpenGL but I noticed that Reshade stopped working at some point (Note: You can always tell if its working when you launch ROR and you see "Reshade" window temporarily appear during the "LOADING" screen) so I removed it (and all associated files) and reinstalled it with Vulcan this time.
I have a AMD Radeon RX 6700 XT gpu w/ Windows11 OS, but my AMD Software: Adrenaline Edition" showed my gpu driver was set to a later version unfortunately.
1. I had to go to Device Manager, selected my GPU > properties > rollback to previous driver > It then set it to a previously driver before 24.9.1 so then I downloaded that driver manually and installed it (uninstalling driver might be a bad idea from what I researched from others online, if anyone doesnt have rollback they should seek advice elsewhere to make sure they dont break their PC,etc).
2. I then added the game in "Gaming > ellipsis > "Add a game..." > WAR.exe (not WAR64).
3. I then clicked on it and set it to "HYPR-RX" mode and enabled "AMD Fluid Motion Frames 2" to enable AFMF2.
4. I then set Idle FPS to 30 (AFMF2 will set it to 60fps ingame) and then Max FPS to 100( AFMF2 will set it to 200fps ingame).

Side note: I did initially try @Pulptenks dll (dxvk-gplasync-v2.6-1.tar.gz) and renamed it with Vulcan's default name (D3D9.dll) but it didnt work for Vulcan, Reshade wouldnt launch, so I just recommend using default D3D9.dll that comes with the Vulcan folder.

5. For RORLauncher, I did this to allow support over 100fps:
RORLauncher > cog icon > "Client Version" > "Experimental"

Reshade works great, except for 1 issue.

I noticed that whenever I click the ingame "Prt-Scrn" button to take a picture, it crashes the game.
6. So what I did as a workaround is unbind the printscreen key ingame, and downloaded "ShareX" from the Microsoft Store to use it as a replacement.
In ShareX, I did "Application Settings" > "Paths" > "Use custom screenshots folder:" and entered "C:\ReturnofReckoning\screenshots", it automatically creates a folder by month in that location.
I also disabled sounds for post-capture in ShareX app by:
"Task Settings":

• leave check for "Play sound after capture is made" (camera sound)

• uncheck "Play sound after task is completed"

• uncheck "Play sound after action is completed"

If I find any more issues I'll make another comment.

It seems that for people with AMD cards that Vulcan w/ 24.9.1 is confirmed stable for Reshade 5.6.0

Another issue I noticed is that Reshade will automatically save all image captures as .png files in the "ReturnofReckoning" game folder, which can take up alot of space over time so its a better idea to turn that off (its redundant/wasteful anyway if you use another image capture app like ShareX, whatever).

When you launch the game,
after your character appears, press the "Home" button > "Settings" tab > "Screenshot Key" field enter something you would never use like "Ctrl+P".
Exit game.
Relaunch game.

Its also a good idea to save your ShareX pictures as JPEG instead of default PNG, if you have ShareX then do:
"Task Settings" > "Image" change "Image Format" form default PNG to "JPEG"

Pulptenks wrote: Sat May 10, 2025 2:08 am

Scottx125 wrote: Wed Apr 02, 2025 4:44 pm I crash with that issue on Vulcan, I don't think there's a work around unfortunately..

The 3d9 dll included in Sildur's pack isn't the most optimal.

Use this one here: https://gitlab.com/Ph42oN/dxvk-gplasync ... type=heads.

Thank you @Pulptenks.

After a second round of tinkering and testing your newer, recommended version of d3d9, I noticed that using Vulkan with the normal "D3D9.dll" that it originally came with from Sildur's Reshade was causing my WAR client app to randomly crash mid-game sometimes, which was frustrating.

I tried turning off ProcessLasso, but it still kept randomly crashing the entire game instantly every once and a while.

I went in my ROR installation folder, deleted Vulkan's default "D3D9.dll" and then replaced it with the named "d3d9.dll" from dxvk-gplasync-v2.6-1 in the "x32" folder (putting it in the ROR installation folder), Reshade w/Vulkan was then able to finally launch and it then caused the game to stop crashing periodically, even during fort (with my Process Lasso enabled too).

For some reason the d3d9.dll from the "x64" folder was causing Reshade to not launch, but it would launch with the "x32". Anyway, now my game is playable again!, thanks a ton.

Khelqhaineion wrote: Sun Jun 08, 2025 3:07 am

Pulptenks wrote: Sat May 10, 2025 2:08 am

Scottx125 wrote: Wed Apr 02, 2025 4:44 pm I crash with that issue on Vulcan, I don't think there's a work around unfortunately..

The 3d9 dll included in Sildur's pack isn't the most optimal.

Use this one here: https://gitlab.com/Ph42oN/dxvk-gplasync ... type=heads.

Thank you @Pulptenks.

After a second round of tinkering and testing your newer, recommended version of d3d9, I noticed that using Vulkan with the normal "D3D9.dll" that it originally came with from Sildur's Reshade was causing my WAR client app to randomly crash mid-game sometimes, which was frustrating.

I tried turning off ProcessLasso, but it still kept randomly crashing the entire game instantly every once and a while.

I went in my ROR installation folder, deleted Vulkan's default "D3D9.dll" and then replaced it with the named "d3d9.dll" from dxvk-gplasync-v2.6-1 in the "x32" folder (putting it in the ROR installation folder), Reshade w/Vulkan was then able to finally launch and it then caused the game to stop crashing periodically, even during fort (with my Process Lasso enabled too).

For some reason the d3d9.dll from the "x64" folder was causing Reshade to not launch, but it would launch with the "x32". Anyway, now my game is playable again!, thanks a ton.

Process lasso is useless with RoR. It's a coding limitation from the game. It would need to be rebuild mostly from ground up. The reason x32 work is because the game on "Experimental" is a x64 wrapper, not true. But that does allow dual core to happen.

It's not without flaws however, the reported result between default and experimental varies. In all honestly the only way to increase performance is to get a CPU with high GHZs, over many cores.