I was really excited to get into the new Final Fantasy release, but I encountered some frustrating crashes shortly after launching the game. After testing different approaches, I discovered my GPU clock speed was set way higher than what my card (Sapphire 7800 XT) should handle. I stumbled upon a relevant issue thread that recommends checking your clock settings against the manufacturer’s specs. Adjustments can be made using the command line or the LACT tool. After tweaking my settings, the game finally runs smoothly in high graphics! Hope this helps if you’re facing similar issues.
5 Answers
Is it just AMD cards suffering? I’ve got an Nvidia setup, and I can’t even get past startup due to freezing. Doesn’t seem like I can tackle the clock speed trick since mine don’t load properly anyway.
You might just be having a lucky break. There’s a known game bug that some folks have worked around using this pull request: https://github.com/HansKristian-Work/vkd3d-proton/pull/2318. So, your tweak might only seem like the solution because of that. Just a thought, maybe look into it more.
I get where you’re coming from, but I kept a close eye on the clock speeds via LACT, and they went way beyond the limit for my card. After my adjustment, everything’s been stable, so I think it was more about the clock speed being mismanaged.
What kernel version are you using? This should supposedly be sorted in 6.11.7 and 6.12, at least that’s what I’ve heard.
I was on 6.12 and tried 6.13 too. I thought 6.12 was the fix, yet the crashing continued, so it seems not quite fixed yet in my case.
I’ve got similar troubles with Space Engineers 2. Thought it might be a GPU issue too, gonna check my clock speeds tonight. Edit: Didn’t help me out, so it might be more game-specific for me.
Whenever I change scenes or cutscenes, my game sometimes crashes and takes the whole desktop down too. Might be due to VRAM pressure, especially since I lower my 6800xt’s clock speeds a bit. Lowering texture settings seems to help for now. Fingers crossed!
That crashing aligns with my experience! Monitoring VRAM/GPU stats with Mission Center helped me a lot in diagnosing and fixing it. Hopefully your tweak holds up too.
The issue I hunted down is focused on AMD cards. Nvidia users have separate driver issues, so maybe check out some threads in the Proton GitHub issues for Nvidia-specific fixes.