Does the 32bit movie syncs with the 64bit emulator, and viceversa?
I will add rchokler as coauthor and ask the file be replaced unless an even better fight is presented within the next day or so.
step by step to inspect possible new run
We should discuss this here or move on to the main thread?
[12:58:56] <Guga_> I have always said it [12:59:00] <Guga_> Trust no one
do that we need do disassemble the whole game.
I will also check if BushRoot could be manipulated. Do you have a list or RAM addresses?
If you want to make movie with killing that lance duck it's OK, but it can't be call "pacifist".
Glad I abstained from voting...
http://tasvideos.org/userfiles/info/20105242395548292 Every level except Steelbeak is now done. I'm thinking of making a proof-of-concept run of SB. Problem is, I don't know if I should just go with what feos says, or just blank out and leave this run at that stage.
There seems to be this concept that the TAS showcases at the GDQ events need to do something special, something never seen before, something that has never been shown nor attempted before, something that shocks even TASers and regular visitors to tasvideos.org. It's like not getting a standing ovation would be considered a failure. This year this idea went so far that there actually was not a single actual speedrun showcased, even though it's supposed to be a "tool-assisted speedrun". Personally I don't see why that has to be some kind of necessity. Just plain regular old TASes, run on a real console, are awesome enough, when the game and the TAS are chosen appropriately. Just take eg. a glitchfest TAS (like the Megaman one), and it ought to be awesome to watch. Not every viewer has seen TASes before. Especially not run on a real console. Of course I don't know if the event organizers will accept just a "regular TAS" for the event. But if that's a concern, why not just ask them? Make a case that 1) it's actually the very idea of TASing, and 2) a cool-enough existing TAS that does crazy things ought to be awesome to watch all in itself. That's not to say there can't be any never-seen-before things at all, but perhaps it would be easier, and even better, if the TAS block doesn't consist solely of those.
RGamma: What would be a range of avsync revisions that require GapFix? Also, as we figured out the header size, can we reliably use it for all dolphin audio dumps?
So here's the build of GapFix suitable for any dolphin wav dump (as soon as sample gaps were filled of course, which was done in https://github.com/nattthebear/dolphin-avsync/tree/3825S and later): https://github.com/feos-tas/Misc/blob/master/GapFix.7z The question remains "When sample gaps were fixed?"Language: cpp// We are now at offset 44 if (file.Tell() != 44) PanicAlert("wrong offset: %lld", (long long)file.Tell());