CDPR - how do you manage to release major patches with major bugs?

[MonarchX]

CDPR - how do you manage to release major patches with major bugs?

I just don't get it... The number of people with identical problems after patch 1.10 is so huge that there is no way you can attribute 1.10 bugs to user error. How does this happen? 1.10 was a major super-patch with 600 fixes. Was it actually beta-tested? How could beta testers NOT get all the bugs that so many people get? Why not release BETA patches to the public before finalizing updates? At least that way you can say "Yeah, this is a beta patch, bugs are to be expected" instead of falling on your face on a dirty floor by releasing "MAJOR" super-patches that contain MAJOR bugs? The bigger the patch - the more fixes it brings and the more new major bugs it brings.

That just isn't cool. This time around people weren't even demanding the patch to be released earlier than upcoming DLC. You could have at least tested the patch over the weekend.

How do I sign up to be a beta tester? I am great at spotting, describing, and properly reporting bugs to developers (not as much to the community though). Yet I bet I will never be selected for any Beta testing because I have not posted here enough, which is not a good metric for deciding who can participate in Beta versions and who can't...

 

[TootyNooty]

Have you ever made a game yourself?

On top of that, have you ever even considered how much work goes into it?

Trust me, you can fix one thing and break something completely different somewhere else with no real explanation, also not all bugs are consistent so it's quite easy for things to slip through, and that can happen even in a tiny game, TW3 is HUGE.
Consider how big the game is, there will be thousands of lines of code, thousands of assets, hundreds of areas which all need to be tested and then fixed, altered or checked off as bug free, it's a lot of work and CDPR isn't a huge studio..

Bethesda for example, left Fallout 3, Oblivion and Skyrim full of bugs which the community itself had to fix, when a studio puts in the time to fix this many bugs you aught to be thankful, and respectful.

Give the Reds a break, at least they are actively supporting their game after launch.

 

[wend92]

Maybe thats the problem. Maybe they should be releasing smaller more quality patches.

 

[Krull32]

Bugs can always appear...No matter how long tests are....
Again best example Blizzard..Beta Patch tests over a few months but always a few bugs left ...some big, some not....also also some Gamebreakers...

 

[MonarchX]

I totally love how CDPR supports their products and dedicated themselves to Witcher 3 until 2017! The problem is that the bugs that their patches come from are not some minor, hard to find, petty issues, but MAJOR and easily-spotted by simple players. For example, HOW could they mess up Video / Post-Processing Options Profile Titles for non-English languages? Do they not test non-English Localizations of Witcher 3??? How could they NOT catch the item-disappearing bug in NG+ mode? I just don't get it.

And then the GOG Galaxy Overlay mode... How posts have been out there about people not being able to launch Witcher 3 just because Witcher 3 patches reset GOG Galaxy settings and make Galaxy Overlay (which often prevents Witcher 3 from starting up), an enabled option by default?

 

[M1ckey258]

CDPR have made a great game... but a great game filled with bugs! every bug they fix they create 10 others.

:rage:

 

[Analikital]

I don't know if CDPR could do this but i would like to suggest either releasing patches as open beta at first, that would give a larger variety of systems so the problems will be spotted easier and faster.
Another think they could do is arrange a close beta testing with NDA singed here in the forums, and the community could help beta test any future patches.
I believe both are reasonable approaches, but of course i am not at CDPR so it's not my place to make that choice

Also may i suggest we keep it friendly and polite, i am just saying it for anyone else thinking of posting here.

 

[SantoDorado]

M1ckey258

Following your logic, if 1.10 patch includes over 600 bugs fixes, ...there sould be at least 6000 new bugs!! oh mah gah!

 

[MonarchX]

I totally love how CDPR supports their products and dedicated themselves to Witcher 3 until 2017! The problem is that the bugs that their patches come from are not some minor, hard to find, petty issues, but MAJOR and easily-spotted by simple players. For example, HOW could they mess up Video / Post-Processing Options Profile Titles for non-English languages? Do they not test non-English Localizations of Witcher 3??? How could they NOT catch the item-disappearing bug in NG+ mode? I just don't get it.

And then the GOG Galaxy Overlay mode... How posts have been out there about people not being able to launch Witcher 3 just because Witcher 3 patches reset GOG Galaxy settings and make Galaxy Overlay (which often prevents Witcher 3 from starting up), an enabled option by default?

 

