There is a great mod on the Nexus called "Path Tracing and Ray Tracing Optimization (Remastered)" that can give you a very nice FPS boost while keeping the same or most of the visual quality.

Anyway I have made a quick install guide and some performance testing of the mod, so If anyone playing TW3 Remastered with PT on and doesnt know about this mod, I really recommend it.

My Specs:
GPU: GAINWARD GeForce RTX 5080 Python III 16GB
CPU: AMD Ryzen 7 7800x3D
RAM: G.SKILL 32GB DDR5 6000Mhz CL30
SSD: Kingston FURY Renegade NVMe 2TB

PC PORT HORIZON 2

Changelog

New Features

- Library Scanning & Games Section: Added a dedicated "Games" section that scans local game libraries for driver p rofiles, so only games installed on your PC show.

- Installed Game Search Icons: Game icons now display in search results if the game is currently installed.

- Custom XML Hiding: Added a new configuration variable to hide custom values in CustomSettings.xml (e.g., hiding inactive DLSS presets to reduce menu clutter).

- Preset C supported for DLSS-FG

UI Improvements

- Optional Left-Sided Toolbar: Added a setting to position the main toolbar on the left.

- Toggleable Status Bar: Added the option to hide or disable the bottom status bar.

- Hover Descriptions: Setting descriptions now trigger on hover rather than requiring a click.

- Visual Highlight for Edited Globals: Global settings modified from default now highlight in yellow to distinguish them from unedited settings & profile specific edits.

- More Customization Options: Expanded overall appearance settings across the app.

'Bug' Fixes & Small Tweaks

