Hughes, B. wrote:
> Happens on this other machine, too, except error popped up at frame 442 
> instead of 448.

Thanks for the report; this has been fixed. Still haven't seen the 'pure
virtual function call' one happen though.

-- Chris

Post a reply to this message