Well as some that know that care Cyberpunk 2077 just got a massive forty something gb patch. With a lot of changes. Some it has increased performance, others it has tanked it by 10-20 FPS. I was one of the ones it tanked. Talking to people, playing with things myself this is what I have found out my average FPS pre patch used to be about 72-78 and I would not drop below that. With the patch I was dropping into the high 50's to low 60's for my low's and my car was being yeeted by expanding collision objects that worked as road dividers of two textures meeting if I flew though the city. Not here to argue but here is my list of talking to people helping them figure out their problems, figuring out my own to stuff I ran into by chance. There have been a lot of changes in this patch to RT, DLSS and other settings/visual elements.

First up is running the game at Windowed Fullscreen, why this works no idea, but it lets the game utilize more of the video card.

If you are running any external visual improvements, like the NVidia overlay for example Nvidia Sharpen. Disable them/remove them, these conflict with the new changes to the game and will tank your FPS to what you may consider unacceptable levels from what you had before the 1.5 patch.

Next is DLSS Sharpening, a new option available to us, the default setting is bad it tanks your FPS, even setting it to off is bad, having something like nvidia sharpen makes it worse. I have found the sweet spot at least for my system is between .20 to .35. I set it too low to off I lose a large chunk of frames, I set it to high I lose a large chunk of frames.
So it may be different for your hardware/configuration so you may have to play with it to find the best performance vs best visual quality that does not kill your FPS too bad.

Lastly something I have overlooked for a while now the HDD setting, it's an option available for those with mechanical hard drives still setting resources aside for some speed. It is set to Auto by default. And even if you have a good SSD it being on auto it will be set to on. This will tank your FPS on a SSD hard. So set it off from Auto if you are on an SSD for the game. It will also cause SSD owners while playing for textures to assets to pop in as the extra process of the game saying you have a mechanical hard drive adds extra steps that affects your gaming experience as assets are loaded in/called on.

If you are going to run the Bench do so with Custom, be it Fullscreen or I do believe more so in windowed Fullscreen as it will go to the set settings you used. So anything custom you did will not apply to the bench.
<Side Note on RT Shadows>
Something they sort of introduced with this patch was the RT Shadows option, well it is also a performance hitter, and honestly makes the game look a little more fuzzy with DLSS if you're on a larger display and have to go to balanced to performance or ultra-performance DLSS. I suggest you disable it. 

Game does a CTD immediately on start-up? it's one of two things some audio shenanigans or you need to run a repair. 
MSI/Alienware and some other companies have snuck in some audio updates with mostly windows 10 that are causing the game to crash.
Currently investigated issues [last updated: 16.02.2022 - Patch 1.5] | Forums - CD PROJEKT RED
From the CP 2077 Discord
A-Volute, Nahimic or Sonic Studio Disable/remove them from the system startup kill the task.
The crash is most likely caused by audio software conflict. So far we've identified this issue with audio drivers such as A-Volute, Nahimic or Sonic Studio. We're currently investigating. Meanwhile, as a temporary solution, we recommend disabling said drivers before launching the game. You can also try following the steps we described in this article.

My sweet spot is .35 DLSS Sharpen I do lose frames on my high, but gain a lot on my low, and thanks to the bench I will never see that low in game.





Here is with DLSS Sharpen set to .30 to show you my highs go up but my min went down. Its one big balancing act and how much information you can give DLSS with DLSS Sharpen.



-=UPDATE=-
Hot fix patch after 1.5 sharpening/none RT light rays/RT lights and shows tweaked more my CDPR, Fullscreen now utilizes more of the GPU. Seems they broke something again for streamers.
Did a fun test if you want to play around and see the difference between no RT or DLSS, No RT/DLSS On, RT/DLSS on just open all three images in your browser tab and flip through them like a flip book. I try to keep my frames well over 70 with RT/DLSS on so my car does not get yeeted by some of the games collision objects that seem to grow and fight with the physics engine when driving a faster car fast. Its a good way if your on a higher resolution display to find out how much eye candy you are willing to sacrifice, and what looks best all around. The big balancing act. I had to play with some stuff on the 1.5 patch and the hotfix patch for 1.5. Its one big balancing act with this engine vs your hardware, any external software running "yes it does affect performancea few frames here and there to your FPS low", resolution, RT/DLSS settings to find the sweet spot of visual/performance and not running into bugs constantly when you play. 

