Werewolf13
02-25-06, 06:24 PM
I've designed a rather simple mission that causes my system to reboot.
I design missions in steps. Add one unit at a time and appropriate triggers, test, add more, test add more until the mission is completely built then test some more. This mission is about a third of the way thru the process. It currently contains the essential units less some Japanese naval forces.
It is designed to be either single or multiplayer. The task for the US player is to transit the Tsugaru-kaikyo strait in Northern Japan and for the chinese player to sink the US sub.
The controllable units are a Seawolf and a Chinese Kilo. Both units have waypoints set with tactics so that the mission should work in Single Player too. There are goals set for each to kill the other. The one caveat is that the US sub will not get any points for sinking the kilo unless the kilo attacks the US sub. This is accomplished thru the doctrine language in the kill Kilo goal where the goal trigger only fires if the kilo attacks the US.
In every instance where the human is controlling the Kilo when the kilo attacks the Seawolf eventually the game causes my PC to reboot.
Since no other scenario reboots now that I set dw's affinity to just a single CPU there must be something weird about the scenario.
I'd like for others to run this thing a few times and see if it reboots your PC's. Or maybe you just see something in the design that you know screws up DW. If you're interested in helping out PM me and I'll send you a zipped up version of the mission.
As an aside this isn't the only weirdness in DW scenario design I've seen.
In another scenario I've since given up on a Japanese P-3 would launch from the Jap airbase in the scenario and attack a Japanese DD. Every single time. P-3's would keep launching until the DD went down. I kept an example replay of the incident after watching the replays with truth on about 10 times running the mission. I even contacted Sonalysts and offered to send them the scenario and the replay file (which I still have if anyone is interested) but they completely blew me off.
DW's scenario designer isn't right - and I've been designing scenarios with it's equivalent on 688i, Fleet Command and Sub Command without problems for a pretty long time now.
I design missions in steps. Add one unit at a time and appropriate triggers, test, add more, test add more until the mission is completely built then test some more. This mission is about a third of the way thru the process. It currently contains the essential units less some Japanese naval forces.
It is designed to be either single or multiplayer. The task for the US player is to transit the Tsugaru-kaikyo strait in Northern Japan and for the chinese player to sink the US sub.
The controllable units are a Seawolf and a Chinese Kilo. Both units have waypoints set with tactics so that the mission should work in Single Player too. There are goals set for each to kill the other. The one caveat is that the US sub will not get any points for sinking the kilo unless the kilo attacks the US sub. This is accomplished thru the doctrine language in the kill Kilo goal where the goal trigger only fires if the kilo attacks the US.
In every instance where the human is controlling the Kilo when the kilo attacks the Seawolf eventually the game causes my PC to reboot.
Since no other scenario reboots now that I set dw's affinity to just a single CPU there must be something weird about the scenario.
I'd like for others to run this thing a few times and see if it reboots your PC's. Or maybe you just see something in the design that you know screws up DW. If you're interested in helping out PM me and I'll send you a zipped up version of the mission.
As an aside this isn't the only weirdness in DW scenario design I've seen.
In another scenario I've since given up on a Japanese P-3 would launch from the Jap airbase in the scenario and attack a Japanese DD. Every single time. P-3's would keep launching until the DD went down. I kept an example replay of the incident after watching the replays with truth on about 10 times running the mission. I even contacted Sonalysts and offered to send them the scenario and the replay file (which I still have if anyone is interested) but they completely blew me off.
DW's scenario designer isn't right - and I've been designing scenarios with it's equivalent on 688i, Fleet Command and Sub Command without problems for a pretty long time now.