[crazy_v_k]

CDPR should recruit more game testers, it's not the first time that they release a patch that fixes something but breaks something else which worked before.

I can help you guys with testings if you need.
and IMO, you shouldn't rush on releasing the new expansion before fixing these bugs (new patch), these things will affect on the game rankings.
and as you know, game ranking is very important for you and for everyone else

Better late than fail.

 

[XeidiDent]

Just another patch by CDPR.

 

[bsalim]

Have you ever made a game yourself?

On top of that, have you ever even considered how much work goes into it?

Trust me, you can fix one thing and break something completely different somewhere else with no real explanation, also not all bugs are consistent so it's quite easy for things to slip through, and that can happen even in a tiny game, TW3 is HUGE.
Consider how big the game is, there will be thousands of lines of code, thousands of assets, hundreds of areas which all need to be tested and then fixed, altered or checked off as bug free, it's a lot of work and CDPR isn't a huge studio..

Bethesda for example, left Fallout 3, Oblivion and Skyrim full of bugs which the community itself had to fix, when a studio puts in the time to fix this many bugs you aught to be thankful, and respectful.

Give the Reds a break, at least they are actively supporting their game after launch.

No I design and build some of this solar systems most complex satellites. We test the shit out of them before delivering to the customer... Even if it means launch and delivery dates slip...

 

[D4rKy2014]

I did not encounter any major game-breaking problems yet, i think u guys are over reacting, played already 10 hours straight.

 

[AvengerGrim]

Squash a bug and two will spawn. That's pretty much game development in a nutshell, more or less, point is, trying to fix something may very well break something else, that's why hotfix exists and that's why release days are often chaotic.

 

[msg4gsm]

Squash a bug and two will spawn. That's pretty much game development in a nutshell, more or less, point is, trying to fix something may very well break something else, that's why hotfix exists and that's why release days are often chaotic.

That's not the point. Everyone knows and realizes that. The problem is that the new bugs created are so major and noticeable (and mostly uniform across users and platforms) that there is no way CDPR is doing any kind of extensive testing or they know about the bugs and are releasing the patches anyway. There are no other options. Either one is totally unacceptable...

 

[LadyStoneheart]

Maybe thats the problem. Maybe they should be releasing smaller more quality patches.

I'd go with that.

It's all very well for some to get supercilious and say "well you shouldn't expect mods to work after a patch" but that doesn't help people in the middle of a mod-heavy play through who now have ruined games with HoS looming. I didn't want to download the patch because I'd seen the problems with it, but because it contained HoS updates I had no option. The save game I'd planned to use with HoS is wrecked and with the fragility of the fledgling modding community I have no idea if some of the mods I've used will get updated in time, let alone can be.

Texture mods and a couple of others are patched, but even beyond that I now have graphics issues (stretchy people, weird blocks) plus the headings in the graphics menus are now just white blocks and not letters, and regular CTD. I had none of these problems before.

 

[AlrightShadow]

Most of the reoccurring problems post the 1.10 patch seem to involve the free add-ons. I imagine since they aren't apart of the core game it's a bit more trickier to see to what extent the game will be affected with them. I do agree that it would've been good for them to have selected some random members of the public to have access to a beta version, though. Or at least have had the patch come out in two installments over these past couple of weeks. A patch this big was destined to come with problems, we're just going to have to be patient.:wondering:

 

[iz.podpolja]

Problems with this patch can be divided into 6 categories:
CDPR:
- DLCs in NG+ (how on earth did they miss it - is beyond me)
- new bugs (Wolven Gear Hunt Part 1, Closed City II marked as failed)
- Stuff that was in patch notes & is missing (hide HUD, Gwent Tracker)

User:
- changes in balancing the game (mainly nerfing stuff) that some view as bugs
- CTDs, graphical glitches, performance hickups, zombie NPCs and such which can be easily fixed with verifying game files, removing tweaked in, and perhaps deleting d3d11.dll form exe folder - these are majority of what I see on these forums.
- mod-related issues.

Most of the user side could be mitigated with simple information (mods will be broken, remove your ini tweaks, VERIFY your game cache) beforhand.

My conclusion is this patch is actually less buggy then it seems (except for the DLC NG+ stuff).