Ender's Game revived once more

tokijnct · Post by **tokijnct** » Thu 28 Apr, 2005 8:33 pm

You could change a few of the if-then booleans if they only contain one command from:

:If etc....
:Then

-8=>X
:End

to...

:If etc...

-8=>X

merthsoft · Post by **merthsoft** » Thu 28 Apr, 2005 8:38 pm

Nothing I can think of to solve the error, but some mem saving:
Make 0->A into DelVar A
Make If [A](B+Y/8+1,A+X/8+1)>35 into If 35<[A](B+Y/8+1,A+X/8+1

Toaster · Post by **Toaster** » Fri 29 Apr, 2005 12:12 am

Invalid Dim usualy means that you went out side of the matrix.

check to see what your matrix size is and than do a text command to show where you are at in the matrix.

dysfunction · Post by **dysfunction** » Fri 29 Apr, 2005 12:13 pm

Obviously it goes off the Matrix, what I'm trying to figure out is why. Well, thanks for the optimizations. I'm working very hard on fixing this bug(s).

Toaster · Post by **Toaster** » Fri 29 Apr, 2005 7:27 pm

With out seeing the map data or were you are on the screen in your screenshot I think it would be pretty hard for anyone to find the bug.

If you want to find the bug right down how large your matrix is on a piece of paper. Then you use a text command like this to display where your at in the matrix.

Code: Select all

Text(0,0,"X:",Where your at on the matrix X axis.
Text(7,0,"Y:",Where your at on the matrix Y axis.

I would think a basic coder like yourself would have tried this.

I have used this simple debuging rountine to find many errors in my programs.

merthsoft · Post by **merthsoft** » Sat 30 Apr, 2005 1:37 am

Instead of that, use

Code: Select all

Text(0,0,X,"/",Y

X where you are on the X, and Y being where you are on the Y (whichever vairable you use), then itlle return it as Xcoord/Ycoord, I think It's easier to understand that way.

dysfunction · Post by **dysfunction** » Sat 30 Apr, 2005 9:42 pm

Nevermind, I guess it's too hard to explain my bug. I know why it goes off the matrix, just not the other part. Normally it can't go off the matrix, there's code to catch that, but it does when values get screwed up. What's happening is as the cursor is brought over a lrge ship, the cursor becomes large and is moved to the top left corner of the ship. The problem is that in certain situations the coordinates aren't changed correctly and the cxursor ends up somewhere it's not supposed to- sometimes off the map, resulting in error.

DarkerLine · Post by **DarkerLine** » Sun 01 May, 2005 5:35 pm

tokijnct wrote:You could change a few of the if-then booleans if they only contain one command from:

:If etc....
:Then
-8=>X
:End

to...

:If etc...
-8=>X

Or X-8(condition -> X
example:

Code: Select all

If K=24:X-8->X

can be changed to

Code: Select all

X-8(K=24 -> X

Instead of that, use Text(0,0,X,"/",Y

or

Code: Select all

Text(0,0,"(",X,",",Y,")

dysfunction · Post by **dysfunction** » Mon 02 May, 2005 12:46 pm

Fixed my bugs! Work is now progressing quickly, I'll have more updates after school.

Post by **tr1p1ea** » Mon 02 May, 2005 1:24 pm

Cool, i cant wait to see progress ... and hopefully another screenie?

.

DJ_O · Post by **DJ_O** » Mon 02 May, 2005 2:29 pm

Cool you fixed it! What was the problem that caused the bug?

dysfunction · Post by **dysfunction** » Mon 02 May, 2005 5:52 pm

Essentialy a large number of arithmetic errors. That's what i suspected, the hard part was finding them all. however once I found two of them I knew where to look for the rest. Basically debugging it involved an hour of running the program, looking at the code in graphlink, and making changes to see what difference they made. Anyways, I've got it and I'll give an update in a few hours. Current size: 14673 bytes.

DJ_O · Post by **DJ_O** » Mon 02 May, 2005 5:54 pm

WOW 14673 bytes!!! I can barely fit a BASIC game in less than 60 KB

dysfunction · Post by **dysfunction** » Mon 02 May, 2005 9:20 pm

Yeah, this should fit in RAM (not including any external levels).

dysfunction · Post by **dysfunction** » Wed 08 Jun, 2005 12:22 pm

Yay! An update! Parallax scrolling is now implemented, thogh buggy, as you can see in this shot, if you look closely:

I think I know how to fix the bug, though, so I'll work on that (and maybe more) today.