ReC98

Commit Graph

Author	SHA1	Message	Date
nmlgc	75a779e82a	[Maintenance] Clean up PI function declarations and comments	2019-12-17 23:27:01 +01:00
nmlgc	6d8ff6b72e	Make previously reduced ZUN functions available to C	2015-02-21 14:12:22 +01:00
nmlgc	a07e5fad42	[Reverse-engineering] Slot-based PI display Also covering the two variations for blitting only every second row or blitting only a 320x200 quarter, as seen in the endings. So yeah, there's indeed nothing wrong with piread.cpp. TH03 just uses that separate function that only blits every second row of an image, and indeed always loads the entire image as it would appear in a PNG conversion. Here's what happens if you display these images using the non-interlacing function: https://www.dropbox.com/s/885krj09d9l0890/th03%20PI%20no%20interlace.png	2014-12-18 14:36:43 +01:00

Author

SHA1

Message

Date

nmlgc

75a779e82a

[Maintenance] Clean up PI function declarations and comments

2019-12-17 23:27:01 +01:00

nmlgc

6d8ff6b72e

Make previously reduced ZUN functions available to C

2015-02-21 14:12:22 +01:00

nmlgc

a07e5fad42

[Reverse-engineering] Slot-based PI display

Also covering the two variations for blitting only every second row or
blitting only a 320x200 quarter, as seen in the endings.

So yeah, there's indeed nothing wrong with piread.cpp. TH03 just uses that
separate function that only blits every second row of an image, and indeed
always loads the entire image as it would appear in a PNG conversion. Here's
what happens if you display these images using the non-interlacing function:
https://www.dropbox.com/s/885krj09d9l0890/th03%20PI%20no%20interlace.png

2014-12-18 14:36:43 +01:00

3 Commits