Patch 2.12

+
Ah ok Redmod, not Redkit (which is mod tools for modder).
But Redmod have its "own" depot, separate from the game itself (in DLCs tab).
At the end, internal QA is a "private" depot for testing purpose (Quality Assurance), hence is name. This depot have been updated 2 days ago, while Remod depot didn't ;)
 
Okay, let me get this straight.
The game still has a lot of serious and annoying issues and CDPR wants you to enjoy it and refuses to fix it?
Now it's all up to the modders, right?
 
Okay, let me get this straight.
The game still has a lot of serious and annoying issues and CDPR wants you to enjoy it and refuses to fix it?
Now it's all up to the modders, right?
Seems like it.
If I was a game dev i would be so embarrassed releasing a game in such a messy state, then leaving it with such bugs.
 
Okay, let me get this straight.
The game still has a lot of serious and annoying issues and CDPR wants you to enjoy it and refuses to fix it?
Now it's all up to the modders, right?

Woah, easy there, how did you jump to that conclusion? Didn't get that straight at all.

The TRUTH is, we don't actually know. All we know is that they're testing some version of the game, as shown here:
Cyberpunk 2077 History · SteamDB

We have ZERO idea what is in the latest version of the internal_QA branch. Maybe it's just FSR3, which would be disappointing, or maybe it includes bug fixes for the last few issues still remaining. Feel free to bump this other thread to maintain eyeballs on said issues and, if you haven't already done so, report to CDPR tech support.
 
The game is still being worked on, and it's likely to see updates in the future for a time yet. (Even when the studio announced officially that "work on The Witcher 3 was concluded"...we continued to see a string of patches, then a next-gen update, then even more patches.)

But, now, reality check. There will always be issues with games (all games -- every, single one) regardless of how many patches they receive. This is due to the nature of computer technology on planet Earth:

1.) Not all bugs can be re-created. If they can't be, then the source of the bug cannot be found. And when you're talking a player base numbering 10 million+ across multiple platforms, than means that even 10,000 people reporting an issue accounts for only 0.1% of player base. That's how rare such issues can be. Of course, efforts will be made to sort it out, and sometimes the bug can be fixed. But other times, it's like trying to track down one needle in a field of haystacks. Chances are, it will never be found.

2.) Certain bugs are the result of changes made to operating systems, driver updates, updates to APIs like DirectX or Vulkan, console OS updates, etc. These are not something a studio can affect. It may require players to, for example, roll back drivers to better function: this will be very common if running the game on older-generation hardware -- very often older drivers will work better. Fortunately, this is becoming less of an issue as backwards compatibility is taken into account much more nowadays by Microsoft, Sony, Nintendo, Nvidia, AMD, etc.

3.) Bugs are a result of modded playthroughs. There is nothing that can be done if players have modified the game in some way. A studio cannot account for the endless myriad of issues that can arise from this or that mod or combination of mods. Modding is always done at the player's own risk.

4.) Many "bugs" are actually the result of unique situations that arise when the game is updated multiple times over a single playthrough. If you're seeing something completely weird that doesn't seem to be a known issue, it's a good idea to revert to an earlier save or simply start a new playthrough. (This normally affects players that have been on the same playthrough for 3+ updates.) It can simply create exclusive scenarios in the game based on way too many potential factors to ever sift through.

5.) Yet other "bugs" are something on that person's system. Conflicting hardware, file system table issues, corrupted installations, hard drives / SSDs that are too full, aggressive anti-virus programs interfering with the game, botched drivers, faulty RAM, etc. This is especially true of people that are unable to reliably start the game, or experience random performance issues or crashing while playing.

6.) And then there are the catch-22 issues, where fixing one bug would knowingly create a chain reaction that causes another bug. Those situations are now impossible to fix, and the decision needs to be made as to which bug will stay in the game.

