Something is wrong on your end me-thinks... It was only 5.2mb for me.Fixes 1 thing, 43GB download..
If you got the game from GOG (which frankly you should) then you can easily get around that by right clicking the EXE and making a shortcut, place it on your desktop and run the game from there. However if you it on Steam then you are screwed because their DRM won't allow that. Then the game will start without GOG and it won't update until you actually start up GOG and tell it to.
And modding ANY game that is still being actively updated is just part of the risk of modding the game. When I upgraded to 4.02 it broke my game too but I knew the risks and so that's on me not CDPR. Since I wasn't actively playing the game I was still on 4.00 because I was starting the game from the desktop shortcut so it wouldn't automatically update because I knew 4.01 didn't really bring anything new to the table and I didn't want to bust my modded build. I only upgraded to 4.02 out of curiosity to see if the threading issue was fixed or at least worked better than before .... Doesn't sound like it was fixed yet so the game remains in a broken state for now since I'm not playing it currently and don't plan to again until it threads correctly which I don't expect will happen until after CP 2077 development is wrapped up. With the upcoming Path Tracing Overdrive update being worked on CDPR's top game engine devs are all busy working on that major and innovative upgrade. Being the first devs to fully utilize Nvidia's new architecture based SER (Shader Execution Reordering) means they likely have their hands full because they are going where no one else has gone before on a new platform (40 series Nvidia) that hasn't even been out there for 6 months yet. Hopefully they can take some of what they learn there and eventually bring it to Witcher 3 although SER only works on Nvidia 40 series
Last edited:
Deactivated all Frame Limiters for max GPU (4090) usage. Played 90 minutes without a single crash now!
(Before Hotfix max 3mins). Thank you very much CDPR for this Hotfix. I really enjoy the game again now.
Ps: No stutter here.
(Dont use Nvidia Overlay --> MicroStutter.)
(Msi Afterburner/RTSS is fine and smooth. Just dont use any Frame limiters with it in combination with FrameGen --> Stutter.).
(Before Hotfix max 3mins). Thank you very much CDPR for this Hotfix. I really enjoy the game again now.
Ps: No stutter here.
(Dont use Nvidia Overlay --> MicroStutter.)
(Msi Afterburner/RTSS is fine and smooth. Just dont use any Frame limiters with it in combination with FrameGen --> Stutter.).
The stutter you mentioned in combination with DLSS 3 Frame Generation - more precisely what it can't handle properly yet are
partial frametime spike adjustments. That's one of the additional tweaks applied by the FPS limiter of RTSS for example, so you
can use FPS limiters if you want (e.g. Nvidia Control Panel) as long as these don't try to additionally smoothen frametime.
Last edited:
on load what? Save game? Fast travel? on what DX mode? What is ur PC spec? Are you using some mods?
I thought it's a fairly well-known issue: DX11 crashes instantly on loading a game from the main screen since 4.02 was introduced (once the load has completed and the transition from the 'story catch-up' has finished). I find it troubling that the game can be patched quickly for a 'crash in minutes' issue but there doesn't appear to be acknowledgement (that I know of) of a much more easily-reproduced crash. I can't speak for others but I have the problem on Radeon VII so obviously nothing RT-related, which is what most people reporting issues seem to be complaining about.
And no, no modifications. On the other hand, I've gone back to playing on Linux via Proton, which is what I did on my first play-through two years ago. No issues there, which is why I've seen some suggest use of DXVK as a work-around.
DX12 is a bust on both Windows and Linux for me. Crasherrific.
And no, no modifications. On the other hand, I've gone back to playing on Linux via Proton, which is what I did on my first play-through two years ago. No issues there, which is why I've seen some suggest use of DXVK as a work-around.
DX12 is a bust on both Windows and Linux for me. Crasherrific.
Just let Windows set you page file size automatically .... Setting a page file manually hasn't been a thing since Windows XP. Ever since Win Vista/7 upgraded the memory management so it just isn't necessary. I'm running a highly modded Skyrim right now and I've seen my memory usage as high as 30.2 GB (out of 32 GB) and my page file grow as large as 86 GB. If I had used a fixed size less than that then the game would have crashed. Another downside is page file fragmentation, if you let Windows manage the page file size when you quit out of a game or other page file hungry application Windows will automatically defrag the page file when it shrinks it and moves all the data it wants to keep to the front of the page file.
Last edited:
You have no problem with 32gb ram, me too but some user told me that increasing virt. Memory helps him solve stability problem with in w3, because he had 16gb ram.
[...]
Last edited by a moderator:
Somehow this hot fix absolutely destroyed my performance in the DX11 version of the game -- would think this update would have no impact at all on this version, but I confirmed it was indeed at least related to the patch. Sharing I guess in case it might help anyone else that doesn't care about dlss or rt -- reversed the update and disabled auto-updates for now, and I'm back to a stable 60 fps at 4k ultra+ settings