.Anyhow, I've been making a map for Royal mode in Storm. On the water base, if that's helpful at all. When I went to compute shadows, the game restarted the shadow computation before it was finished, and kept doing that. If I minimized the game I would see that my "graphics driver has stopped responding but has recovered" and if I extended the icons on the bar at the bottom right of the taskbar (windows vista, don't ask why) I would also see the icon for Data Execution Prevention, but I wouldn't be able to click on it.
I've tried updating my graphics driver (which was already up to date according to Device Manager and the nVidia website) and then rolling it back several versions, but to no avail. The card on this computer is an nVidia GeForce G102M.
The shadow computation problem only seems to happen on this specific map, I tried computing shadows on a stadium map, a canyon map, and another storm map (for all three of them I just opened the editor, put a few random blocks on the ground and clicked Compute Shadows) and they all worked fine.
So I'm guessing you might need the map to find the problem. It's here: http://www.mediafire.com/download/gf66x ... us.Map.Gbx.
I would appreciate if this got dealt with, I spent a lot of time on that map blocking out areas (something that's much more time-consuming in such an open game as Storm than in a "tunnel" game like Doom, Descent, or Half-Life 2), interconnecting areas, creating different ways to get to the pole and all that other multiplayer shooter design theory stuff which you know far better than me
. I don't really want to abandon it.
. Much appreciated.