Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
However, a huge help that i found on another post, is just increasing RAM. I went from 16GB > 32GB RAM and the difference is insane. Mind you still ♥♥♥♥♥♥ performance, but 32GB helped A LOT i can play the game around 60-75 FPS excluding hogsmead ofc. I have similar specs on RTX 2070 Super.
"I had awful performance until I used a tool to change the DLSS version, after that, ran smoothly. Just google DLSS hogwarts legacy. It's hardly the best workaround and shouldn't need to exist, but ah well."
16GB is a stutter-fest, especially in Hogsmeade. This has been tested ad nauseam. 0.1% lows drop to single digits even with extremely good systems.
I had a longer post typed out, but lost it as I wanted to load the game and go into Hogsmeade and see what was going on in performance from the task manager.
My RAM was [almost] maxed out, however I had a steady frame rate. Throwing more RAM at the issue might solve it but, I do think the underlying cause is poorly optimised code, leaning heavily on a DLSS tech that it hasn't quite managed properly. Changing the DLSS version the game uses should, imo, be the first port of call before expensive and perhaps unnecessary hardware upgrades.
My man, you need to move on from the hyper focus on DLSS. Not everybody uses it, it isn't even necessary unless you're trying to run a higher resolution than your card is designed for. All you're doing is rendering at 67% and shifting load to the CPU. Its a very, very simple technology. The game is a resource hog, this isn't a revelation for a console port. Nothing magical is happening here, its just like every other console port in the last few years.
do have a read around on the descriptions, and in the "posts".
Author of the mod is using a 3070.
Just to demonstrate the problem, I did a quick test for you. I used this machine at 1080p Ultra with RT reflections on Medium:
-i7 12700KF
-32GB DDR4 4000mhz
-AMD 6900XT
-Samsung 980 Pro 2TB
Not top of the line any more, but plenty powerful for 1080p Hogwarts. I did two runs, one with 32GB of ram, and removed one stick and then ran 16GB. Same save in the middle of Hogsmeade, run in a circle around the big tree in the square.
16GB is a stuttery, terrible mess (I even checked it with another RAM kit that was 2x8GB just in case it was single channel pulling it down - its the same)
I logged with AMD's radeon software datalog at .5 second increments and then made a spreadsheet with the outputted csv files so I could compare.
32GB RAM
AVG GPU usage: 91%
RAM utilization: 23.4GB
GPU VRAM use: 13.0GB
AVG FPS: 107
Lowest FPS: 74
16GB RAM
AVG GPU usage: 60%
RAM utilization: 15.4GB
GPU VRAM use: 11.6GB
AVG FPS: 70
Lowest FPS: 18
One experience was buttery smooth, and the other was a very noticeable stutterfest. 1% and 0.1% lows suffer badly with RAM limitations, so even if your FPS was lower due to a weaker graphics card, your experience overall would still be much smoother with the extra RAM. I am not condoning the company for letting it be this way instead of fixing it, just showing what I've seen for myself.
https://steamcommunity.com/app/990080/discussions/0/6348431004279095468/
IN CONCLUSION:
The ram was the limiting factor. For those who have helped, thank you. The game is smooth and actually enjoyable. If anyone is seeing this discussion in the future and has the same problem now you know.