Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MEGA65: VIC-III (!) palette precision problem compared to the hardware #259

Closed
lgblgblgb opened this issue May 23, 2021 · 1 comment
Closed

Comments

@lgblgblgb
Copy link
Owner

lgblgblgb commented May 23, 2021

As it turned out in #256 , I have some palette precision problems when using "legacy" (VIC-III) palette registers, in terms of actual values represented in VIC-IV palette. Maybe other problems as well. Since it's kind of different topic than just reading back pixels in issue #256 , let's open a new issue on this specific topic.

New findings: palette handling in Xemu is somewhat wrong, by writing legacy VIC-III palreg with value $F (for example) results in $FF for Xemu for the real VIC-IV palreg (my idea was to allow to use the whole brightness spectrum via VIC-III as well). However it seems, on MEGA65 it's only done with writing the most significant nybble to set.

@lgblgblgb
Copy link
Owner Author

Now actual RGB values seems to be kinda identical with MEGA65 with the commit above. This also changed the palette slightly, which is not a problem, since it means it should be closer to MEGA65 now anyway ;)

@lgblgblgb lgblgblgb changed the title MEGA65: palette precision problem compared to the hardware MEGA65: VIC-III (!) palette precision problem compared to the hardware May 25, 2021
@lgblgblgb lgblgblgb removed the WIP label Jun 5, 2021
lgblgblgb added a commit that referenced this issue Sep 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant