Potential Game Crash

Matrix Games Forums

Forums Register Login Photo Gallery Member List Search Calendars FAQ

My Profile Inbox Address Book My Subscription My Forums Log Out

Potential Game Crash

View related threads: (in this forum | in all forums)

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [Current Games From Matrix.] >> [World War II] >> Steel Panthers World At War & Mega Campaigns >> Potential Game Crash

Page: [1]

Message

<< Older Topic Newer Topic >>

Potential Game Crash - 1/12/2001 9:57:00 PM

Greg McCarty

Posts: 234
Joined: 6/15/2000
From: woodbury,mn,usa
Status: offline

I observed this phenom during scenario developement. It may seem obvious, but I have not run across mention of this. So just as an FYI... When initiating a fire order with morters or for that matter, any other indirect fire artillery, DO NOT attempt to move the firing unit before the fire order has been completed --unless you make sure you have cancelled that order. In earlier SP models this would simply have resulted in the loss of the fire order, but in the SPwaw current design, the result will be a near certain crash to the desktop when the fire routine attempts to execute. Probably from a range to target contradiction or firing unit status contradiction that the code cant cope with. Strict attention to sensible proceedure will avoid this unpleasant experience. ------------------ Greg. 37 mill AA... can suddenly ruin your day.

_____________________________

Greg.

It is better to die on your feet
than to live on your knees.

--Zapata

Post #: 1

- 1/12/2001 10:55:00 PM

Paul Vebber

Posts: 11430
Joined: 3/29/2000
From: Portsmouth RI
Status: offline

Thanks Greg - We'll check on that!

_____________________________

http://www.matrixgames.com/images/sig-logo-02.gif

(in reply to Greg McCarty)

Post #: 2

- 1/12/2001 11:49:00 PM

Bonzo

Posts: 676
Joined: 9/3/2000
From: Peace River, AB, Canada
Status: offline

Hi Greg, Are you seeing this in scenario development only, or in regular game play also? ------------------ Robert (Bonzo) Lindsay, Coordinator 28th (North-west) Battalion Headquarters Main http://nwbattalion.tripod.com E-mail [email]nwbattalion@icqmail.com[/email]

_____________________________

Robert (Bonzo) Lindsay, Webmaster 28th (North-west) Battalion Headquarters Main http://www.nwbattalion.com E-mail

(in reply to Greg McCarty)

Post #: 3

- 1/13/2001 4:47:00 AM

Greg McCarty

Posts: 234
Joined: 6/15/2000
From: woodbury,mn,usa
Status: offline

quote:

Originally posted by Bonzo: Hi Greg, Are you seeing this in scenario development only, or in regular game play also?

Saw it when I was playtesting, and I actually committed this act, and I saw it occur during an early design where I had set up an initial fire order at the beginning of a scenario on the side controlled by the A.I. The A.I. attempted subsequent moves in spite of the fire order. Brought on the crash quite often. As you might imagine, it took me awhile to figure out what was going on. I suspect Grigsby included a code check to see if the firing unit had changed position since the fire order had been given, which then nullified the fire order. No muss; no fuss. But something has changed during the code evolution and the computer is no longer looking at this until the tubes actually fire. If the unit is on the move, or not in the original position, bad things happen. ------------------ Greg. 37 mill AA... can suddenly ruin your day.

_____________________________

Greg.

It is better to die on your feet
than to live on your knees.

--Zapata

(in reply to Greg McCarty)

Post #: 4