|
On March 13 2018 08:43 GGzerG wrote:
I have a serious question, I feel like it is almost impossible to get the same mouse accuracy I had before Remastered...
-Does Verticle Sync effect your mouse accuracy / speed?
-Does HD Graphics affect mouse speed? ( In FULL Screen)
-Does RealTime lighting OR Environmental effects, effect mouse speed or potentially the game speed if your computer isn't running it fast enough?
-Shadow Stacking?
-Enable Color cycling does seem like it effects my mouse speed, not sure though...
I am perplexed by all of these settings, I am not even really sure what they all do really, as they are not all well explained, and how they effect the performance of the game.
Anyone have any input on this?
I'm having the exact same problem, I've tried playing around with all the settings and can't get it right, I presume it's due to the limitations of my computer. I
|
On March 13 2018 18:29 jello_biafra wrote:Show nested quote +On March 13 2018 08:43 GGzerG wrote:
I have a serious question, I feel like it is almost impossible to get the same mouse accuracy I had before Remastered...
-Does Verticle Sync effect your mouse accuracy / speed?
-Does HD Graphics affect mouse speed? ( In FULL Screen)
-Does RealTime lighting OR Environmental effects, effect mouse speed or potentially the game speed if your computer isn't running it fast enough?
-Shadow Stacking?
-Enable Color cycling does seem like it effects my mouse speed, not sure though...
I am perplexed by all of these settings, I am not even really sure what they all do really, as they are not all well explained, and how they effect the performance of the game.
Anyone have any input on this? I'm having the exact same problem, I've tried playing around with all the settings and can't get it right, I presume it's due to the limitations of my computer. I
Yea, I feel I am going to have to get a new computer, keyboard and mouse to be safe lol
|
France1919 Posts
A feature that would be awesome is the ability to select some of your replays and make them public, they would appear on your profile with a little description that you wrote and people could click directly to watch them.
|
On March 14 2018 17:39 HaN- wrote:
A feature that would be awesome is the ability to select some of your replays and make them public, they would appear on your profile with a little description that you wrote and people could click directly to watch them.
i believe u can do that on starlogg
|
I'm back and will update OP today.
|
Observing/Casting requests:
- Ability to either set colors specifically, or have 1v1's directly change colors to red/blue in observer mode. Ability to swap player colors on command (i.e. red player is now blue, and vice versa)
- All-Chat/Referee chat to players when in observer slot
- Observer slot scalable to >4 if smaller map.
- Observers to have best-efforts networking, meaning the two players dont have to worry about how many obs exist. This would be hard AS FUCK for the engineers to do, but GOOD GOD it would be awesome for live events.
- Ability to set where center of screen is for following-units. This is because on some casting gigs, people fill the bottom with overlay stuff, making the "center" of the screen slightly higher than the exact middle of the monitor. Makes easier obs/casting experience.
- Top right player stats/info box to be set width
- Open API or ability to read player names/races/color directly from games actively observing. That would be dope for automated overlays. I know you can do it retro for replays, but live events are difficult.
- Disable F5 key.
- Replay and observer intefaces to be exact same or similar window positions. (Why is the replay unit window so massive?)
- Text to display map name over/under player stats on top right.
|
I don't care if my opponent race picks, but Blizz better not do something dumb like implementing matchup-specific ladder queries. Every little bottleneck in the match-making can throttle the whole thing with how few players we have left outside Korea.
Instead, they could adopt a system where each player specifies preferences that have no bearing on the match-seeking process but comes into play after the match is made.
What would the inputs be?
John would enter TvZ > TvP > PvT > PvZ > PvP > TvT > ZvP > ZvT > ZvZ. John is a Terran player who would like to play as Protoss to avoid TvT but not as Zerg.
Bob would enter ZvP > ZvT > TvZ > TvP > PvZ > ZvZ > PvT > PvP > TvT. Bob is a Zerg player who off-races as Terran to avoid ZvZ and also enjoys PvZ more than ZvZ.
If the match up lists Bob's race second, then Bob would enter PvZ > TvZ > ZvT > PvT > ZvP > ZvZ > TvP > PvP > TvT.
Based on these inputs, an algorithm can produce the list of match ups from which no person can be made happier without making someone else less happy. From this list, the algorithm would then choose the match-up that reduces the rank difference in the following sense: In the case of John and Bob, that would PvZ and TvZ. Of these, John ranks PvZ 4th and Bob ranks it 1st with a difference of 4-1=3. In the case of TvZ, John ranks it 1st and Bob ranks it 2nd with a difference of 2-1=1. The algorithm would select TvZ, where John is T and Bob is Z.
What if John is matched against his Twin?
If the Twin's race is listed second, then the Twin would enter ZvT > PvT > TvP > ZvP > PvP > TvT > PvZ > TvZ > ZvZ
In this case, TvZ, ZvT, TvP and PvT would be the match-ups that survive the first pass. TvP and PvT survive the second pass since both minimize rank difference. However, who gets to play their main race? Randomize.
The downside to this system is that there will be occasional mismatches when someone doesn't get to play his main race and god damn it starcraft fans will be whiny again like they always are. Wawawawawa boohoo. But hey, you would like this more than TvT, right? Oh wait, I am sure that the TvT fanboys will start complaining then. "I never get to play this beautiful and most complex matchup that is like go boohoo wawawawa woe is me." Some group ALWAYS complains, and complains loudly.
--
That was a joke. I don't mind if you implement this, but all joking aside, I just want you to fix the bare basics Blizzard. You know...adding friends across servers? Reducing the unnecessary part of lag (the part that is due to your software rather than due to latency). Stop logging me out every five minutes on some days. 2v2 ladder. How about making the SD graphics reasonable for people priced out of the video card market by cryptocurrency mining? Even cartoon graphics would be preferable to the weirdness that is SCR SD graphics.
|
France1919 Posts
- /whois "channel name"
does a similar command exist? if not implement it
- ability to see if there are observers in the game
- also a minor thing, put the TR info slightly more in the corner on the same height as minerals-gas-population infos
|
On March 14 2018 23:31 kogeT wrote:
I'm back and will update OP today.
I always wanted a feature like if you had 20 island maps in a folder, it will randomly pick a map from targeted folder.
|
I updated OP with following points:
- 2x and 4x speed on replays seems to be same / close to the same (tested on 2 computers)
- Random map selection from a folder
- F10 menu in game loads slowly; Preload the menu?
- Improve latency when opening user profiles (it takes a long time to load now)
- Ability to either set colors specifically, or have 1v1's directly change colors to red/blue in observer mode. Ability to swap player colors on command (i.e. red player is now blue, and vice versa)
- All-Chat/Referee chat to players when in observer slot
- Observer slot scalable to >4 if smaller map.
- Observers to have best-efforts networking, meaning the two players dont have to worry about how many obs exist. This would be hard AS FUCK for the engineers to do, but GOOD GOD it would be awesome for live events.
- Ability to set where center of screen is for following-units. This is because on some casting gigs, people fill the bottom with overlay stuff, making the "center" of the screen slightly higher than the exact middle of the monitor. Makes easier obs/casting experience.
- Top right player stats/info box to be set width
- Open API or ability to read player names/races/color directly from games actively observing. That would be dope for automated overlays. I know you can do it retro for replays, but live events are difficult.
- Option to disable/reassign F5 key (as a player I hit it quite often when trying to hit F5, same progamers!)
- Replay and observer intefaces to be exact same or similar window positions. (Why is the replay unit window so massive?)
- Text to display map name over/under player stats on top right.
- /whois <channel> command doesn't work
Rest of stuff I found too fluffly / not relevant / covered by other points (meaning Blizzard should first focus on some of the other great points we came up with)
|
I just posted this on your blizzard forum, Koget.
Right now, foreigners can't play ANY koreans it seems. You wait 1000+ seconds only to get paired against someone "local" to you, with 300 pts lower MMR. What kind of ladder is this? Sure, no lag, but we need blizzard to realize, we DONT NEED 24 TR to play. Neither do the pros.
If Blizzard is aware of the old Fish server during 1.16 patch, the pros played on "#L2" which is basically TR14 or so. We should optimize around that TR, not try to optimize around some TR24.
(in response to one of your list items).......
- Keep on working on 1v1 matchmaking algorythm. IDEA, a step model: initial 30 seconds look for players with close MMR/good latency, 30-60 second - extend latency range (TR10-12), 60+ second extend MMR range and regions, 120+ 300~ MMR range + latency up to TR10.
|
On March 16 2018 23:04 ProtossGG wrote:
I just posted this on your blizzard forum, Koget.
Right now, foreigners can't play ANY koreans it seems. You wait 1000+ seconds only to get paired against someone "local" to you, with 300 pts lower MMR. What kind of ladder is this? Sure, no lag, but we need blizzard to realize, we DONT NEED 24 TR to play. Neither do the pros.
If Blizzard is aware of the old Fish server during 1.16 patch, the pros played on "#L2" which is basically TR14 or so. We should optimize around that TR, not try to optimize around some TR24.
(in response to one of your list items).......
- Keep on working on 1v1 matchmaking algorythm. IDEA, a step model: initial 30 seconds look for players with close MMR/good latency, 30-60 second - extend latency range (TR10-12), 60+ second extend MMR range and regions, 120+ 300~ MMR range + latency up to TR10.
we DONT NEED 24 TR to play. Neither do the pros. Are you there official speaksmen of koreans/pros? "We dont need perfect latency!". This has to be a first. What about all the muta micro people? You are trying to worsen it for the majority, just to make a minority happy
|
On March 16 2018 23:21 Poixyois wrote:Show nested quote +On March 16 2018 23:04 ProtossGG wrote:
I just posted this on your blizzard forum, Koget.
Right now, foreigners can't play ANY koreans it seems. You wait 1000+ seconds only to get paired against someone "local" to you, with 300 pts lower MMR. What kind of ladder is this? Sure, no lag, but we need blizzard to realize, we DONT NEED 24 TR to play. Neither do the pros.
If Blizzard is aware of the old Fish server during 1.16 patch, the pros played on "#L2" which is basically TR14 or so. We should optimize around that TR, not try to optimize around some TR24.
(in response to one of your list items).......
- Keep on working on 1v1 matchmaking algorythm. IDEA, a step model: initial 30 seconds look for players with close MMR/good latency, 30-60 second - extend latency range (TR10-12), 60+ second extend MMR range and regions, 120+ 300~ MMR range + latency up to TR10.
we DONT NEED 24 TR to play. Neither do the pros. Are you there official speaksmen of koreans/pros? "We dont need perfect latency!". This has to be a first. What about all the muta micro people?
Since original bw was with L3 L2 L1 and 2 years ago a program called low'latency hack started to be really popular that emulate the muta micro from single player,and TR8 10 =l1 TR12 14=L2 and TR16 =L1 we are in new waters already with tr 20 tr 24,why? I JUST WANNA KNOW WHY! Why they are adding more trs like this.
|
On March 16 2018 23:04 ProtossGG wrote:
I just posted this on your blizzard forum, Koget.
Right now, foreigners can't play ANY koreans it seems. You wait 1000+ seconds only to get paired against someone "local" to you, with 300 pts lower MMR. What kind of ladder is this? Sure, no lag, but we need blizzard to realize, we DONT NEED 24 TR to play. Neither do the pros.
If Blizzard is aware of the old Fish server during 1.16 patch, the pros played on "#L2" which is basically TR14 or so. We should optimize around that TR, not try to optimize around some TR24.
(in response to one of your list items).......
- Keep on working on 1v1 matchmaking algorythm. IDEA, a step model: initial 30 seconds look for players with close MMR/good latency, 30-60 second - extend latency range (TR10-12), 60+ second extend MMR range and regions, 120+ 300~ MMR range + latency up to TR10.
Im more for a fixed one tr12 to 16,fix your problem via low high extra,game lags well that sux go find other oponent,as a zerg player is just terrible to play in tr8 and most of cases is just the TR acting stupid,one game tr16 high,next game same oponent tr8 just like that.
|
On March 16 2018 23:21 Poixyois wrote:Show nested quote +On March 16 2018 23:04 ProtossGG wrote:
I just posted this on your blizzard forum, Koget.
Right now, foreigners can't play ANY koreans it seems. You wait 1000+ seconds only to get paired against someone "local" to you, with 300 pts lower MMR. What kind of ladder is this? Sure, no lag, but we need blizzard to realize, we DONT NEED 24 TR to play. Neither do the pros.
If Blizzard is aware of the old Fish server during 1.16 patch, the pros played on "#L2" which is basically TR14 or so. We should optimize around that TR, not try to optimize around some TR24.
(in response to one of your list items).......
- Keep on working on 1v1 matchmaking algorythm. IDEA, a step model: initial 30 seconds look for players with close MMR/good latency, 30-60 second - extend latency range (TR10-12), 60+ second extend MMR range and regions, 120+ 300~ MMR range + latency up to TR10.
we DONT NEED 24 TR to play. Neither do the pros. Are you there official speaksmen of koreans/pros? "We dont need perfect latency!". This has to be a first. What about all the muta micro people? You are trying to worsen it for the majority, just to make a minority happy
What are you talking about? You're probably some 1700 MMR player who is allured by the best TR ever. You probably can't even discern TR 24 vs TR 16.
Do you even know how Fish was played? It was played PRIMARILY on #L2 which is basically TR14/TR16. No one ever complained on Fish and it worked well enough ... "well enough"
There is no reason to have TR 24 and base the algorithm on that. You're missing the point that I am trying to make. I'm not trying to be a spokesman, but simply voicing the ladder concerns that many 2100-2500 foreigners face. You're probably not in this pool, so you don't get it. Try to understand other perspectives.
Pros didn't sit there and say "WOW #L2 SUCKS." They played happily on it. Sometimes, yes, they'd go to #L1. But either way, basing the algorithm on TR12/14/16 makes a lot more sense than trying to pair players based on TR 24 and keep it "local." And this suggestion isn't helping a small minority -- it would be trying to help everyone because everyone can play happily on reasonable TRs. It's not fun knowing I will wait 1000 seconds to get a match only to play someone in Peru because that's considered "local" and is -200 pts my MMR.
|
On March 16 2018 23:33 [sc1f]eonzerg wrote:Show nested quote +On March 16 2018 23:21 Poixyois wrote:On March 16 2018 23:04 ProtossGG wrote:
I just posted this on your blizzard forum, Koget.
Right now, foreigners can't play ANY koreans it seems. You wait 1000+ seconds only to get paired against someone "local" to you, with 300 pts lower MMR. What kind of ladder is this? Sure, no lag, but we need blizzard to realize, we DONT NEED 24 TR to play. Neither do the pros.
If Blizzard is aware of the old Fish server during 1.16 patch, the pros played on "#L2" which is basically TR14 or so. We should optimize around that TR, not try to optimize around some TR24.
(in response to one of your list items).......
- Keep on working on 1v1 matchmaking algorythm. IDEA, a step model: initial 30 seconds look for players with close MMR/good latency, 30-60 second - extend latency range (TR10-12), 60+ second extend MMR range and regions, 120+ 300~ MMR range + latency up to TR10.
we DONT NEED 24 TR to play. Neither do the pros. Are you there official speaksmen of koreans/pros? "We dont need perfect latency!". This has to be a first. What about all the muta micro people? Since original bw was with L3 L2 L1 and 2 years ago a program called low'latency hack started to be really popular that emulate the muta micro from single player,and TR8 10 =l1 TR12 14=L2 and TR16 =L1 we are in new waters already with tr 20 tr 24,why? I JUST WANNA KNOW WHY! Why they are adding more trs like this.
Exactly the point I'm trying to make. L2 was good enough even by pro standards, so why be fancy and add new TRs and make people wait 1000+ seconds to queue a match. Eon gets it. 
|
The rare occasion i get a korean I can play them on tr14--- and they leave, and call me a lagger. tr 24 is caviar. I give up. Moving on to another rts. Blizzard wont fix this, they dont care about our community. Move on. Stop wasting your time.
|
On March 17 2018 02:11 Dazed. wrote:
The rare occasion i get a korean I can play them on tr14--- and they leave, and call me a lagger. tr 24 is caviar. I give up. Moving on to another rts. Blizzard wont fix this, they dont care about our community. Move on. Stop wasting your time.
Or play iccup. It worked well in the past, no reason it's not good enough anymore :D
|
On March 17 2018 02:17 Cele wrote:Show nested quote +On March 17 2018 02:11 Dazed. wrote:
The rare occasion i get a korean I can play them on tr14--- and they leave, and call me a lagger. tr 24 is caviar. I give up. Moving on to another rts. Blizzard wont fix this, they dont care about our community. Move on. Stop wasting your time. Or play iccup. It worked well in the past, no reason it's not good enough anymore :D
Divide the playerbase. Great idea
|
On March 16 2018 22:47 kogeT wrote:
I updated OP with following points:
- 2x and 4x speed on replays seems to be same / close to the same (tested on 2 computers)
- Random map selection from a folder
- F10 menu in game loads slowly; Preload the menu?
- Improve latency when opening user profiles (it takes a long time to load now)
- Ability to either set colors specifically, or have 1v1's directly change colors to red/blue in observer mode. Ability to swap player colors on command (i.e. red player is now blue, and vice versa)
- All-Chat/Referee chat to players when in observer slot
- Observer slot scalable to >4 if smaller map.
- Observers to have best-efforts networking, meaning the two players dont have to worry about how many obs exist. This would be hard AS FUCK for the engineers to do, but GOOD GOD it would be awesome for live events.
- Ability to set where center of screen is for following-units. This is because on some casting gigs, people fill the bottom with overlay stuff, making the "center" of the screen slightly higher than the exact middle of the monitor. Makes easier obs/casting experience.
- Top right player stats/info box to be set width
- Open API or ability to read player names/races/color directly from games actively observing. That would be dope for automated overlays. I know you can do it retro for replays, but live events are difficult.
- Option to disable/reassign F5 key (as a player I hit it quite often when trying to hit F5, same progamers!)
- Replay and observer intefaces to be exact same or similar window positions. (Why is the replay unit window so massive?)
- Text to display map name over/under player stats on top right.
- /whois <channel> command doesn't work
Rest of stuff I found too fluffly / not relevant / covered by other points (meaning Blizzard should first focus on some of the other great points we came up with)
Really nice work! This thread is absolutely wonderful! :D
|
|
|
|
|
|
EPT
