Hi,
On Sun, 2 Dec 2001, Matt wrote: > ego appears to be colliding with Wilbur and stops. The MoveTo for ego then > never finishes, putting the game into the state where you can't move/type, > but menus work. IIRC the mover _does_ stop by collision with Wilbur, but this appears to happen too early (before the relevant control map zone is touched). > Sierra SCI appears to let ego move one more pixel right, allowing the > MoveTo to finish. (I think.) Its mover finishes three pixels to the right, which is probably one more step. > Is this an OB1 error in collision checking in general, or an interpreter > difference or..? An OB1 bug causing this collision is unlikely, given that ego is at least two pixels into wilbur's brRect horizontally and vertically. It might have been an indirect cause, though. Could you try to inspect Wilbur once again after he has entered the house, please? We'll need the brRect and his signals. (Wilbur is in script.010, which appears not to be unloaded here.) His FreeSCI brRect is the area covered by [167..188]x[118..120]. Signals are 2. He is still on the dynview list (cast::elements; you can traverse the list with the bracket keys in Sierra SCI). > On a side note, I've entered the lsRect values not being setin that scene > as bug #278. That effect is unlikely to be limited to this scene. llap, Christoph
