Update 2.3 Release Date

+
2_3 FHD.png


Hey chooms,

We initially hoped to put Update 2.3 in your hands on June 26. However, we'll need some more time to make sure we're happy with it — we're aiming for a scope similar to Update 2.2. We'll update you further as soon as we can!

We appreciate your patience!
 
It's all jokes and everything but I actually had adjusted my vacation to July because of the false 26th of June announcement. There's no way to turn it back, so I'm totally fucked :3
 
I'm still seeing the word "promise" and "promising" and "promised" cropping up. There were exactly 0 (zero) "promises" made or implied. When a release date for anything (an entire game, a patch, a DLC, new cosmetics, etc.) is announced, that is the studio sharing its plans. Players are promised nothing, and are owed nothing on that exact date. That is a studio sharing with the community that it looks like that will be the date. It generates interest, excitement, and data on what sort of response the studio can expect.

Now, simple logic. Of course, the studio (any studio) is going to aim to hit that date. Of course, the date was chosen because it looked like a reasonable deadline when it was set. Of course, everyone is pulling to iron out issues and get things ready by that time. Of course, the studio doesn't want to announce a delay.

Then...at some point...there's a knock at the proverbial door. When it's opened...Reality leaps into the room and spin-kicks everyone seven times in the face.

No one can be expected to understand this who has never worked in a professional setting on a major, team-based project involving hundreds of people and has no experience dealing with this type of misfortune in an actual, real-life situation. (Anyone who has real-life experience and claims this has never happened is either unaware of what happened and who saved their project...or is quickly running out of luck.)

Setting "release dates" for something is not about "calculating percentages". That's not how it works. It doesn't matter if a studio is 75% sure...or 88% sure...or 94.36% sure...

It's either going to work out or something is going to crop up. It doesn't matter if the issue crops up early on or if it presents itself in the eleventh hour. It's not a "percentage" that "professional risk assessors" are "responsible" to foresee. It's either there or not there. If it's there, the "chance" of it occurring is 100%. If it's not there, the "chance" is 0%.

There's no "accurate statistical measurement" for the future. There's reality. And reality is based on 1 or 0. If you want a 1 and you get a 0...doesn't matter when or how it happened...circuit cut. Now, work will need to be done to close that circuit whether it takes a day, a month, or a year.

(And the analysts will go, "Oh! I should have accounted for that!"

([And the patch is not going take a year. :) ])
 
I'm still seeing the word "promise" and "promising" and "promised" cropping up. There were exactly 0 (zero) "promises" made or implied. When a release date for anything (an entire game, a patch, a DLC, new cosmetics, etc.) is announced, that is the studio sharing its plans. Players are promised nothing, and are owed nothing on that exact date. That is a studio sharing with the community that it looks like that will be the date. It generates interest, excitement, and data on what sort of response the studio can expect.

Now, simple logic. Of course, the studio (any studio) is going to aim to hit that date. Of course, the date was chosen because it looked like a reasonable deadline when it was set. Of course, everyone is pulling to iron out issues and get things ready by that time. Of course, the studio doesn't want to announce a delay.

Then...at some point...there's a knock at the proverbial door. When it's opened...Reality leaps into the room and spin-kicks everyone seven times in the face.

No one can be expected to understand this who has never worked in a professional setting on a major, team-based project involving hundreds of people and has no experience dealing with this type of misfortune in an actual, real-life situation. (Anyone who has real-life experience and claims this has never happened is either unaware of what happened and who saved their project...or is quickly running out of luck.)

Setting "release dates" for something is not about "calculating percentages". That's not how it works. It doesn't matter if a studio is 75% sure...or 88% sure...or 94.36% sure...

It's either going to work out or something is going to crop up. It doesn't matter if the issue crops up early on or if it presents itself in the eleventh hour. It's not a "percentage" that "professional risk assessors" are "responsible" to foresee. It's either there or not there. If it's there, the "chance" of it occurring is 100%. If it's not there, the "chance" is 0%.

There's no "accurate statistical measurement" for the future. There's reality. And reality is based on 1 or 0. If you want a 1 and you get a 0...doesn't matter when or how it happened...circuit cut. Now, work will need to be done to close that circuit whether it takes a day, a month, or a year.

(And the analysts will go, "Oh! I should have accounted for that!"

([And the patch is not going take a year. :) ])
It would be much relieving to know what exactly are going to be added. Total silence just play on the nerves, especially considering how bad they've started their CP2077 journey, it's still haven't forgotten. We still expect that another patch is going to lead to another crash and we're still facing bugs, 5 years have passed! In other case, with any other studio, with any other game, it would be okay, but not in this particular case. There's a good example in the face of Hello Games who developed "No Man's Sky". They constantly interact with their player base, they at least have a dev map, and they did this not because it's humble, or not from their condescension, but because players actually payed them.
 

