Howler

And yet, you proceed to do exactly that.

Watch your suppression meter though. It is effected by nearby fire from friendlies.

Congrats! What happens is a de-cluttering of useless data. Like the day of the week. Every day is now a Saturday so why keep Monday around... that sort of thing.

No problem. I just wanted to reported behavior of Dragon AT teams to not get lost in translation. Javelins won't fire on Target Light. But I haven't verified this since the 'collapsed' LAW/RPG patch was made available.

A TOW won't be fired from a Bradley. You've even posted in threads discussing this. Also, Javelins won't be wasted when a Target Light is issued. You've posted in these threads too. The Dragon, in CW, may be classed differently. If so, I'll need to keep this in mind. Hoping some kind soul here will port a shooting range (ala CMBS) saving me some effort. I would in turn commit to reporting tests of LAWs and such in this title as they should not normally be fired with a Target Light. Maybe the change altering the look (collapse tube) of LAWs (M72 & RPG-18) in the recent patch caused some unintended consequence?

I have and do. That's why I asked if this was changed in CW. Thank you @Combatintman for confirming that these levels haven't changed in CW.

I'm not sure I follow; are you saying that Elite/Iron don't use 'realistic' wait times? I thought once someone played on 'Warrior' the only difference was the amount of 'spotting' information provided. With 'Iron' requiring friendlies to also be 'spotted'.

I wasn't aware of a difference in wait times. I thought all three used realistic wait times. Was this changed recently?

Lower right of post, you should see a heart. Clicking that heart icon now reveals upvote/thank. Just tried to both upvote and thank your post but only the last one selected seems to stick. Anyhow, we can: Like, Thank, or Upvote.

Anyone know the difference between the three? I'm particularly interested what 'upvote' means in the context of this board.

It doesn't already exist. Spotting updates continuously over the course of a 60 second slice and teams have varied movement rates depending on status (number of KIA/Wounded). I'm not sure what feature you're alluding to. When I displace a squad, I alter waypoint movement rates (eg Fast/Quick) of the individual elements accordingly. EDIT: Again, it might be my not understanding what is being requested.

It isn't easy and results in stragglers not to mention the spacing is too close while on the move. Why everyone seems to think this is easy all of a sudden must have not experienced the path finding issues only recently alleviated (not corrected) with "withdraw" and movement generally in close terrain. How would this magical 'follow' command work exactly? All I've seen mentioned is a 'replicate' function which would also include pause(s). You'd still need to tweak it as vehicles differ in speed. Infantry differ in both number of men and wounded men in a given element. How far could the last element be from it's lead to be included? What happens when there's impassable terrain between the lead and follow unit? I've never been involved in devising/testing this feature but can readily understand the desire to not include/clutter the UI panel with a player command that would rarely function as intended. Please do continue to believe BFC is being mean by holding this back from us. Oh, and explain to me how 'Hunt' would behave when a mixed formation of (light/heavy/tracked/wheeled/transport/etc.) vehicles? And, again with a mix of vehicles and infantry? We can repeat with a mix of Fast/Quick/Move/Slow... I'd rather they fix 'Hunt' and then move on to next quirk (eg infantry dispersal/spacing). EDIT: I micro manage and know full well the tedium of tweaking individual elements. It's brutal, but adding a 'cheat' key that wouldn't work reliably would only force me to continue to use 'double-click', shift way point, add pause, repeat...

The problem might be with my comprehension of the feature being discussed. Are we looking at a command to allow movement in column exclusively? If so, why introduce a command with limited use to an already crowded panel? Can't we already copy/paste movement now by selecting the parent command (aka double-click)? Then move/pause waypoints around as desired? I thought the feature being requested included moving commands in wedge/line/column formation across any terrain (not limited to roads) with a defined spacing appropriate for the desired formation. My apologies. I don't mind responding to your points if you were envisaging something other than a copy/paste of both waypoints and pause which the current available mechanics don't do (eg pauses aren't copied over). I assume it would be expected of the feature to sort elements belonging to different organizations on the fly... Otherwise, given the fact we still can't cross bridges or road intersections (the latter being CMCW Fleeing Altdorf) with 100% certainty; I understand why this feature has failed to appear. Surely, I can't be only one noticing 'quirks' in the path finding as it is now. Asking this to be mirrored to every element can only lead to more frustration (new players more so). A wise vendor seeks to minimize such things... making their decision to not implement it perfectly understandable and rational. Assuming a design consideration is improving ease of use while avoiding additional frustration. Anyhow, apologies for not fully grasping what is being sought. I'll go back into the background.

