nesdev.com

I'm 90% sure that my game won't be done in time, and I don't want to reveal it partially done. When I switched from CNROM to UNROM, I ended up getting deep into the weeds of graphics tile compression, probably way more than I needed to. It was a fun excursion and I learned a lot, but it stalled my p...

I realize this is well-trod ground already, but since switching my project from CNROM to UNROM I needed a tool for manipulating my CHR tile files more than TileLayerPro would allow for. So I made it myself. Introducing TileNipper, a command line tool for resizing and compressing data files. http://g...

If I decide to enter it (I'm not sure if I'll be done in time--now it's looking increasingly unlikely--we'll see) I'll keep it to 64 KiB. When I first started, my goal was to make a game sort of like SMB1 on NROM. Then decided to switch to CNROM with 4 CHR banks to get some visual variety, but I fou...

I'm starting to consider switching to UNROM. 32 KB fills up fast. If I do, how many banks of PRG ROM are allowed?

Just don't do naive fades that subtract $10 from the color value, and you won't end up writing $0D (blacker than black) to the palette. My fade-out routine checks for $1D and $2D and changes them to $0F, so that's not an issue. Thanks guys. I think I'll keep using the $XD entries and not worry abou...

In my current project, I'm using color $2D quite a bit. I find that I like it better for dark gray than $00, which I find too light most of the time. I know that the RGB PPU from the Playchoice machine will treat this color (as well as all $XD palette entries) as black. Is this going to be a problem...

Don't be afraid of NOT releasing your game if you feel it isn't up to what you wanted to actually do with it

Thanks, that's good advice.

I had hoped to have my game done by the end of the year, but I think that's increasingly unlikely as that gets closer and closer. I'm torn on whether to submit whatever I do get done, or to wait until it's completely finished before revealing it to the world.

I finished my solution. basically, I buffer sound effects as various objects try to initiate them, then in my audio engine I loop through each audio channel once to process all the music or sound effect data and then load the first two bytes of each channel (the second of which doesn't really do any...

Try this: sweep, #$FF -> $4017, pitch. Thanks Drag, I think I'm on the right track now. in my routine that loads sound effects, as a quick and dirty test, I inserted a write to $4017 in between updating the sweep and the pitch: LDA [sFXPointerLo], Y STA $4000, X INY LDA [sFXPointerLo], Y STA $4001,...

So how do you reset the Sweep to prevent it? like I said, I tried writing $FF to $4017 right beforehand, and also every frame, neither helped. I also tried writing 0 to $4015, then re-enabling the channels right beforehand, and that didn't help either. I also tried writing the data to the audio regi...

I'm using the sweep for several sound effects. Sometimes, it sounds like the sweep is skipping the first pitch and going directly to the second pitch. It seems to be happening right after playing a different sound effect. I thought maybe the data from the previous sound was affecting the next one, s...

I like using the $XD column because it gives me more options in terms of shades of gray I can use. in my fade-out routine, I do it in 8 steps, alternating between setting all the color emphasis bits to slightly darken the screen, then dropping to the next palette row darker, and any value that becom...

I found these requirements on a thread for a previous contest multicart. Are these still valid requirements? tepples wrote: Mapper-specific advice: NROM-128: Be careful not to write to $8000-$FFFF. Test with a breakpoint on writes to ROM. NROM, CNROM: Be careful not to overwrite CHR ROM. Test with a...

Thanks for this. I was going to make a post asking if all the black entries are different or the same. Now I don't have to.