From: Iowan in MD/DC
Im using my old Laptop at the moment its a Duel core intel t9300 2.50ghz, it has 4gb ram and is running vista home premium. In the comand line of the short cut i started out with : -
-fw –px1680 –py1050 –altFont –cpu2 –multiaudio –dd_sw at the end of the line.
I the took out -dd_sw and -multiaudio but it still happened again a few turns later.
ive reduced it to "C:\Matrix Games\War in the Pacific Admiral's Edition\War in the Pacific Admiral Edition.exe" -fw –px1680 –py1050.
The next time it happened i'll try to get a screen shot of the error.
I have played the original Witp on the same laptop and never had any problems.
Do you suggest i remove the tweeks completely and try it as normal?
Take out the -px -py portion and see if it still crashes.
I believe that crashes in the past have also related to DirectX installs. There is a DirectX diagnostic program you can run and post which has been of help in the past. I don't know the commands to do that, however.
If it runs fine for a few turns and then crashes you might have other laptop-related issues with bad RAM, too much heat, overheating graphics chips, etc. Do other programs crash too?
Or, it's faintly possible you have a corrupted install. Usually it woudln't run at all if that were the case.
Does it crash in the same spot or during the same part of a turn each time? Or are the crashes random? Are you multi-tasking while playing?
Probably other questions, but you haven't given much to go on.
Ah, yes, dxdiag. There is a sticky thread on this, but it's pretty simple. Open the start menu, type in "dxdiag.exe" in the search box that is there at the bottom, and it should open the tool for you. The sticky thread is here: http://www.matrixgames.com/forums/tm.asp?m=2178205. I think you should generate that file and post it as an attachment here; it will give us a lot more information to help you out.
Typically, bad RAM will cause a hard system crash (particularly in Windows - it's happened to me a lot over the years, building PCs for myself and friends). So unless you're having problems with other applications crashing, I don't think this is the case.
Since you are able to run the program for some length of time, and boot it up with no immediate problems (until it crashes again), I really think this is some kind of driver error. Posting your dxdiag file might help us figure it out, but you can try playing around with the startup flags in the meantime. Add/remove the following flags to your original command line, one at a time, to see if you can isolate which one (if any) is causing the crashes:
-fw: try simply -f, or -fd.
-cpu1/-cpu2: since you have a dual-core system, using anything other than these won't do anything. I see you used to have cpu2 in there. If you use this flag at all, I would use -cpu1 (a bit of computer science superstition).
-multiaudio: since you have a multicore machine, this may be something you want to use. But not if it crashes your game (but then we know that it might be a problem with your audio drivers in some way).
-dd_sw: This one is related to your graphics driver.
-px1680/-py1050: could be unnecessary if you are running in full screen
I noticed that you have been using the -fw flag (for weekly autosaves). Do you know if the turn it is supposed to autosave is the same turn it crashes? I don't think this is the problem, but changing to -fd will test whether there is a problem if autosaving. If it crashes every turn when you change to the -fd flag, then that may be the problem.
Another thing I think you should try is running in windowed mode. I used to have crash issues (which I think were related to my graphics driver) when I first installed the game, and running in windowed mode prevented them from occurring. Switch the -fw flag to -ww, -w, or -wd. I would recommend changing to -px1600 and -py900 when running in windowed mode.