Matrix Games Forums

Under the latest patch in window mode, both the Coral Sea and Guadalcanal scenarios CTD (right before attempting to send Micro$oft an error report [:-]). The problem does not occur in the 1000 Mile scenario. I’ve tried numerous switch settings to no avail. The latest being:

" -w -px1680 -py1050 -SingleCpuOrders -cpu2 -multiaudio"

Is anyone else experiencing this problem? Any fixes, workarounds or hints?

Would a save be helpful? If so, from before or after the crash?[8|]

AMD Phenom II
GeForce 9500 GT
XP Pro

Cheers,
Doug

Does it run without the -px -py options?

It may be that the widow size is not compatible with the size of the map area defined for those scenarios.

Michael,

The results are the same without the -px -py options.

I also tried increasing the x-axis of the game to allow for the increased pixels of the option. It decreased the "jitters" but didn't keep the crash at bay.

<Screen shot w/o -px -py>





Edit: By increasing the x-axis I mean I used the editor to decrease and increase the Left X and Right X respectively.

Have you tried opening these scenarios in the editor? Does it always crash during loading of new game? Does it crash after loading of new game, if so when? I'm trying to understand when it crashes and under what circumstances.

I've edited the Coral Sea scenario to bring the playing area into line with the aspect ratio of my monitor (see attachment). The game crashes under both versions.

The game loads fine. It crashes after noodling around for awhile. It usually goes down about five or so minutes after loading. Or 100 mouse clicks? I haven't timed it nor have I counted the clicks. Your results may vary.[:'(]





Did I say "playing" field? I must be on acid...

So if you just load the scenario and do abosolutely nothing, does it crash? If clicking the mouse crashes the game then is it the same item that you clicked on that causes the crash or just anything?

Upload a save because I'm not having problems with these scenarios.

Have you tried rebooting your machine?

By "absolutely nothing" mean simply wait? I'll pay more attention to clicks and let you know.
Meanwhile, here's a Coral Sea save out of the box.

And here's a Coral Sea save with expanded X ordinates.

And thanks for your attention.

Heh. I just noticed when clicking on a base, some info seems to be missing. So, here is more grist for the mill.

ORIGINAL: dorjun driver

Under the latest patch in window mode, both the Coral Sea and Guadalcanal scenarios CTD (right before attempting to send Micro$oft an error report [:-]). The problem does not occur in the 1000 Mile scenario. I’ve tried numerous switch settings to no avail. The latest being:

" -w -px1680 -py1050 -SingleCpuOrders -cpu2 -multiaudio"

Is anyone else experiencing this problem? Any fixes, workarounds or hints?

Would a save be helpful? If so, from before or after the crash?[8|]

AMD Phenom II
GeForce 9500 GT
XP Pro

Cheers,
Doug

remove the -px1680 -py1050 from the command line and you should be fine.

map sz too small.

Ran your extd cs save with no problems and clicking a bunch of stuff. Check your pc temp values maybe you are running a little hot.

It's curious these phenomena don't occur running the 1000 Mile scenario.

Joe: Removing the -px -py switches have no effect.&nbsp; The game still crashes when running Coral Sea and Guadalcanal only.

BigJ: Both cores are running well within spec. Quiescent < 29c, executing < 40c.&nbsp; Although with the current switch settings, only the second core is under any strain during execution. Hmm.&nbsp; My process affinity and priority jammer may be on the blink.&nbsp; My "map sz too small?" My dear sir, to what are you referring?

In any case, why would the bottom panel be devoid of information for the Coral Sea scenario, yet work fine for the 1000 Mile scenario?

TTFN,
Doug

increase the map extents and the bottom bar will work again.

what is the temp on video?

I should have pointed out that the missing bottom bar only occurs in the Coral Sea scenario only.

I've already extended the X axis by six hexes on either side.&nbsp; Are you suggesting increasing the X axis more or the Y axis?&nbsp; Or both? Any recommendations?

GPU is at 47c, climbing to 48c when it gets pi$$ed.

Thanks

your save file works just fine on my machine including the bottom bar.

Well, I suppose I'll just have to run full screen. Sigh...

J & B, thanks for your suggestions.