nesdev.org

Cool, thanks for the feedback!

Just wanted to get some input on my character physics model before I move on. There is no real collision detection yet, so it won't fall down the hole.

http://www.yibbleware.com/nes/cartlemmy-test-0.3.nes

Usually the worst case is the beginning of a pattern. And the second worst case is a row when all channels are starting new notes. Yeah, I think that is why my short song might seem a little big, for something larger it will be more efficient. EDIT: Ah you were probably referring to how much CPU ti...

Memblers wrote:For a game too, performance is somewhat of an issue, just be careful with the 'worst case' path the execution can follow.

Very good point, I'll have to make sure all is well with that.

Memblers wrote:Demo looks pretty cool!

Thanks, so far so good

Mmh, this song is REALLY simple and short, so yeah 69 bytes for it seems like quite big, IDK but maybe it'd be like ~25-30 bytes on my engine. (I just put in random numbers). But yeah 300 bytes for a sound engine sounds like nothing. You should have done something either really efficient or really ...

Just to check with you guys, here is a working example of the sound engine. This short song uses 69 bytes, does that seem like too much?

http://www.yibbleware.com/nes/setest.nes

I take the point here to be that unless you're only having one short song, song data dominates, so you should spend some extra code on allowing a more compact song format, because each extra byte of code will result in the reduction of many bytes of music data. Definitely! I'm trying to make the so...

Perhaps you're referring to RAM usage and not the actual engine's size? As I recall, the Famitracker driver uses more than a whole page of memory. That seems closer to what you might be talking about. And in that case, it does sound like quite a lot. No, that is the engine's size. I did forget that...

Cool, I forgot to mention it does not do sound effects yet. But I was just making sure I wasn't going to run into trouble down the road. The data format I'm using uses 1 byte for most instructions. So far it supports envelopes, octave set, looping, duty cycle, and DMC. I'm pretty happy with the resu...

Is 320 bytes (including note table) unreasonably large for a sound engine? I know that is a relatively vague question, but I'm curious as to how small everyone else has managed to make their engines. I want to be sure it is not too bloated.

Group Hug!

Thanks so much for this tool... Now I just need to figure out how to implement the DMC sounds into my sound engine

I think this is a great thing! To me great thing about it is it provides and easier starting point for those just new to NES development. Naturally when they reach the limitations of C code they will be forced to move on the ASM, and by that point they should understand enough that it won't be seemi...

RT-55J wrote:

psycopathicteen wrote:What would make this website more interesting?

• An flashy Flash introduction (like this)

Wow, just wow...

Yeah, what's with the negativity... It may be the nOOb in me, but I'm in awe that any one man can make a game for the NES.

(EDIT: I realize constructive criticism is a good thing, in case y'all was wonderin' )