For NESICIDE...
zzo38 wrote:
[*]Record specified memory locations by time.
Yep. If by 'time' you mean CPU/PPU/APU cycle.
zzo38 wrote:
[*]Track uses of memory as instruction/data/operand/nothing.
Yep. I have a very similar interface to the ICU64 that Shiru plugged...all I need is some OpenGL text help and it's done.
zzo38 wrote:
[*]Breakpoints.
Yep. Break on just about anything occurring in the CPU, PPU, APU, or mapper or the memories associated with them.
zzo38 wrote:
[*]Custom plugins for input/output/audio.
[*]Specify configuration profiles for individual games.
Nope.
zzo38 wrote:
[*]Emulate unofficial opcodes (unless option is set to disable this and cause error instead; might be useful in case you are making something and might not work on other emulators, hardware clones, or newer version of hardware, or to find obscure bugs).
Yep.
zzo38 wrote:
[*]Ability to load program from external media (for optical media, use the DVD-ROM drive of your computer (I believe many PlayStations emulators can do this); for ROM cartridge, you could use something like the UNIX block devices), in addition to possibility of loading from files.
Nope.
zzo38 wrote:
[*]Loop test mode (possibly useful with NSF in order to find the length of a song).
I have a Test Executive that allows running any ROM with prerecorded inputs and comparisons of screen captures.
zzo38 wrote:
[*]Ability to use cheat code with music files.
[*]Option to emulate NTSC color artifacts.
[*]Option to emulate battery levels.
[*]In case of multiplayer with multiple devices (such as GameBoy), allow an emulator to not only emulate multiplayer by itself, but also connect to other instances of the emulator and connects to the real hardware (for example, if you have a GameBoy game on a real GameBoy, you could connect it to a GameBoy emulator on computer to play multiplayers game).
[/list]
Nope.