Hi, the title may seem a bit weird, but it's the shortest way of describing what happened yesterday, three times.
What happened is the following. I had been playing a couple of hours in my 1.06 GC as Austria, after I had fixed my sound problems (see other thread). Suddenly, to my amazement, I see the regular Windows hourglass appear at the tip of the EU2 mouse cursor. It even moves when I move the mouse. This I had never seen before.
After 4 or 5 seconds, the screen goes black, and I get thrown back to the desktop. My first reaction was, 'hey a new type of CtD'.
So I double clicked the EU2 icon on the desktop to restart. CtD's, after all, are (alas) a fact of life in EU2
So far, nothing out of the ordinary. EU2 restarts without problem, and I load the autosave, as I had done so many times before (sigh).
Now, for the weird thing. Two game years had passed after the restart, and I wanted to check my BB value. So paused the game, Ctrl-ESCaped to the desktop, to open up the autosave to check the value. This is when I noticed the weird thing. EU2 appeared TWICE in the task bar. Being curious by nature, I clicked on the first one. It brought me back in the game I thought had crashed. It was still running, although the time had not progressed. The time started progressing, though, as I had reactivated it.
I surrendered this one, got back to the desktop with the resolution messed up (happens a lot on my system. According to the guys over at bug reporting, I must be almost the only one in the world to have that happen
). Well, I clicked on the second (and now only) EU2 on the taskbar, and this copy was unaffected by all this, and still running.
Well, I didn't trust it completely, so I saved and surrendered this one as well (this time with a correct reset of the desktop, go figure), and restarted. This was funny as well, as I could restart EU2 without a reboot. Normally, when the resolution is messed up after a surrender, EU2 (or any other DirectX game for that matter) cannot (re)start without a reboot, as DirectX hasn't been properly closed down. Appearantly, the second correct surrender has corrected the DirectX mess the first surrender would have created.
The mysterious appearance of the hourglas, followed by a TtD (throw to desktop, by lack of a better description) happened another two times yesterday, but now I was ready for it. Instead of restarting the game, I simply clicked on the taskbar button, and I got back in the game.
The best explanation I can come up with, is that for some as yet unexplained reason the screen saver has kicked in. I think that, because in all three cases I had been playing (or pausing) continuously for roughly the amount of time that is considered as idle by the screen saver, without switching back and forth to the desktop. Needless to say, upto now this has never happened, but then again, upto a few days ago I was playing with 1.05, not 1.06.
The one think I find mystifying in all this, is the fact that I was able to start EU2 twice at all. This is normally not possible with DirectX programs. As soon as one has initialized DirectX, a second game (or second copy) refuses to run, being unable to gain access to DirectX resources.
Jan Peter
What happened is the following. I had been playing a couple of hours in my 1.06 GC as Austria, after I had fixed my sound problems (see other thread). Suddenly, to my amazement, I see the regular Windows hourglass appear at the tip of the EU2 mouse cursor. It even moves when I move the mouse. This I had never seen before.
After 4 or 5 seconds, the screen goes black, and I get thrown back to the desktop. My first reaction was, 'hey a new type of CtD'.
So I double clicked the EU2 icon on the desktop to restart. CtD's, after all, are (alas) a fact of life in EU2
So far, nothing out of the ordinary. EU2 restarts without problem, and I load the autosave, as I had done so many times before (sigh).
Now, for the weird thing. Two game years had passed after the restart, and I wanted to check my BB value. So paused the game, Ctrl-ESCaped to the desktop, to open up the autosave to check the value. This is when I noticed the weird thing. EU2 appeared TWICE in the task bar. Being curious by nature, I clicked on the first one. It brought me back in the game I thought had crashed. It was still running, although the time had not progressed. The time started progressing, though, as I had reactivated it.
I surrendered this one, got back to the desktop with the resolution messed up (happens a lot on my system. According to the guys over at bug reporting, I must be almost the only one in the world to have that happen
Well, I didn't trust it completely, so I saved and surrendered this one as well (this time with a correct reset of the desktop, go figure), and restarted. This was funny as well, as I could restart EU2 without a reboot. Normally, when the resolution is messed up after a surrender, EU2 (or any other DirectX game for that matter) cannot (re)start without a reboot, as DirectX hasn't been properly closed down. Appearantly, the second correct surrender has corrected the DirectX mess the first surrender would have created.
The mysterious appearance of the hourglas, followed by a TtD (throw to desktop, by lack of a better description) happened another two times yesterday, but now I was ready for it. Instead of restarting the game, I simply clicked on the taskbar button, and I got back in the game.
The best explanation I can come up with, is that for some as yet unexplained reason the screen saver has kicked in. I think that, because in all three cases I had been playing (or pausing) continuously for roughly the amount of time that is considered as idle by the screen saver, without switching back and forth to the desktop. Needless to say, upto now this has never happened, but then again, upto a few days ago I was playing with 1.05, not 1.06.
The one think I find mystifying in all this, is the fact that I was able to start EU2 twice at all. This is normally not possible with DirectX programs. As soon as one has initialized DirectX, a second game (or second copy) refuses to run, being unable to gain access to DirectX resources.
Jan Peter
Last edited: