Yeah im not using SMC for data storage, but more as a way to get past the memory limitation imposed by hardware.  And im having the program itself count bytes so that i dont have to anticipate byte numbers myself

Yeah im not using SMC for data storage, but more as a way to get past the memory limitation imposed by hardware.  And im having the program itself count bytes so that i dont have to anticipate byte numbers myself

Well, data does not count for the execution limit because the data is not executed. If you program for ION or Mirage, you can have programs as big as you want as long as the code itself does not exceed 8KB or so.

Does storing stuff to vars count as data too?

The actual act of storing is code. The data that was stored is data.

Builderboy, im currently working on a Lunar Lander prgm, but since i cant get decimals, my acceleration (gravity or moving up) is always 1 or more (accelerating downwards). 1 meaning 1 pixel per frame.. How did u get ur Acceleration to be so smooth.. is there a way to make the graph screen 1000x1000 or something? if theres another way u see, plz share it with me =D

uhh.. im not quite sure i understand..  for example instead of Pt-On(X,Y,Pic1 do.. Pt-On(256X,256Y,Pic1 ?

if that doesnt make sense, il give u more detail about my prgm (idk how everyone else does their gravity and such but..)

basically my prgm subtracts 1 from acceleration every single time it repeats, and then i add acceleration onto my Y coordinate (so up and downs) ect.

so with that strategy, do i do .. idk.. lol if u can, id like some examples =D. Btw ty for making AXE.

luuuuuvvvvvv itttt

Well what I think Quigibo is saying is that during the calculations and such to determine the point you are multiplying something by 256. Then when you go to display it's something like Pt-On(X/256,Y/256,Pic1. I'm not sure but that is what it sounded like to me.

That's basically what it is.  If I were to explain, I'd say it's stored as a big number, 256 times what you've got it at now. (ex: (0,0) is (0,0) but (1,2) is stored as (256, 512) ) You calculate on it with those large numbers to give you 256 times the precision.  When you display it, you divide be 256 just as Meishe showed.  Did this make sense?

im not sure why it works, but thank youuuuu.   cause wouldnt say.. 100/90 = 1.111? which is decimal? hmmmmm uh actually, idk if it works OO" it doesnt seem to be working atm. oh well

Nvm=D I divided the wrong waylol. It works

EDIT: wow thanks, my ship is running very smoothly =D