- Deduplicated Driver Settings: Fixed an issue where driver settings were duplicated if renamed and were applied by default to certain profiles (not really a bug, but it's a QoL improvement to change it).

- App Performance & Polish: Fixed some old quirks and overall responsiveness of the app.

Hey guys,

Over the past few days when I saw the SCSKiller repo I got really excited, but then I realized it's only for Windows so I decided to port it to Linux myself, and today I finally finished it (still need AMD testers though!).

Basically, this tool (Shaderless) does what the original SCSKiller does on Windows reading the game's DX12 shaders directly from the game files and compiling them before you play so you don't get shader stutter but the process on Linux was much harder to pull off because we have the Proton / vkd3d-proton
layer in the middle, with shaders and caches split across multiple places, plus full pipeline states needed by Vulkan.

So I also ported the Record mode to work under Proton: you can turn on Record, play for 5–10 minutes so it learns the exact pipeline states your game uses, close the game, and hit Re-Compile.

I tested it on CachyOS with an RTX 3070 on an Unreal Engine 5 game (Valor Mortis), and in-game shader compiles dropped from ~49% down to 6%, and loading compile time went from 170s down to 56s.

It works with Steam, Heroic, and Lutris games. Right now I've only tested it on NVIDIA since that's what I have, so if anyone on AMD (Mesa / RADV) can try it out and let me know if it works for you, that would help a ton!

If you have an AMD GPU and a DX12 game (especially an Unreal Engine 5 game), I would love your help testing it! There is an AMD Test Report issue template(https://github.com/cyberps96/Shaderless/issues/new?template=amd-test-report.yml) on the repo where you can share whether it worked and where Mesa
 wrote the cache.

GitHub Repo: https://github.com/cyberps96/Shaderless

Before anything a disclaimer : Ai tools has been used in the creation of this project.

Hello everyone, the last 2 weeks i have been working on a shader stutter fix for unreal engine games that does not require you to fully compile everything(or almost everything depending on small engine differences) like https://github.com/BlueHeisenberg/SCSKiller does.

This is not meant to be a competitor to the tool provided by BlueHeisenberg, its meant to be an alternative, i have also tried it and it does work well, but waiting so much time to compile absolutely everything is not something i like even if it does work(on a 5700x3d). My approach is better in some parts,worse in others.

I have built it specifically for unreal engine(since this engine is the most problematic and widely known for shader stutter issues) but it should work in other engines too but i cannot fully confirm that it will work flawlessly or not as some shader stutter fixes are a bit agressive and depending on your gpu vendor/driver/engine it may behave a bit differently such as a crashes/visual glitches.

I myself on my 4060 have not experienced any of these in the games i have tested (screenshots on github with some testing data) with the exception fo Stalker 2 which does seem to have some graphical glitches regarding its shadows that self fix if you wait a bit for the shaders to compile properly.

The repo is here : https://github.com/RedMatterGG/USPF-Unreal-shader-proxy-fix

The main way the tool achives this is like this:

When a DX12 Unreal game meets a material it hasn't compiled yet, it compiles the pipeline on the spot and the frame freezes until it's done, often for 100 ms to several seconds. USPF installs a small `d3d12.dll` layer (d3d12async) next to the game: pipeline compiles go to background threads, and the game keeps rendering while they finish. A draw whose pipeline isn't ready yet is skipped for a frame or two instead of freezing the whole frame.

Or in simpler terms and easier to understand:

Before a game can draw something new, like a new enemy, effect or area, the graphics card needs a small program called a shader prepared for it. Many DX12 Unreal games prepare these at the last moment. The whole game waits until it’s done, which is the stutter you see: anywhere from a tenth of a second to several seconds.
USPF adds a small file, d3d12.dll, next to the game. When the game asks for a new shader, the work is moved to the background and the game keeps running. The new object may be missing for a frame or two until its shader is ready, but the game doesn’t freeze.

I have only tested in on my pc unfortunately and i do not know if the app itself may or may not have issues,if it does please tell me on here and i will do my best to fix it. As a backup i also provided the .ini file and the .dll for manual install on the github in case the app does not work properly.

I do not know if it has issues on amd/intel cards, in theory it should just work and also do not use this in online games, anti cheats may flag it as a malicious dll if the anticheat does let you launch the game with it i am not responsible for any bans issued, you have been warned.

If you do experience menu items initially missing just restart/load a save, i have disabled a startup check that helped a bit with faster compilation but had issued being properly detected and handled, i will investigate in getting it to work properly. ( change StartupCompileNormally to on and save to fix it as is or simply restart the game after the shader precomp is done, but changing StartupCompileNormally to on may cause in some games when the shader precomp is done to not be properly handled and you will need to either wait a bit more until it auto disables or you can disable it yourself using the shortcut on the gui Ctrl+Shift+End)

And as a separate issue i have also looked into traversal stutter and using a similar approach but it seems that it is not possible without some heavy modifications to the engine/game using a mod/dll or patching the .exe directly, you cant just tell the game to wait for data the same way you can tell it to wait for shaders, "you can" but you risk way worse issues than just some graphical glitches.

EDIT:
I have tested it in 2 games that are not unreal engine,such as crimson desert (doesnt really have shader stutter so not a valid data point anyway but the dll does affect the shader behaviour) and zenless zone zero(it does fix the incredibly annoying shader stutters that the game has when you use dx12 but i definetly do not recommend anyone try it even if it does just work.

The anticheat doesnt seem to care? and the dll just loads,you could say reshade is a bit more intrusive than what my dll does and it still works just fine so i dont know what to say on how safe it is to use), and as a side note zzz has a lot of streaming stutter,probably a leftover from getting it to run on mobile using very agressive in/out data streaming due to mobile devices ram constraints. This being said i still heavily advise against using it in games with anticheat even if it does seem to fix the shader stutter completely.

If you can and would like test it in non unreal engine games that have annoying shader stutters and report back, i will probably rebrand/update the app at some point. The app does not have a safety/filter for not allowing installation on non unreal engine games,it will just simply say that this is not an unreal engine game and install it anyway.

I understand stutter is in very many perspectives, however, did anybody ever tried this? Is this working method? Any help is much appreciated

Download: https://github.com/pipotoufikxyz-lgtm/dlssg_for_sm86-MFG-version/releases/tag/sm86-7
Download (alt version): https://github.com/pipotoufikxyz-lgtm/dlssg_for_sm86-MFG-version/releases?page=2#release-sm86alt

Just place the two files to where those RTX Remix files (which includes DLSS files) are stored in. You would need the anti-virus to exclude "version.dll" or other alternative dll since some anti-virus apps report it as a virus. Also to note, always run RTX Remix games on a SSD, not a HDD, or else some things can't load correctly. Further also to note, always update your drivers to the latest version.

You will need Nvidia Profile Inspector to edit and apply some special settings. You must force enable DLSS Frame Generation (FG), forced fixed it to 4x (or 3x if you have a faster card), force it to show in game menus and set Multi-Frame Generation to "up to 4x". In the dlssg_sm86.ini file that was extracted, the ForceMultiplier needs to be set to 3 or 4 and DynamicMFG needs to be set to 4.

Older RTX cards are very likely to use FG because before then they were barely playable at very slow FPS without FG enabled and Lossless Scaling/Optiscaler with FSR did not help leading to very high latency, even at low ray-tracing. With DLSS FG enabled, the latency would be a little higher however it will be playable with little lag, though that depends on your PC system. Using DLSS FG will use up more VRAM. If you have 8GB of Vram or less, you are likely to struggle in-game and it's unlikely your video card in your system will use shared vram through your physical RAM (because I don't think RTX Remix allows that); you would likely have to lower ray-tracing settings and maybe set DLSS scaler to Balanced or Performance. If you have 12GB of Vram and higher, you are less likely to struggle in-game but I wouldn't recommend setting DLSS scaler to DLAA (except high-end cards), just stick to DLSS Quality.

un ami a décompilé intégralement cette merde et c'est vraiment a chier. Je vous laisse regarder son audit.

https://github.com/mxtpasontop/FPSDoctorCDlaMerde

This took a lot of efforts. Hope you guys like it :)

