Is today backwards day? Both of today's "Added" runs have a longer listed time than what they "obsoleted".
Your eyes must be going bad, this is a cross-hack obsoletion, and therefore the time isn't relavent.
If it's a different hack, why doesn't it get it's own entry?
Edit: I just looked at it, and indeed the obsoleted game is different from the new entry. I guess the idea of a different game obsoleting a different game was so obsurd to me I never thought to check.
I look forward to the say when Symphony of the Night obsoletes Super Metroid.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Are my eyes going bad, or does this have a longer time than what it obsoleted? Should we put in the description why that is?
Possibly the old movie was timed at 60 fps and the new one at 59.7275005696058
Don't you guys usually mention that in the description when that happens?
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Is today backwards day? Both of today's "Added" runs have a longer listed time than what they "obsoleted".
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Are my eyes going bad, or does this have a longer time than what it obsoleted? Should we put in the description why that is?
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Are we purposefully omitting a "Modern" encode on Archive.org?
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
For reference, what is the proper Aspect Ratio for this? 4:3?
Assuming Aspect Ratio is supposed to be 4:3.
And the bars and blank space on the left is never meant to be sent to the TV.
Adjustment is 1.6840 for X Axis and 1.0000 for Y Axis.
PS: I'm also curious what the encode size for this would be with UT Video.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
So, like an "unoptimal character" run, it forces the TASer to use limited resources to complete the run?
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
If low% sacrifices time to complete the game less you put that label?
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Ah, it was low% i saw.
What's the difference? Does low% sacrifice time to complete the game less?
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Is any% assumed? Or did someone forget to add it to the name?
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
And when replaying this run, we get disappointed because it doesn't verify. Controller or not it won't verify, so don't cry harder than usual.
Just in case of an implementation error (which I doubt - only the first data frame plays, and plays correctly as verified by logic analyzer), I will test this on my old device when the conversion boards come in...should be sometime this week.
What happens after this is I get one more clock and the console controller polling is dead. Screen is black. Music plays. I am sad. Masterjun is probably happy.
Masterjun, would it be possible to make a movie with the old glitch, and have some open bus reads done with screen printout to see what's going on? Or is this too much work? :)
Wasn't an earlier version of this run verified live on Good Games Done Fast or something like that?
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
I replay input. I refuse to replay a controller. I refuse to support TASing a controller.
Good for you.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
The benefit would be a category that is actually "doable" on a stock SNES with a stock controller.
The only thing left now: go convince the crown that it's worth it. I bet you still didn't read that long post, right?
The one about reset glitch?
It's up to you guys to convince people that things need to be changed. All I can do is give you my opinion on the matter. I'm not qualified to tell you guys how to do things. You can fight amongst yourselves.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Your only support is "we've been doing it all this time, so why should we change"?
It's not "support", neither it is "only". It's a question: why does something need to be changed? Especially when it's a common and traditional practice. Can you list the benefits?
"Tradition"? For something that we've only been doing for a few years?
The benefit would be a category that is actually "doable" on a stock SNES with a stock controller.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
If you want to limit yourself to "stock controllers" we need to reject any game using the Mouse, Super Scope, or Multitap too.
Except those games say on the box that they support or require those controllers.
feos wrote:
Ah, okay. My point is, we can't apply some new approach that would contradict our traditional one, right? L+R was considered virtually legit for all those years, as was resetting during saving, and all such stuff. It also syncs on the console as we feed it directly. Then what's the point in banning it suddenly when doing the real verification? Why suddenly limit ourselves with stock controllers?
That post tells why not.
Your only support is "we've been doing it all this time, so why should we change"?
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
We could not have been using any approach for 10 years on something that has only existed for less than 10 years. Console Verification hasn't even been a thing long enough for us to have any policy for it for 10 years.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
The point was that the runs use extra buttons that don't even exist on a stock contoller.
Then it doesn't matter for me. The device can't do something, but the console accepts it => it's legit. That is the approach we were using for 10 years. Disagree?
We haven't been using Console Verification for 10 years.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
But you can't do that on a normal controller by design. Hence, since many of our tases use it, it won't be legal on your "ideal verification machine".
Don't mind me, I'm an idiot with no published runs. If you want to remove Left+Right, that's fine by me, but I'm not the one who decides what counts a "Verified" and how many levels of "Verification" we have on the site.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
You imply that left+right is not legitimate input on a "stock controller" of a SNES console.
I was saying that it's not designed as a feature.
Mothrayas wrote:
Otherwise, I still don't get why you brought this up in the first place.
We use that technique no matter what for 10 years now, which should make it a borderline for the guy who wants stock controllers for verification. Either he considers the very approach illegal, or agrees to stretch his views.
xnamkcor: read the post I linked there, the one that JXQ (does he need an introduction?) called "very well-written".
The one with Left+Right? I'm perfectly fine with Left+Right.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
We're console verifying the run, we need to use the stock controller that that console uses.
The 10-year practice of pressing opposite directions during TASing kind of disagrees with you.
You imply that left+right is not legitimate input on a "stock controller" of a SNES console.
Otherwise, I still don't get why you brought this up in the first place.
I never brought up Left+Right. They did.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
And if you disagree with someone, just call them an idiot.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Please do cite specifications that says pressing left and right or up and down on a controller must be mutually exclusive actions.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
No, that's a definition of a controller. The definition of an SNES controller is different. We're console verifying the run, we need to use the stock controller that that console uses. Emulating signals of buttons you can press instead of pressing the mechanical buttons is fine, but sending raw signals down the pipe and pretending it's a legitimate console verification is stretching it.
Like I said, I'm all for separate categories. I'm not saying we should delete or stop making these runs, we just need to make a separate category that defines that the run was made using only signals a stock SNES controller could produce by pressing it's buttons.
Wire up leads to the button switches on the SNES controller and send signals that way if you aren't sure.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Masterjun, would it be possible to make a movie with the old glitch, and have some open bus reads done with screen printout to see what's going on? Or is this too much work? :)
