Matrix Games Forums

Forums  Register  Login  Photo Gallery  Member List  Search  Calendars  FAQ 

My Profile  Inbox  Address Book  My Subscription  My Forums  Log Out

Pointless merges and fixed platoons

 
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: Last Stand Arnhem >> Pointless merges and fixed platoons Page: [1]
Login
Message << Older Topic   Newer Topic >>
Pointless merges and fixed platoons - 7/27/2010 3:01:57 PM   
Rift

 

Posts: 37
Joined: 7/23/2009
Status: offline
I love the flammpanzers they are awesome tanks but Pz. Kp. 224 is small, it has 4 vehicle slots available but only 2 support slots which only allows you 2 infantry squads to cover the tanks. This seems ridicules there is no way a BG would go into battle like this. Maybe the other way round with 2 tanks and 4 infantry units?? Although to be honest going into battle with only 6 squads seems too little to have a good fight on these huge maps.

I thought that by merging PZ Kp 224 with another BG I could provide my lovely Flammpanzers with some shiney SS and FJ troops so I merged them with KG Walther.

On carrying out the merge I discovered that I had lost all but one of my tanks. It would appear that whatever is in the active roster is lost and not returned to the forcepool. This must be a bug surely??

Is it also possible to look at altering the vehicle/support/infantry layouts IMO it would be best to remove the restrictions on each platoon. The introduction of the fixed inf. veh. and sup. only platoons is an interesting idea but for me it just results in unrealistic load outs. Particularly in Pz. Kp. 224 and 280 Stug. BDE.

What are your thoughts?
Post #: 1
RE: Pointless merges and fixed platoons - 7/27/2010 7:28:16 PM   
Rift

 

Posts: 37
Joined: 7/23/2009
Status: offline
Here is the end result of the merge, all but one of the Flammpanzers is lost:






Attachment (1)

(in reply to Rift)
Post #: 2
RE: Pointless merges and fixed platoons - 7/27/2010 7:45:06 PM   
xe5

 

Posts: 783
Joined: 5/3/2009
Status: offline
Ive also seen teams in the active roster of the subordinate BG get lost when merging. This is contrary to the game manual: "Merging Battle Groups moves all teams from the absorbed Battle Group into the forcepool of the absorbing Battle Group." (pp. 62-63).

Always possible they meant to say "...from the forcepool of the absorbed battle Group..." but the loss of the absorbed BG's active teams from the combined forcepool is a penalty that doesnt make sense. Penalty enough that you cant 'un-merge' and have one less manuever BG.

(in reply to Rift)
Post #: 3
RE: Pointless merges and fixed platoons - 7/27/2010 8:01:59 PM   
Ivan_Zaitzev


Posts: 49
Joined: 6/19/2009
Status: offline
You can always just put them together but not merge them.

(in reply to xe5)
Post #: 4
RE: Pointless merges and fixed platoons - 7/27/2010 8:11:41 PM   
Rift

 

Posts: 37
Joined: 7/23/2009
Status: offline
Sadly that doesn't seem to work either:

As you can see in the photo below you can't choose anything from Kp Pz 224 even though there is an empty slot??

Yeah sorry just realised why I couldn't choose any tanks, NO CREDITS!! doh my fault.

However it still illustrates that even if I didn't merge I could only have used one of the tanks (if I had the credits).






Attachment (1)

< Message edited by Rift -- 7/27/2010 8:22:30 PM >

(in reply to Ivan_Zaitzev)
Post #: 5
RE: Pointless merges and fixed platoons - 7/27/2010 11:15:36 PM   
RD Oddball

 

Posts: 4836
Joined: 2/10/2007
Status: offline

quote:

ORIGINAL: xe5

Ive also seen teams in the active roster of the subordinate BG get lost when merging. This is contrary to the game manual: "Merging Battle Groups moves all teams from the absorbed Battle Group into the forcepool of the absorbing Battle Group." (pp. 62-63).

