bloodsport
wat
that would be nice.
that would be nice.
Play to win.
Excuse for what? Them being hard to execute matters. And them not being practical in a high level match matters too. You're saying "an infinite is an infinite", which is 100% not true and again... ignorant.
Right, that's why they were two different sentences and the word "and" was used. They're impractical and require execution.
excuse for infins,you said there hard to do and you dont seem them often so its ok,that a bit short sighted
It's the exact same as a combo video where someone is doing highly situational 70%+ combos in MK9, and then when someone says they're impractical and you won't see them in a real match, you come in and say "that's an excuse and you're trying to justify these high damaging combos". That's retarded and an argument a 3rd grader would make.
Yeah since a game being good is based on whether it's at EVO or not, right?
Frame data isn't effected by this. Saying something is now +1 on the 1 player side that is 0 is misleading. A better use would be saying after something is 0 on block, a 6 frame d1 now must be blocked unless the other player is using KL spin or armor.
I was thinking this exact thing while listening to the KTP. Nice post Dizzy.
i know p1 is winning most of the time but if p1 really had the advantage shouldn't p2 never win whatsoever?
Nope, it would not. Its a simple true false to determine if p1 has priority or p2 (true p1 does, false means p2 does). Second, the check only needs to be done on the collision detecting, and even then it only needs to be done if p1 and p2 really did hit each other on the exact same frame. Especially with the speed of the processors, such a check is inconsequential. Toggling a bit from 0 to 1 or 1 to 0 is also a non-issue.
That's not correct. Something similar to below would have to run 30 times a second:
I can see you don't program. This is what would run everytime. There's no need to keep that priorty state on the player data; it can be a flag on the engine.
Yes, I actually think the game has random lag for one player. I asked hanzo if he could record the screen to see when the game was reading the inputs but he couldn't. The game always shows player 1 winning when moves become active on the same frame but it seems like it forces player 1 to go last at times. Every other situation then pressing a button at the same time still applies, it would still be something you have to be aware of. I can't think of any other explanation really.
Maybe they tried to alternate priority, but messed up and it only works a small percentage of the time.
That line is definitely more efficient than my if check above. I'm sure you are more knowledgeable on this than me so if you say the toggle would not affect execution time then I can't argue. I wish they would have programmed it in.
Ya, its not to say it doesn't take any time at all, as every instruction does, but processors are really good at that sort of thing, so its unlikely to have any measurable impact considering all the other things that go into the game state loop that draws a frame.
Or as simple of not letting him throw 2 nets on a same combo. That isnt hard to code uh?
Well remember, we're talking about two moves colliding with each other on the exact same frame. While its possible, its probably not all that likely. I doubt in match that two players would consistently be able to cause collision ties such that this makes much of a difference.
