diff options
author | Colin Snover | 2017-05-06 00:23:46 -0500 |
---|---|---|
committer | Colin Snover | 2017-05-06 10:38:58 -0500 |
commit | 8a590e600f06a1a7635b399f649a1b7d7d3d6e54 (patch) | |
tree | deabe0448f20a67c71416f5335abc5132907b969 /backends/platform/ios7/ios7_main.mm | |
parent | 8b49313af30a283b7b9517b69c10a148e099cf01 (diff) | |
download | scummvm-rg350-8a590e600f06a1a7635b399f649a1b7d7d3d6e54.tar.gz scummvm-rg350-8a590e600f06a1a7635b399f649a1b7d7d3d6e54.tar.bz2 scummvm-rg350-8a590e600f06a1a7635b399f649a1b7d7d3d6e54.zip |
SCI32: Disable VMD kPlayFlagBlackPalette flag
Videos in GK2 use this flag (e.g. the chapter 6 intro).
Now that GfxPalette32::updateHardware no longer calls
OSystem::updateScreen (only GfxFrameout::frameOut does this now),
every time a palette swap occurs during playback, there is a frame
of blackness that should not exist. This is because the order of
operation is:
1. Send black palette
2. Call frameOut (which updates the screen)
3. Send new, correct palette
4. No frameOut (so the screen is not updated with the correct
palette)
OSystem::updateScreen cannot be called multiple times for the same
frame due to vsync, but also, there does not appear to be any
reason to send a black palette, since it seems to be intended to
avoid temporarily rendering video frames with the wrong palette on
a hardware device that cannot guarantee simultaneous application
of a new palette and new pixel data. ScummVM does not have such
a problem, so this feature appears to be unnecessary for us.
For the moment, this 'feature' remains hidden behind an ifdef,
instead of being removed entirely, to avoid potential confusion
when comparing VMD code from SSCI.
Diffstat (limited to 'backends/platform/ios7/ios7_main.mm')
0 files changed, 0 insertions, 0 deletions