Sprite Pattern Upload: Difference between revisions

From SpecNext Wiki
Jump to: navigation, search
No edit summary
Core 2.00.22 changes.
Line 7: Line 7:
|Subsystem=Sprites
|Subsystem=Sprites
}}
}}
Used to upload sprite patterns. Sprite patterns are 16x16 (256 bytes) and are sent in English reading order. Each byte is the offset, 0-255, within the active sprite palette. After sending 256 bytes, the target sprite is auto-incremented. This auto-increment is independent of other sprite registers.
Used to upload sprite patterns. Sprite patterns are 16x16 (256 bytes for 8 bit colour and 128 bytes for 4 bit colour sprites) and are sent in English reading order. Each byte is the offset, 0-255 or 0-15, within the active sprite palette. After sending 256 bytes, the target pattern slot is auto-incremented. This auto-increment is independent of other sprite registers.
 
With 4 bit sprites each pattern slot contains effectively two patterns, each 128 bytes long, the sub-pattern displayed is selected by 7th bit "N6" in 5th sprite-attribute byte.

Revision as of 02:06, 20 December 2018

Number PortNumber::$xx5B
Decimal NumberDec::
Short desc. ShortDesc::Used to upload the pattern of the selected sprite.
Bit Mask PortMask::%---- ---- 0101 1011 ??
Readable Readable::No
Writable Writable::Yes
Subsystem Subsystem::Sprites

Used to upload sprite patterns. Sprite patterns are 16x16 (256 bytes for 8 bit colour and 128 bytes for 4 bit colour sprites) and are sent in English reading order. Each byte is the offset, 0-255 or 0-15, within the active sprite palette. After sending 256 bytes, the target pattern slot is auto-incremented. This auto-increment is independent of other sprite registers.

With 4 bit sprites each pattern slot contains effectively two patterns, each 128 bytes long, the sub-pattern displayed is selected by 7th bit "N6" in 5th sprite-attribute byte.