What about the undocumented instructions?

Ah, that makes sense now. Have you tested the version with Rect(?

Drawing the text on the right side every frame is very slow. You should draw it once before the game and then only clear the 64x64 px area. You could use Copy(, Fill( and/or a for( loop to achieve that.

Yeah, also great idea.

It doesn't need to be dynamically. Maybe just a button to show/refresh the cycle calculator and one to hide it. When you click the show button, another column will appear next to the text field for the code (parallel scrolling) and you can select the loops to multiply. At the bottom the total sum is displayed.

EDIT something like this:

I used the average number of cycles.

To test if whether a pixel is set you could make a simple routine that shifts the byte right by one and checks for carry.

Ok then maybe do something like this:

But this clears the whole screen, right?

Which routine?

Are you doing clrdraw every frame? That would make the pxl-Off redundant.

Why do you have to multiply with W at the end? I don't get the point of that. Can you post that part of your code?

I don't know, can you post the solution you came up with so maybe we can optimize that.

What do you mean with a "a line with a different size"? One that is wider than one pixel?
When you only need vertical or horizontal lines, you should use the Rect( command. It is a lot faster than Line( and you can adjust the width.

Yeah, it is probably the fastest way to do it. If you don't need the sprites anywhere else, just store them rotated. That is faster and takes less memory.

Btw, your raycaster looks awesome so far. I built one myself last week. Does yours run at 6 mHz or at 15 mHz?

To get the vertical line, just rotate the sprite 90 degrees right and then you add the line you want. The result is the vertical line from bottom to top.


EDIT: When you only use that sprite you said it doesn't need to be turned because it is the same then.

And L (without *8 ) should be correct.