|
I also started a topic on us.forums.blizzard.com.
I have many top foreign friends and we just met one friend on ladder.
Trutacz is from Europe, Poland and we were able to play on TR 16 HIGH for completely fine.(He had VPN on)
However, today we just played each other and he didn’t have VPN on. Every minute the game pass, we don’t know the exact reason for dropping TR much more lower.(TR 8 LOW)
So I came up with an idea that it would be nice to have a command like “/SET TR number”
Previously ICCup was using “/ally ID” and confirming with “/ok” command to prevent the error recording match history when your ally gets eliminated and you still win the game.
This would be great idea when we have this kind of command when the dynamic turn rate goes wild and uncomfortable to play with.
|
I think this would be a nice quality of life improvement.
|
tr16 high = tr10/tr12 low.is not exactly that fine.but I agree turn rate is way sensitive.it basically drops by alt tabbing..
|
Either blizzard should fix this dynamic turnrate issue or add this command in... or both.
Would really help with peru
|
|
|
The command is a neat idea.
|
|
|
I think such a command would do more harm than good, because sadly most people don't put in the effort to research WHAT turn rate and latency really IS.
So you would end up with many people using the command wrong and making the game worse for everyone.
Many people will blindly use /SET TR 24 because they think 24 = good, but don't realise there is a valid network connection related REASON that the TR should NOT be 24 in this specific game.
If you set a turn rate too high, the game will stutter a lot more than a slightly lower turnrate.
|
Can someone actually explain me the difference between TR and Latency? Like why is TR16 High more or less same as TR12 Low? why do we have 2 things that does very similar thing? I am legit confused (btw I know that TR is turn rate, and what is latency, im confused as the difference between the two) thanks
|
On August 24 2019 07:45 sM.Zik wrote:
Can someone actually explain me the difference between TR and Latency? Like why is TR16 High more or less same as TR12 Low? why do we have 2 things that does very similar thing? I am legit confused (btw I know that TR is turn rate, and what is latency, im confused as the difference between the two) thanks
Well this is an amazing question I hope someone can explain better...
I feel like this could be a good thing at the top of the ladder / tournaments for the top players, but I don't feel the command would be widely used aside from that.
|
Here is an expanation about Turn Rate and Latency by blizzard:
https://us.forums.blizzard.com/en/starcraft/t/turn-rates-matchmaking-and-you/519
As i already said: It takes some time and effort to fully read and understand. Its not a one sentence explanation.
And since i believe 95% of the players will NOT put in this time and effort, they will actually use the command in a wrong way, which would be very bad.
|
On August 24 2019 09:04 MasterReY wrote:Here is an expanation about Turn Rate and Latency by blizzard: https://us.forums.blizzard.com/en/starcraft/t/turn-rates-matchmaking-and-you/519As i already said: It takes some time and effort to fully read and understand. Its not a one sentence explanation. And since i believe 95% of the players will NOT put in this time and effort, they will actually use the command in a wrong way, which would be very bad.
this can be overcome by only activating if both players agree.
Example:
P1 does /tr 16
P2 has to also type /tr16 for it to go into affect
|
average player is dumb and cannot be trusted with such a command. they will just set tr 24 on everything then blame blizzard for the stutterfest that follows. the best thing is for blizz to finetune the dynamic tr algorithm so that it works better in niche situations like scan/trutacz
|
On August 24 2019 12:40 ggsimida wrote:
average player is dumb and cannot be trusted with such a command. they will just set tr 24 on everything then blame blizzard for the stutterfest that follows. the best thing is for blizz to finetune the dynamic tr algorithm so that it works better in niche situations like scan/trutacz
You know what would be an easy way to fine tune it? Just make the lowest turn rate 12. I'd rather have a slightly laggy 12 than attempt to play at 8 or 10.
|
On August 24 2019 01:57 -Debaser- wrote:Either blizzard should fix this dynamic turnrate issue or add this command in... or both. Would really help with peru
is funny cuz peru players play vs each other in TR8.most of them have closed port so they are using proxies that are going to USA then return to Peru :d
|
Wow, finally I see a good explanation! Thank you for linking this! 
|
On August 24 2019 09:04 MasterReY wrote:Here is an expanation about Turn Rate and Latency by blizzard: https://us.forums.blizzard.com/en/starcraft/t/turn-rates-matchmaking-and-you/519As i already said: It takes some time and effort to fully read and understand. Its not a one sentence explanation. And since i believe 95% of the players will NOT put in this time and effort, they will actually use the command in a wrong way, which would be very bad.
Thank you, this is exactly what I was looking for. Everyone needs to read this.. so many people on b.net arguing over TR and lag it makes me insane, especially in the fastest community (basically people that never played on anything better than TR8 before SC:R since they werent on iccup).
|
On August 24 2019 23:49 sM.Zik wrote:Thank you, this is exactly what I was looking for. Everyone needs to read this.. so many people on b.net arguing over TR and lag it makes me insane, especially in the fastest community (basically people that never played on anything better than TR8 before SC:R since they werent on iccup).
Nothing ticks me off more about Brood War than people who set their hosted lobbies at TR24 despite having abysmal internet/connection, and the people who set extra high latency repeatedly in the game when it is unnecessary. The whole "more = better" mindset is so infantile and idiotic.
PS The change for keystrokes to set latency between 1.16 and 1.18 was annoying for a while for this reason. Sadly, this is a keystroke combination that just about any long-time player needs to have in his arsenal along with 1a2a3a and enter gg enter, because there are people who legitimately just continuously change the latency back to whatever their dumbass thinks is "better." So many lagless games where some idiot just keeps changing it back to what they think is better. I have had games where I had to change the latency legitimately over 30 times.
|
On August 24 2019 07:39 MasterReY wrote:
I think such a command would do more harm than good, because sadly most people don't put in the effort to research WHAT turn rate and latency really IS.
So you would end up with many people using the command wrong and making the game worse for everyone.
Many people will blindly use /SET TR 24 because they think 24 = good, but don't realise there is a valid network connection related REASON that the TR should NOT be 24 in this specific game.
If you set a turn rate too high, the game will stutter a lot more than a slightly lower turnrate.
^ exactly
|
On August 25 2019 02:15 Jealous wrote:Show nested quote +On August 24 2019 23:49 sM.Zik wrote:On August 24 2019 09:04 MasterReY wrote:Here is an expanation about Turn Rate and Latency by blizzard: https://us.forums.blizzard.com/en/starcraft/t/turn-rates-matchmaking-and-you/519As i already said: It takes some time and effort to fully read and understand. Its not a one sentence explanation. And since i believe 95% of the players will NOT put in this time and effort, they will actually use the command in a wrong way, which would be very bad. Thank you, this is exactly what I was looking for. Everyone needs to read this.. so many people on b.net arguing over TR and lag it makes me insane, especially in the fastest community (basically people that never played on anything better than TR8 before SC:R since they werent on iccup). Nothing ticks me off more about Brood War than people who set their hosted lobbies at TR24 despite having abysmal internet/connection, and the people who set extra high latency repeatedly in the game when it is unnecessary. The whole "more = better" mindset is so infantile and idiotic. PS The change for keystrokes to set latency between 1.16 and 1.18 was annoying for a while for this reason. Sadly, this is a keystroke combination that just about any long-time player needs to have in his arsenal along with 1a2a3a and enter gg enter, because there are people who legitimately just continuously change the latency back to whatever their dumbass thinks is "better." So many lagless games where some idiot just keeps changing it back to what they think is better. I have had games where I had to change the latency legitimately over 30 times.
People setting extra high latency ingame because they think higher = better should be demonstration in itself that having a command to set the turn-rate is a *terrible* idea lol. Blizzard should never have released settable turn-rates at all; they can't explain it to people and took like what, 2 years? to even confirm that 3rd parties were correct about what the equivalent turn-rate for L2 was (when we had prominent people like Artosis trying to claim it was equivalent to TR24). People were obviously going to want to play at TR24 always, given the option, and it just leads to Korea's player-base being even more insular than they already were. Whereas TR12/L2 has latency requirements that are roughly okay for anyone in the world to play anyone else (outside of some problematic areas like Australia), TR24 is too strict for even parts of the same continent to play with each other reliably.
Dynamic turn-rates in itself is a fine idea, but why in the hell would you implement that and *also* leave the user-set Low, High, Extra High latency settings? What person in their right mind would want to play on a higher latency than necessary to maintain a stable connection?
The "real" fix for the problem mentioned in the OP is to implement a better dynamic turn rate system, and also build better network infrastructure so people don't have to play on VPNs to get stable connections to each other. If you implement a dynamic turn rate system and people are still having to mess with the latency all the time, you've fucked up. Blizzard needs to stop giving players the things they ask for directly and start thinking about the problems that cause players to ask for those things. That, or stop futzing around and let the community deal with it properly.
|
|
|
|
|
|
EPT
