You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When specifying an explicit palette using -c hex it seems the palette entries are rotated within the palette. In particular it seems if the input order is 0123 the output order is 3012.
For example, I would expect the input data: (This is test1.hex)
ffffff
b2b2b2
4c4c4c
000000
to output the following GBC format data, with white first and black last:
FF7F D65A 2925 0000
However, the actual output is this:
0000 FF7F D65A 2925
Included are two test images and three test palettes, for a total of 6 test commands. The reason for all of these tests is to test whether the order was affected by either the first color seen in the image, or the brightness of the palettes. However, it seems to consistently rotate the order as described above, so really only 3 of the test cases are relevant, as the output from the black and white tests is identical.
Here's the input and output I observed during for the other test cases:
test2.hex
ffffff
4c4c4c
b2b2b2
000000
black-test2.pal/white-test2.pal
0000 FF7F 2925 D65A
test3.hex
000000
ffffff
4c4c4c
b2b2b2
black-test3.pal/white-test3.pal
D65A 0000 FF7F 2925
Notes:
In all tested cases, the input order 0123 is transformed to the output order is 3012. The brightness or order the colors are seen in the image don't seem to matter.
Specifying a palette with -c gbc preserves the order in the input file in all my tests. I have not tested other palette formats than those.
The generated tile data has been internally consistent with the palette data in all my tests, so used as is the data would create the correct image on the screen. (But in my use case it caused other problems with code that assumed that the order was as specified.)
When specifying an explicit palette using
-c hex
it seems the palette entries are rotated within the palette. In particular it seems if the input order is0123
the output order is3012
.For example, I would expect the input data: (This is test1.hex)
to output the following GBC format data, with white first and black last:
However, the actual output is this:
Included are two test images and three test palettes, for a total of 6 test commands. The reason for all of these tests is to test whether the order was affected by either the first color seen in the image, or the brightness of the palettes. However, it seems to consistently rotate the order as described above, so really only 3 of the test cases are relevant, as the output from the black and white tests is identical.
Command invocation:
Here's the input and output I observed during for the other test cases:
test2.hex
black-test2.pal/white-test2.pal
test3.hex
black-test3.pal/white-test3.pal
Notes:
-c gbc
preserves the order in the input file in all my tests. I have not tested other palette formats than those.Test cases:
gfxtest.zip
The text was updated successfully, but these errors were encountered: