nesdev.org

The site is sometimes slow to respond but have patience.. Some US-residents have trouble reaching it because some DNS-servers are not properly updated (Use Google's.)

I've uploaded a new betaversion that enables you to rip PPU-data (titlescreens, cutscenes, objects etc.) from certain ROMS. Data can be exported to .bin/.asm or .png.

The PPU object viewer on the CHR side, looks wonky on my Win7 laptop, so the offset of the viewer's graphics needs adjusting for some computers like mine!

Screen is included

Wow that looks pretty terrible. I'm running Windows 7 aswell so I have no clue at the moment what's causing that behaviour. I'll check it out somehow..

Yes, both FDSExplorer and NESExplorer still show diagonally-warped CHR (for FDS) and PPU objects (for NES).

Also, the offset in the "hex" tab is really strange, showing decimal, for one, and weird offsets:

16
31
47
63
.
.
.

31, 47, 63 I can understand (last byte in a 16-byte group), but the 1st one should be "15", no?

Or preferrably: $00000, $000010, $000020...

Perhaps you're relying on hex/CHR/bitmap decoding libraries that suffers from different behaviour on different OS revisions?

Also, best to mention that NESExplorer requires .NET framework in your readme, as did the FDSExplorer docs.

Thanks for reading our feedback!

Thanks for the hex-related info Chris. I'll check that out.

About the imagebug. I'm using standard .NET-stuff, nothing out of the ordinary so it's pretty odd it doesn't work. I've tried it on several
machines here, no problem. All running Win7.

And yes, it requires .NET framework, but I guess most modern computer should have this installed already if you
haven't lived under a rock or so.

oRBIT2002 wrote:And yes, it requires .NET framework, but I guess most modern computer should have this installed already if you
haven't lived under a rock or so.

blah blah blah blah linux whining blah

In seriousness this is a cool tool.

Works once you install (debian) mono-runtime, libmono-corlib2.0-cil, and libmono-winforms2.0-cil.

Just adding that to the readme.txt would be good enough.

oRBIT2002 wrote:And yes, it requires .NET framework, but I guess most modern computer should have this installed already if you haven't lived under a rock or so.

With my main computer 11 years old, kept because it can run old DOS progs and has a parallel port that works with several copier devices, yes, it is kind of in a self-imposed sublithication

I've uploaded a slightly updated version now. I've changed some bitmap-init-code so I hope the graphics-part works better(??).
Please let me know how it goes.

oRBIT2002 wrote:I've uploaded a slightly updated version now. I've changed some bitmap-init-code so I hope the graphics-part works better(??).
Please let me know how it goes.

Still not properly working...

A friend has managed to recreate the problem, however it only appears when running the exe, not when running the sourcecode directly from Visual Studio. Very very odd.

EDIT: Problem located and hopefully fixed (new version uploaded). I can't explain the bug, currently it looks like it's related to the .NET framework itself.

I've updated this tool to v1.0 now, many fixes/bugfixes has been made. I hope there's more people than me that finds it interesting in snooping around in these ancient ROMs.