aboutsummaryrefslogtreecommitdiff
path: root/dists/riscos/!Run,feb
diff options
context:
space:
mode:
authorColin Snover2017-09-29 14:57:22 -0500
committerColin Snover2017-09-29 19:56:24 -0500
commit3cdf26b355d5d0c387858bd85e546d6fff549dd4 (patch)
tree0e88ca1a1a71f8fec9eea8472137e8c9c57aa5be /dists/riscos/!Run,feb
parenta99c6774ffd3b7686db63b3b66696bb290465e82 (diff)
downloadscummvm-rg350-3cdf26b355d5d0c387858bd85e546d6fff549dd4.tar.gz
scummvm-rg350-3cdf26b355d5d0c387858bd85e546d6fff549dd4.tar.bz2
scummvm-rg350-3cdf26b355d5d0c387858bd85e546d6fff549dd4.zip
SCI32: Fix bad text rendering in RAMA
In SCI3, Sierra removed the ability of the main renderer to automatically scale CelObjs with different source resolutions. Instead, in SCI3, all CelObjs are treated as having the same resolution as the screen (i.e. 640x480). In all SCI3 games other than RAMA, keeping the code paths for resolution-dependent scaling is not a problem because all the assets and game code are correctly designed to use the same 640x480 resolution throughout. RAMA, on the other hand, was written with the text subsystem set to a resolution of 630x450 (Phant1's screen resolution), and in SSCI, resolution-dependent scaling code was not removed from the *text* subsystem. As a result, RAMA's game scripts rely on the slightly larger scaled dimensions coming out of the text system when determining the size of screen items for rendering, and then also rely on the main renderer ignoring the 630x450 resolution baked into the bitmaps generated by the text subsystem when drawing them to the screen.
Diffstat (limited to 'dists/riscos/!Run,feb')
0 files changed, 0 insertions, 0 deletions