Possible reasons: 1) what distance to maintain between 'travelling' elements? 15m, 25m, 50m, etc.. We already know that maintaining spacing within an element is an issue (too bunched up). 2) path finding - while much improved - still rears it ugly head depending on the quality/condition of the map. Older maps not refined/updated to incorporate current terrain objects resulting to make this more apparent. 3) Magic! How would individual elements upon having lost LOS to their 'lead' know when to stop? 4) when the 'lead' element is destroyed, engaged in an ambush, or otherwise unable to continue (immobilized/bogged) - what happens? 5) Any new command introduced needs to be absolutely bulletproof. You need to look no further than the 'Hull Down' to see how that was initially accepted. We can be a critical crowd... I can go on but let's not pretend the beta testers and BFC didn't give it their all. I can roll off a few other reasons as you like...

The issue remains in the execution and not the plotting itself. Formations can be selected and then the waypoints can be moved accordingly. You've shown this can be accomplished fairly quickly. The challenge is in who needs 'X' second of pause so as to not break the formation (eg wedge or column). For example with vehicles, which one and where in the formation will it bog? If the lead vehicle slows/bogs, the follow-ons will start to route around it. That 'route around' behavior is likely something we all want to retain. So, when/which use cases do we want troops *not* to move around obstructions? Troops are already not as dispersed during movement as we would like. How much "bunching" are we willing to tolerate when the lead element encounters a wall/hedge/forest/etc.? For these reason and a few more - it's never been incorporated in game.

Usually, the reshade dll (opengl32.dll) needs to be in the same location as the executable for the game. I don't have the steam versions of CM but assume that would be somewhere like '../Steam/steamapps/common/Combat Mission Shock Force 2'.

@Gkenny Thanks for that. TBH, I'm experimenting with CMCW to see how much it differs engine wise. I just never noticed squads popping *two* smokes before and wondered if it was WAD when both corners were hugged... One each in opposite directions seemed excessive and new to me.

First time I notice this behavior when popping smoke. Had a squad lined up along the outside of a building that threw smoke in both the direction of the last 'Face' command (good) *and* at the opposite corner of the building in the other direction (bad). I'm forcing myself to use squads more often than teams in this title when playing the Soviets. The above might have always been the case when Squads are used to smoke (ie. they always threw two smoke grenades?). Granted, this might be long known and expected behavior. I simply never noticed before as I use teams exclusively (wearing out the Combine Squad button!) before now. Teams will also position a man at both corners of a terrain piece occupying an action spot but throw *one* smoke in the direction of the 'Face' command (my SOP -> Face then Smoke). So, squads throw two smokes where teams only throw one? When covering both corners a squad will throw smoke from both corners in opposite directions?

My understanding is that currently, your off-map support has, for example, 156 rounds allotted . All of which may be HE and no more than 'X' can be smoke. In other words, your limit is 156 HE fires and no more than 'X' fires can be something else (smoke, WP, precision, etc.). A ratio of 156 HE/ 56 Smoke means 100 HE when 56 Smoke have already been fired. If you have already fired 36 smoke than your HE count is 120 (and no more than 20 smoke remaining). I have learned to look at the top line for ammo count (HE) and anything else available listed below that line are 'type' limits *within* that overall HE count. On-map assets differ in that they actually carry what they show and may also fire directly.

Pretty nifty - thanks BF!

Thanks @IanL.

You beat me to it! I made the mistake of not checking the site yesterday and, other than also being part of the Fightin 41st, missed the opportunity to be first to change over to that patch! Well done, Sir. My priorities are a mess. I'll always wonder if the deck needed staining yesterday of all days...

What video card are you using? An AMD card will show white spots for hit decals with shaders turned on. At least, that was my case when I last had one (couple of years ago).

Final Update My opponent was kind enough to KO the HT which reset the team stuck in embark limbo. That team has since moved to a more secure location out of sight.

In the modern titles, anything 120mm plus will hurt *and* demolish structures. Anything caught in a barrage is pinned. Casualties are a bonus. Do expect a lot of bonus. Infantry in a building isn't an issue as there are too many things (brads/bmps) that will cause the structure to collapse. The challenge, normally, is how best to clear the building while leaving it still standing. You want to clear mines or demo a structure - call a short mission (linear or point) with 155s. You want to demo a building - target light with a brad or abrams.