I get that. And I get that expecting something to be 100% perfect is unrealistic. What I don't get is if you are saying that it's more normal for things to function improperly rather than properly? Almost as if expecting things to function is a bad thing, which I don't agree with. At least now I know the rough time frame for a response so I don't wonder what the silence means.
Yes and no.
Yes, it's perfectly common for things to function incorrectly. And the vast majority of the time, serious issues are the result of user-end errors. Hardware, driver, firmware, operating system, file table, BIOS -- system configuration issues. Sadly, due to the complexity of modern tech, even consoles are beginning to suffer from a degree of this.
No, it's not at all problem to
expect something to work well. Just don't be surprised when (not if) you encounter issues. And, for example, CP2077 works very well now. If the problems you're experiencing were due to the
game not functioning properly, then every, single person in the world would be seeing exactly the same issues in exactly the same areas. The code doesn't change from one PC to the next.
The problems exist somewhere in your save, installation, or system config. We just need to narrow down where. If it's appearing in a brand new game under a clean installation...this is going to be a bit of a challenge, I'd expect.
As I stated previously the game is Clean-Istalled and the save file is brand new. All old saves were deleted. All issues are still present. So I am unsure how mods being the issue here will be the answer. This is unless GOG is doing something and I should have uninstalled GOG after the complete uninstallation and residual files removal of CP2077.
I was more or less double-checking on that. It would have been the easiest solution. The errors are classic for things like LoD mods or graphical overhaul mods that are removed mid-playthrough, resulting in assets being incorrectly drawn into the game, since the game is still trying to load modded assets that have been removed.
Since you're certain that such isn't the case, that makes things much more difficult.
The issues start as soon as the mission "The Rescue" I think it's called. The one where you save Sandra Dorsett. After all one of the screenshots shows texture glitches in the final room of that quest. I don't think you can explore the world before that to check for issues. As a side note turning raytracing on and off doesn't change a thing as well as DLSS. In general changing graphics settings does nothing.
But the prologue and training missions are fine, as well as everything up to that point. Hm. That is quite weird.
So:
- CPU - AMD Rysen Threadripper 1900x
- MB - Asus ROG Strix X399
- GPU - Nvidia RTX 2080 Super FE
- RAM - 64GB Corsair Vengance
- PSU - Corsair RM850i
- Game installed on a WD m.2 SSD 500gb
- Windows 10 22H2 build 19045.2251
Let's start with all the basics. Move through each of the steps below, then try the game before moving on to the next step:
0.) Verify / repair the installation through GOG, Steam, Epic, etc. (I'm assuming you've probably already done this.)
1.) If the program is installed anywhere under the
Program Files or
Program Files(x86) directory, move the installation (or installation library) to the root of the drive or a folder of your own creation. For example:
C:\Cyberpunk\...
or
C:\MyRPGgames\Cyberpunk\...
The default Windows installation paths will be protected directories. It can wreak havoc with games under certain security settings. You should be able to just move the installation -- you do not need to reinstall. Just move it via whatever method your platform uses (GOG, Steam, Epic, etc.) and verify the installation.
2.) If using any form of overclocking or underclocking, return ALL hardware to default clock and voltage speeds.
3.) Anti-virus. Completely disable it for testing. For really aggressive programs (Norton, McAffee, Comodo, etc.) you may want to completely uninstall it. Anti-virus can cause a lot of problems with games. (Especially if they're installed under protected directories.)
4.) Drivers. Doing this is a pain, now, thanks to Windows automatically installing things if it detects them missing. First, get the latest drivers directly from Nvidia.com, but do NOT install them yet. Download and install both Display Driver Uninstaller (DDU) and CCleaner. Then, in the following order:
- Restart in Safe Mode without networking.
- Remove all GPU drivers using Display Driver Uninstaller. Get everything Nvidia related.
- Run CCleaner to clean the Registry of any empty keys. When it finishes, run the cleaning option over and over until it reports "No conflicts."
- Restart the computer into Safe Mode without networking again.
- Run CCleaner repeatedly again until it reports "No conflicts."
- Restart into Safe Mode without networking.
- ^ Keep that up until the program reports "No Conflicts," immediately following a restart. If you have a system that's been used heavily for a year or two, this might take a few rounds.
- Now, still in Safe Mode without networking, install the new Nvidia drivers manually, selecting the CLEAN installation option. I strongly discourage using Geforce Experience. It's not only relatively ineffective, but it can be a bit invasive and introduce issues where there would otherwise be none.
- Lastly, restart the PC into Windows normally.
That should resolve any form of driver issue that may exist.
Let's see if any of that has any effect.