This is TAS of the year for me as you already know ;), yes vote. Corner boosting and perfect timeline surgery everywhere.
Is anyone planning to upload this to nicovideo?
Cpadolf wrote:
I haven't played this game enough to notice these things, so I have to ask: What are the things you managed to do to achieve the good ending without collecting all the stars, and are these things possible in an unassisted run?
Anyway, good stuff overall, definite yes vote.
Yes, any realtime speedrun gets the good ending. The trick is that the level is designed assuming you do NOT get any corner boosts. If you get good corner boosts you can get an early pirahna plant cycle at the end and reach the chandelier. This is meant to only be possible if you have all seven other stars (which makes a lever green which makes it super easy to get the early cycle)
I found the random trajectory value in MHS. I'm going to describe it rather than posting a value, because everyone has different mupen builds.
Why not say, 'if HP is at address X then random trajectory is at address Y', and everyone else can find the difference between their HP and your HP, remove the same difference from your Y and find their Y?
I tried Genesis and Mega Collection with no luck (I got to the point in the Megaglitch where the game restarts, but nothing is laggy, music is normal, and no Blue Knuckles).
Memory corruption related glitches are usually so random that it may be nearly impossible to repeat it as it’s shown there, even in a TAS.
Only if you understand the things inside, you may be able to pull it off, but it will not be trivial (for example, you may need to force certain byte to contain certain value and so on)
Glitches that involve reading very odd parts of memory, crashing, illegal operations, resetting and so on may operate differently on emulator and console if there is a bug in the emulator.
You could try seeing what version(s) of emulator(s) the Megaglitch works on.
Falling Hero, available here http://www.kaser.com/mesh.html , is a great turn based puzzle game with surprisingly deep and subtle interactions in spite of its simplistic, grid-based, 2D appearance. The demo has only 15 levels, but they range over a huge number of concepts and difficulties from the full set of 102 with the game - which is what convinced me to buy it. Plus, if you ever finish those 102 levels (I haven't), there's a huge number of downloadable levels from the bottom of the page! Great puzzle game despite simple appearances.
In particular, you should search for information, tricks, timesavers, routes, do test run semi-optimized TASes etc, until you feel comfortable enough to do the TAS itself, otherwise you'll have to figure out so much stuff all at once that you'll progress slowly and be demotivated.
Apparently Gohdan's hands can be hurt by bombs. It might be a good TAS strat to lay bombs in his hands while bombing the head, so they go off after he re-activates. It even fully takes out the hand, maybe Gohdan can be done REALLY fast now?
Link to video
It is possible to tell if someone used savestates or not if they are sloppy. Here are some ideas:
1) Making really risky, unnatural dodges.
2) Reacting to things before they happen ed: or consistently faster than human reaction speed.
3) "Jittering", in the case of -loading a savestate made while moving then proceeding to not move, or move in a different direction -loading a savestate made while not moving then proceeding to move. If this happens a lot you can leave 'clutter' in the timeline that's meaningless, but left in because it didn't lead to you dying and because you didn't rewind far back enough.
I love this question.
The way I see it is:
- All memory cards must start in their factory state, including spare ones.
- Having multiple consoles running in parallel is OK.
- Swapping memory cards with spare ones is OK.
- Formatting a memory card and/or copying data between memory cards is OK if done on any available console.
- Ejected memory card data can be moved from a console to another, starting from the frame the memory card was ejected.
- There should be full input provided for all consoles for verification.
Of course the final decision will go to a judge, but I believe it's the only possible way you could be allowed to do what you want to do.
This is unlikely because it implies that some dev has to code the operation 'transfer memory card to another instance of dolphin running in parallel' and have it be sync-stable, TASable, etc. Given how often anyone would want to use this, is it worth not just the development time but the development burden (has to not break or break things in the future)?
Lately, the Nicovideo troll seems to have struck again. This has been going on for a while, but it is really bad as of late (and that's saying something).
For those who wish to search for TASes, but would most desire not to have troll videos on their search results, the minus tag is for you.
Responsible Nicovideo users have taken the time to label all troll videos with the tag 検索妨害 (the troll is incapable of stopping this). Therefore, by minusing the tag, these videos will vanish from your search results.
Here are the links with the minus tag in action. You can use them as a bookmark if you wish.
Plain search: http://www.nicovideo.jp/search/TAS%20-%E6%A4%9C%E7%B4%A2%E5%A6%A8%E5%AE%B3?sort=f
Tag search: http://www.nicovideo.jp/tag/TAS+-%E6%A4%9C%E7%B4%A2%E5%A6%A8%E5%AE%B3?sort=f
(It doesn't really matter which one you choose.)
Surely if a TAS is obsoleted by a real time run it'll be because of some new glitch that no one has got around to making a new TAS with yet, not because the TAS got out-optimized?
This run needs a table of how fast each track was. Then any new run (assuming this gets accepted) would have to set faster times for those tracks.
Couldn't you get faster times per track by completing more tracks outside of test drive, levelling up your test drive vehicle further, but yet this would waste real time?
Very nice TAS! I loved the metal gear solid world 'die and yet save' trick in particular. Lots of deathtraps breezed through like they didn't exist.
I think for publication purposes, at the very least the sound glitch in the megaman battle would have to be fixed (1 frame saving is not worth it) :)
As for updating the TAS before that to include 1 frame shooting, though, that's up to you - the bosses are already so fast, so it wouldn't be a large entertainment change.
Also, people have been able to get hit and glitch into walls and the ceiling. Though people haven't been able to find a reliable way to do it. I've never had it happen to me personally. It's considered TAS only territory. If you could figure out how it works, that would be awesomeness. It would also change the route you'd want to take in some places.
Do you have any videos of this? The only glitch-into-walls I know off the top of my head are the one in Infinite Corridor and the one in late game Chamber of Extinction from the statue dude.
Looks good! I have a question, from a TAS perspective what are the mechanisms by which you manipulate enemy movement? You said that the RNG is popped whenever an enemy has to decide what action to take, but is that also influenced itself by where you are on the level / what you kill and when?
Do you know why physics being different could possibly be caused by emulator problems? For example, in NES games like mega man sprites are moved around by specific pixel and subpixel amounts, so for that to be wrong it would have to not emulate basic math (and then nothing would work). What's the difference between that and Mupen?
IMO the best way to get a stronger RNG for the next pokemon game is to flagrantly and publicly abuse it as much as possible. Nip the problem in the bud so to speak :)
(And the fact that programs like RNG Reporter exist mean that understanding of how RNG works is strong and that the capability is there anyway)