^ Any and all of those are the reality at any time. YEARS of work have been done and will continue to be done to make the game as stable as possible, but there will always be sneaky bugs and new issues cropping up as time goes on. Guaranteed. For every game under the sun. The more complex the game, the more issues will be seen. (Just remember that simply because you, personally, are not seeing any issues with a given game, it doesn't mean that they're not there. It's just that you're fortunate enough not to have encountered them -- or more pointedly -- didn't notice them when they occurred.)

Lastly, modders, while many do excellent work, are often not equipped to "fix" anything. Many of the mods that claim to "fix" things are either causing other issues in the game somewhere, unbeknownst to the author, or they're simply altering a facet of the game that certain players dislike. Meaning, there's no bug, some players just want it to be different. Totally separate considerations.


_______________


So, yes, if you encounter a bug, can reliably recreate the issue (listing the steps), and are playing a 100% vanilla copy of the game that has never been modded, do send a ticket into CDPR Support. If an issue can be fixed, the team will help you fix it. Just be aware that some issues will continue to be mysteries. It's the nature of huge, sprawling RPGs with wildly detailed worlds spread out over 1,000,000+ lines of code.
 
Woah, easy there, how did you jump to that conclusion? Didn't get that straight at all.

The TRUTH is, we don't actually know. All we know is that they're testing some version of the game, as shown here:
Cyberpunk 2077 History · SteamDB

We have ZERO idea what is in the latest version of the internal_QA branch. Maybe it's just FSR3, which would be disappointing, or maybe it includes bug fixes for the last few issues still remaining. Feel free to bump this other thread to maintain eyeballs on said issues and, if you haven't already done so, report to CDPR tech support.
Bug fixes are welcome, but I wouldn't despise FSR3 either. I hope the SteamDB updates actually mean SOMETHING.
 
Last edited:


Patch 2.12 for Cyberpunk 2077 and Phantom Liberty is being rolled out on PC, PlayStation 5 and Xbox Series X|S. It focuses on main issues experienced by players after Patch 2.11, such as key bindings.

Check out the list of changes below for details:

PC-specific
  • It will now be possible to properly rebind the Radioport and dropping bodies to a different key on AZERTY keyboards. Switching quest objectives will now be assigned to the T key on all keyboards.
  • Fixed an issue where trying to bind the T key to actions in Exploration & Combat resulted in a "Binding Failed" error.
  • Together with Intel we fixed the stuttering issue that occurred while the "Prioritize P-Cores" option was enabled.
  • Together with Razer we fixed a crash that occurred when using Razer Chroma enabled devices.
  • Fixed an issue where NPC hair could appear extremely bright inside vehicles when Ray Tracing is enabled.
  • Fixed a crash that occurred on Steam Deck when playing with Ray Tracing enabled.
Xbox-specific
  • Addressed an issue where the game could enter an infinite loading state, hang up or crash on Xbox when using some saves.
All Platforms
  • Fixed an issue causing the inability to access the menu, inventory, stash, holocalls and fast travel.
  • Updated the description of the Sonic Shock quickhack so that it properly reflects the changes made to its behavior in 2.1.
  • Improved visibility of the controller cursor in menus and when using computers or keypads. This change will primarily help Steam Deck users, but will also benefit consoles and PC when using a controller.
  • New Dawn Fades - Fixed an issue where it wasn't possible to open the phone to read the notification from the Automated Delivery System.
  • I Can See Clearly Now - Lowered the Body attribute check required to move the dumpster.
  • I Walk the Line - Sasquatch's jump attack will now properly register as a hit and deal damage.
  • Riders on the Storm - Enemy cars in the chase sequence will now shoot at Panam's van.
  • Nocturne Op55N1- Fixed an issue where, after choosing to call Reed, the conversation sometimes wouldn't trigger, blocking progression.
  • Sonic Shock will now be properly categorized as a Covert quickhack.
  • Fixed instances where groups of immortal enemies could appear across Night City.
  • Fixed an issue where some elements on the perk screen wouldn't change after switching to Colorblind Mode.
  • BioDyne Berserk will now properly have increased Crit Chance from its Reflexes Attunement.
pls add an option to play the game with mouse and keyboard in ps5
 
Just reinstalled my game on steam and purchased the liberty dlc. The game crashes during the intro screen. Would appreciate any help with what might be going on. I have mods disabled and have not added any mods. Attached the crash report
 

Attachments

  • report.txt
    5.5 KB · Views: 41
Just reinstalled my game on steam and purchased the liberty dlc. The game crashes during the intro screen. Would appreciate any help with what might be going on. I have mods disabled and have not added any mods. Attached the crash report
Maybe you shoud try to perform a clean install of the game (above all if you used mods) :
 
Did not use mods and I just installed from steam.
You said :
I have mods disabled and have not added any mods.
What do you mean?
- You used mods at time and disabled.
- Or you never used mods ever.
If never, well, maybe a clean install shouldn't be required.
So you should try to verify the game files first :
Then maybe perform a clean install of your drivers :
NVIDIA
I. Download the latest drivers using the following link: https://www.nvidia.com/Download/index.aspx?lang=en-us
II. Download Display Driver Uninstaller and run it to remove previous versions of drivers.
III. Clean install drivers that you've downloaded in step 1.
AMD
I. Uninstall your graphics drivers using the AMD Cleanup Utility software.
II. Download and clean install the latest drivers from here: https://www.amd.com/en/support
 
Portable radio audio randomly cut out
 
Fixes for the TV and radio audio bugs that they introduced with the last update, hopefully. Bonus for fixing the Waiting for Dodger quest.
I doubt the "cdpr_amd_dev" depot is about fixing gameplay/quest bugs, but rather somehow related to any kind of AMD feature in the game which is as far as I know, only FSR ;)
 
I doubt the "cdpr_amd_dev" depot is about fixing gameplay/quest bugs, but rather somehow related to any kind of AMD feature in the game which is as far as I know, only FSR ;)
Yeah, I was referring to the overall patch. Which I realized after the fact was not your point. Apologies. My inattention to detail aside, I agree it looks hopeful that both the bug patch lobby and the FSR lobby will receive some joy in the coming update. Then I can finally start a new game with all the immersion-enhancing in-game media goodness that’s been missing from NC for several months.
 
Fixes for the TV and radio audio bugs that they introduced with the last update, hopefully. Bonus for fixing the Waiting for Dodger quest.

It would be so wild if they didn't fix the TV audio because looking at Deceptious's mod in Wolvenkit, the fix looks super simple. Things like the Waiting for Dodger bug, the End Cutscenes "telepathy" bug, etc., are probably more fidgety, I would think, but I'm praying they all get fixed... :giveup:
 
Top Bottom