I could always borrow a friend's calc, but ya, the main reason why I don't do z80 is because I can't seem to get anything to compile these days.

also, I feel really overwhelmed because this is my first real project.  I don't really know where to start coding.  Thoughts brew in my head, such as, should I start with the tilemapper? should I make external level support available? should I work on the physics/character movement/key input engine first? when should I start puting enemies in the picture.  I have no idea.  

Right now, it boils down to: should I start with movement first, or tilemap reading and writing?

Notes: (just writing down ideas so I don't forget )

lots of math to look at.  I have to decide between two tiling methods.  

so far, I've got a player structure that has an x position and a y position.  there's key counter too for each key.  The hard part is to decide how to write a scheme for position change.  I can't have the character change more than 2-3 pixels in position or the character might possible pass through enemies during the enemy collision.

I was thinking that the key counter has a set limit so you can't hold the jump key and go up forever constantly accelerating/decelerating. and you can't run and get faster and faster.  I think a seperate variable for additional vector effect is needed to allow for jump pads.

Things that affect position:
1.) key press
2.) tile vector structure
3.) jump pads

I think that's it.

Jump pads is it's own curved equation in itself.  So is key press.  I don't want to add many calculations by adding together 2 different log/exp/quadratic equations.  That's why I originally wanted to position change variables for both x and y.  The first position change would affect the second, and the second put into an equation and modified by tile vectors would result in the final position change of 1-2 pixels per loop.  I'm guessing that the speed of the 68k will make periods of not moving and moving seem like the sprite is slowing down.
So moving 1 pixel every game loop is maximum speed.  Idk how double buffering will affect the speed and the blurriness of the game.

Oh ya, i forgot, to make everything work correctly, I'll have to make all the maps the same size.  IIRC, the screen coordinates and map coordinates of tilemap engine and the screen itself are 0,0 at the top left, whereas most of my math right now is done with 0,0 at the bottom left.  I'll have to change stuff to make it work.

As for tiles, tiles have an associated tile vector structure.  As long as the sprite is "on" that tile, the tile vector will change the position change.  So  a slope of 45 degrees might have a -1/-1, which will reduce the + whatever that the run key gives.  The vertical and horizontal tiles will have INSANELY high vector changes, making it possible to run up a vertical wall if you're fast enough.  (idk if i like this though)

Calculation Processes:
1.) key input calculation
2.) tile vector calculation
3.) jump pad calculaton
4.) INSANE DEATH velocity detection.
I hope the complexity of my design doesn't slow the game down.  there's just so many variables in the problem I've kinda lost where to start and not screw up so badly i'm totally discouraged.  Maybe it's about time to work on r/p/s again.

btw, what does this mean?
c1-->

CODE

ec1 DelVar XRepeat 0 A->B:getKey->A If Ans:Then (X+1)(Ans=B->X Output(1,1,Ans Else:ClrHome End:rand(1:End c2

QuoteBegin-Ranman+May 25 2006, 12:02 AM-->

QUOTE (Ranman @ May 25 2006, 12:02 AM)

I finally looked at the N-Game on the internet. Wow!! O_O What a cool game! Great idea for a port!

I tried the flash version and its wicked amazing I cant wait to see this come out for 89

Liazon, don't give up. My advice is that you make a couple of mini-games first, to get your feet wet with TIGCC. Ask us questions (also try the TIGCC board, http://tigcc.ticalc.org) and we will do our best to help you.

N-Game is a very ambitious and complex game to code. Keep in mind that the 'original' was "coded" in Flash, which has some very straight-forward routines for terrain detection, collision, etc. - coding it in C, where you have to do everything yourself is of course a very grueling task.

- Alex

I see low self esteem in there. Liazon dont give up always feel free to ask help if you need it even if you don't want to.  

QuoteBegin-shadow+May 31 2006, 08:50 PM-->

QUOTE (shadow @ May 31 2006, 08:50 PM)

umm is just me or do a lot of poeple on this site seem depressed/have low self esteem....

-->

QUOTE

( 100th post!!! WOOT)