Curious_Labs opened this issue on Apr 29, 2003 ยท 55 posts
Dale B posted Wed, 30 April 2003 at 9:07 AM
Y'know.... It might be wiser to actually -see- what SR-3 does before chewing the walls again. Until we have it and have it installed, we don't know =WHAT= may be fixed. Those resolved 'playback' issues for the hair room could very well -be- the collision problem. Half of that list could very well have been the source of one or more memory leaks, and now they are fixed, no more leak. Some of those 'little' problems working in concert could have been the cause of what appeared to be a major FUBAR (HOW many issues that were attributed to 'rotten, incompetent coding' went away when the InterLok protection was decoupled? Remember?). And the last code monkey I knew who professed to being able to 'fix a problem' with a few lines gave up at around 700 lines and embarassed himself horribly. It wasn't his source, he'd never met the original coder, and got bitten by the different work style and code structure. Thank you for the info, Katherine. It is -very- much appreciated. ;)