I'm not so quick to assume it's something you've done wrong, just keeping my mind open to every conceivable possibility. It's entirely conceivable I made a mistake somewhere, especially if the camera is moving independently every single time it crashes (it could be an unlikely coincidence, or it could mean the crash is related to the campaign_script). But I really don't have enough information to start narrowing down the possibilities. As holmes says, i can't make bricks without clay. Need data =)
And you know, sometimes the engine itself is responsible for unpredictable results. I've discovered several quirks and hardcoded limitations during the course of this project that not many people still around seemed to know about. This could theoretically be something new and unforeseen.
The console command isn't advice per se. It is not intended as a direct solution to your problem. It's intended to give you access to information you wouldnt otherwise have access to, so that you can pass this information to me, so that I can start narrowing down the possible sources of the crash =)
The result of the command is that it lifts the fog of war for the human player. Youll be able to see the entire map and all the armies and agents upon it. Omniscience, basically.
And yes you can turn it off again just as easily by inputting the command again. If I wasn't entirely clear, you access the command console screen when the game is running.
As I said, it might not be the problem, but knowing exactly where the camera is moving seems to be the most reasonable place to begin.
The spies around dol goldur wouldnt be related to the entwives script. They are found in a random province in the very far east or very far south of the map. Sorry for the spoiler =)