NO RT or DLSS Max settings on all
https://cdn.discordapp.com/attachments/943607551029837834/945017256268681216/NORTorDLSS.jpg

 
NO RT, DLSS set to Quality max settings all, DLSS Sharpen .35
https://cdn.discordapp.com/attachments/943607551029837834/945017374195724288/NORT.jpg


RT On DLSS Performance RT Shadows/RT Local Shadows off/Ultra RT/DLSS Sharpen .35
https://cdn.discordapp.com/attachments/943607551029837834/945017455133225030/RT-DLSS-ON.jpg

I havn't fired up the game since the patch, but the changes  sound interesting.

aka_STEVE_b
Sounds like they took a long time to put out a bonejob of a patch...
They should have done more frequent, smaller patches to make it easier to identify what changes had negative effects.  Now they have this huge 50 gigs worth of code to dig through to figure out... ..

Just glad I have it all figured out now. Only took a day.

aka_STEVE_b
https://www.polygon.com/2...sh-reports-bugs-pc-ps4
 

Cyberpunk 2077 devs probing crash issues on PS4, PC

No answers yet; crashes affect disc versions of PS4, sound drivers on PC

Yeah saw that good thing we are on the PC, like seriously I keep the game above 70 to very close to it constantly I do not run into a majority of the issues a lot of these people run into on the PC even at launch. The audio thing that cannot be helped that is on CPPC and those making the audio drivers/software. I do not really use external software controllers for my audio. Could care less about the consoles tbh.

Also lots of small updates on a game this size means increasing the potential of breaking something more.

Brad_Hawthorne
I'm one of those persons that believes that game makers have always made mistakes by having settings be organized by general labels like low, medium, high, max instead of being smart enough to automatically adjust to a requested FPS medium figure. I'm also one of those types that think worrying about anything over 60fps is wasted angst.

Try CP 2077 going below 70, at least for my the collision objects on the roads go nuts at the stop lights the metal yellow bars on the ground, or the concrete rectangular dividers on bridges... My car gets yeeted if I am flying though the city or highway If I go too far under 70 FPS for a long period of time. Games are changing. On my 3070 + 10th gen config it was below 64-67ish on my Wide 1440p display, 70 is for my 12th gen i9+3080 on a Ultrawide 1440p. 

Brad_Hawthorne
Tying client side physics to the frame renderer speed sounds mildly insane. I've seen a lot of games unfortunately do that though. It's also why some games are locked 30 fps.

It's in a different set of rules with it being open world, no instanced interiors, RT Lighting/Shadows/Reflections, DLSS now with DLSS sharpening, physics of the cars, physics of everything else, the mass NPC's, the pure amount of stuff everywhere, massive databases for everything, there has not been a game made before at this level of insanity. Locked 30 FPS would not good, game does even worse stuff at those frames on the PC. You see all the bug videos, most of those are those locking their fps lower end systems and the engine goes banana's. It's also why it was so bad on the xbox one and ps4 and why CDPR is trying to get any performance increase they can with more frames the FPS lock didn't help it made things a lot worse. 

Get 66 fps avg, and 54 min with the settings I use at 4K.

donta1979

Sajin
Get 66 fps avg, and 54 min with the settings I use at 4K.

Got an in-game bench results screen shot?
 

Yep...
 







 
 
 

My game keeps on flatlining when trying to open it.

Sajin

donta1979

Sajin
Get 66 fps avg, and 54 min with the settings I use at 4K.

Got an in-game bench results screen shot?
 

Yep...
 







 
 
 

Do not think I could put up with those FPS, I go that low the bugs creep in, to my really fast cars get yeeted by growing collision objects/physics on car rigs going berserk. That screen shot looks awesome though, plus the fact you get those FPS at 4k without DLSS is nice. Just wait until you see the 40 series, I see you upgrading this year haha.

Yeah, I need a 40 series card already. :)

donta1979

badboy64
My game keeps on flatlining when trying to open it.

run a repair or its the audio bug
Currently investigated issues [last updated: 19.02.2022 - Patch 1.5] | Forums - CD PROJEKT RED
Since you have an EVGA board I am betting it's the audio bug sadly. you will have to read the article or see what the tech wrote above. Oh and the game seems to be extremely sensitive to overclocks.

I don't run the onboard audio on the motherboard just the nvidia audio drivers.

now that the patch fixed it,   its time to get it 

Should i give it a try again since new patches are out🤔

Sajin

atfrico
Should i give it a try again since new patches are out🤔

Yes. 👍

Thank you ye 😼 😁👍