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
This document, overall, is great in its information density and organization. However, it's slightly cumbersome to use as a reference while coding due to the fact that the register layout map is only provided once at the top of the document.
Example:
The section explaining the Layer 0/1 Registers should have the heading as:
Layer 0/1 Registers ($F2000-$F200F / $F3000-$300f)
This way, you don't have to scroll back to the top to find out the offset for the layer registers.
This back-and-forth is much more tedious on busier sections such as the Sprite Data registers which are near the end of the document and there are 8 registers to read through.
The text was updated successfully, but these errors were encountered:
This document, overall, is great in its information density and organization. However, it's slightly cumbersome to use as a reference while coding due to the fact that the register layout map is only provided once at the top of the document.
Example:
The section explaining the Layer 0/1 Registers should have the heading as:
Layer 0/1 Registers ($F2000-$F200F / $F3000-$300f)
This way, you don't have to scroll back to the top to find out the offset for the layer registers.
This back-and-forth is much more tedious on busier sections such as the Sprite Data registers which are near the end of the document and there are 8 registers to read through.
The text was updated successfully, but these errors were encountered: