Turrican for MSX new WIP

just checked. it behave the same on both C64 and Amiga versions, like mine (I just have to add a little explosion when the bullets touchj some solid surface)

Cool. Certainly progress here I like it

I had an msx1 in the past. Only some year ago I bought an MSX2 (wich was my dream machine, in the past, until I bought an Amiga500+). So it is a matter of love <3
But I'm planning to study (in the meanwhile) the v9938 and add features on msx2 if I'll be able to... also because in Freedom Fighter post credit scene I imply that Freedom Fighter 2 will be developed on msx2... so I have to!

And yes, Turrican 2 on Amiga is the best game ever and forever (at least in my heart)

well, 5 more characters, to say the truth... you aren't considering 5way (the bullets of the 2 diagonal types aren't the same).
bullets are updated every frame inside the isr. for each bullet I have to set the address and then out it to vram after the screen draw (yep, every frame). I'm already in need of cycles (well in 60Hz machines) so I use 2 different screendraw routines for pal and ntsc: pal screen contents are updated using unrolled otir (soa serie of outi), ntsc ones instead using the classic

label:
     outi
     jp nz,label

(else the bottom of the screen is corrupted)
this because i do a lot hooked in the isr:

redefine 8 sprites (the main character) (256 bytes, unrolled otir)
output the SAT (128 bytes, unrolled otir)
check player movement (not joystick input, stuff like jump offsets, background collision, coordinates updates , and so on)
output the screen (640 bytes, pal unrolled otir, ntsc classic way)
bullets (up to 15 addresses to set and up to 15 bullets to out on vram, they will be deletd next frame from screen output and updated again from this routine)
check frequence and play music at correct speed
update some flags/variables

so added another check (for up to 15 bullets) and maybe use another way to decide wich bullet shape write (actually I use the b value, the counter of the routine because in the bullet table the bullets are stored by type so knowing b we know wich bullet we are writing in vram)... I think I will keep it this way

I wanted to do the same before, but in previous version the screen was refreshed only every 3/50 of sec (outside the isr) and the video buffer on ram could be moved in 8 directions. Bullets have to be fast so I decided to update them during isr, storing their locations, restoring them before drawing again the bullets but always during isr so retrieving the addresses and doing this operation for up to 15 bullets. Ir wasn't a matter for horizontal bullets (only one address retrieve from table, out(98h) old backgound value out(98h) bullet value, thanks to auto increment). But for diagonal ones I had to retrieve address, out old bg value, add the right offset to address re send address data and out bullet value. And in 5way bullet we have 12 diagonal bullets (so 24 addressess out)...
So I preferred to output the whole screen before drawing new bullets to avoid all those double addressess out(99h)