Although I agree -they basically see us as "testers who pay us to test our game"-, that wasn't my point. When the unexpected happens and they happen to fix a bug -mostly after months and many reports-, when there's an upgrade and beta branch becomes the normal branch, we encounter the same bug, that led me to think, maybe there's something funny going on with version management, wanted to check if I get some answers.Why does TW need to bug test when they have people playing ea to do it for them?
Yeah I get what you're saying I was just being a sarcastic jerk. I may be wrong but it just seems like their internal testing is for ****. It appears as though they'll run the game through simulations but no one internally is actually playing the updates because most of these bugs are readily apparent after an hour or 2. But as far as why we get the same ones over and over your guess is as good as mine.
That would be a rookie mistake, but also the most likely explanation. The alternative explanation is that they are making so many small changes (presumably to fix something) that some of those changes inevitably cause more bugs and performance drops, that may or may not have the same cause, but have the same symptoms - the most likely culprits being the engine team who are responsible for performance. It's as if the experienced people in the team left and were replaced by interns.
I'm thinking of a scenario, where they forget to carry the fix over to the beta branch. After what I have seen, it doesn't seem so unrealistic to me. Don't take me wrong but stuff like "being able to enable auto-block in MP" pretty much sets my expectations at the bottom. That kind of scenario would be.. comedy material, if true.
Any time you see a fixed bug reappear in the next version it is almost always out of date code being merged back into the project. Proper use of source code management software should prevent this. Games like Space Engineers is rather infamous for this problem.
