Change Details

I've yet to see people complain about this and I can't identify the reproducible-ness because it seems to be random, although it does happen about 95% of the time Basically, starting a multiplayer game the normal way (open the lobby, wait for everyone to join and pick their slots, start the game) results in everyone, even the host, crashing the desktop. Launching the mission with just the host having picked a slot, and having everyone else join in progress, works fine. The only time I have not has this problem was a mission where the only units on the map were rangemasters and empty offroads. Perhaps it is tied to coop?

I've yet to see people complain about this and I can't identify the reproducible-ness because it seems to be random, although it does happen about 95% of the time Basically, starting a multiplayer game the normal way (open the lobby, wait for everyone to join and pick their slots, start the game) results in everyone, even the host, crashing the desktop. Launching the mission with just the host having picked a slot, and having everyone else join in progress, works fine. The only time I have not has this problem was a mission where the only units on the map were rangemasters and empty offroads. Perhaps it is tied to coop?

I've yet to see people complain about this and I can't identify the reproducible-ness because it seems to be random, although it does happen about 95% of the time Basically, starting a multiplayer game the normal way (open the lobby, wait for everyone to join and pick their slots, start the game) results in everyone, even the host, crashing the desktop. Launching the mission with just the host having picked a slot, and having everyone else join in progress, works fine. The only time I have not has this problem was a mission where the only units on the map were rangemasters and empty offroads. Perhaps it is tied to coop?