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
It looks like you are drawing all tilemap layers to a buffer very quickly and then dumping it. The real hardware most likely did not work that way. Tilemap layers are normally read on the fly and dumped directly to the video signal. There are very few systems that had a double line buffer (not single line) for the scroll.
Unless the software does raster effects, this difference in implementation will not be noticed by the player. Still, consider changing it. You can close the issue if you prefer to leave it as it is, of course.
Pretty much all cores in the repository do a direct video dump, so you have plenty of examples to check.
It looks like you are drawing all tilemap layers to a buffer very quickly and then dumping it. The real hardware most likely did not work that way. Tilemap layers are normally read on the fly and dumped directly to the video signal. There are very few systems that had a double line buffer (not single line) for the scroll.
Unless the software does raster effects, this difference in implementation will not be noticed by the player. Still, consider changing it. You can close the issue if you prefer to leave it as it is, of course.
Pretty much all cores in the repository do a direct video dump, so you have plenty of examples to check.
jtcores/cores/toki/hdl/tile.v
Line 33 in e63a12e
The text was updated successfully, but these errors were encountered: