I've been trying to work out if this was possible myself. I suppose the question id be seeking to ask next is : What is the overhead of this "display mode" , I presume its using a lot of interrupts - how much time is left to do play with ?
The 4x4 FLI display mode isn't too bad. It only needs an interrupt every 8th raster line to trigger a "bad line". The bad line in itself steals 40 cycles and the IRQ code probably takes around 50-60 cycles So it probably takes somewhere around 12% of the CPU time per frame... The timing is a bit finicky though... Have look at codebase64.org/doku.php?id=base:4x4_fli_chunky_mode
It'd make a great 3D world overlay for a sprite to walk around in! Well done!
Finally
Someone did it
Wow. Nice... Great job, Alex...
Mode 7? Never heard of that. But then too I don't know what FLI is really.
Same here. I wonder what we used to call whatever it is.
I've been trying to work out if this was possible myself.
I suppose the question id be seeking to ask next is : What is the overhead of this "display mode" , I presume its using a lot of interrupts - how much time is left to do play with ?
The 4x4 FLI display mode isn't too bad. It only needs an interrupt every 8th raster line to trigger a "bad line".
The bad line in itself steals 40 cycles and the IRQ code probably takes around 50-60 cycles
So it probably takes somewhere around 12% of the CPU time per frame...
The timing is a bit finicky though... Have look at codebase64.org/doku.php?id=base:4x4_fli_chunky_mode
Nice !
feels a bit quadratic
How large is the image being manipulated here?
Half the screen in this resolution. So the part being actively updated is 80x25 pixels.
@@CogitareComputing How big is the texture ?
@@NickFellows pretty big