I found a typo. In the mission "Firestarter" when Reed first calls you over the intercom (once you've entered the stadium and are touring around), the subtitles say "ealier" instead of "earlier".
Whole quote is "I couldn't get started ealier without risk of bein' compromised". I think there's also an extra space between the words "started" and "ealier".
Whole quote is "I couldn't get started ealier without risk of bein' compromised". I think there's also an extra space between the words "started" and "ealier".
It’s just funny to read the descriptions of the patch, is that all you could do in 1 week of fixing?
I wash my hands of this game and will continue playing baldur's gate 3
I wash my hands of this game and will continue playing baldur's gate 3
"Allow me to play the Devil's advocate" - Gale
- In case it was missed, it is noted under the patch notes that these are merely highlights of the upcoming patch, NOT the entire patch.
- Also it is better not to rush patches without properly testing them first because a rushed patch can be far worse and cause far more damage.
So there you have it, a reason why you do not want to rush patches.
When is this patch coming out so PS5 owners can finally play? How about you just hurry up and increase the save file size to correct this problem or issue refunds to those of us who can't play
@Vattier
First off, Thanks for continued support for this awesome game.(Possible bug)
On Xbox there is a delay of several seconds before the game actually starts loading a save file. I know this because i have an LED activity indicator on my ssd. This only happens if you load a save file. When you fast travel the game starts loading in the assets instantly. Fixing this would decrease loading times on console with several seconds when you load up a save which is a pretty big deal. I don´t know if this affects PS5 as well.
Last edited:
well release the patch for PC pls. more time in weekend for it. thanks in advance!
Need a setting for mouse sensitivity in the menu! There are mouse sensitivity settings in the game itself, from the first and third person, but in the menu the mouse behaves quite differently, this also applies to hacking, it is very difficult to choose the right number for the correct hacking
I've already reported this bug, but since no one's mentioned it yet - Shutters are closed on the Black Sapphire when returning for the Run This Town quest offered by Mr Hands. The doors behind them open just fine, but I don't yet have the cyberware to phase through solid steel.
From discussions on Steam it appears that this happens if you left the building via shootout rather than sticking to the 'escort' like glue. Momma didn't raise no doormat, so no way was I going to let that guy's attitude slide. Anyway, hopefully this can be included in the fixes because the quest is quite literally impossible to complete without getting inside.
From discussions on Steam it appears that this happens if you left the building via shootout rather than sticking to the 'escort' like glue. Momma didn't raise no doormat, so no way was I going to let that guy's attitude slide. Anyway, hopefully this can be included in the fixes because the quest is quite literally impossible to complete without getting inside.
Attachments
-
20230930091608_1.jpg
No first aid kits disappear anyway, even if there is nothing not to use and not to drink. After a conversation with the sheriff, a bug happens and there is no first aid kit and we do not pass the prologue.
Post automatically merged:
Here you are protecting the developers. And I can't play for a nomad for a week on the highest difficulty because we don't pass the prologue and I'm not the only one. And I paid the money. and I'm sitting waiting for the patch. It's okay to be a lawyer.
Incorrect.
What I am doing is stating that rushed updates do not benefit us regardless of which studio does it, which is why I mentioned Larian because they also can make a mistake and just like CDPR they also "fix one thing, break a hundred more".
So actually I am protecting US the players from rushed and unpredictable non-playtested updates, because of which now YOU as a player are unable to play the Nomad intro on the hardest difficulty and why Playstation players have to abandon their progress due to corrupted saves which are not recoverable.
Why? Precisely because the update wasn't playtested. There are so many bugs in the game, from visuals to gameplay to gamebreaking ones with 2.0 that shouldn't have been.
So... do we really want to rush them into releasing more non-playtested updates which may cause even more severe issues? I do not think we do, so as the Internet lately likes to say; "Let them cook."
Last edited:
I’ve encountered a game breaking bug on Series X, where I cannot progress any longer as auto saves cause the game to crash to dashboard.
This wasn’t an issue until later on in Phantom Liberty. The issue has gradually gotten worse - it started crashing occasionally, then around 50% of the time and now I’ve reached a point where ANY auto save is crashing my game. (I’m currently at ‘I’ve Seen That Face Before’)
I have tried re-installing, turning off cross platform saves, clearing persistent data and re-syncing my saves and nothing has helped. Don’t know if there’s anything else to try or just hope that the issue is fixed in the upcoming patch. I’ve sunk 20+ hours in the DLC at this point so it’s extremely disappointing and frustrating.
This wasn’t an issue until later on in Phantom Liberty. The issue has gradually gotten worse - it started crashing occasionally, then around 50% of the time and now I’ve reached a point where ANY auto save is crashing my game. (I’m currently at ‘I’ve Seen That Face Before’)
I have tried re-installing, turning off cross platform saves, clearing persistent data and re-syncing my saves and nothing has helped. Don’t know if there’s anything else to try or just hope that the issue is fixed in the upcoming patch. I’ve sunk 20+ hours in the DLC at this point so it’s extremely disappointing and frustrating.
i 'm fine with that's but i'll be more on the other side ; the one says fix flc+update 2.0 if i was not even able to launch , play without crash after buying the new dlc .
consummers , us player we don't have the know the "secret sauce" behind dev making patch fix , beta test .. that's their jobs , not our
the good at least , after many days and many topic reporting day one update 2.0 some "majors" issues we get an official statement from Dev , its coming soon xD
i hope only they' wont do the same as on wither 3 NG , 4 patch fix that even resolved some issues , like performance , bug .. thanks to modders i can run finally witcher 3 NG max graphics Ultra + , without bug .. or crash ...
as a player i'm aware , that some update can "brake" some "few" thing , but here we're not talking , a game that launch yesterday but a game that having almost 2 years of fix/improvement : its not like they make patch 2.0 out nowhere . as if 1.63 was a dream and they revamp new skill tree , adding police system on Cyberpunk 2077 1.0 ...
keep in mynd they announced patch 2.0 since almost one year ..
Larian - We hope you have 2h to read through the hundreds of bug fixes, among other fixes that we prepared in these two weeks.
CDPR - Here's 2 or 3 things that will take who knows how long to deploy, and won't even touch the main concerns of the players.
I'll be on CP2077 1.63 until (if ever) this mess is reverted/fixed, and playing BG3 in the meantime.
CDPR - Here's 2 or 3 things that will take who knows how long to deploy, and won't even touch the main concerns of the players.
I'll be on CP2077 1.63 until (if ever) this mess is reverted/fixed, and playing BG3 in the meantime.
CDPR needs to inform Sony to issue PS5 players full refunds for this broken, unplayable joke called Phantom Liberty
(I've inserted multiple full-size images. They're downscaled to 1080P, but if it's still causing lag let me know and I'll insert them as thumbnails)
So after really looking at this rather than begrudgingly focusing on reworking my viz mods for 2.0 - I think it's a stop-gap, meaning they did it on purpose.
Reason being that (I think) they've made serious changes to their RT shading model, either to satisfy some unsaid prerequisite for RR(Ray Reconstruction) or just making changes. People have blamed RR for making characters... chalky/smeared, that's true in non direct light scenarios certainly. Think late day outside of Dicky Twister where you have lots of neon lights but nothing direct. Even with RR off though it's not the same as it used to be. The SSS model for skin has changed as well, likely due to make use of RR. I'm certain of this as a skin mod I previously used gave me similar results to what the base shader did when turning denoising off pre-2.0. Hair shadows aside; Just look at how dead characters are now compared to what they were...
The lost depth, the lack of specular highlights and gradations from dry to oily skin. Gone.
Another striking example is that characters almost look as if there's a second model not being drawn that's replicating their movement. You get areas of solid blackness that undulate across the NPC's surface, sometimes as if there's an unseen box in front of the camera that occludes light as well. That's surely not what's happening, but it looks that way and I suspect it's a consequence of the changes to support RR. This is most prevalent when they are in motion, but you can catch it if you're in a dialogue sequence and the character rocks back and forth a lot, especially if you zoom in.
Wait a minute, Alex, you're not saying.. Alex? WTF?
In WKit one of the changes to the env is a new table called "CharacterBrighteningAreaSettings". With this off, at distance, character models are solid black regardless of the world lighting. So we don't even get the actual ground truth global illumination we had in 1.63.
Thirdly - look at the edge contrast on the head hair below. Hell, the entire model. It's almost like an inverse pre-multiplication error. As if he's bathed in shadow and re-lit... and the hair glow is even stronger that before. Previously Denoising was causing the hair glow when RT is on, now RR is doing it even though it's purpose is to solve the issue that denoising causes all while introducing artifacts of it's own. Great work...
Fourth(also below image) - is that when using Sosuine's RT shadow restoration mod, hair shadows from stubble and bears looks downright awful on skin. Starkly dark, just bad. Not Sosuine's fault to be clear. Just check out this almost absurd darkness that looks like an overblow AO pass. You can't see it because of what is happening, but his facial hair is actually white!
I don't have images for the last issue, but one of the touted benefits of this was to be increased rendering accuracy, but so far I haven't seen that. Light and shadow motion rendering are much better now, but I still see tons of areas where shadows are wiped out even more so that before. That's not a result of more accurate rendering, because without RR and denoising off I can see everything clearly - it's because RR is acting as some kind of Deep Learning Image Based Lighting and over correcting whats on screen. Sometimes it creates there peculiar bright and dark spots. It's bad in it's current form.
So, my take is mostly the same as before; CDPR either f*cked up and/or ran out of time to fix it... leading to a f*ck up and disabled some stuff to cover their tracks while figuring this out in the mean time. Or it's a new RT shading model gone awry - result is the same. It's bad. The game runs even worse while looking substantially worse other than reflections. Sure puddles in the rain are incredibly crisp but now a fantastic cast of characters look like mid quality silicon sex robots amongst other issues.
Last edited: