Search options (Page 15 of 54)

Save States and Battery Save are kind of apples and oranges.

I like that you made this ROM saveless by design, I agree with your design philosophy on that one.

No complaints from me in the slightest!

If you did want a hacked together way to "save" in cajóNES using a PowerPak, you could experiment with Kalle's PowerPak Save State Mappers.

I don't personally own a PowerPak yet and haven't played with his Save State on Hardware system, so I have no idea how it will work, but that's a thing one could try if they really wanted to save instances in this program.

Whoah, that's pretty cool!

That makes a neat way to study the composition styles of some greats like Koji Kondo of Nobuo Uematsu.

As to the earlier comment about disassembling a .GBS, I haven't done that and am just speculating. I'm not a very good programmer.

That said, BGB is a highly accurate game boy emulator with a built in disassembler and assembler.

The issue here is that this gives you GBZ80 Assembly code to work with, which isn't readily human readable unless you really know what you're doing. So you could use it to see exactly how something is being done in a game, but that doesn't mean you'd be able to understand it per se.

I managed to repaire my ESS Maestro 2 laptop, so I have an FM Tracking machine again. Even if it sounds kind of off.

Finesse when you peel the polarizing film is the only answer unfortunately, guys.

Rubbing alcohol is fine and wouldn't have damaged the ribbon cable, it probably mechanically separated when you were removing the rear polarizing film.

I'm excited for this. My only real released material at the moment is nanoloop iOS, and I'm about to get a copy of nanoloop 2.5.

Maybe we'll be doing some stuff together soon.

If you're going to emulate, which there are legitimate causes for doing, then BGB is the way to go. There's no real reason to use a less accurate emulator unless the alternative is that much more convenient.