Attachments

  • c17a49d0-55e9-11eb-b3be-5afc3613ea0c.jpeg
    c17a49d0-55e9-11eb-b3be-5afc3613ea0c.jpeg
    19.9 KB · Views: 105
It would be much relieving to know what exactly are going to be added.

I have good news for you. You are going to have exactly this information in due time.

You know you're getting a patch and you know you're going to find out what's in it.

You're not going to find out what's in it until first they're sure what's definitely going to be in it. They could be working on all sorts of little things and end up killing half their babies before the thing comes out.


Total silence just play on the nerves

Are you alright? Maybe try some mindfulness and self-reflection? I say this to everyone in the thread itching for an immediate dopamine fix, despite the fact that this is not an important thing and is going to come out eventually anyway.
 
And you're under the presumption that this wasn't the case.

Again, you're missing the point about an UNEXPECTED thing arising.

It was not anticipated to be an issue, but unexpectedly it was. Therefore ruining their project management.
That's precisely why good project management builds in contingency buffers: not because it can predict the exact issue, but because it accepts that something will go wrong at some point.

So no, I’m not assuming they didn’t do any risk planning - but if a single unexpected issue was enough to completely blow past a public deadline with no alternative plan in place, that points to either a lack of sufficient buffer or overconfidence in the schedule. That’s not a moral failure - but it is a planning flaw, and it's valid for the community to notice that.

Saying “this wasn’t anticipated, so it’s not bad project management” misses the point. Good project management doesn’t hinge on avoiding surprises - it hinges on absorbing them without letting everything slip.

Again, this is under the assumption that this UNEXPECTED scenario was something that was clearly evident and expectable.

It is most likely that the overall implementation was not seen as risky but this unexpected issue suddenly caused it to be out of nowhere.
I'm not assuming that the specific issue was obvious or “clearly evident” ahead of time. I’m saying that if any part of the project still depends on components that are inherently unstable or prone to unexpected complications - then publicly committing to a date without explicitly accounting for that risk is a misstep.

No schedule is risk-free. That’s why public dates - especially when self-imposed - need to be backed not just by optimism, but by a realistic appraisal of remaining uncertainties. If you leave no margin for error and something goes wrong, that’s not just bad luck - it’s a lack of strategic buffer.

So whether the issue was likely or not isn’t the point. If it was possible, it should have been part of the decision calculus before going public with a deadline.

Yes, but that's the thing. Any single hinting towards anything will ALWAYS lead to people assuming that said thing has been explicitly promised.

This is the nature of things. This is why developers have to be very careful of what they say, especially in regards to content that is in development.
I agree that developers have to be cautious with how they communicate - especially when features are still in flux. But transparency doesn’t require promising or even hinting at content. It can simply mean acknowledging why a delay happened in more meaningful terms than “it’s not ready.”. Clarity doesn’t create false promises - it creates trust.

So yes, I agree: words matter. But avoiding all specifics out of fear that players will misinterpret them often results in sterile, opaque communication, which can feel like a lack of accountability - even when that’s not the intent.

You quite literally accused them of "Dishonesty"
Just to be clear - I’ve never accused the developers of lying or being dishonest.

If someone inferred that from what I wrote, then I’d like to clarify: my criticism was focused on communication style, not intentions. I’ve spoken about the lack of clarity, vagueness, or incoherence that can emerge when dates are missed without meaningful explanations - but that’s not the same as accusing anyone of acting in bad faith.

At no point did I use the word “dishonesty”, nor did I imply that the team deliberately misled the community. I’ve consistently argued for better communication, not because I believe the developers are untrustworthy, but because clear and responsible messaging is part of maintaining a strong relationship with the player base - especially when things don’t go as planned.

Please don’t attribute claims to me that I haven’t made. I’m here to exchange ideas and perspectives, not to question anyone’s integrity.

What's not straightforward about the update of "Patch isn't ready. It needs more work. We'll update you later"?

Yes, it doesn't say specifically what the exact issue is... But you don't NEED to know the exact specifics to know what is being communicated. That the content is not ready for release and needs more development time.
The message "it's not ready, we'll update you later" is indeed straightforward in form - but what I’m pointing out is that, when it follows a missed public deadline, that level of vagueness can easily come across as evasive, even if it’s not meant to be.

I’m not saying we need to know every technical detail - but when you set a specific timeframe and then miss it without offering any meaningful context (even at a high level), it creates a communication gap. That’s where frustration builds, and it’s fair for people to feel that the messaging has become more about damage control than community transparency.

A good middle ground exists: acknowledging what type of issue arose - without overpromising or naming specific features. That kind of honesty helps maintain trust, even in the face of delays.

