emu.frameadvance is special and can only be run from the lua main loop. basically "emu.frameadvance" is equivalent to "exit lua and run for a frame and then return to lua". This is nonsense from the context of a button event, and consequently it got coded in such a way that when you tried it, it just crashed.
Don't expect this basic execution model to change any time soon, so don't expect this to work any time soon.
You should work around this by using emu.yield or emu.emuyield or some such in a loop so that your lua script doesnt exit. then when the button is pressed, set a flag. pick that flag up in the main loop in your lua script.
Thanks for reply! I'll try your workaround :)
(Good luck if one day, someone decide to work on this stuff)
Another question, I've encouter this error tonight:
As we can see, it happens when I try to load a N64 ROM. The weirdest is that the same ROM successfully loads few hours ago. I tried to load another ROM and it works.
So, I suppose that a wrong setting have been saved but I can't find where... I tried to remove my config.ini and even a fresh downloaded package; the result is the same...
I also had look into my appdata folders but I didn't find anything...
EDIT: Bizhawk version is 1.9.4
Emulator Coder, Site Developer, Site Owner, Expert player
(3572)
Joined: 11/3/2004
Posts: 4754
Location: Tennessee
Hâthor wrote:
zeromus wrote:
Hathor, reboot.
Still the same :/
I tried to use Process Monitor but it doesn't help me as much as i expected...
Your error message mentions Jabo. Jabo is the one thing in BizHawk that currently uses directx (it is a closed source plugin, we have no choice about that). Did you by chance update or uninstall directx since it last worked?
Try other N64 video plugins and see if that changes anything.
I fixed it...
When I watch a TAS, I often hear: "Yup, that happened!" and it's perfect for what I got.
I don't know how but the ROM has been corrupted (I lost "only" 24Mb). I re-download the rom and it works fine.
After hacking Twitch chat, TASBot is able to re-write ROM over network... Impressive.
So, thanks everyone! and good luck for future releases :)
*Back to lua scripting*
On running the SMB1 romhack Rohrleitung Gate, I noticed some problems with the background. Note that this video is not meant to show skill, and I do abuse the backwards function. Also, this video uses quicknes, but the same problems appear without it. Also, this is running on my windows partition, not linux with wine.
Link to video
Shouldn't the real question be, "How does it act on real hardware?"
zeromus's question is actually better, because
1) if it works correctly in an emulator, by definition correct = same as real hardware
2) since an emulator is provided, the code can be studied to fix Bizhawk
if it works correctly in an emulator, by definition correct = same as real hardware
No. What would you say about all the smw and sm64 hacks that work fine on less accurate emulators that don't work on real hardware? Thus, Master of Puppet's question is better.
@adelikat: I think the hack works fine in FCEUX, but I can't test it atm.
No. What would you say about all the smw and sm64 hacks that work fine on less accurate emulators that don't work on real hardware? Thus, Master of Puppet's question is better.
@adelikat: I think the hack works fine in FCEUX, but I can't test it atm.
I'm glad you understand that. The ideal behavior would be for it to match hardware, like you've said. I think the question zeromus asked would help determine why it doesn't work in BizHawk, whether it be due to the romhack itself, or emulation accuracy.
On running the SMB1 romhack Rohrleitung Gate, I noticed some problems with the background. Note that this video is not meant to show skill, and I do abuse the backwards function. Also, this video uses quicknes, but the same problems appear without it. Also, this is running on my windows partition, not linux with wine.
That rom won't run on quicknes (VRC7), so it gets automagically redirected to neshawk. I wonder if we should show the user something in that case.
As far as the background goes, I can make it work by fudging up something, but I'm not sure if it's the right thing to do. The problem is that the ROM is a VRC7 with 40KB chr rom, which is a nonsense configuration; VRC7 didn't support dual chr roms (in fact, very few things did). If you guess what it wants correctly, you get the right thing.
Bizhawk keeps throwing this message after a fatal error of some kind.
Any idea what is going on? Version 1.9.4 running sega genesis.
The error occurs when I am playing back a movie in TASstudio after loading a savestate.
I found a way to mess with a menu.
1. Start BizHawk
2. Open a game (I used a gameboy color one)
3. Open an existing wch file
4. Add another memory watch and select it
5. Open a movie
6. When asked to save, click no
7. At the RAM watch window, hover over "Watches"
Also another bug regarding bkm -> bk2.
1. Start BizHawk
2. Open the Rom "Stuart Little - The Journey Home (U) [C][!].gbc"
3. Start this movie.
4. It would give the message: "Movie system Id (GBC) does not match the currently loaded platform (GB), unable to load." despite it being a gbc rom.
Edit :Both using 1.9.4
Bizhawk keeps throwing this message after a fatal error of some kind.
Any idea what is going on? Version 1.9.4 running sega genesis.
The error occurs when I am playing back a movie in TASstudio after loading a savestate.
Similar error here, but when I load some Lua Scripts :P (N64)
I think this is caused by running some lua scripts while using gdi+ display method, right? Change that option, and if only gdi+ display method is supported on your system, then youre out of luck right now.
Hey. I found a way to crash BizHawk using TASStudios:
1. Load a ROM
2. Pause the game
3. Start TAS Studios
4. Without advancing a frame, create some input using the piano roll
5. Undo all the input.
6. Frame advance once.
jlun2 wrote:
I found a way to mess with a menu.
1. Start BizHawk
2. Open a game (I used a gameboy color one)
3. Open an existing wch file
4. Add another memory watch and select it
5. Open a movie
6. When asked to save, click no
7. At the RAM watch window, hover over "Watches"
As we can see, it happens when I try to load a N64 ROM. The weirdest is that the same ROM successfully loads few hours ago. I tried to load another ROM and it works.
So, I suppose that a wrong setting have been saved but I can't find where... I tried to remove my config.ini and even a fresh downloaded package; the result is the same...
I also had look into my appdata folders but I didn't find anything...
EDIT: Bizhawk version is 1.9.4
After hacking Twitch chat, TASBot is able to re-write ROM over network... Impressive.
So, thanks everyone! and good luck for future releases :)
*Back to lua scripting*
Bizhawk keeps throwing this message after a fatal error of some kind.
Any idea what is going on? Version 1.9.4 running sega genesis.
The error occurs when I am playing back a movie in TASstudio after loading a savestate.
1. Load a ROM
2. Pause the game
3. Start TAS Studios
4. Without advancing a frame, create some input using the piano roll
5. Undo all the input.
6. Frame advance once.
