aboutsummaryrefslogtreecommitdiff
path: root/engines
AgeCommit message (Collapse)Author
2017-10-03TITANIC: DE: Fix horizontal placement of PET mode buttonsPaul Gilbert
2017-10-03SCI32: Fix audio dumper decompressed size calculation for 16-bit audioColin Snover
2017-10-03SCI32: Restore gameplay time in RAMAColin Snover
This will cause non-linear time shifts in the system timer that the game's custom save logic may not expect, but in initial testing the game doesn't seem to care about this. Fixes Trac#10259.
2017-10-03TITANIC: DE: Fix dimensions of text area in PET Translation tabPaul Gilbert
2017-10-02SCI32: Always sort kernel-generated screen items above script-generated ↵Colin Snover
screen items in last-ditch sort Fixes Trac#10257. Fixes Trac#10261.
2017-10-02TITANIC: DE: Allow for two lines in PET Rooms tab tooltipsPaul Gilbert
2017-10-02TITANIC: DE: Translation for .avi files directly referred toPaul Gilbert
2017-10-02TITANIC: DE: Fix perched parrot animationsPaul Gilbert
2017-10-02TITANIC: Work around loading savegame when Marcinta is activePaul Gilbert
Loading a savegame directly from the launcher or Continue dialog when Marcinta is active shows her as inactive in the original, but still allows you to talk to her. To fix the inconsistency, now when this occurs, it will also reset the active NPC back to none.
2017-10-02TITANIC: DE: Correctly play back entire 1st class upgrade speechPaul Gilbert
2017-10-02TITANIC: DE: Fix upgrading to 1st classPaul Gilbert
2017-10-01SCI32: Fix missing transparency in RAMA title screenColin Snover
2017-09-30COMMON: Introduce a shared hash function for pointer typesBastien Bouclet
2017-09-30BUILD: Define pointer sized integer types and remove SCUMM_64BITSBastien Bouclet
2017-09-30SCI32: Add detection for SQ6 demo (from Sneak Peeks 2 CD)Martin Kiewitz
2017-09-30SCI32: Fix crash when dying in RAMAColin Snover
As it turns out, autorama.sg *is* actually used sometimes. Fixes Trac#10253.
2017-09-30SCI32: Stop trying to clean up uninitialized VMDsColin Snover
Fixes Trac#10252.
2017-09-30SCI: Fix printing of super calls on clones in debuggerColin Snover
2017-09-30SCI32: Fix support for RAMA demoColin Snover
Fixes Trac#10251.
2017-09-29SCI32: Fix extremely broken patch for RAMA RESOURCE.SFXColin Snover
Obviously, games other than RAMA need to have sound effects volumes.
2017-09-29SCI32: Improve RESOURCE.SFX fallback for RAMAColin Snover
Since Datafiles says to rename any RESOURCE.SFX to RESSFX.00n, and there is only a RESOURCE.SFX on CD 1, don't confuse users by failing to use RESSFX.001 for CD2 and CD3.
2017-09-29TITANIC: Fix leaks in CGameState _movieListPaul Gilbert
2017-09-29SCI32: Promote Lighthouse and RAMA to ADGF_TESTINGColin Snover
2017-09-29SCI32: Clean up unused kBitmap code/subopsColin Snover
2017-09-29SCI32: Fix bad text rendering in RAMAColin Snover
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.
2017-09-28SCI: Add script patch for QfG2 Jackalmen Oops - bug #10218Martin Kiewitz
Was a game bug, finally fixed. This was a combined effort of wjp and myself. Thanks to wjp. We both don't own QfG2 1.000 atm, so we could not try it for that version.
2017-09-28SCI32: Disable change directory button in original save/load in RAMAColin Snover
2017-09-28SCI32: Allow save games to be deleted from original save/restore in RAMAColin Snover
2017-09-28SCI32: Block RAMA from creating PREF.DAT fileColin Snover
This file normally stores brightness, music volume, and most recently used save game directory. Since we store the music volume ourselves and don't use the save game directory, the only potentially useful information is the brightness level, and that is fine to just restore from the save games.
2017-09-28SCI: Remove resolved TODOColin Snover
2017-09-28SCI32: Add audio volume sync support for RAMAColin Snover
2017-09-27SCI: Add SQ3 1.0P 720K to detection tableColin Snover
Fixes Trac#10245.
2017-09-27SCI: Remove old SCI32 view scaling code from SCI16 graphics codeColin Snover
2017-09-27SCI: Add support for keyup eventsColin Snover
Basic keyup event support appears to have been added in the SCI1.1 IBM keyboard driver, and more robust support was provided in SCI32 which actually gets used by at least Lighthouse. This patch adds support for keyup events in SCI1.1+. Fixes Trac#10242.
2017-09-27SCI: Fix use-after-free when kernel call debugging is active during a save ↵Colin Snover
game restore
2017-09-27SCI: Do some clean-up of event handling systemColin Snover
Convert macros and vars to enums, rename keyboard events in preparation for adding key up events, clean up unnecessary nested conditionals, add TODOs for potential future work.
2017-09-27SCI: Add uninitialized read workaround for shoplifting in SQ4CDDavid Fioramonti
When in Galaxy Galleria, going into the software store and trying to shoplift the SQ4 Hintbook will crash the game after you leave and are electrocuted. Fixes Trac#10229. Closes gh-1031.
2017-09-27SCI32: Implement SCI3-variant volume handlingColin Snover
Trying to find differences in Lighthouse's audio sample playback, I discovered that SCI3 had its own variant of handling volumes and sending this volume information back to game scripts. It is not known if this fixes any sound bug.
2017-09-27TITANIC: DE: Changes for DoorbotScript::chooseResponsePaul Gilbert
2017-09-27TITANIC: Fix leak of wave file audio streamsPaul Gilbert
2017-09-27SCI32: Fix backwards palette checkColin Snover
2017-09-27TITANIC: Fix memory leak in CStarViewPaul Gilbert
2017-09-26TITANIC: DE: Fix switch in DeskbotScript::doSentenceEntryPaul Gilbert
2017-09-26TITANIC: Convert some remaining strings to use their titanic.dat entriesPaul Gilbert
2017-09-26TITANIC: Fix exit crash freeing wave files whilst still playingPaul Gilbert
2017-09-26TITANIC: Add missing CSound destructorPaul Gilbert
2017-09-25TITANIC: Fix loop limit in TTsentenceConcept destructorPaul Gilbert
2017-09-25TITANIC: Add missing destructor for TTsentenceConceptPaul Gilbert
2017-09-25TITANIC: Free wave files on game exit like original doesPaul Gilbert
2017-09-24SCI32: Dummy kPlayVMDSetFrameRateColin Snover
This subop is used only by RAMA. The VMD objects in RAMA's game code contain a frame rate field, which is usually -1, but occasionally is not. In the cases where it is not -1, it appears to be either set for a video with sound (so the value doesn't do anything to that video), or it is just resetting back to the baked-in frame rate of the video file (so it doesn't need to exist, except to fix videos broken by earlier played videos with explicit frame rates). Since this is a global state flag that does not get reset in SSCI, the ultimate effect of kPlayVMDSetFrameRate in RAMA is that it does nothing to any of the videos where the explicit frame rate is set, but it does inadvertently cause *other* videos with no sound and no explicit frame rate to have a different frame rate depending upon what was played earlier in the game (and whether or not the engine was restarted in the meantime). This bad transferring of frame rates is most noticeable with the exit-video of the vidmail player, which is played when you back out after selecting a vidmail. Its nominal framerate is 10fps, but it will play at whatever frame rate was last set by some other video that happened to have an explicit frame rate, even if that frame rate was bogus. So, just ignore all calls to this subop, as it is fatally buggy.