This is the tiniest and least urgent feature request ever, but could there be an on-screen message to say the sound has been muted/unmuted when using the toggle sound hotkey?
Is there maybe some way to customise which actions display messages that I'm not aware of?
Obviously a lua script can do this, but it seems like it would be simpler as an inbuilt feature.
Always great to see new BizHawk releases. A lot of really nice little improvements and features in this one that make the TASing process easier. Thank you, BizHawk team!
BizHawk v1.9.3 is released. BizHawk is a A multi-system emulator written in C#. BizHawk provides nice features for casual gamers such as full screen, and joypad support in addition to full rerecording and debugging tools for all system cores.
BizHawk Supported Systems
- Nintendo Entertainment System (NES)
- Sega Master System
- SG-1000
- Game Gear
- PC-Engine (TurboGrafx-16) / CD-ROM
- SuperGrafx
- TI-83 Calculator
BizHawk Experimental
- Sega Genesis (low compatibility list)
- Gameboy (Debugger only)
BizHawk v1.9.2 Changelog:
- From revision 9182 and cherry picked revisions 9212, 9201, 9198, 9193, 9190, 9207, 9208
Is the Lua interface still in early development? I keep getting this error:
LuaInterface.LuaScriptException: Lua511.LuaCSFunction
Or is it just my script maybe? It's very short and simple:
Nisto:
From a quick look at your script I see that background and forecolor aren't defined anywhere. Not sure if that would cause the error you name, but it's a bug nonetheless.
phoenix1291:
Well yes, but we don't have any affiliation with Emucr. If their description is wrong, that's something you'd have to take up with them, not us.
Are you sure, Scepheo? My Lua skills have become quite rusty as its been a while since I wrote that bit of code. However, I don't think I would wittingly keep the code like that if it was actually causing problems or was somehow against the language syntax. Doesn't Lua parse undefined variables as nil or a "blank argument"? I would imagine that's why I wrote it like that, since it skips having to go back and check the documentation for gui.text() if I ever wanted to change the defaults. I could be wrong though... I will try.
EDIT: Nope, that doesn't appear to be the issue. I should add that the script does run exactly as expected, it just randomly throws the aforementioned exception and inactivates the script after some time of use - almost seemingly within a certain time interval (EDIT: scratch that, it just crashed on me after only 5 seconds of use... Most of the times I'm able to run it for at least some minutes)
Oh and I'm on Windows XP.
For some reason, EmuCR builds are linked from the main BizHawk page. Since there has been some recent confusion regarding EmuCR, I have removed it from the page.
For those who haven't noticed yet, BizHawk 1.9.2+ supports GDI+ for those who cannot use OpenGL (I have confirmed this on my older computer). If you weren't able to run BizHawk 1.7.0-1.9.1, this is probably the case. You'll need to put this config file into the main BizHawk folder:
http://www.mediafire.com/view/clq48v2rw83yx8b/config.ini
A way to configure this after installation without needing to download this config file would be welcome.
Isn't that what selecting "GDI+" under Config -> Display -> Display Method does?
(Or would you need to be able to run on OpenGL by default to even be able to access that option in the GUI?)
EDIT: Also, instead of anyone having to downloading an entire config file, you can change it by one single value manually: set "DispMethod" to 1.
If you can't run BizHawk using OpenGL, then right after installation:
1) You can't get to the Display Method menu in BizHawk unless you run BizHawk successfully, but you can't.
2) You can't get a config.ini file unless you run BizHawk successfully, but you can't.
3) Not everyone knows how or is willing to deal with a command line.
Though for the last one, a provided batch file is a possible substitute.
Hmm yes, very valid points. I never noticed the config was created after the first run.
For the batch/command-line idea though, there's a simpler way (at least for Windows users):
1) create a shortcut of EmuHawk
2) add " --gdi" (without quotes) to the end of the path (in Properties -> "Shortcut" tab -> "Target" field)
3) open BizHawk through the new EmuHawk shortcut
EDIT: Actually, come to think of it... You can just create a config.ini file from scratch with this code:
3) Not everyone knows how or is willing to deal with a command line.
I feel that if using something as straightforward as a command line is too technical for you, even if you have to do it exactly once, to work around a bug, you're not the kind of person we want to cater for.
3) Not everyone knows how or is willing to deal with a command line.
I feel that if using something as straightforward as a command line is too technical for you, even if you have to do it exactly once, to work around a bug, you're not the kind of person we want to cater for.
It's not too technical for me, but even I would be stumped at first when encountering that error. My first instinct would be to search for a readme.txt file, but BizHawk doesn't ship with documentation. The project page mentions the config file, so that's good, but there's no documentation of the command-line options. Only when you go to the Google Code project page (which will be gone next year) there's a link at the bottom of the page, and it doesn't mention --gdi either.
I'm not saying that it's an unsolvable problem at all because the solution is available, but it doesn't seem like the user-friendliest and most straight-forward way to go. I'd add a check before loading OpenGL DLLs (or when they return an error); when that check fails I'd just switch to GDI+ automatically. If that's not possible I'd pop up a message box describing the problem and the solution. If that's not an option for some reason I'd put it in the readme (a properly formatted one - lsnes' documentation makes my eyes and head hurt).
we DO switch to GDI+ automatically. some video cards are SO BROKEN that they crash anyway. We can't display a message. The process crashes IN THE VIDEO DRIVER.
I should probably try writing the ini back out before initializing opengl.
We're talking about unfinished code here, like literally everything else I've ever put into bizhawk. When its finished, we'll be using d3d again instead and all this will be moot.
