The amount of "bad ptbs" are worrying
I know the ptb is for testing and are not final builds. But is really bad look the amount of bad ptbs with game breaking changes that the community finds out in less than an hour.
How does this stuff keep happening?
Comments
-
That's actually a good thing, they want to test crazy changes before they go live to see where stuff lands.
4 -
I was about to say something like this.
Of course it isn't the best if the PTB's are bad, but atleast they are willing to test new stuff
1 -
Of course it's good to test new changes, but a PTB like this is supposed to be a playable product. It's not like the finisher mori test, to see where it lands. There is also not that much time to implement too many changes and fixes in the 2-3 weeks before next patch goes live, across all the different platforms.
I am for sure glad players are able to identify bugs and problematic aspects before the actual update drops, but it doesn't really create confidence when there's this many that are this obvious.
2 -
What about the current PTB is "unplayable"?
0 -
It's simple good Q&A testing doesn't come cheap so do the minimal testing then give it to us to bug test/QA for free.
0 -
The ptb is something you opt into and is a TESTING server. It's never been meant to be stable as live.
2 -
This PTB they're upgrading the game from Unity Engine 4 to 5 or w/e it's called and it's unreal how many things that got broken with the transfer. This better be one PTB with no strict dead line to be pushed out to live cause with all the bugs it's gonna need a lot more time for polishing before they push it to live.
4 -
What worries me is this:
Note that it says my video card there, and despite what the error says of the minimum required being 23.3.2, the latest drivers for the R9 380 Series cards is 22.6.1. Now that video card prices have gone back down from the crazy NFT/Bitcoin days I might be finally able to get a new card, but it won't be soon, not until July or August at the soonest.
I really hope these "known issues in D3D12" will not make the game unplayable.0 -
I get a similar message with my PC every single time I boot up the game and it still runs the game just fine.
1 -
Ah, good thanks for that. Wish there was a way to make it stop. It's going to get annoying next patch.
0 -
If they actually listen...
0 -
I just feel like some of this stuff is so obvious that they shouldn't even come to a testing server. They should have been identified as bad and never seen the light of day.
If something is so problematic that players could predict it before even testing it what is the point
3 -
So, i want you to take a look back at all of the multiple PTBs we have had lately, where something wasn't good, and how they changed it. Remember:
- They wanted to nerf billy addons, they didn't
- They wanted to make trickster ridiculous, they walked back some changes before it went live
- They wanted to make Huntress ridiculous, they walked back some changes before it went live, and then again some more later
- They made changes to sadako that made her terrible, walked back some of the changes before they went live, and some more after
- They wanted to do the basekit unbreakable, turned out that failed and they didn't do it.
These are just a few i could think of off the top of my head.
I am critical of BHVR most of the time, but right now they are doing testing right. They are finally making ACTUAL changes to things, and putting them on the PTB so we can test things, and then actually listening to feedback.
1 -
Because it isn't always the case. Like, we don't know that they don't know. It could be that they know, but they want to get it out there anyway, because they know its not going to work, but aren't sure all the reasons why and it takes time to figure those things out.
0 -
I wouldnt say unplayable but bugged to the max. DH is bugged Ds is Bugged Moris are bugged vaulting is bugged flashlights are bugged player models are bugged. The maps have multiple new bugs I can go on just lets say the whole game is one huge bug.
2 -
My complaint is for bugs reported that remain in the game half a year after reporting them.
0 -
I don't recall the previous PTB being that bad.
This one's a rough one for sure, though.
0 -
I mean that card is nearly a decade old at this point, it's gonna fall behind as things get updated.
0 -
How is that good? Everyone knows this is not gonna make it to live servers anyway. What's the point?
0 -
That's not related to the PTB
0 -
Because it takes some nuance to figure these things out. What exactly IS the problem. Its "strong" yes, but is it just plain too strong? Does it lack counterplay? Do they need to weaken it to just make it weaker? Or is there some counterplay that might be added? These are the types of things that you need to test to determine what exactly the problem is. Maybe the whole thing actually feels pretty good, but its just too strong, or maybe it feels totally wrong, and they need to go back to the drawing board.
It gives you an indication of where to go with things.
0 -
My problem is when it seems clear that they didn't do much internal testing when pushing the PTBs out. Victor is undoubtedly one of the most broken killers to ever grace this game and I don't understand how this version even makes a PTB. If they conducted thorough internal testing, the version of the Twins that hit the PTB would be much closer to a balanced killer and it would be much easier for them to make the adjustments necessary to make them fair and fun for both sides. Add on to this that they've apparently been working on this Twins rework for years, and this is what it was?
Things like the DS animation as well. Just seems so poorly made and looks so clunky honestly. Did they really need the community to tell them that? Why couldn't their team just look at that animation and realize that it's not something that fits or looks smooth in the slightest. It's just disappointing honestly.
0 -
So you're asking why are Public Test Builds so buggy when they come out? You pretty much answered your own question. They release PTBs so that the community can find tons of bugs/glitches/crashes that they (the devs) didn't find.
0
