Experienced Forum User, Published Author, Player
(127)
Joined: 12/3/2011
Posts: 1579
I'm just going to assume you missed all the times this was pointed out in this topic, but a max rings goal will not work. You have to draw some kind of arbitrary line when it comes to renewable ring sources. Do you spam slots for nine minutes and murder the TAS's entertainment value? Do you stop once the ring counter starts displaying gibberish instead of numbers? Do you completely ignore them? (That isn't really "max rings" then, is it?)
Getting all of the floating rings seems like the obvious solution to me. Not sure why anything else would even be considered.
There's also a difference between looking almost perfect and actually being almost perfect.
Experienced Forum User, Published Author, Player
(127)
Joined: 12/3/2011
Posts: 1579
CoolKirby wrote:
So this latest official build is the recommended revision now?
Unless it breaks something in your game, i'd definitely recommend it, yes. The more-save-fixes branch is just getting way too far behind.
Well, with that and the encoding breakthroughs
That should work with any revision. It only takes a few minutes to apply the patch and compile. But again, i'd highly recommend upgrading if you can easily do so. The newer revisions are not only much faster, but also less buggy.
So that build keeps the emulation speed of the pre-PokéPark fix revisions as well as the fix itself? And it still doesn't include the more-save-fixes or TAS-input changes, right?
It is about the same speed as the last build (479) i posted (slightly faster actually), and includes a few more bug fixes. It does include the tas-input branch. All revisions in master up to the one i linked, as well as the more-save-fixes/tas-input branches are included in this build (and all future builds i'll post here).
Experienced Forum User, Published Author, Player
(127)
Joined: 12/3/2011
Posts: 1579
Zavalix wrote:
Well, yes, maybe I'm being harsh. For now, why you take damage in the plant at 1:15 of the encode?. It appears you can get to that place with just a jump instead of getting hurt.
You can, and it's faster to jump over it than to jump into it.
Experienced Forum User, Published Author, Player
(127)
Joined: 12/3/2011
Posts: 1579
Spikestuff wrote:
The damage is actually needed to get up to some point or to get past something faster, also that the game makes it look sloppy so I got pissed when I watched it on playback cause I did everything perfectly as I can
You get hit quite a lot in places where it slows you down a lot, and offers no benefit.
Experienced Forum User, Published Author, Player
(127)
Joined: 12/3/2011
Posts: 1579
Slowking wrote:
MrGrunz wrote:
As adult bushes drop 5 rupees. Slashing each one costs averagely 30 seconds. So getting 40 rupees would take around 4 seconds and it can be done even quicker, because you can slash more than one bush with one slash.
Experienced Forum User, Published Author, Player
(127)
Joined: 12/3/2011
Posts: 1579
CoolKirby wrote:
rog wrote:
If the only difference were shorter text, with identical gameplay, then obviously that would be judged as being the same. If however the actual gameplay is faster, even if only by 10 seconds, i would consider that a mistake made in the original tas, especially now that the language rule has been changed.
The difference he was speaking of is text speed. Gameplay would be unchanged as far as I know.
Ok, ignore me then. Obviously test speed is not enough to obsolete a run.
Experienced Forum User, Published Author, Player
(127)
Joined: 12/3/2011
Posts: 1579
CoolKirby wrote:
Isn't he talking about the same exact run, just with 10 seconds of text taken out? 10 seconds is too small of a difference to justify switching ROMs.
I don't know. I'm not familiar with the version differences in this game. If the only difference were shorter text, with identical gameplay, then obviously that would be judged as being the same. If however the actual gameplay is faster, even if only by 10 seconds, i would consider that a mistake made in the original tas, especially now that the language rule has been changed.
Experienced Forum User, Published Author, Player
(127)
Joined: 12/3/2011
Posts: 1579
sonicpacker wrote:
rog wrote:
The issue appears to be video dumping. As far as i can tell, it dumps only once per VI, even though there can be frames where no VI occurs. I've been successful in getting a/v to to sync by recording the vi/frame counter and adding extra frames to the encode whereever VIs fall behind relative to the frame counter.
I made the SA2:B encode match Dolphin's frame counter, frame-for-frame (visually) and the audio wasn't even close to matching up with any of my audio dumps. Even when I matched up specific parts (like Iron Gate alone), it would slowly DS over time regardless of lag. However, lag caused even larger desyncs.
The missing frames don't really seem to correspond to anything. The twilight princess wip encode i posted needed 120 frames to be added, and according to the lag counter, there were only 2 frames of lag.
Experienced Forum User, Published Author, Player
(127)
Joined: 12/3/2011
Posts: 1579
The issue appears to be video dumping. As far as i can tell, it dumps only once per VI, even though there can be frames where no VI occurs. I've been successful in getting a/v to to sync by recording the vi/frame counter and adding extra frames to the encode whereever VIs fall behind relative to the frame counter.
Experienced Forum User, Published Author, Player
(127)
Joined: 12/3/2011
Posts: 1579
CoolKirby wrote:
How does Dolphin start a new recording from a savestate anyway?
Start the game without recording, and then while playing start recording. It will make a save state and start recording. It won't actually work as far as i've been able to find with the original save state, but if you make a new save state manually right after you start recording, you can then start playback from that.
