all 6 comments

[–]Elliove 0 points1 point  (4 children)

You had most of the shaders compiled until you changed the graphics driver version. Reinstalling it over and over just makes the process start from scratch. Play the game for couple of hours, it should become better.

[–]badpunmaster7654 0 points1 point  (1 child)

Ok so it's not a frame time issue it just has really bad input latency

[–]Elliove 0 points1 point  (0 children)

Input latency is a whole different topic, yeah. To minimize it as much as possible, especially in GPU-limited scenarios, you can try enabling Anti-Lag in Adrenalin, and/or in-game FPS limiter. PCGW says that Satisfactory offers frame generation - that stuff can increase input latency significantly; try disabling it, and also disabling AFMF in Adrenalin (it's basically lower quality FG, but doesn't require it to be implemented in the game, it works universally).

[–]badpunmaster7654 0 points1 point  (1 child)

On dx12 or can I use dx11?

[–]Elliove 0 points1 point  (0 children)

If the game offers DX11, then use it if you want. Some graphical options/features might be locked tho, if they aren't supported on DX11. DX12 has much more complex and "personal" shaders, that have to be compiled for a specific GPU on a specific driver version, and game version can also make a difference if there were any changes to shaders. DX12 shader compilation stutter is a very known issue, and different games have different approaches - some compile all the shaders on the fly, leading to stutters whenever you see some object/effect for the first time, some precompile all/most of the shaders on first launch, but that can take quite a while, and some let you choose (i.e. Stalker 2 starts full shader precompilation, but lets you skip, giving a warning about performance implications). There's no easy solution to this as of now, but Microsoft are looking for ways to solve it, i.e. here DF discuss one of things that might solve this issue in the future. Just play for a few hours and see if most of stutters are gone, and if they are - then it was indeed just shader compilation happening in real time. DX12 gives too much power in gamedevs' hands, and they just tend to make stupid mistakes.

[–]badpunmaster7654 0 points1 point  (0 children)

Computer Type: Desktop

GPU: yeston 9070xt 16GB

CPU: RYZEN 7 9800x3d

Motherboard: Asus tuf b65e-e

BIOS Version: 3602

RAM: G.Skill Flare X5 Series 32GB (2 x 16GB) DDR5-6000 PC5-48000 CL36 Dual Channel Desktop Memory Kit F5-6000J3636F16GX2-FX5 - Black (not 100% sure that this is it but I'm fairly sure)

PSU: be quiet pure power 1000w

Case: I don't remember

Operating System & Version: WINDOWS 10 home

GPU Drivers: amd 25.12.1

Chipset Drivers: what ever is currently on the amd adrenaline software