DeeZire Online - View Single Post

Renegade · 03-09-2005, 08:28 AM

Hmm. I am assuming this happens with a mod installed.

There is a copy-protection part of RA2/YR that will blow all your stuff up after 30 to 40 seconds, it generally appears if your registry was touched; it is possible that this happens, but one of the death animations or attached warheads (or anything else connected to a unit's death) is fuxx0red, so instead of just exploding, you get an IE.

Another possibility would be that the timing is actually irrelevant, that it's a simple bug that leads to an IE when you build/do something specific, and the timeframe is just always the same because the AI does it after about 30 to 40 seconds.

Best thing would be to launch a network game and do nothing on both comps. If you still get an IE after 30 to 40 secs, reinstall the game. (On the other hand, if it happens on both comps, it may be possible that it's a problem with your mod, but that's unlikely.)

03-09-2005, 08:28 AM	#2 (permalink)
Renegade Senior Member Join Date: Jan 2003 Location: Hamburg, Germany Posts: 2,208	Hmm. I am assuming this happens with a mod installed. There is a copy-protection part of RA2/YR that will blow all your stuff up after 30 to 40 seconds, it generally appears if your registry was touched; it is possible that this happens, but one of the death animations or attached warheads (or anything else connected to a unit's death) is fuxx0red, so instead of just exploding, you get an IE. Another possibility would be that the timing is actually irrelevant, that it's a simple bug that leads to an IE when you build/do something specific, and the timeframe is just always the same because the AI does it after about 30 to 40 seconds. Best thing would be to launch a network game and do nothing on both comps. If you still get an IE after 30 to 40 secs, reinstall the game. (On the other hand, if it happens on both comps, it may be possible that it's a problem with your mod, but that's unlikely.)