but after talking to the GDQ submission committee it's clear that they really wanted us to have the opportunity to show content that is representative of what can be found on TASVideos and they felt Super Monkey Ball was a better choice.
So far the only particularly successful TASes at the GDQ's have been the technical demonstrations. If you want TASes to be at GDQs, prove they can be successful cause so far the evidence doesn't suggest they really can.
Nice work with this new core. Although I don't understand about programation, those SMS/GG runs made on the current Z80 core (aka since BizHawk 1.11.9) could sync on the new core?
Not sure if you're aware, but there was already a C# Genesis core a few years back with that stuff, but it was highly buggy. It got replaced by GPGX. As to how complete/bad it was, someone has a video of it on YouTube here: https://www.youtube.com/watch?v=eufJpZJjgfA
Would this benefit a Genesis core? Since it uses a Z80? And Hoorah for accurate Sega stuff!
Can we also see a new MSX core soon too?
Thanks for your work! Are you interested in writing a Coleco Adam core?
I've been working on this for quite a while, but the new T-cycle based z80 core is finally coming together. I'm about 95% done with only some clean up and bug fixes, particularly for flags, to go.
This is a modern core which should allow for much easier maintanance (containing about 10K fewer lines of code), expandable to other systems (which might include wait states or other interrupt sources), as well as natural accounting of the WZ register which hobbled the current core. It also contains numerous bug fixes from the old core that ZEXALL didn't catch.
It won't show up in the Dev builds for at least another couple weeks, but I thought I would make an announcement for anyone considering making a TAS for systems using the Z80 (GG/SMS, Coleco, TI83) in case anyone is interested in waiting for it. I'm fixing the trace logger at the same time so the new core might help a bit more with code analysis.
This is also the first step in modernizing those systems' emulator cores, but that's a longer term project. For now it will just be a CPU core replacement.
If anyone has any questions/comments/concerns feel free to post them here.
EDIT: I should mention that performance hasn't suffered either, as I can still run SMS at 4x on my laptop.
TASing has always been about overcoming human limitations, and show what it would be like if a perfect superhuman were to play the game to its absolute perfection. And Ocarina of Time any% would be the absolutely perfect place for this. When did this change?
The OoT topic on the forum here has been dead for a long time.
Action 52 is broken as of a few versions ago it appears. Still broken in the latest dev build. It launches into one of the minigames and you can't make it to the main menu. This is in NESHawk and QuickNES doesn't support it.
Good job! Are you doing anything in particular to track horizontal position or speed?
What is the significance of this category? Why no doors? All the categories are made up, and the doors only matter because we will them to.
One further question - for the purposes of the oninputpoll event, what counts as an Atari input? Is it just controller inputs, or also system inputs (reset, difficulty select, etc)? Going through the code I see far more direct calls to just the button and the system inputs than there are polls occuring per frame.
To clarify, I don't think sub-frame is necessary for improving the current TAS, but may be necessary for true optimality later on. I believe Alyosha mentioned he could produce a 32.61, so that's at least an improvement. Sub-frame would be nice, but I understand the difficulty in making that happen from an emulator development perspective. At least, a better understanding of the system would make it possible to reason a theoretical limit, assuming sub-frame inputs were possible.