If you want, I can check with him to see if that old build still causes issues on his machine and if does, I can have him run the build that's causing Sonia trouble to see if it occurs. Might help track the issue down?
Completely unrelated, but just in case you didn't see this thread already: http://forums.nesdev.com/viewtopic.php?f=3&t=16507 It's a FDS test rom that validates the IRQ's behavior - Bizhawk currently fails a number of the tests (which causes Kaettekita Mario Bros to crash). Should be pretty simple to fix though.
Could you please update it to the correct one?
Ah, I didn't know about joypad.setanalog(nluatable controls, [object controller = null]). Can you give an example for a table "controls" to help me understand how to use this function?
buttons = { };
analog_sets = { };
while true do
buttons = joypad.get();
analog_sets["P2 Zapper X"] = "30.5";
joypad.setanalog(analog_sets);
console.writeline(buttons);
emu.frameadvance();
endYoshi Topsy Turvy requires tilting and apparently you can't bind tilt controls to the keyboard or use lua to tilt. I think last time I brought this up, zeromus told me to use a joystick. But why should I have to use a joystick to TAS? I request that tilting be assigned to keyboard keys and/or support for tilting cntrols be added to lua.
What I suggest though, is to try to present this thing on some GDQ-like event. Running TASes on console is precisely what such events want, so why not give it to them? Then maybe some day a person with a solution moves in and saves us all, who knows...
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.