Hi,
On Mon, 24 Dec 2001, Matt wrote: > I have updated the screenshots on my website from the SSCI debugger. I > have noticed a pattern: the horizontal coordinates (x, brLeft, brRight, > etc) for both haines and shopwoman seem to be offset by -50 or so. How so? At the very least, brRect and nsRect are consistant (relative to the coordinates) between SSCI and FSCI. It seems that you simply inspected/dumped the view objects when they were at a different position, which would explain the difference. > > That would indicate that she has collided with something. Could you test > > this with +b so that we know what she hit, please? > > > > (Check for 'finished mover by collision'; the cause can usually be derived > > from the text printed before that.) > > That message never happens, Sorry, it's "finished mover xxxx by collision", where xxxx is the heap address of the mover object (It's in the trace on your web site, so I guess you knew what I meant...) The shopwoman collides with haines; the reason for this is that the area checked for haines is much higher than his brRect. The only reason I'm aware of that could cause this would be that haines bears the mark of the stopUpdate()d, which is stored in the dynview list (please run 'gfx_print_dynviews' on the debug console). If this is the case, we have to start looking for a difference between him and the motivator unit- the easiest difference would, of course, be that he moves, which we can check for relatively easily, but there might be some other, unusual constellation of haines::signal flags. I think we can safely patch around this by checking for movement ATM, until a list of values of 'haines::signal' in correct temporal order can be assembled more easliy. > Hmm.. perhaps doing a CVS binary search between the time it was beaten and > now would be a good idea.. That's what I thought, too, but it looks like we'll just stumble upon the point where dynview collisions were (mostly) fixed, once again. > > Only the sound server remains to be fixed now. > > I'm working on this (from win32 side). I'll let the list know if/when I > get somewhere. Don't know if this will have any affect on the problems I'm seeing (LSL3 stopping on a black screen after finishing the test), but Alex made a good suggestion on how to handle this in order to still get out a release real soon (due to restrictions on my end, I will have no time to work on FreeSCI in January or February at all, so either it'll happen soon or not for the next few months). Good night and Merry Christmas, llap, Christoph
