nesdev.com

The point of using hexadecimal is it directly translates to binary. 0xB0 tells the values of the two groups of four bits. B = %1011, 0 = %0000, so 0xB0 = %10110000. Then when you OR in the volume, as long as it's 15 or less (0x0F or less), it'll only affect the low 4 bits. As for interpretation of ...

Hi, I'm using blargg's NES sound APU library in visual studio 2005. I'm still learning reading his and brad's docs as well as getting assistance on #nesdev(thanks blargg, kev and thefox). I'm having a bit of trouble with understanding some write register functions and the logic behind them. To start...

Can we just ask memblers to sticky this till its done and delete all of these bumps?

Roth wrote: Maybe I'm just dumb... dunno.

That's what i think until all of the pros tell me that his stuff is nonsense

he's talked so much foolishness that's confused me and annoyed me in the past, that just the mention of his name gives me a headache. even though i try to be nice and tolerate him, listening to his garbage is honestly just fuel for my own self destruction...

so how much could you expect to get done with CC65? There's nothing stopping us from making a better C runtime for NES development. But what does it matter, since we're aiming for asm development (and CC65's code efficiency isn't very good either)? ok. can see your point. sorry to turn things aroun...

tepples wrote: As far as I can tell, it's intended for quick throwaway recompiles of C code on the NES, not for serious NES development in pure assembly language.

so how much could you expect to get done with CC65?

tepples wrote:I've started on this: Installing CC65

it looks great. i dunno how safe this could be to post, but could there be an addition to this tutorial to add CC65 to the environment variables?

-edit-
i guess it'd be ok if you first get everyone to make a backup copy of the environment variables...

i guess like other programming languages, you learn about initialization first. but i see where this could be an issue. maybe in the beginning, or even for early debugging use 6502 simulator as well. before any code can be seen in an emulator(i could be wrong about this too, now that you mention it...

- What level of knowledge will these assume? I'd say very beginning. most tutorials are full of lots of holes, and i haven't ben able to peice them together with other tutorials - Will the very first code examples be standalone, or use some kind of shell that hides the details? (this mostly depends...

so are we suggesting a new tutorial?

I'm thinking this code wont be used in that way. unless someone gets blarggs permission and does it themselves.
I'd do it, but you'd be teaching me about what i'm documenting as i'm doing it. so i dunno how well that would work out.

is there some kind of list of NESASM and 6502 commands and syntax? as far as labels and all that other stuff that i don't know about? :D just got this from here: http://e-tradition.net/bytes/6502/assembler.html and wanted to know if this is true for nesasm? Syntax The assembler supports the followin...

this post has been in the back of my head since your reply. i'm gonna get to it over the weekend hopefuly, thanks.

triiiiiicky tricky tricky tricky.
btw i'm still taking in the last post in the controllers thead. that's why i haven't replied.