nesdev.org

I'm sure this has been done before, but I wanted to share it anyway. This a simple little project I've been working on that will eventually allow for any 4 kilobyte file to be interpreted as raw 6502 assembly code and disassembled accordingly. However, all it can do right now is disassemble 28 bytes...

BTW, the Dreamcast, PlayStation 2, Xbox and Gamecube are not 128-bit, the PlayStation 3, Xbox 360 and Wii are not 256-bit, and the PlayStation 4, Xbox One and Wii U are not 512-bit. This bit counting system was a silly thing invented during the 16-bit era to show everyone how superior the new conso...

I want to use this thread to basically ask any stupid short question I think of that doesn't deserve its own thread, and that I can't find a simple answer to elsewhere. I have a couple of questions right off the bat, and I'll ask more in different posts if/when I think of any. 1. Does $2002 have to ...

rainwarrior wrote:There's no "standard" syntax. That particular article on 6502.org just adheres to this particular convention.

So MOS didn't come up with the instruction mnemonics?

tokumaru wrote:For some assemblers, A is implied if you write ASL with no operand, but others (NESASM?) will require you to write ASL A.

NESASM3 requires you to put A, but I believe ASM6 will throw an error if you do this.

However, 6502.org says and is the standard syntax

If by (right now it still seems like an off) chance I run out of room in my fixed $C000 bank, what other mappers would you guys recommend? How does something like FME-7 compare to something like MMC3?

Thank you so much for this, tokumaru. I had originally planned on trying to read 2 bytes of the stack for the $2006 updates, reading another byte for how many bytes to copy, putting that in X, and then using a loop to copy X amount of bytes, and I was gonna try to do this with both palettes, 25 tile...

I think the NES is at the perfect spot where, sure it's hard, but a lot more "possible" than something like the SNES. The atari just seems too limited for my taste, and while I think it's cool that you're a lot more involved with the TIA than you are with the PPU (from what I've read at le...

You do this by first updating the X and Y positions of the "Dominant" sprite like what you've been doing (In your controller reading code). I usually make the dominant sprite the most upper-left one. Then you jump to a subroutine to update what's called the "meta sprite". If you ...

Alright, it looks like turning the process of finding the player's position relative to the collision data into a subroutine and calling it for each button was all I needed to do. It seems to be working correctly now. On a side note, I was disallowing diagonal movement of the player on purpose, (in ...

After tinkering with it some more, I seem to have solved my one problem, but have now run into yet another one. When my player collides with a wall, it can only move in the direction opposite of where it was moving. (i.e if you collide with a wall while moving right, you can't keep moving right, but...

When did CPUs start being able to handle multiplication of and division by numbers other than powers of 2? Is it still super slow compared to addition and subtraction?

So I got it to work...kind of. I've run into the problem that I'm sure many before me have experienced. The collision only works if the object is perfectly aligned to the grid. So if it's halfway between a solid section and an empty section, it'll go through. My current code is as follows: @ReadUp: ...

So I've been looking into this for a couple days now, and after some trial and error I think I've got the basic idea down. I could probably make the data part of this smaller, and probably should, but for now I just have 1 table of 208 bytes of collision data for 1 test screen. My status bar takes u...

Why is doing DPCM so friggin convoluted?