From ScummVM :: Wiki
Revision as of 20:57, 20 January 2010 by Sev (talk | contribs) (→‎Known games that can be completed: -- turn into list)
Jump to navigation Jump to search

Engine Status

Known games that can be completed

  • Hero's Quest (10/24/2009)
  • King's Quest 5 (10/18/2009)
  • King's Quest 6 (10/2009)
  • Larry 1 (01/01/2010)
  • Larry 5 (10/19/2009)
  • Larry 6 (10/2009)
  • Laura Bow 1 Colonel's Bequest (12/28/2009)
  • Space Quest 1 VGA (10/21/2009)

Currently running tests

  • Quest for Glory 1 VGA - [md5], m_kiewitz
  • Quest for Glory 2 - syke


Missing features (SCI0-SCI1.1)

  • Palette morphing (kPalVary - used for example in the SQ5 intro) and kAssertPalette - assigned to m_kiewitz
  • GM instrument mapping
  • Channel remapping
  • Amiga support for SCI1
  • Mac support
  • Loading from the launcher

Missing minor stuff (SCI0-SCI1.1)

  • Scaling inside kAnimate - scaleSignal bit 1 triggers setting of scaleX/scaleY. I don't fully understand the code yet. ffs. animate.cpp


  • Show priority and control map in original interpreter (SCI1/SCI11)
    • search for A9 06 00 74 05 in original interpreter, replace with all 90h (NOP)


Known bugs

Castle of Dr. Brain

  • computer room - right side puzzle
    • After finishing, a sound is played that contains a digital channel, which has data + 4 != 0
  • computer trivia
    • Scrolling text doesnt work right (seems to be a VM issue)

Conquest of the Longbow

  • In chapter 1, room 110, when Robin meets Little John at the lookout, a signal is sent to a non-object when Little John stops walking. Ignoring this selector modification freezes the screen (VM issue, this room never worked properly even in FreeSCI)

Hero's Quest (Quest for Glory 1 EGA)

  • Graphics?!
    • on character customization screen the percentage bar isn't shown

Island of Dr. Brain

  • Graphics
    • intro has some weird view issues - is "caused" by palette merging, if one does straight mapping the views are correct
  • VM?!
    • right at the first puzzle clicking on the bricks on the bottom of the screen makes the engine freeze (endless loop)


  • Graphics
    • corruption on difficulty setting menu when challenging jones (ega/cd)
    • statistics are broken (list control), dollar amounts missing (ega/cd)
    • speech bubbles are drawn under the faces of people, instead of on top

King's Quest 5

  • Graphic
    • At least in the desert when getting the staff grahams head is where his feet should be and his body is completely gone. Fixes itself as soon as he walks

King's Quest 6

  • Graphics
    • Flickering right in the first room when discovering the chest - caused by 2 lists that are being used on kAnimate. One rect overlaps with the ring animation, that's why it flickers.
  • Missing sync resource
    • Right at the beginning, go to bookshop and get the book thats on the table. 2nd portrait has no sync resource but audio. We are currently ignoring that, so no animation at all, and the original low res version drew random portraits, which we could do as well. Still the following video illustrates that there is correct mouth movement in the hires version (2:30). One speculation is that the hires portrait code calculated lip syncing from the sound resources, when sync resources were missing

Larry 1 (Remake)

  • Reason unknown
    • bartender animation when ordering a whiskey and the rat animation in the room with the drunken man are much too fast
  • Graphics (newgui only)
    • doors at the casino wont open. A workaround is in place till the actual issue is found. Issue seems to be caused by signal of the door set too late or kAnimate being call too few times. If you move the .doit calling code to the end of kAnimate door will open.
  • Remarks
    • Priority issues in bathroom right at the start are also in original interpreter and not caused by us

Larry 5

  • VM
    • one screen nearly at the end with text disappears far too quick
  • Graphics
    • tramps casino: when woman asks about random number, cursor of textedit control is not correctly positioned (i am not able to replicate the issue though there are still problems with textedit control that will get fixed)
    • Window placement is not 100% like sierra sci. it seems this only happens on windows with shadows. In sierra sci shadows are shown so actually the window is moved one up. Under our engine the shadow is not there, because the window is outside screen
  • Remarks
    • during first flight Larry dreams about Patti: she is playing the piano. Strangely this isnt animated, but it is if you save/reload your game. Seems to be a script issue, because original sci does the same thing
    • tramps casino: during mud wrestling the script is using cycle counts. Currently its playable but a bit difficult to do cause its quite fast (not a bug but ffs when changing speed throttler)
    • almost at the end during last flight, one textbox in the patti conversation gets overdrawn with patti. Happens only in german version and I guess this also happens with original interpreter. I am unable to test this easily because I would need to play through the whole game again

Space Quest 1 (Remake, VGA)

  • Graphics
    • Ulence Flats - when entering the ship, another ship appears. We see this ship shortly completely and then it starts appearing, probably related to kAssertPalette()
    • Some effects missing, definitely non-implemented kAssertPalette()/kPalVary (example: when destroying lasers on kerona)

Bugs from freesci, probably some of them are already solved

