This is why whenever any 'gamer' or dev tries to pretend that game development is some mysterious, extremely difficult thing. I do believe it's just a lie to cover up their incompetence.
Well it actually is. These people are just incompetent.
If, for example, you don't understand algorithmic complexity and suddenly your n! collision algorithm is taking 30ms, the only way you're going to know how to fix it is "get faster hardware."
The thing is, today's hardware has made it way easier for incompetent developers to survive because it's simply fast enough to brute force almost everything.
that only affects end users? I'm gonna put a big ol' doubt on that one. That doesn't even make any sense unless they're shipping some sort of script compiler as part of their engine and if that is affected by hardware somehow, they've done something monumentally stupid architecturally.
Third act has a shitton of cut content and is very buggy as well. One whole are was cut that they showed off just a couple months ago. One character can only get a bad ending because the quest just ends there since the content was cut. Minthara romance bugged as well.
Game development is why I got into coding as a kid. However, I learned later on that it's a stressful and lower paying job for the skills you bring to the table.
You say that like they're rare.
Many bugs can come out of compiler errors.
of course, I don't see it as likely but I've found quite a few when doing deep investigative dives on specific topics even when you're shilling out enterprise $$ on accuracy.
Considering that major CPU errors make it to the end user as well, I don't doubt it.
Some errors are just subtle from these, and the ones I've seen could have easily made it past every check before someone finally realized something was wrong.
Is there seriously zero testing anymore? They could make a voluntary beta testing group, offer them an exclusive cosmetic thing, have them test a week ahead of a patch. Droves would sign up and when you break something so obvious it's in the test group.
I think it's a bit unfair claiming that they don't have anyone to fix these bugs. They most likely so but they'll be in crunch trying to keep the claim of the least buggy launch of a AAA game.
And considering how broad and many paths Act1 (at least) has. I wouldn't be surprised if they fix one and make four more because of this.
It does fall on panic pushing updates and not properly quality testing patches before release. They might be but as PC gaming is such a broad area with so many varying hardwares; at least from the above quote they mustn't have encountered it.
Not defending shit patches for an overly hyped (not) Baldurs gate (3) but bugs getting created because of quick update life cycles is common in and software development when they panic push updates weekly. So I wouldn't treat this as an outlier. It's just a bunch of employees most likely running ragged trying to get it all fixed whilst they're being whipped by their managers
In my experience, the passionate yet small indie devs in gaming make less buggy games than AAA studios. Bugs have nothing to do with complicated code and unsolvable problems related to computer hardware. Like all other things in a job, it comes down to the competency of the people working. AAA studios are much more likely to hire and employ useless people, fulfilling the Pareto principle. Smaller, more passionate groups are less likely to be accepting of idiots, slackers, and parasites.
Applies to every industry really. I always credited that approach to SpaceX for being able to accelerate so fast as a startup, which (probably still) underpays and overworks their employees leading to quick burnout. But those employees REALLY want to be there and take pride in their accomplishments. Contrast to Boeing, or BlueOrigin that carbon-copied the big cost+plus contractors approach to space and where Bezos has given them more than enough money yet they've barely moved an inch. I have nothing against the employees of the other companies but they have different working environments and different priorities.
Agreed. I'll take it even further, and it applies to all groups of humans, regardless of pursuit. It's also why hobbies always start out with small, passionate groups, and the more "normies" enter it, the more it becomes watered down, pushing out the people who started it because they can no longer stand the medium or the people part of it.
Not sure how this can be combated, except through stringent gate keeping, and as a general rule, having a healthier wider society, with healthier and better people as part of the larger group of people/nation, that are less prone to watering down niche groups, and less wanting to do so, knowing the destructive nature of it.
Wow, look at mister bigshot gamedev, here. You think figuring out that you have a bug and finding out what causes it is as simple as Godot telling you "There is an error in line xxx." Tell me you are a barely competent coder without telling me that you are a barely competent coder. Is this how you want to earn your cred? First you shit on your fellow video content creators and now you shit on your fellow gamedevs. Ah, but they aren't your "fellow" anything. They're your competition. There's not enough pie for everyone. It all makes sense.
I might agree with you on the "compiler corruption", which could mean anything from bad compilier flags to something on the level of the Pentium FDIV bug, but what's with the cohort identity politics?
All QA testing budget went to the gay sex scenes.
I thought that was a pedobear reference?
Totally straight guys rushing into every BG3 converstaion so he can tell everyone about the gay bear sex.
Comment Reported for: Rule 3 - Harassment
I don't see how.
They're just malding and using the report as a "super downvote" because they can't handle the bants.
Well it actually is. These people are just incompetent.
If, for example, you don't understand algorithmic complexity and suddenly your n! collision algorithm is taking 30ms, the only way you're going to know how to fix it is "get faster hardware."
The thing is, today's hardware has made it way easier for incompetent developers to survive because it's simply fast enough to brute force almost everything.
Also:
that only affects end users? I'm gonna put a big ol' doubt on that one. That doesn't even make any sense unless they're shipping some sort of script compiler as part of their engine and if that is affected by hardware somehow, they've done something monumentally stupid architecturally.
Third act has a shitton of cut content and is very buggy as well. One whole are was cut that they showed off just a couple months ago. One character can only get a bad ending because the quest just ends there since the content was cut. Minthara romance bugged as well.
I suspect working for these gaming companies is a shit job so good people don't stick around.
Bold of you to assume they're even hiring any competent developers to begin with.
I wonder if anyone has started calling this game BG 3/10 yet.
Game development is why I got into coding as a kid. However, I learned later on that it's a stressful and lower paying job for the skills you bring to the table.
Compiler error?
Is every large company 99% diversity hires?
https://x.com/mugenlord/status/1690749143336075264
🙄
You say that like they're rare. Many bugs can come out of compiler errors.
of course, I don't see it as likely but I've found quite a few when doing deep investigative dives on specific topics even when you're shilling out enterprise $$ on accuracy.
Compiler errors that make it to the end user? No, this just means that they didn't test their game on all platforms.
https://en.wikipedia.org/wiki/Pentium_FDIV_bug
Considering that major CPU errors make it to the end user as well, I don't doubt it.
Some errors are just subtle from these, and the ones I've seen could have easily made it past every check before someone finally realized something was wrong.
Is there seriously zero testing anymore? They could make a voluntary beta testing group, offer them an exclusive cosmetic thing, have them test a week ahead of a patch. Droves would sign up and when you break something so obvious it's in the test group.
Aside from making sure it literally doesn't make your console explode? Not really. If anything, the playerbase are the beta testers.
One more benefit of only playing games 6 to 10 years after they launch. It's also why Early Access is the dumbest shit ever.
Meanwhile, Cult of the Lamb just had another update that added a kind of survival mode (where you have to eat and sleep like your followers).
Just started a new save a couple days ago, having a blast with it.
I think it's a bit unfair claiming that they don't have anyone to fix these bugs. They most likely so but they'll be in crunch trying to keep the claim of the least buggy launch of a AAA game.
And considering how broad and many paths Act1 (at least) has. I wouldn't be surprised if they fix one and make four more because of this.
It does fall on panic pushing updates and not properly quality testing patches before release. They might be but as PC gaming is such a broad area with so many varying hardwares; at least from the above quote they mustn't have encountered it.
Not defending shit patches for an overly hyped (not) Baldurs gate (3) but bugs getting created because of quick update life cycles is common in and software development when they panic push updates weekly. So I wouldn't treat this as an outlier. It's just a bunch of employees most likely running ragged trying to get it all fixed whilst they're being whipped by their managers
In my experience, the passionate yet small indie devs in gaming make less buggy games than AAA studios. Bugs have nothing to do with complicated code and unsolvable problems related to computer hardware. Like all other things in a job, it comes down to the competency of the people working. AAA studios are much more likely to hire and employ useless people, fulfilling the Pareto principle. Smaller, more passionate groups are less likely to be accepting of idiots, slackers, and parasites.
Applies to every industry really. I always credited that approach to SpaceX for being able to accelerate so fast as a startup, which (probably still) underpays and overworks their employees leading to quick burnout. But those employees REALLY want to be there and take pride in their accomplishments. Contrast to Boeing, or BlueOrigin that carbon-copied the big cost+plus contractors approach to space and where Bezos has given them more than enough money yet they've barely moved an inch. I have nothing against the employees of the other companies but they have different working environments and different priorities.
Agreed. I'll take it even further, and it applies to all groups of humans, regardless of pursuit. It's also why hobbies always start out with small, passionate groups, and the more "normies" enter it, the more it becomes watered down, pushing out the people who started it because they can no longer stand the medium or the people part of it.
Not sure how this can be combated, except through stringent gate keeping, and as a general rule, having a healthier wider society, with healthier and better people as part of the larger group of people/nation, that are less prone to watering down niche groups, and less wanting to do so, knowing the destructive nature of it.
All this is even worse when you realize that the game has been out for... what? Over a year?
Wow, look at mister bigshot gamedev, here. You think figuring out that you have a bug and finding out what causes it is as simple as Godot telling you "There is an error in line xxx." Tell me you are a barely competent coder without telling me that you are a barely competent coder. Is this how you want to earn your cred? First you shit on your fellow video content creators and now you shit on your fellow gamedevs. Ah, but they aren't your "fellow" anything. They're your competition. There's not enough pie for everyone. It all makes sense.
You're a snake, Lethn.
I might agree with you on the "compiler corruption", which could mean anything from bad compilier flags to something on the level of the Pentium FDIV bug, but what's with the cohort identity politics?