Always possible they meant to say "...from the forcepool of the absorbed battle Group..." but the loss of the absorbed BG's active teams from the combined forcepool is a penalty that doesnt make sense. Penalty enough that you cant 'un-merge' and have one less manuever BG.


Steve provided that section of the text for the manual writing so doubtful he meant to say something else. I'll report it as a bug and see what he says. Maybe there's an explanation but it doesn't look like it at first blush.

(in reply to xe5)
Post #: 6
RE: Pointless merges and fixed platoons - 7/27/2010 11:17:27 PM   
xe5

 

Posts: 783
Joined: 5/3/2009
Status: offline
Apparently you can keep merging BGs (and absorbing static BGs) until youve merged your entire OOB into a single BG with a huge forcepool...so huge the forcepool slider cant handle the load and it cuts off at the start of the available FJ units.




Attachment (1)

(in reply to Rift)
Post #: 7
RE: Pointless merges and fixed platoons - 7/28/2010 1:44:12 AM   
xe5

 

Posts: 783
Joined: 5/3/2009
Status: offline
Sometimes the Infantry/Vehicles/Support platoons arent so fixed. Occasionally the game will stock my Veh Platoons with Ersatz.




Attachment (1)

(in reply to Rift)
Post #: 8
RE: Pointless merges and fixed platoons - 7/28/2010 4:39:08 PM   
stolidog


Posts: 76
Joined: 11/1/2008
From: Virginia
Status: offline
Nice, thats like a corp size BG, im suprised the slider even went that far to show all those units/teams

(in reply to xe5)
Post #: 9
RE: Pointless merges and fixed platoons - 7/28/2010 6:05:42 PM   
Ivan_Zaitzev


Posts: 49
Joined: 6/19/2009
Status: offline
Today I put two AB BG in a map, one of them was really mowed down, with only a couple of HQ a sniper and a Bren squad. The other one was in full strength with all the slots filled.
When the I was to choose my forces for the battle, the main BG was the mowed down one, and I could only put one squad from the other BG, that was pointless.

(in reply to stolidog)
Post #: 10
RE: Pointless merges and fixed platoons - 7/28/2010 6:33:49 PM   
xe5

 

Posts: 783
Joined: 5/3/2009
Status: offline
@Ivan - unfortunately that battle was "pointless" due to an incompetent Allied commander who remained ignorant of how Battle Group Orders work (pp. 60-62).

(in reply to Ivan_Zaitzev)
Post #: 11
RE: Pointless merges and fixed platoons - 7/28/2010 7:12:09 PM   
Ivan_Zaitzev


Posts: 49
Joined: 6/19/2009
Status: offline

quote:

ORIGINAL: xe5

@Ivan - unfortunately that battle was "pointless" due to an incompetent Allied commander who remained ignorant of how Battle Group Orders work (pp. 60-62).


I Know it was my mistake, just sharing.

(in reply to xe5)
Post #: 12
RE: Pointless merges and fixed platoons - 7/28/2010 8:19:01 PM   
TheReal_Pak40

 

Posts: 186
Joined: 10/8/2003
Status: offline
Yet another bug in the strategic layer and another reason to wait for the patches before playing the campaigns. *sigh*

Oddball, The merging topic reminds me of a question I've been yearning to ask:

Why on earth can you merge units but not split them? Seems like every battalion should have the ability to split from it's parent regiment/brigade/kamfgroup, much like they did in real life. You should at least have the ability to split units that were previously merged, but to be realistic it should be all battalions. If map crowding is the reason then you could just simply force auto-merges of 3 or more units on the same map.

(in reply to Ivan_Zaitzev)
Post #: 13
RE: Pointless merges and fixed platoons - 7/28/2010 9:07:53 PM   
Andrew Williams


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

I Know it was my mistake,


I've heard that can happen

(in reply to TheReal_Pak40)
Post #: 14
Page:   [1]
All Forums >> [New Releases from Matrix Games] >> Close Combat Series >> Close Combat: Last Stand Arnhem >> Pointless merges and fixed platoons 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

1.656