That is probably the simplest and fastest method and shouldn't slow it down much, but there might be order-of-operations issues, so you might need:
If (A>(X-8)) and (A<(X+8))
Alternatively:
If (A-X>-8) and (A-X<8)
But for Axe, that can probably be optimized to:
If A-X+7 < 15
(This is taking advantage of "negative" numbers actually being really large, so you don't need to make sure A-X+7>=0. If it was "smaller" than zero, it would actually be around 65000 which is not less than 15 )

You have the Fix 4 inside the loop so after the first iteration, it starts drawing directly to the LCD again. If you move it outside the loop (after the End), then it should work.

Also as general forum etiquette, you can Modify your post instead of double- (or triple-) posting (Double posting is when you post twice in a row. General rule of thumb is that after a day since the last post it is okay to double-post.)

Wow, it has been over a year since I last updated this thread!

I've added support for IEEE-754 binary32 floats here!
What is really nice about this is that compilers like fasmg have built-in support for these floats, and there are a plethora of existing tools to work with them.
I've rearranged the project a bit and I am working on making the code more agnostic (so not relying on spasm's unique features). I've added a lot of conversion routines, especially for f32 and f24 floats.

I took an unplanned path with the f32 floats and ended up making addition, subtraction, multiplication, division, and square roots work entirely within registers and the stack, so no external RAM was required. I haven't taken the time to do a speed analysis of these, but I'm thinking they are a little slower than the single routines. I expect that multiplication and division are slower, and hopefully addition and subtraction are faster.

I don't think I can do an OnlyFans; I'm just not ready for that kind of responsibility :|

I think what I would suggest is what you are already trying to do. For irregular collision boxes, I set a "collision buffer" the size of the screen (1bpp), and in that buffer I set the pixel on if it's a collision point, else off. Then when I am drawing the tile, so draw it's collision sprite to the collision buffer.

I have no idea how to do this on the 68k calcs

Again, on behalf of Soru from Discord:

are you sure it is reset completely? try leaving the room and then come back in

Nover 3 was created ~7 years ago for the nspire. The nspire CX II is similar, but fairly different and I would be surprised if nover 3 even worked on the CX II. That said, I don't really follow the CX II series, so I could be wrong. I just know the software and hardware have changed since the original CX models.

Oh, thanks for confirming that. I know the code to set 15MHz mode does take some advantage of that, because it essentially writes a 0 to port 20h (mirror of the link port) on those calcs which is generally safe, but writes a non-zero value on the other calcs.