Quest for Glory

  • The FileSelector (SCI) class used in the import screens in QfG2 and QfG3 has a 'text' pointer, and 'cursor' and 'lsTop'/'topString' pointers that should point to inside 'text'. However, in FileSelector::readFiles, 'text' is freed and reallocated, causing the other pointers to sometimes become invalid.


  • The sound of the bow in the opening screen is repeated a number of times
  • After leaving the cave and the conversation that follows, a list is not sane anymore (perhaps it's related to pathfinding? There's a relevant warning just before this occurs)

Bugs observed from FreeSCI

check here

Codename: Iceman

  • displays the warning "NodeValue() on a NULL pointer attempted" at numerous points during the map table scene

Quest for Glory 1

  • displays the warning "List node at x is not sane anymore" when the dinosaur snaps at you during the intro

Space Quest 3

  • calls functions from a script which has already been unloaded when Roger climbs up the ladder from the rat cave (the place containing the reactor at the very beginning of the game) - NOTE: This should be fixed in ScummVM, to the best of my knowledge


  • calls CanBeHere() with a disposed object in the clip list when Keith enters the car


  • tries to allocate zero bytes of memory when entering Molto Lira.


  • accesses property 0xf02 in a couple of cases


  • calls UnLoad() with only one argument when exiting the Ulence Flats bar


  • will set the speed to maximum if you access the control panel without tweaking the speed slider. Either tweak the speed slider, or use function keys to access the control panel functionality

Timer issues

Larry 3

  • Working fine currently due workaround inside speed throttler for room 290
  • Pushups (room 380) are machinespeed dependant. That one is calculated after the ranchy questions (room 290). Machinespeed is calculated by counting cycles for 60 ticks (1 second).

Larry 5

  • None of those are apparent in our sci
  • intro is timer dependant (typing of the title while patty walks by) - note that the "mistyping" should be noticeable
  • wrestling is timer dependant (room 740)

Note: This list has been taken from and can also be found at the Space Quest wiki

Space Quest 1

  • None of those were apparent during my playthrough, so the speed throttler seems to work well
  • In the Arcada, you'll notice the screen is shaking and shaking. And it should (every once in a while). Your ship is under attack, remember?!? But on faster computers, it just won't stop. And that's incredibly annoying.
  • You will dehydrate in the desert way too soon. A message will pop up almost immediately when you've landed, telling you you need to drink. You'll die of thirst before you can even think of exploring the planet.
  • The spider droid will come too soon. Thus giving you little chance to explore the planet.
  • You will be unable to get past the falling acid drops in the cave on Kerona because the drops fall very rapidly. A tropical rainstorm is nothing compared to it!
  • Some animations in the game are too fast. The droid that passes Roger in the hallway at the start of the game rushes by at the speed of light. Roger looks like he's headbanging or something. But in fact, on slower computers he looks around every now and then. Also, the cartridge retrieval droid moves way too fast. There are perhaps more of these small, but annoying, animation problems.

Space Quest 4

  • When Roger enters a screen where the "droid-0-death" can/will appear, it will come almost immediately. It will be very hard to get the rope, the unstable ordinance, the PocketPal and to hide yourself from this droid, not to mention successfully entering the sewer grate. The biggest problem is, of course, that the game doesn't give you any time to explore and look around carefully because you're too occupied escaping the droid. The droid should not appear for at least a full minute.
  • Boarding the transport shuttle on the streets of Xenon is almost impossible. The Sequel Police are already standing there, waiting to kill you. When playing the game on a slower computer, the Sequel Police will only appear after some seconds, giving you enough time to examine the shuttle and to enter the landing gear compartment.
  • The same goes for entering one of the time pods on the Sequel Police dispatch. They will kill you almost immediately after they finished talking. You won't have time to do anything, how frustrating! Normally, you have at least some seconds to move. If you move downwards towards the time pods, the game will give you even more time to solve the puzzle. With a faster machine, you virtually don't have any time at all.
  • On Estros, the timepod of the Sequel Policemen will almost come immediately after you've landed. You will never have the time to "trigger" the pterodactyl to pick you up. And, you just don't have time to walk around and explore the planet... You'll think you are stuck (that is, if you have the time to think that at all, you might be dead already), and will run to the nearest walk through paradise. While in fact, it's a timer related problem.
  • And of course the Skate-O-Rama scene. The Sequel Policemen won't give you any time to make your move.
  • Near the end of the game you're supposed to use the Super Computer to "flush" the droid and the brain icon. When you've flushed the brain icon, the countdown will begin and you're supposed to make your way to Vohaul's room. On today's computers, the countdown will happen so fast that you won't have the chance to leave the room and go back out to the maze.
  • Some animations go too fast, scrolling screens don't look like they are scrolling (because of the speed), the pterodactyl that moves even faster and so on.

Space Quest 5

  • As far as I know, the only timer problem in Space Quest 5 is the EVA scene were you need to rescue Cliffy with the pod. The controls are very hard to handle because the ship moves too fast. Normally, this puzzle is already very hard. Not only is it already fast, but you have little fuel. This puzzle requires some mouse skills, so don't whine if it doesn't work right from the start.
  • I've spotted some small animation problems, most notably the GradeMaster 2000 sequence. Maybe some scrolling screens effects are eliminated by timer problems, but so far I haven't found any.