I've been running into this video corruption from time to time. The entire screen at once.
I've been moving all vdp access inside the nmi routine. Still hasn't improved though.
I'm wondering does any of these statements actually access VRAM which are not inside the nmi_routine. In other words do I need to move them inside the nmi routine.
sprites[1].x=100;
sprites[1].y=100;
sprites[1].colour=4;
sprites[1].pattern=(25*4);
or does only updatesprites(0,16); access vram which I alrea
This is just my guess based on my own experience.
We all experience video corruption from time to time. This one reminds me of three cases I experienced long time ago in my projects : many times I just typed the parameters in the wrong order or typed the wrong data table name to be uploaded in VRAM, I also saw what updating VRAM in a bad timing can do and now I tend to use NMI for updating VRAM in batch, and I also saw corruption when uploading the sprites table in VRAM without the byte at t