devtrackers.gg
3 months
ago -
SylenThunder
-
Direct link
Personally, it is totally because of them pushing the console release out.
They are doing exactly what I have always used as a perfect example of what NOT to do.
And to make matters worse, they pushed it out before it was really ready. The only reason I can see for this is to make bank on the summer sales event, and from kids that aren't even in the targeted age group being home for summer vacation and buying games for their consoles.
If you had asked me just prior to this announcement, I would have said to not expect any updates before Thanksgiving. And this would have been based on what I can see from internal testing. (In fact, if you check my post history, you will probably find that I did in fact say that a few times.)
I understand TFP doesn't follow "conventional" development, and that they do things a bit differently. However, they always seemed to be sticking to the traditional Alpha/Beta/Gold process. And I have always stood behind them in that regard. Now they have thrown it all out the window though.
So basically, V1.0 doesn't mean anything. It's just Alpha 22 with a new name for the sake of releasing on the consoles.
And it gets worse. They are basically just dumping out patches willy-nilly with a big lack of information. Look at the Pinned Patch Notes thread, and compare the most recent update with all of the previous ones.
I'll also note that there are a couple of pretty critical issues crippling dedicated servers. One was noted as being included in V1.1 experimental, but wasn't actually. So now it will supposedly be in the next update of 1.1. Even though it should have been a hotfix for V1.0 when they knew what the cause and fix was, and had already implemented it internally.
But wait, there's more! Since something like Alpha 18, their settings for the Steam API have incorrectly reflected the ports for the game. Somehow, they managed to swap the connect port with the query port. You can see this quite easily using Battlemetrics.com.
Address
68.41.181.46:31012 (Game Port)
68.41.181.46:31010 (Query Port)
In that example, the game port is actually 31010, and the Query port is 31012. I had initially reported the discrepancy to Battlemetrics, who informed me that they didn't make any change, they only pull what is in the Steam API.
For a couple of years, I reported this to TFP and was basically told that it wasn't an issue. I clearly explained what the issue with misreporting the data is and was pretty much ignored.
Now we are seeing something similar with downloading the dedicated server. Since Alpha 21 experimental there has been an issue where they push the experimental releases under the stable branch. It isn't consistent either. Sometimes it only affects the Windows build, and sometimes it only seems to affect certain regions. Steam says it is the way TFP is pushing the releases, and TFP's only response has been from a QA rep to say that using the "public" betas tag will pull the stable. Do note that it was almost a year and a half before this information was available.
Sorry, this came out a lot longer than I intended. You have every right to be frustrated about how they are handling this. They are basically making every mistake they can with this release, and it really feels like they are just rushing things for the sake of getting views. Almost like half the streamers that annoy the crap out of us.
They are doing exactly what I have always used as a perfect example of what NOT to do.
And to make matters worse, they pushed it out before it was really ready. The only reason I can see for this is to make bank on the summer sales event, and from kids that aren't even in the targeted age group being home for summer vacation and buying games for their consoles.
If you had asked me just prior to this announcement, I would have said to not expect any updates before Thanksgiving. And this would have been based on what I can see from internal testing. (In fact, if you check my post history, you will probably find that I did in fact say that a few times.)
I understand TFP doesn't follow "conventional" development, and that they do things a bit differently. However, they always seemed to be sticking to the traditional Alpha/Beta/Gold process. And I have always stood behind them in that regard. Now they have thrown it all out the window though.
So basically, V1.0 doesn't mean anything. It's just Alpha 22 with a new name for the sake of releasing on the consoles.
And it gets worse. They are basically just dumping out patches willy-nilly with a big lack of information. Look at the Pinned Patch Notes thread, and compare the most recent update with all of the previous ones.
I'll also note that there are a couple of pretty critical issues crippling dedicated servers. One was noted as being included in V1.1 experimental, but wasn't actually. So now it will supposedly be in the next update of 1.1. Even though it should have been a hotfix for V1.0 when they knew what the cause and fix was, and had already implemented it internally.
But wait, there's more! Since something like Alpha 18, their settings for the Steam API have incorrectly reflected the ports for the game. Somehow, they managed to swap the connect port with the query port. You can see this quite easily using Battlemetrics.com.
Address
68.41.181.46:31012 (Game Port)
68.41.181.46:31010 (Query Port)
In that example, the game port is actually 31010, and the Query port is 31012. I had initially reported the discrepancy to Battlemetrics, who informed me that they didn't make any change, they only pull what is in the Steam API.
For a couple of years, I reported this to TFP and was basically told that it wasn't an issue. I clearly explained what the issue with misreporting the data is and was pretty much ignored.
Now we are seeing something similar with downloading the dedicated server. Since Alpha 21 experimental there has been an issue where they push the experimental releases under the stable branch. It isn't consistent either. Sometimes it only affects the Windows build, and sometimes it only seems to affect certain regions. Steam says it is the way TFP is pushing the releases, and TFP's only response has been from a QA rep to say that using the "public" betas tag will pull the stable. Do note that it was almost a year and a half before this information was available.
Sorry, this came out a lot longer than I intended. You have every right to be frustrated about how they are handling this. They are basically making every mistake they can with this release, and it really feels like they are just rushing things for the sake of getting views. Almost like half the streamers that annoy the crap out of us.