nesdev.com

Probably lack of rainbows because it's not generating a picture the way a NES does (no square waves between two specific voltage levels)

Split topic to somewhere else. That's the usual way to deal with derailed threads.

Here is how Super Mario Bros 1 level numbers work. First the RAM variables used: 75C = Displayed number after the dash (Only used for display, and making world 5 harder once you reach 5-3) 75F = WorldNumber, 0 to 7. (1 is added to this number when it is displayed) 760 = AreaNumber, 0 to 4, or 0 to 3...

You're going way too easy on the spambot...

For me, it's an IP ban immediately, then a subnet ban after the second offense.

Also, I can see that the background color is wrong, it should not be separate for each group of 4 colors, it should be the same background color.

There is a NSF importer version of Famitracker that can import an NSF file at one frame-per-row, so you can see what parameters are used every frame.

You can always try to reverse engineer anything, or load it into a debugger. But without the source code or debug symbols, it's a hell of a lot harder to do. Also "open source" refers to the blessing of the creator, not necessarily that the source code is available. If the creator doesn't give permi...

Also called "ARPOTHS" (the initials)

NightScript wrote: ↑

Sun Jan 24, 2021 8:36 pm

Only a limit of 1000 hours per month on the free plan.

How does the unit "Hours" exist for hosting static websites?

While FM has a lot of registers, not that many actually need to be written to play a note.

I still like the idea of a simple discrete logic mapper that would expand the number of tiles from 256 to 1024, depending on whether it is a top-left, top-right, bottom-left, or bottom-right tile. (You look for a Nametable byte fetch and automatically trigger bankswitching)

There have been NEW things, such as running DOOM on another processor, and using the NES to display the result.

One NES frame is about ~16.6394ms (might be rounded to ~16.6666ms).
Waveform can only change that often, so it can be hard to match the source wave, considering that there are non-looping parts as well.

Need to make sure the wave number changes every frame when editing the instrument.

I suggest you try running NES Tetris in RetroArch (full screen), using RunAhead 1. It's amazing how much less input delay there is between that and running FCEUX in a window.