No, the random number generator uses 3 levels of random.  First it uses a seed.  Then it reads a whatever memory location that seed points to and integrates that into the number, then it checks the "r" register which is kind of like a timer and adds that to the mix.  So seeding is rather pointless.

But yes, you can retrieve the last random number generated like this: {L1-2}^r

Use this for now, I'll put a copy of it in the next update, which might be tonight since I think I may have a serious bug that needs fixing.  Nothing new in the update and not a separate version, just a fix to the previous.


The numbering actually kind of makes sense in hexadecimal, but in base 10, the numbering system seems kind of random.

Uh oh. That's really weird.  I'll go fix that, I must have changed something by mistake...

its 6 bytes per program, not six bytes per call correct?  Or else that would be very significant yayyyy line routine!  This is one i have been waiting for a while, glad its finally in and signed division yaayyyyy!  Haha now to go through and re-optimise some of the code i have

Yes, for the entire program.  Glad you like the update

Hope everyone likes the new update!

I had a bad experience when I accidentally did drawing off-screen.  I couldn't get the calculator to ram clear and removing the batteries wasn't helping either.  I had to actually unscrew the case and remove the little button cell battery to unfreeze the calc.  Anyway, I don't want that to happen to anybody else, so I added a little check when drawing pixels.  Its only 6 more bytes total and any slowdown is negligible compared to the entire routine.  It also allows you to clip lines off the right and bottom sides of the screen if they overextend.

WOW how did I miss that... I forgot I moved it to the end, thanks.

It should be as long as all the data is one after the other, but be careful with the size counting!  I think the limit to program sizes is 16k though or something just becasue of the way the RAM is works.  What are you doing that uses that much memory?  Is it picture files or something?  And how is the parser working by the way, I haven't actually tried it with that much data before.

EDIT: As for individual levels at a time, there really isn't an easy way to do that.  You could split the level data into more than one appvar maybe.  Also, you can get more room in the ram if you have the program archive itself at the start (doesn't affect the copy of the program that is actually running).

Quote from: Quigibo on April 25, 2010, 12:13:47 am

I think the hardest part of learning asm is the shift in paradigm.  In my opinion, someone with very little programming background will be able to learn the language and understand it better initially than someone who has exclusively programmed in higher level languages their whole lives.  I remember the concept of flags, registers, unsigned arithmetic, bit shifting, etc.  seemed so foreign to me when I was first learning.  You never cover that stuff in high level.  In my head I kept trying to make my code look and feel like the languages I was used to so then it would all be simple and I could just naturally pick it up.  But you can't do that, its impossible.  You miss all the concepts that are absolutely essential to do all the low level tasks which is the whole point.

You have to start with a very open mind.  Your knowledge of how to ride a bike isn't going to help you much when you're trying to fly a helicopter.  It took me about a whole summer to get the hang of it and it was almost a year before I could write a game with it.

Can you explain that?  Are you saying I should not talk to people with the idea of Ti-Basic, assuming that they know that language?  Otherwise, what do you mean?

Yeah that's the general suggestion I'm making.  It wasn't in response to the lesson you posted, I haven't read it yet, I was just giving my personal experience.