Difference between revisions of "TsAGE/TODO"

Jump to navigation Jump to search
249 bytes added ,  21:03, 24 May 2011
Updated scene 2100 bug.
(Added "***I have no response.!" issue in scene 2100.)
(Updated scene 2100 bug.)
Line 24: Line 24:
*Scene 4100: If you enter from scene 4150 (the sleeping chamber/kitchen), and Rock is already passed out from the ale, the mouse cursor will stay invisible until you click the mouse.
*Scene 4100: If you enter from scene 4150 (the sleeping chamber/kitchen), and Rock is already passed out from the ale, the mouse cursor will stay invisible until you click the mouse.
*Scene 4025: Trying to save while looking at the "Tech" triggers an assertion: "engines/tsage/saveload.cpp:76: void tSage::Serializer::syncPointer(tSage::SavedObject**, Common::Serializer::Version, Common::Serializer::Version): Assertion `idx > 0' failed."
*Scene 4025: Trying to save while looking at the "Tech" triggers an assertion: "engines/tsage/saveload.cpp:76: void tSage::Serializer::syncPointer(tSage::SavedObject**, Common::Serializer::Version, Common::Serializer::Version): Assertion `idx > 0' failed."
*Scene 2100: Talking to or looking at Miranda right after Seeker has been lost in the cave causes an "***I have no response.!" error. I guess that means that _globals->getFlag(59) didn't return 0 ("getflag 59" in the debugger prints 1), but what does that mean...? Forcing the flag to be 0 prints appropriate messages for the situation, but is it the condition or the value of the flag that is wrong?
*Scene 2100: Talking to or looking at Miranda right after Seeker has been lost in the cave causes an "***I have no response.!" error. I guess that means that _globals->getFlag(59) didn't return 0 ("getflag 59" in the debugger prints 1). Forcing the flag to be 0 prints appropriate messages for the situation, but is it the condition or the value of the flag that is wrong? (The flag is set when the transmission ends and you leave scene 3700, and since that's when you find out that Seeker is lost, I'm guesing it's the test that's wrong. The flag is tested in a few others places, but those aren't necessarily wrong just because of that of course.)


Game status:
Game status:
409

edits

Navigation menu