Again, you seem to be under the assumption that they were NOT reasonably confident in being able to meet the deadline.

Again, I'll mention that it's most likely that they were entirely confident in meeting the deadline, hence them setting the deadline. With the only disruption to that estimation being an UNEXPECTED issue.
It's entirely possible they were confident internally. But confidence alone doesn't justify making a public commitment unless you’ve also factored in a buffer for uncertainty.

That’s really the core of what I’m saying: it's not that they didn't believe they could meet the deadline - it's that when you go public with a specific date, you're assuming a communication responsibility. And if something unexpected does derail the plan, it’s then also reasonable for people to ask: was that risk truly unforeseeable, or just underestimated?

Public announcements aren’t just reflections of internal confidence - they’re also promises to the audience, and with that comes the expectation of accountability if things don’t go as planned.

But... What else should they say?

You say that deep technical insight isn't necessary, but clear communication that doesn't involve it is somehow not enough?

Yes, it's generic. But that's because not everything is a wholly unique and special scenario. In this case it's quite a simple thing. Patch is not ready for the time being, thus they're delaying its release until its ready. They'll update us when they have news to share (Which is normally just "We'll announce a new release date when we figure it out")
I understand that sometimes the situation may be straightforward, and the patch simply isn’t ready.

However, clear communication isn’t just about stating the obvious; it’s about how you present it. Saying “the patch isn’t ready, we’ll update you later” may be factually correct, but it lacks the tone and nuance that make the community feel respected and included in the process - especially after a missed deadline.

Acknowledging that the delay is disappointing, explaining that the team is working hard to resolve specific kinds of challenges (without going into technical minutiae), or even just recognizing the impact on player expectations can go a long way in building trust.

So it’s not about providing “deep technical insight” - it’s about demonstrating accountability and empathy, which generic statements often fail to do.

But they haven't gone silent. They provided this update that says they're delaying it to work on it more.

Also, moderators aren't "Community Voices". They're moderators. They help manage the forums, ensuring people follow the rules and clean up threads. That's it. Outside that, they're simply any other forum user with their own independent views and opinions that are unrelated to any sort of relation to CDPR or the community as a whole.
I agree moderators are not official representatives of CDPR, nor do they speak on behalf of the company.

My point was more about the perception of silence or insufficient official communication - when official channels provide only minimal updates or no detailed context, players naturally turn to community voices (including moderator) to seek clarification or fill gaps.

This is less about who exactly those voices are, and more about the dynamic that emerges when people feel they don’t have enough information from official sources.

Clear, transparent, and timely communication from the developers helps prevent misunderstandings and speculation within the community. When that’s lacking, even well-meaning moderators or community members can become focal points for discussion - whether they want to or not.

Where have they gone radio silent?

They quite literally made an update. That's what this thread is. Them communicating the update.

That they haven't made any further updates simply suggests that there is nothing new to report. Unless you want a daily blog of them saying "Still working on the patch"
I understand that frequent updates on the same status might feel redundant. However, my point is not about the quantity of updates, but about the quality and clarity of the communication.

There’s a difference between saying “the patch isn’t ready, we’ll update later” and providing updates that help the community understand what challenges are being faced, even in broad terms. The goal isn’t daily status reports, but meaningful communication that balances honesty, transparency, and managing expectations - so that the community doesn’t feel left in the dark or dismissed.

Also, it’s worth noting that several days have passed since the June 26 update, and we still haven’t received any additional information or context beyond what was already communicated at the time of the delay announcement. This prolonged silence can unintentionally contribute to frustration and speculation, as the community is left wondering about the progress or challenges faced.

Regular, even if brief, updates that acknowledge ongoing work - even without new breakthroughs - can help maintain trust and reduce uncertainty.

Where's the weak communication?

THIS THREAD IS LITERALLY THEM COMMUNICATING!

I've experienced companies with weak communication. You know what they do? Nothing. Literally nothing. Never respond to anything. Something is delayed? No updates it just doesn't ship when it's supposed to and eventually drops sometime later.

CDPR have quite literally communicated that the patch is being delayed. A reason for the delay. Also, they mention that they will provide more communication later.

This is a far cry from any notion of "Weak Communication". We are not left in the dark. We know exactly what is going on.
I understand that CDPR made an initial update announcing the delay, and that is indeed a form of communication.

However, it’s important to note that this first post is the only official communication so far - the same message that has been shared across various channels.

Since then, what follows in this thread are mostly community posts and discussions, without further direct interaction or updates from CDPR or their official representatives.

In that sense, the ongoing conversation here isn’t really “communication” from the developers, but rather community members trying to interpret, speculate, or ask for more information.

True communication implies an ongoing dialogue or at least periodic official updates to keep the community informed, not just a single announcement followed by silence.

