Oh I think he meant how the HUD is redrawn everytime the map is. Hence why we suggest only erasing parts of the screen that need to be modified.

You don't even need to erase it, though, since Output( should overwrite what was there. So you can just draw the new map over top the old one and avoid the ClrHome and outputting spaces.

You don't even need to erase it, though, since Output( should overwrite what was there. So you can just draw the new map over top the old one and avoid the ClrHome and outputting spaces.

In Illusiat 11 case, though, I think it's best to erase the map before redrawing the next one, because back in the days I tried not doing that and it looked confusing during map transitions for the player, especially when two maps looked identical.

Yeah on the CSE with the slow display it matters, but on the monochrome calcs the impact on speed is zero to none.

Yeah I agree. Trust me I tried in 2002 lol. It works better when maps display in one or two seconds.

Also btw don't be afraid of using the same color for the floor and objects whenever other options make maps look ugly.

EDIT: Btw the new version of xLIBC fixes the Output() glitch with drawing commands so you probably won't need your ASM program anymore.

I know this is probably not gonna be implemented since the game uses pictures for map data, but I thought it would be cool to see how parts of the game could look like if the map engine was more complex, such as using two pictures at once for maps or Illusiat 13-style data:

If I still have the full 6 pic vars, I could, in theory, add two clones of the map to each image for an effect like this. It would be pretty cool