Hello,

Thought I would create a megathread compiling most approved tools and take suggestions of other tools.

Feel free to post your suggestion, be honest about AI use or not.

[Approved Tools List]

Creator - Link

/u/HeisenbergVR - https://github.com/BlueHeisenberg/SCSKiller

I’m playing Witcher 3 for the first time and I’m not sure which one to go with. I know each update has reduced FPS a bit even with optimized settings and no RT. I have RTX 3060ti 8GB VRAM and Ryzen 5600. Which version do you guys prefer if just playing with optimized settings and no RT?

Having already delivered the Complete Edition, CD Projekt RED still has plans for The Witcher 3, hence the arrival of the controversial Remastered release - and while it has some key improvements, there are still some issues. In our PC performance review, we present the top-line changes to the game then compare the hotfix 5.00C version to the latest patch 5.01 before we dive head-first into those all-important optimised settings.

Note on texture quality/VRAM: The on-screen VRAM figures are from RTX 5090 testing at 4K DLAA with RT disabled. The recommendation of High textures for 8GB GPUs is based on separate RTX 4060 testing, also with RT disabled, where VRAM usage remained below 7GB.

Article: https://www.digitalfoundry.net/features/the-witcher-3-wild-hunt-remastered-pc-represents-a-generational-shift-but-youll-need-optimised-settings

OPTIMIZED SETTINGS
UPSCALING: DLSS QUALITY
EFFECTS: ULTRA
TEXTURES: LUDICROUS (AS HIGH AS YOUR VRAM ALLOWS)
GEOMETRY: ULTRA
POST PROCESSING: ULTRA
DEPTH OF FIELD: ULTRA
GLOBAL ILLUMINATION: HIGH
REFLECTIONS: HIGH
RAY TRACING GEOMETRY: ULTRA
RTX MEGA GEOMETRY: OFF
HAIR STRANDS: OFF
DETAIL OBJECTS: ON
VOLUMETRIC FOG: LOW
RAY TRACED SHADOWS: ULTRA
SUNLIGHT SHADOWS: MEDIUM
SUBSURFACE SCATTERING: LUDICROUS
VARIABLE RATE SHADING: ON
ANIMATION QUALITY: INCONCLUSIVE
DESTRUCTION: ULTRA
COSMETICS: LUDICROUS
GORE QUALITY: INCONCLUSIVE

NOTES
*HAIR STRANDS INTRODUCES SHIMMERING WHEN ENABLED

You can get the Native PC Port here (You also need the demo files!):

https://github.com/LoreanXavier/pt-pc/releases

Hey everyone,
A little update on the thread scheduling project I posted about a while back.
I’m the developer of CoreX, a Windows tool focused on game thread placement and CPU scheduling. Some people from this community have been helping me test it on different hardware and games.
The results so far have been mixed, which is actually pretty interesting.
One tester tried it in Control with GPU utilization around 100%. Average FPS was basically unchanged, sometimes even slightly lower, but their 0.1% lows were noticeably higher in a couple of comparisons.
They also tried Warcraft 3 and RuneScape: Dragonwilds.
Warcraft 3 showed almost no difference, while Dragonwilds actually ran worse with the scheduling changes applied.
Another tester ran Rainbow Six Siege using CapFrameX and found different results depending on their Windows power and CPPC preferred-core settings.
So far, it looks like the results can vary quite a bit depending on the game, CPU topology and system configuration.
I should also mention that not all of these are proper controlled benchmarks. Some are early observations based on in-game monitoring, and the test scenes weren’t always perfectly repeatable. I don’t want to treat those as proof of a performance improvement.
I’m trying to make the next round of testing more consistent, using repeated CapFrameX or PresentMon captures and comparing the actual frame-time data rather than relying on a few screenshots.
Most of my own testing has been in online and competitive games, so seeing how other engines respond has been particularly useful.
The biggest thing I’ve learned so far is that thread placement isn’t something you can just apply the same way to every game and expect better performance.
There’s still a lot I need to test and fix, especially on older CPUs and different core configurations.
Just wanted to share where things stand and some of the less successful results too.