None of these work for me. wip1 hard-crashes after pressing start at the title screen, wip2 and wip3 don't even render the title screen, they just show solid grey. Running fceux 2.2.3 and Nestopia 1.4.1. Do I need a specific build?
Are you trying to run a53menu.nes by itself, without using a53build.py to add games? Do I need to add code to the menu to detect that no games have been added?
tepples wrote:Are you trying to run a53menu.nes by itself, without using a53build.py to add games? Do I need to add code to the menu to detect that no games have been added?
I think the simplest way to keep people from running a53menu.nes and being disappointed is to rename it to a53menu.bin so we don't mistake it for something that we could run.
I, like dustmop, had made this same mistaken assumption but didn't mention it. Of course I could have read 10 pages of README.txt to discover that it's not supposed to work as-is, but I'd already assumed it was some other problem long before then.
Agree with rainwarrior here. I think POLA applies. Either the ROM shouldn't be runnable (.bin extension works), or it should fail fast, with a more obvious indication that things are broken.
Turns out README.txt already mentioned that problem:
Q. Why does a53menu.nes just hang?
This file contains the code for the menu. It contains no activities
and thus will not work unless activities are added using a53build.py.
But the fact that this wasn't very discoverable is itself a bug. So I want to make several layers of fixes:
Build a53menu.prg without a header instead of a53menu.nes with a header: Done in my tree
Display an error message if the key block is still FF-filled: Done in my tree
Describe the expanded capabilities of Action 53 when running with mapper 28: Begun in my tree; detailed documentation will have to wait until step 4 is done
Reorganize the documentation to make it less tl;dr: I'll need help with finding a good approach.
I initially had trouble compiling Action 53 because I didn't see where the config file was in the makefile, but then I found it in the tools directory. While editing the config, I had thought you had placed all the stuff outside the a53menu directory because of all the ../. I eventually figure out that the working directory for that script seems to be the tools directory instead of where the makefile was.
JRoatch wrote:While editing the config, I had thought you had placed all the stuff outside the a53menu directory because of all the ../. I eventually figure out that the working directory for that script seems to be the tools directory instead of where the makefile was.
I have changed the builder to drop the implicit rule "paths are relative to the working directory, and the working directory happens to be tools". Instead, paths in a config file will have the same semantics as paths in C #include, ca65 2.14+ .include, and HTML href and src attributes: paths are relative to the directory containing the config. I did this for two reasons: to make volume 3's workaround for the PowerPak's PRG size limit easier to automate in the makefile, and to make the rule easier to explain in the docs to avoid confusion like yours.
