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
Discussions Rules and Guidelines
Report this post
Yeah, gsync with vsync on in the Nvidia control panel which I use for all my games. Only thing I've changed since is creating a custom resolution for 100 hz - would like to try 110 next though, after I've hit 3 hours or so. Will have additional time to test this weekend (if a hotfix isn't realized before then, sheesh).
Edit: Hit 3 hours with no issues.
I'm going to try to a new game, with lower refresh rate.
I'll report back later
I'm actually frustrated with myself. I tested this theory shortly after the patch was released as a potential fix. Problem was, my display only had 160/144/120/75/60. So I only went as far as 120hz.
I gave it another go since reading this on the thread. I limited my FPS in Nvida Control Panel for this game specifically (FYI, Frame caps in NCP work fine with FG/DLSS 3). Native refresh rate @160hz. I suspect it's not a refresh rate problem. More an FPS and GPU utilization issue. Here's my findings...
Everything MAXED in game. FG on, DLSS Performance. i7 13700k/RTX 4090. *NOTE*, I usually less than 5 minutes before crash. Usually it's within the first 60 seconds.
Attempt #:
1. Set FPS cap to 100. Ran around, collected ♥♥♥♥, day/night shift, fast camera rotations, crowded NPCS, (20 minutes) *SUCCESS*
2. Set FPS cap to 120. Barely started running 20 seconds in, *CRASH*
3. Set FPS cap to 115. Maybe got 30 seconds while running, *CRASH*
4. Set FPS cap to 110. Did the same as #1, just didn't play as long, (10 minutes) *SUCCESS*
What I don't know yet is if it's an FPS issue, or a utilization problem. Is the GPU pinned @100% with all the Bells and whistles enabled causing the problem? Or simply just FPS? @ 110 FPS, my GPU is to 90%+ most of the time in open areas, so it will be interesting to see how it goes when it's getting hit hard in larger cities, or fights, etc...
One other thing to note...while I was trying to make the game run better prior to 4.02, I noticed thread scheduling issues which I suspected was causing Stutters. I turned off Hyper Threading, and that did make enough of a difference for me to just keep it off. Which also allowed me to get an even higher overclock :D
Thanks for the results - I still haven't crashed at 100 hz yet, and my GPU load rarely if ever hits 99%. At 110 however it was hitting 99%, and I pretty quickly got a crash after about 10 minutes.
I'm at 4k DLSS Quality/FG with everything maxed. I tried limiting my fps with the Nvidia control panel earlier and it didn't seem to work (like I was still hitting 120 fps) and I got a crash. Limiting it with Rivatuner worked but resulted in horrible input lag. The only thing that's actually been successful for me so far is setting the refresh rate to 100 by creating a custom resolution in the Nvidia control panel.
Strange. There isn't any reason why the FPS cap in NCP wouldn't work. Also, I'm not sure how you even hit 120 if your Refresh is 100hz with REFLEX on...something is not right there. Also, don't use any FPS Limiter other than NCP with FG. If you do, you'll most likely have to set the limiter to 1/2 of the FPS you want. Which you can do in the Witcher 3 as well. Set the FPS limit to 50, if you want 100fps with FG enabled. I still recommend using NCP FPS cap, or set your desired refresh rate and let REFLEX handle it.
I'm wondering if you maybe set the FPS limit to the Witcher's launcher instead of the Executable? Could try it at the global level for temporary science.
Good to know about 110 crashing. I might adjust a few things to make sure I can hold 100 consistently without constant 100% GPU. Guess we'll see while we still wait for a patch.
What I meant was my refresh rate was 120 hz and I was still hitting that when only using the Nvidia limiter - like it wasn't actually working and limiting the fps, and did nothing to help the crashing. I had to manually set the monitor refresh rate for the fix to work, which is basically the most guaranteed way to test this method and not interfere with reflex/introduce input lag. Working for me at least - no crash yet but I'll keep testing.
It's not the driver that's the problem, it wouldn't have crashed on the previous ones! I stopped crashing after doing the above. Three days without crashes with frame on!
I have 144hz 4k, but fps is always locked at 60fps because the 3800x processor can't keep up with the 4090
Ah ok, my bad. I still don't understand why the frame cap isn't working, and REFLEX should not be letting your FPS get anywhere near your Refresh Rate. I don't get more than 153 FPS @160hz with REFLEX. 120hz I think sits around 115? If your FPS counter says your hitting 120, something isn't working.
For me, I'm going to limit to 100 FPS via NCP @160hz, and see how long I go without a crash.
Also I'm not trying to argue. Just wanna help. Are you actually seeing 120 in your FPS counter?
So I looked into this again, and this is what's happening - fps counter shows max 100 fps in game (with the Nvidia limiter), but when I check the hz on my TV with GSYNC/VRR enabled it's still consistently peaking above 100 hz like it's not being limited. Not sure what's going on exactly, but I do know that it crashed not long after I tested it last time. Guess I can try it again and report back, but I still think limiting the display refresh rate is the safest bet.
Edit: GPU load looks consistent with 100 fps, so I guess the refresh rate is being reported incorrectly. Not sure why it crashed before though, as the limit does seem to be working like you stated.
*And yeah, when you limit it through the custom resolution it does stay at 3 fps below max, at 97. This does result in a slightly lower GPU load, but I'm not sure that's enough of a variance to keep it stable vs. crashing (if that's the cause). Man, it'd sure be great if CDPR released a hotfix so we can stop dealing with this crap.
I was messing around a few minutes ago and decided to search the forum to see if anyone else had already posted this.
Game crashes fullscreen DX12 runs a little choppy Borderless DX12
Game runs fine Fullscreen DX11
GTX 1080 531.29
I changed no other settings from default.
Maybe you should make a new topic so it doesn't get buried in here since your post is the only one that mentions borderless you might as well get the credit for the fix.
just received it, will test later, thank you!!