What kind of game do you want to make, and how does the ASM programming fit in?

____________________
Wife make lunch - Shampoo
Opera - give it a spin
Spare some of your free time?
<GreyMaria> I walked around the Lake so many goddamn times that my sex drive was brutally murdered
Kawa rocks — byuu

And what CPU would that be?

____________________
Wife make lunch - Shampoo
Opera - give it a spin
Spare some of your free time?
<GreyMaria> I walked around the Lake so many goddamn times that my sex drive was brutally murdered
Kawa rocks — byuu

I'm starting to get some ideas here. Why specifically the SNES?

____________________
Wife make lunch - Shampoo
Opera - give it a spin
Spare some of your free time?
<GreyMaria> I walked around the Lake so many goddamn times that my sex drive was brutally murdered
Kawa rocks — byuu

Butt out Paulguy. I haven't offered to code anything and I wasn't planning to. I'm just trying to help in some way I can.

Besides, I can barely even read SNES ASM.

____________________
Wife make lunch - Shampoo
Opera - give it a spin
Spare some of your free time?
<GreyMaria> I walked around the Lake so many goddamn times that my sex drive was brutally murdered
Kawa rocks — byuu

Those are pretty good reasons on first glance, except for the palette thing.

The Super Gameboy, Color Gameboy, Gameboy Advance and DS all use the exact same color format. The only difference is the amount of palette entries.

Still, the other two are perfectly good reasons. Got any more?

____________________
Wife make lunch - Shampoo
Opera - give it a spin
Spare some of your free time?
<GreyMaria> I walked around the Lake so many goddamn times that my sex drive was brutally murdered
Kawa rocks — byuu

No it isn't. On any system, there's several levels of speed.

ASM is at the very top, but if it's badly written it drops a level or two.
C is right below it. Given a proper compiler, it is so fast that only very intensive parts might require some inline ASM work. C++ is often one (or one half) level below that, but only because of extra OO overhead. Using a C++ compiler, yet writing plain C with it could even help create faster ASM output.

Somewhere at the bottom are interpreted languages, not counting any game script interpreter you might use.

Now, the SNES might not be the fastest horse in the stable but I think, if you write good C code, it'll work fine.


And now, some life experience: I write C on the Gameboy Advance. One of the first things I learned is to use native-width integers for stuff like parameters and globals, and only use other types in structs and stuff. This because having a byte or halfword parameter or return value would require extra ASM code to make sure it is a byte or halfword. With native ints, that code can be left out, making the resultant ASM smaller and faster.

These days, most if not all games are written in C (or C++) with preciously little ASM work. Most I've seen that's consistently done in ASM is stuff like sound mixing.

____________________
Wife make lunch - Shampoo
Opera - give it a spin
Spare some of your free time?
<GreyMaria> I walked around the Lake so many goddamn times that my sex drive was brutally murdered
Kawa rocks — byuu

Posted by DahrkDaiz

---

You have to love for it to be any good.

---

No matter what language you write in.

I won't code in COBOL for anything less than five hundred though

____________________
Wife make lunch - Shampoo
Opera - give it a spin
Spare some of your free time?
<GreyMaria> I walked around the Lake so many goddamn times that my sex drive was brutally murdered
Kawa rocks — byuu

Well, I have some GBA C code to draw stuff like a tilemap. It's quite close to the SNES, format-wise, as far as I can remember so if you want I can give you some sample code. I also have a simple tile-based print function that could theoretically work on any system with tilemaps.

Sprites I'm not too certain about, so I'd rather not give (possible) C code for that until I've studied the ASM side of it myself.

____________________
Wife make lunch - Shampoo
Opera - give it a spin
Spare some of your free time?
<GreyMaria> I walked around the Lake so many goddamn times that my sex drive was brutally murdered
Kawa rocks — byuu

What do you mean, "it doesn't work"?

Anyway, here's some sample code. It's just from the top of my head and unfit for consumption, but it's the basics.

//Just imagine this is more, about one screenfull. //The ones are wall pieces, two, three and four are //shadow variations and five is floor. Can you visualize the data? const u16 someMapData[] = { 1, 1, 1, 1, 1, 1, ... 1, 2, 3, 3, 3, 3, ... 1, 4, 5, 5, 5, 5, ... 1, 4, 5, 5, 5, 5, ... 1, 4, 5, 5, 5, 5, ... 1, 4, 5, 5, 5, 5, ... ... }; void LoadTestMap() { //Again, top of my head. memcpy(someMapData, BG0, sizeof(someMapData)); }

Assuming you have, through similar methods, loaded the graphics tiles into their proper memory area, you should get whatever you visualized on screen. This all assumes you have a header file to describe whatever "BG0" is supposed to be -- in this case, a pointer to the VRAM area where the bottom background layer is stored.

Also note that I used "const u16" instead of just "int" -- for one, such data should be defined constant so it doesn't take up extra RAM, and for two it really should match the type of the target.

____________________
Wife make lunch - Shampoo
Opera - give it a spin
Spare some of your free time?
<GreyMaria> I walked around the Lake so many goddamn times that my sex drive was brutally murdered
Kawa rocks — byuu