nesdev.org

It sounds like ObjectSlot is a struct, so they definitely don't want ObjectTable - ObjectSlot or * - ObjectSlot.

Offset-per-tile allows you to scroll tiles individually. It uses values in BG3 as scroll values rather than tile data IIRC; I don't have much experience with it. Mode 5 is one of the high-res modes (doubling the horizontal resolution from 256 to 512), the other being mode 6. Taking half of the pixel...

Also note that even with the palette set, color 0 of that palette will always be transparent regardless of what value you set it to, so if the sprite pixels are all 0, it won't show up at all.

I just don't want to make something in LoROM and then need the extra 32Mb later Oh, LoROM and HiROM don't have anything to do with maximum ROM size. Both have a maximum of 4 MB. The difference is just that LoROM gives you 128 banks of 32 KB, whereas HiROM gives you 64 banks of 64 KB. It adds up to ...

Must just be on the SNES then; the emulation mode's status register flags are shown on page 60 of Programming the 65816.

On the 6502, both external IRQs and BRK instructions used the IRQ vector; it wasn't until the 65816 that they had separate vectors. The break flag was used to differentiate the two, and that flag does exist in emulation mode. (The reason there seems to be a hole there in the middle of the vectors is...

byuu wrote:Either you give up on 1/1/1 users, or you only use DMA during Vblank.

There is unfortunately no other viable option.

Well, there is a third option, which is obvious but should probably be listed as well: just don't use any HDMA when you need to DMA outside of Vblank.

In other words, DMA is so fast in comparison to any other method of copying data that there's no point in using anything else for large chunks of data. As for small chunks, that depends on how much overhead there is. Also, it's worth noting that DMA can't copy between two PPU registers, nor copy bet...

I'd really recommend http://problemkaputt.de/fullsnes.txt as a general resource, personally. It consolidates a lot of thorough information in one place. There's also http://problemkaputt.de/fullsnes.htm which has formatting, but seems slightly older, being "extracted from no$sns v1.5" inst...

Keep in mind that this code either needs to run during VBlank, or you need to have forced blanking on.

By the way, where does higan look for 21fx.rom and 21fx.so by default on Windows? Trying to figure out what interface->path(ID::System) and interface->path(ID::SuperFamicom) resolve to took me on a journey through higan's code that didn't really clear things up.

Unless you are keen on doing this through real hardware, you could just modify an open source emulator to do this kind of thing. Well, for me, programming for the SNES at all is entirely motivated by the cool factor ;) (It's certainly not practicality!) For me, it's just not the same if I can't do ...

Gotcha, thanks for the response! A lot of my concerns came from the idea that I'd have to handle the IPLROM every frame, but if I can just deal with reads/writes myself in my NMI handler, that's no problem. All of my concerns are pretty much taken care of then; setting the NMI handler override addre...

So, I've seen information here and there about 21FX, though it's been heavily focused on its use for ROM dumping. What I'm more interested in is its use for development; for instance, a level editor that can edit the current level (loaded into RAM) during gameplay, allowing for rapid testing. But th...

According to its readme, it was written in Turbo Pascal. Edit: Also, it'd be a fair bit more complicated to port the assembly, as this is software running in an operating system; it'd have to be changed to work with Windows rather than DOS. Furthermore, there's some major differences between 8086 an...