I am programming a 2048 game, and have a decent one that works right now, however it runs dreadfully slow. I wonder if anyone can help optimize it so it runs faster?
I expected to use output and random more, that is why they are separate, I will combine in future though. Output just outputs the numbers on the screen, and random picks a random unoccupied spot to put another 2.
EDIT: I do not know the source code for prgmASM, since I got it off the internet, but all it does is switch the prgm and home commands, allowing me to use Archive and UnArchive within the program. I run this from mirageOS so that it doesn't take up RAM, and have the other programs(except ASM which is really small) archived as well.
EDIT2: Pic3 is the grid which I drew, and GDB0 is the standard graph screen, in case of functions interfering.


Code:


prgmOUTPUT code:

Code:


prgmRANDOM code:

Code:

Can you post the dode for prgmRANDOM, prgmOUTPUT, and the source to prgmASM?

Code:


Can be Fill(0,|LZ048

UnArchive and Archive take a bit of time to do, if the programs have any decent size at all to them. You're better off with a program or routine to copy them from archive to ram as a temp program.

All those conditionals in the first program.. Might look into creating something a bit more dynamic in searching and manipulating.

As to your second program, you realize that if you are only doing one thing, in your case using Text( after a conditional, you don't need Then and End. If blah:Text(blah

Will let you do some thinking and modifying based on those thoughts first, and we'll go from there.

Thanks, didn't know about the fill command. I am going to just get rid of subprograms, originally I thought I would use output more than once, so that'll get rid of the archives. I could use while and variables to do each line in each direction instead of doing each line manually, which would shorten it, but I think that that makes it go slower? Maybe I don't know what u mean by something dynamic, but I don't think it would go faster, since it would add another layer of while/if.

As far as archiving and unarchiving from within programs, I strongly suggest that you make it a Doors CS program instead of a MirageOS program. This will allow you to use ExecArcPrgm and all of the other BASIC libraries that Doors CS offers (including sprite routines if you want tile sprites for your game. As far as programming suggestions for your existing code, you have a great deal of conditional repetition that could be combined into For() loops. Fixing this wouldn't help the speed, but it would drastically reduce the size of your program. Have you considered looking at some existing 2048 clones for reference, like my color version?

Ok, I made some changes and now it is all one program and drastically reduced in size. Now it takes a while to reoutput all of the numbers, resulting in a split-second of no numbers on the screen when it clears then reoutputs the numbers. I have an idea on how to fix this, using if else statements, but that would have the cleartext code twice, and wouldn't that take longer on an already slow program?


Code: