Quote:
Originally posted by Bungleau:
Hmmmm.... haven't heard of that before...
My first guess would be system overload. Before you run W&W, go into task manager and stop all unneeded programs. Then go in to play the final scene.
Second is movement. Move as little as possible during the battle and following discussions. That's less visual imagery to display.
Third is drivers. I'm sure you know the drill -- get the most current ones, etc.
Fourth, on a lark, if you're on W2k or XP, consider doing the virtualdub thing on the final movie. I'm not sure where it is, but that might make a difference.
Other than that, I'm fresh out of ideas.
|
The first guess in Bungleau's excellent post would be my guess as well. I'm not sure about the fourth since the movie apparently starts to play. But it is worth a shot alhtough I have never had any problems viewing the final scenes on Win 2000. It could also be over heating if you played the game for several hours before reaching the end. But I do not believe W&W is a cpu-hogger.
Now I'm off to do an exciting experiment on W&W.
