So back when Axe first came out I decided I would attempt to make a PiCross clone. Well I failed horridly at axe and eventually managed to pick up asm which is what I am now writing this in, so here we go!



So far not to much is done. I have most of my graphics routines done. and 2 of the underlying support routines done.

ToDo list (in no particular order):
Features:
- external levels
- overlay mode
- highscores
Everything else:
-rendering of levels
-code to check for level completion
-code to handle input
-...why am i typing this huge list of things out





Needless to say a lot still needs to be done but were getting some where!

*Too much, *And two, *somewhere. But your spelling and grammar is magically getting much better! Perhaps our nagging is helping.

I'm very happy that my masked sprite routine is helping, and I hope you'll both continue to ask us all of your ASM questions in your topic or in the channel, and keep us abreast of your progress.

I plan on it. I'm on the hunt for a line routine currently but I think runer/axe has one that will work for me. This is slowly looking like it may be a possible nostub game...I have yet to use any calls outside of my own xD

I strongly recommend Doors CS!

http://dcs.cemetech.net/index.php?title=Fastline

Issue with that is I can not change the buffer its drawn to. The way I am doing the grey scale is just by altering what buffer everything is drawn to. Sadly I don't get that option with Fastline

Ah, that's an excellent point. The MirageOS libraries that Doors CS emulates let you select what buffer address you want to copy to the screen from using my super-spiffy interrupt-aware iFastCopy routine, but sadly, the line and rectangle routines don't provide the same flexibility.

Which is a big bummer but tis ok. Im just hoping I have enough executable code space for the entire game. its filling up fast xD (compiled program is ~900bytes only 64bytes of that is graphics and other things)

Since you're planning on grayscale, hopefully you can push the bulk of the program, namely the grayscale sprite and graphics data, up above $C000 with enough room for your code, as you said. I vote that you make it a DCS program anyway if you so decide. Also, I'm required by my conscience to say this: since this is your first ASM game, if you get frustrated or roadblocked, I strongly recommend you put this aside for a week or two, write and complete a simpler, perhaps monochrome, game or program, then pick this up again. If progress goes well, though, by all means carry on.

You mentioned the other night that you may want some help with redoing small pieces of your code (namely, the part does does all the drawing), and I'd still be glad to help out. Also, I could have sworn that one of the MirageOS routines let you choose what piece of RAM you wanted to use. Hmm, guess not. I guess I was thinking about the one that let you choose what buffer iPutSprite goes to :/

If I can not figure it out on my own I will gladly ask for help. ... or if i just get lazy which ever comes first >.> <.<

I got lazy/stupid

I need help optmizing this.


Code:

Well I got Iambian to help me. Its slower then what I had but much smaller so. I'm happy with it.


Code:

Oh god, with the freaking $+N, don't oh please don't do that. Use labels or I will stab you with a calculator for making life unnecessarily difficult. I see a few more optimizations I can suggest after that.

Tis not my code its Iambians. That just makes sense to him....Cadan's source is riddled with them X.x

Ill see what I can do right after I solve this grey scale issue I am having

I know, when I was consulting with the Celtic III code I had to spear my eyes with all of those. Tell me more about this grayscale issue, and perhaps you have a screenshot?

Grayscale issue was me messing up a value. it was calling my empty mapper like 200 times every second or so X.x

as for Iambian's Code. We now have lables Instead of relative adressing. ^_^
(I apologize for crappy tabbing....)

Code:

The labels are still non-descriptive. If you're going to use them like that,why not use anonymous labels? I find that they're more powerful, and they won't clutter up your namespace.

Also, nice to see the grayscale is now better

In all honesty I have no idea *how* this code works yet I am reading/learning that now. All I currently know is it works....it will be spiffed up and better commented/labled in my source when all is said and done lol

Yay Double posts.



A proper title screen now. Will get one more thing added to it eventually, but for now I like it.

now to go work on the actual engine xD

Do I see some fades in there? That looks great, if so. And I'm happy that you're running it from Doors CS. Do you need help designing an icon?

Fades as in abusing greyscale to make a line look like its fading? Then yes.

Probably. Have not put to much thought into the icon as currently it may not stay DCS . It may have to be converted to an app due to code length restriction things, And the fact that it only uses DCS's quit to shell routine which means it could easily be adjusted for no shell as of now.