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
None of this happens. It works fine.
HAving a 12 core CPU helps not having issues. The less CPU cores, the biggest chance of having issues.
edit:
As a general rule: never ever set priority to realtime to any process that has a chance of having high CPU usage, because that will create many issues. Performance may drop (as even the GPU drivers will get CPU starved), to the system to completelly lock. Realtime must only be used for very light processes that for some reason require extremelly low latency, Realtime priority is about lowering latency as much as the OS allows, not to increase performance.
Same here, CPU is fine temp wise but GPU is about 15c higher than it should be based on other demanding games I have played at 1440p. Im running at 13700k and 4070ti. Otherwise enjoying the game but do hope they keep improving performance,
Remnant 2 had the same GPU high temp issue (in my case) on release but was eventually fixed.
As for using "realtime": Don't ever set any of your games or other programs to "realtime". While this does indeed give the process the highest possible priority, it can screw over your overal system performance and stability. If the game runs with realtime priority and there's a bug that causes too heavy load, the rest of your system will no longer be able to react. In other word: it could freeze, without recovery, where otherwise (without setting the game to "realtime") you might have been able to force-close the game or maybe it might not have happened at all.
I noticed very little improvement honestly.
Do you have any stats about your gpu, like usage%, voltage, frequency. People are quick to complain but most really don't ever investigate anything. It could be a driver issue, or maybe the game yes. But without having stats, there is no way to have a meaningful discussion.
Gpu temp is tied to voltage, frequecy and usage. And of course your cooling setup as well.
Maybe investigate and try to find what is different to remnant 2 which you say is now fixed.
So I have a similar issue. Previously when playing, my AIO monitoring software shows the GPU pegged at 100% and CPU at like 1-2%, while playing or even in the menu. AMD Ryzen Master would weirdly show -1 degree C and Limit temp at 1 degree C and all the other categories behaved like the cpu wasn't running. This occurs everyday when I boot my pc the next day after being off for the night, Upon windows loading I do my normal routine web searches, web article reading, etc.... Once I do all that I attempt to run NRFTW and it will load into Sacrament at horrible fps again like 20-40 fps max. I attempted to change priority with no effect.
I run a 7800x3d, 4070 super, 32gb ddr5, gen 5 nvme m.2 so I should have no problem at 1440p with max settings. I played around with it some more and decided to reboot my pc to see if my monitoring software would read properly and decided to immediately startup the game before i do anything else once windows loads completely. To my surprise the game then ran at 80-100fps consistently in Sacrament and 130fps plus in the open world and dungeons at 1440p max settings. No matter how many times I exited to desktop and restarted the game, it would continue to run properly until I shut down for the night. Next day, same scenario. I'm glad I can get it running properly but this is the only game I have such issues with. I did nothing to modify any Nvidia settings or windows settings or anything at all actually other than rebooting and immediately running the game. Sometimes it takes multiple reboots but typically after 2 it runs properly for the rest of my session for the night/day.
It didn't occur to me to grab my logs or dxdiag while it was running poor but I have them for when its running properly. I am gonna grab them next time it starts and runs poorly which should be tomorrow and I will compare. I can't replicate the poor performance once it starts to run good until the next day. It also shows proper GPU/CPU utilization in my monitoring software as well once it starts running properly. Logically I would say it has something to do with my power states or initial boot power after being off all night but it's weird that everything else runs like it should, including other games, videos, etc.
this game is....UNOPTIMIZED....because its nowhere near finished....
Look up 4090 gameplays, and see the answer. You cant bruteforce this. Im on a 4080 Super, and its struggling with this game, CPU is a 7800X3D.
Just wait 3 more years for the next patch, maybe they fix it.
EDIT: And do NOT set this game, or any other game, do Realtime Priority, ever, in the taskmanager. You will crash eventually, because you are allocating ALL resources to a game that hasnt been properly optimized. Realtime is never used. Set it to High, and stop there.
Or do whatever you want, i truly dont care if you break your stuff becasue some rando suggested it.