409
edits
Difference between revisions of "TsAGE/TODO"
Oops, I put the scene 4150 glitch in the wrong section.
Eriktorbjorn (talk | contribs) (Added scene 4150 oddity.) |
Eriktorbjorn (talk | contribs) (Oops, I put the scene 4150 glitch in the wrong section.) |
||
| Line 18: | Line 18: | ||
*Scene 2320: When Quinn picks the arms, there a priority glitch (to be verified) | *Scene 2320: When Quinn picks the arms, there a priority glitch (to be verified) | ||
*Scene 6100: At the end, texts are not skippable, it looks wrong (to be verified) | *Scene 6100: At the end, texts are not skippable, it looks wrong (to be verified) | ||
Known hardcoded logic bugs in CD version: | Known hardcoded logic bugs in CD version: | ||
*Scene 2320: If you try to activate the flycycle, it will appear but Quinn will say "Too bad you don't have time to take it out for a spin right now." and then the game becomes unresponsive. I'm guessing that there is a missing call to enableAction(), possibly in Action1::signal() or Action4::signal() since both those functions are being called a couple of times during the animation. | *Scene 2320: If you try to activate the flycycle, it will appear but Quinn will say "Too bad you don't have time to take it out for a spin right now." and then the game becomes unresponsive. I'm guessing that there is a missing call to enableAction(), possibly in Action1::signal() or Action4::signal() since both those functions are being called a couple of times during the animation. | ||
*Scene 2100: Examining the middle console triggers an assertion: "./engines/tsage/globals.h:84: bool tSage::Globals::getFlag(int) const: Assertion `(flagNum > 0) && (flagNum < 256)' failed." This is because Scene2100::Hotspot14::doAction() calls _globals->getFlag(0), which will of course always trigger the assertion. | *Scene 2100: Examining the middle console triggers an assertion: "./engines/tsage/globals.h:84: bool tSage::Globals::getFlag(int) const: Assertion `(flagNum > 0) && (flagNum < 256)' failed." This is because Scene2100::Hotspot14::doAction() calls _globals->getFlag(0), which will of course always trigger the assertion. | ||
*Scene 4150: Using the duck produces the message, "You don't need to use your stunner, the fire is sufficient for heating their meal." which seems a bit out of place. | |||
Game status: | Game status: | ||