nesdev.org

MMC1 is comparatively complex, but the number written there changes what section of ROM the CPU can see. It might be easier if you try to understand CNROM first? I feel like CHR ROM bankswitching is an easier concept, and the concepts carry over easily. I'm looking for a mapper that works with NES ...

That's wrong. There's no upper three bits (not even ignored ones). All registers in the MMC1 are only five bits wide, and written in one bit at a time. That's what the doc says. The code I'm looking at doesn't try and shove in any more bits after the first five. My question was much more basic thou...

So I've been using the Mesen debugger some code I found on github that is using MMC1, so I've been looking through some docs for the mappers. When switching levels, the code is writing to $E000 with 5 sta calls and lsr calls in between. I'm trying to understand the significance of the values being p...

Does anyone have any Mesen Label Files (.mlb) that they would be willing to share with a noob trying to learn NES Dev?

Thanks

You guys are right... it was missing the header information. I've never used ophis, so I'm not sure what it did to include that header information.

It's still not working, but now at least it's not throwing the FDS error.

Thanks for your help

So, I grabbed some code off of github for a project someone wrote using the ophis assembler, and I wanted to change it so I can build it with ca65. I'm pretty new to NES Dev, but I changed the code around and got an error in FCEUX saying "FDS BIOS ROM Image missing", but I'm not sure why i...

The NES's hardware sprites are always 8x8 or 8x16 pixels. "Metasprite" is just a term of art that means a single logical object (enemy, player, &c) that uses multiple hardware sprites. So they don't equate to anything in the hardware? It's just something you have to implement programm...

So I'm trying to figure out what exactly meta sprites are and I can't seem to find any documentation for some reason. There's a metasprites tab on NES Screen Tool, and I was wondering if that data ends up in the .chr file or somewhere else. I'd like to have more information on the subject in general...

tepples wrote:They do the same thing. The +0 is there to remind the (human) reader of the source code that the variable is a multi-byte variable.

Ahh... that makes sense.

Thanks

Thanks guys, this has been really helpful.

QQ for rainwarrior:
Does do the same thing as If so, why add the +0, and if not what is the difference?

Thanks

Is the .chr file format just a ppu pattern table in memory set up as a file? Or is it something more than that?

Thanks

pubby wrote:An easy way is to use the .repeat directive (CA65 syntax)

Interesting. Out of curiosity, what would you do if you had a prime number of items?

Thanks

Hi everyone... wasn't sure if this should go here or in NESDev, but it's kind of a noob question so I figured I'd start here. Let's say I have a label and a chunk of 500 bytes of data I want to loop over datachunk: .byte $20,$21,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00, ... etc out to 500 bytes S...

In the save dialog, at the bottom just below the filename is a "save as type" field. Click that and select an RLE format. It will save as the binary .rle, but when I save as the .asm RLE, nothing happens. The file won't show up and if I try and save over an existing file it doesn't change...

If the export-to-file feature doesn't work, you can alternately try using "Put to the clipboard -> ASM data" to put a ton of .db statements into the clipboard, which you can paste directly into your source code (if you wish to do it that way). There is no point in discussing which method ...