Hey guys,
Ok I'm 40whatever years old, bought my first NES when I was 8 right when they came out, and now I'm a MSc in Nanotech PhD in ChemEng, and I bought the NES classic mini for my kids (hahahah yeah for my kids... no seriously they love it so far) and of course now I am thinking of making my own games for them (hahahah yeah for them).
I can fart around in C++ and python, I can write scripts in dosshell and a bunch of other languages, I have zero assembly experience, but I'm rocking a high-end wetware processor and can generally pick up any kind of logic orientated language in very short time. I understand computer hardware at a reasonably solid but not expert level (I know more about how the chips work physically at the atomic level than I do about how they are put together in a machine), I've programmed some "simplistic" monte-carlo molecular simulators, and I even used to write zones for MUDS online.
Luckily, I also love to read, so I am going to be reading a lot here, I can see. But right off the bat, I can see this new crazy hobby of mine is going to be way more complex than I had first supposed. There are already an overwhelming number of options in the stickies... If I want to spend some extra time learning to do something "right" (or more complete ie at a higher level) rather than starting with a training-wheels kind of setup, but at the same time am not a professional coder, what is a good option for getting into assembly?
And as I cannot find anything in my precursory search of the forums, are there any important differences from the orginal NES system and the new mini-classic, with respect to programming your own games? I am aware that the mini has far more memory and assume this is an open resource, but are there any more differences? I have a sneaking suspicion that the mini is probably an emulator, so there might be I guess some things one can do differently if one is not working with an actual 1986 era CPU/PPU/APU network, yes?
Thanks for your time,
-daggaz
Ok I'm 40whatever years old, bought my first NES when I was 8 right when they came out, and now I'm a MSc in Nanotech PhD in ChemEng, and I bought the NES classic mini for my kids (hahahah yeah for my kids... no seriously they love it so far) and of course now I am thinking of making my own games for them (hahahah yeah for them).
I can fart around in C++ and python, I can write scripts in dosshell and a bunch of other languages, I have zero assembly experience, but I'm rocking a high-end wetware processor and can generally pick up any kind of logic orientated language in very short time. I understand computer hardware at a reasonably solid but not expert level (I know more about how the chips work physically at the atomic level than I do about how they are put together in a machine), I've programmed some "simplistic" monte-carlo molecular simulators, and I even used to write zones for MUDS online.
Luckily, I also love to read, so I am going to be reading a lot here, I can see. But right off the bat, I can see this new crazy hobby of mine is going to be way more complex than I had first supposed. There are already an overwhelming number of options in the stickies... If I want to spend some extra time learning to do something "right" (or more complete ie at a higher level) rather than starting with a training-wheels kind of setup, but at the same time am not a professional coder, what is a good option for getting into assembly?
And as I cannot find anything in my precursory search of the forums, are there any important differences from the orginal NES system and the new mini-classic, with respect to programming your own games? I am aware that the mini has far more memory and assume this is an open resource, but are there any more differences? I have a sneaking suspicion that the mini is probably an emulator, so there might be I guess some things one can do differently if one is not working with an actual 1986 era CPU/PPU/APU network, yes?
Thanks for your time,
-daggaz