Matrix Games Forums

 Forums  Register  Login  Photo Gallery  Member List  Search  Calendars  FAQ 

My Profile  Inbox  Address Book  My Subscription  My Forums  Log Out

Northern Flank campaign bug

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

Logged in as: Guest
Users viewing this topic: none
  Printable Version
All Forums >> [New Releases from Matrix Games] >> Close Combat Series >> Close Combat: Wacht am Rhein >> Tech Support >> Northern Flank campaign bug Page: [1]
Login
Message << Older Topic   Newer Topic >>
Northern Flank campaign bug - 4/6/2009 12:58:24 AM   
TDeacon

 

Posts: 62
Joined: 12/25/2005
From: NE Illinois
Status: offline 		When playing a 2-player "Northern Flank" mini-campaign, the game locks up when all 5 of the following steps are performed in sequence:
1) German player hosts.
2) German player disbands both the 12th VG and the 3rd FJ BGs.
3) German player assigns artillery and morters to both Kullman and Peiper BGs.
4) German player moves Kullman into Krinkelt and Peiper into Losheim.
5) Both US and German players hit execute. (lockup occurs at this point).

I have seen this consistently both with a remote opponent, and also with a simulated opponent on my LAN. The problem does not occur when certain variants of the above are tried. For example, if either 12th VG or 3rd FJ are not disbanded (but the other still is), and if then the corresponding armored BG isn't moved forward to replace the disbanded BG, then this issue isn't observed.

Mark

< Message edited by TDeacon -- 4/6/2009 5:47:03 PM >
Post #: 1
RE: Northern Flank campaign bug - 4/6/2009 5:34:11 AM   
Andrew Williams


Posts: 6116
Joined: 1/8/2001
From: Australia
Status: offline 		When you do all 5 of the ABOVE or any 1 of the 5?


(in reply to TDeacon)
Post #: 2
RE: Northern Flank campaign bug - 4/6/2009 5:37:45 PM   
TDeacon

 

Posts: 62
Joined: 12/25/2005
From: NE Illinois
Status: offline 		All 5; I edited the original post to clarify. I'm hoping that if you do these 5 things on your test setup, you will see the issue as well.


< Message edited by TDeacon -- 4/6/2009 5:43:35 PM >

(in reply to Andrew Williams)
Post #: 3
RE: Northern Flank campaign bug - 4/6/2009 8:47:33 PM   
Andrew Williams


Posts: 6116
Joined: 1/8/2001
From: Australia
Status: offline 		Will try it today.

(in reply to TDeacon)
Post #: 4
RE: Northern Flank campaign bug - 4/12/2009 10:48:42 PM   
TDeacon

 

Posts: 62
Joined: 12/25/2005
From: NE Illinois
Status: offline 		Hi Andrew,

So, were you able to duplicate this?

MH

(in reply to Andrew Williams)
Post #: 5
RE: Northern Flank campaign bug - 5/2/2009 3:03:42 AM   
TDeacon

 

Posts: 62
Joined: 12/25/2005
From: NE Illinois
Status: offline 		Resend...

(in reply to TDeacon)
Post #: 6
RE: Northern Flank campaign bug - 5/2/2009 4:36:49 AM   
Andrew Williams


Posts: 6116
Joined: 1/8/2001
From: Australia
Status: offline 		Sorry, no, lost track of this hen I went on holidays.

Will take a look this week.

thanks

(in reply to TDeacon)
Post #: 7
RE: Northern Flank campaign bug - 5/2/2009 6:24:43 AM   
Andrew Williams


Posts: 6116
Joined: 1/8/2001
From: Australia
Status: offline 		Ok

I can reproduce this too

We're looking at it.

thanks for the post

(in reply to Andrew Williams)
Post #: 8
RE: Northern Flank campaign bug - 5/2/2009 5:27:15 PM   
Tejszd

 

Posts: 3437
Joined: 11/17/2007
Status: offline 		What a detailed report TDeacon, way to go.

Andrew glad to hear you can reproduce the problem and it is being looked at for the next WAR patch....

(in reply to Andrew Williams)
Post #: 9
RE: Northern Flank campaign bug - 5/2/2009 9:45:04 PM   
Andrew Williams


Posts: 6116
Joined: 1/8/2001
From: Australia
Status: offline 		tDeacon  would make great tester material  :)

(in reply to Tejszd)
Post #: 10
RE: Northern Flank campaign bug - 5/6/2009 3:52:41 AM   
Andrew Williams


Posts: 6116
Joined: 1/8/2001
From: Australia
Status: offline 		Ok, We've tracked it down.


The lock up issue is a sync problem between host and client. 

As part of the sync when both hit 'Execute' the host and client exchange data about locations where there might / will be a battle (depending on the phase).

When the host disbands all BGs in contact it doesn't think there will be any battle data to transmit on the first 'Execute', so it sends nothing. 

The client has not yet received the info about the disbanding and so it sees BGs in contact and sits waiting for battle data that is never going to come -- deadlock.

This will be fixed for the next patch.

Interim measure.

Don't disband all Battlegroups that are in contact.




(in reply to Andrew Williams)
Post #: 11
Page:   [1]
All Forums >> [New Releases from Matrix Games] >> Close Combat Series >> Close Combat: Wacht am Rhein >> Tech Support >> Northern Flank campaign bug Page: [1]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.906