The attached image has sprites to add details to the SC2 image, but RECOIL renders this file without the sprites. On the real MSX the sprites are shown.
I also attached a reference PNG rendering of how the image should look with the sprites.
You're right. And this indeed brings a dilemma. If RECOIL just ignores the problem and renders the sprites on images like this, this will hide a problem that might showup on the real machine depending on what was loaded before.
This would go on the contrary direction of what I asked on ticket #80.
Is it possible for recoil2png and recoilwin to print warnings for the inconsistencies it finds on the files then? That would be a great help to quickly detect and fix files with such problems.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Diff:
This file is one byte too short. It's not a padding byte that's missing, it's a byte of sprite data. Attached is this file with a zero byte appended.
It's possible to allow truncated files, but this raises a question to which degree to accept the files that are known to be malformed.
Do you have more such files?
You're right. And this indeed brings a dilemma. If RECOIL just ignores the problem and renders the sprites on images like this, this will hide a problem that might showup on the real machine depending on what was loaded before.
This would go on the contrary direction of what I asked on ticket #80.
Is it possible for recoil2png and recoilwin to print warnings for the inconsistencies it finds on the files then? That would be a great help to quickly detect and fix files with such problems.