The crux is "Reasonable"

From my point of view, what they have done is reasonable. Since I understand the situation as it pertains to this announced content, I don't feel confused about what is happening, I don't feel left in the dark about what is happening, I am not left with a bunch of questions I want answered.

Yes, I am disappointed that the content was not ready for its stated release date. But I'm not going to lambaste them over it, because there's a myriad of things that can cause issues with meeting deadlines especially in regards to programming. I know I've had my fair share of deadline mishaps due to unexpected issues throughout my life.

Maybe I'd be less lenient if this was an ongoing trend... But outside the initial game release there hasn't been any issues like this. Phantom Liberty and all prior patches released without unexpected delays. So I would not consider 2 hiccups 5 years apart to be a "Trend" (No, I'd consider something like Blizzard patches to be a trend... Where EVERY SINGLE ONE has issues and has done forever). Even more so when you consider the overall development turmoil surrounding the initial release.
Holding developers to a reasonable standard of communication and accountability is not about harsh criticism or hostility - it’s about fostering trust and showing respect for the player community’s investment and opportunities to strengthen that trust through clearer, more transparent communication - especially given the scale of interest and passion around the game.
 
Well yeah,
Announcing a release date and then having to cancel it just before that is always a let down.
For themselves, for the fans, for everyone ... That's why they apologize for it.
Of course there's a good reason for the delay. and everybody will understand that.

But how to avoid this?
Take your time to devellop it, show the fans some transparency on what's cooking, have it tested and when it's ready, announce it's release.
Like they did earlier, Release? when it's ready!
Or just give a release window / timeframe.

But hell, we will see what's coming. Just try to stay alive until then! ;)
 
Ugh, yes. The spin-kicks. How I hate the spin-kicks.
I don't mind them so much on the left. I hate when they hit me on the right. Sensitive ear.

It would be much relieving to know what exactly are going to be added. Total silence just play on the nerves, especially considering how bad they've started their CP2077 journey, it's still haven't forgotten.
This, I believe, is exactly why there's no announcement of specific features. If I say, "Here are the individual things we're doing," then some of those need to be cut because they're causing unexpected issues (or they're creating an enormous delay), that they means I have to go online and disappoint people by saying such-and-such is now canceled or not happening yet.

Personally, I am 100% behind either complete transparency during the dev process, or complete radio silence until something is actually done.

Transparency is still a valid option, but with something as huge and complex as The Witcher or Cyberpunk...there's not going to be a lot to talk about. It would be updates that basically say: "Still working on this or that at the moment. Probably 2 more weeks to go." I think the general internet has more than proven incapable of accepting the actual complexity and workload that goes into something that they view "so simple."

Hence, I like the radio silence idea. Announce the most basic version of, "Something's cooking!" Explain nothing in detail. Share as little as possible. Finish what can be finished. Make sure it's good to go. THEN drop a cool trailer or something, and at the end, put, "Available now." In a sense, no hype train. (So far, I think the release of the Oblivion Remaster shows that this approach can be massively effective if played right. [But I would still have fixed the dang bugs. Bethesda is Bethesda.])
 
I'm pretty sure they're polishing FSR 3.1.4 & FSR 4 with AMD to the best possible extent :).
Don't get your hopes up. These guys are Nvidia partners and unlikely to cater for us AMD owners. They didn't even update the game to FSR3.1 and that was released over a year ago.
 
Don't get your hopes up. These guys are Nvidia partners and unlikely to cater for us AMD owners. They didn't even update the game to FSR3.1 and that was released over a year ago.

Hence they smiley at the end. I don't have high hopes.
 
Just getting back into this game, never made it too far. Should I wait on the 2.3 Update and start from scratch?
 
Just getting back into this game, never made it too far. Should I wait on the 2.3 Update and start from scratch?
These updates have been presented as lovely bonus things to have, not total overhauls, since the major overhaul of the game was released at the same time as Phantom Liberty, so it's very unlikely it will make massive changes.
 
Can we get a sneak peak? Kinda like the "what's new in night city" stuff for 1.2 & 1.3 way back in 2021
 
Last edited:
No you shouldn't. I don't think there will be anything worth waiting ;)
(At least anything which you wouldn't be able to do/enjoy mid game).

These updates have been presented as lovely bonus things to have, not total overhauls, since the major overhaul of the game was released at the same time as Phantom Liberty, so it's very unlikely it will make massive changes.
Sounds good then. Thank you for the info. I've been debating which origin to start with. I literally have all three "intros" completed with different characters and saved. Debating which is best. They all were fun takes in their own ways.
 
More than two weeks now without any further information. Interesting...

a.) there definitely went something wrong
b.) they decide to integrate further stuff and so weren't ready
 
Top Bottom