Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Another strange thing related to the "graphics overwriting"
#4
After debugging your program for a LONG time, I've concluded that you use optimized sprite routines that relies on memory alignment addresses. I'm going to implement that (yes, an ALIGN n directive, so the code will be aligned to the closes n*ADDRESS code; this will be difficult to implement at the moment).

So basically, I discovered you have an INK O (instead of INK 0) sentence. By replacing it with INK 0, everything it's fixed. After a lot of tests, adding or removing NOPs to your code mades it to work ok or "dirty". These are alignment issues, and it seems to be on the sprite2.bas file. Probably you're using INC L and INC E instead of INC HL and INC DE or something. I guess that's the point. Other than that, your program is Ok.

A fast fix for that is to use "Spare" zones as you did: DEFS N, 0. Start from 1, and increase N until the program works ok.
¿Can you fix it?
Reply


Messages In This Thread

Forum Jump:


Users browsing this thread: 1 Guest(s)