-
Content Count
922 -
Joined
-
Last visited
-
Days Won
10
domfluff last won the day on November 2 2020
domfluff had the most liked content!
About domfluff
-
Rank
Junior Member
Converted
-
Location
UK
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
C2 & Information Sharing (REDUX)
domfluff replied to MOS:96B2P's topic in Combat Mission - General Discussion
Yup. They're also the ones with the radios in WW2 titles, if anyone does. I often use my HQs quite aggressively, spotting with them, running them back and forth between units to share spotting contacts, etc. It's a risk, obviously, but I think there's a lot you can gain from that. -
Freyberg reacted to a post in a topic: C2 & Information Sharing (REDUX)
-
C2 & Information Sharing (REDUX)
domfluff replied to MOS:96B2P's topic in Combat Mission - General Discussion
Eight squares would assume no radios and voice distance, but sure - visual distance is longer than that, and is still "in C2", albeit to a worse level. There's a trade-off, was my point - you spot faster with shared spotting information, and the fastest way to share spotting information would be for the HQ to have the spots (a leader recon). Therefore, for the unit to fight at maximum efficiency, you'd want an HQ up front and spotting things (possibly with a short arc to not engage themselves). The trade-off is that putting the HQ in a position where they can spot things means that they -
C2 & Information Sharing (REDUX)
domfluff replied to MOS:96B2P's topic in Combat Mission - General Discussion
Based on Josey Wales' testing, he didn't see a difference in the recovery from suppression based on the formation HQ's leadership value - in that sense it didn't make a difference, and the results are a binary "in C2" and "not in C2" thing. If that is the case, that doesn't mean it's not important. Suppression of the HQ unit will break C2, so a higher leadership HQ unit will stay unsuppressed for longer over the course of a firefight, and therefore maintain C2 for the rest of the formation. You could avoid this by keeping the HQ unit out of the fight, but since information is shared in s -
This was definitely fixed, a while ago. It was actually improved over CMSF 1, in that Quick moving (what the AI defaults to) will still be covered by this, when it would not in CMSF 1
-
There is also the IED mine in CMSF - it works like the other minefields, but it's a single, massive explosion (with a 0% failure rate, or at least as much as mines can fail).
-
As always with IEDs, I think it's useful to consider the manual's failure rate as a best-case scenario. The triggerman still has to spot the target, not be obscured by dust, not be suppressed, not be distracted by a passing kitten, whatever. I imagine if you ran a thousand tests, the failure rate would be significantly higher than stated.
-
Hapless reacted to a post in a topic: Syrian Army tutorials and best scenarios for H2H
-
badipaddress reacted to a post in a topic: Syrian Army tutorials and best scenarios for H2H
-
Syrian Army tutorials and best scenarios for H2H
domfluff replied to badipaddress's topic in Combat Mission Shock Force 2
Yup. ATGMs are essentially one shot weapons, but if that one shot trades efficiently with a Bradley, you're up significantly. I typically try to fire one shot then Fast move to relocate. ATGMs are best used in at least pairs, and dispersed - this creates a C2 problem to solve, but it means that you can more easily score flank shots (more important for Abrams), and can't have both assets suppressed at the same time. When relocating it's important to pop back up in a different position (i.e., far from the contact marker you'd be leaving behind as you break line of sight). This means w -
badipaddress reacted to a post in a topic: Syrian Army tutorials and best scenarios for H2H
-
Lethaface reacted to a post in a topic: Syrian Army tutorials and best scenarios for H2H
-
Syrian Army tutorials and best scenarios for H2H
domfluff replied to badipaddress's topic in Combat Mission Shock Force 2
Red vs Red and Blue vs Blue are both fine in CMSF multiplayer - it's just the mixed game which I'm suspicious of. In general I think I prefer Red vs Red, but that's mostly because the more advanced stuff pushes it more towards one shot kills and heavy punishment for mistakes/random surprises. To be entirely clear, I do think it's possible to win, but you have to do all the work. You can also sometimes do everything right and still lose. In the broader sense this is true for anything "lower tier" in a competitive game. -
George MC reacted to a post in a topic: Syrian Army tutorials and best scenarios for H2H
-
Roter Stern reacted to a post in a topic: Syrian Army tutorials and best scenarios for H2H
-
Falaise reacted to a post in a topic: Syrian Army tutorials and best scenarios for H2H
-
Lethaface reacted to a post in a topic: Syrian Army tutorials and best scenarios for H2H
-
Marwek77 aka Red Reporter reacted to a post in a topic: Syrian Army tutorials and best scenarios for H2H
-
Syrian Army tutorials and best scenarios for H2H
domfluff replied to badipaddress's topic in Combat Mission Shock Force 2
I'm deeply suspicious of Red vs Blue in CMSF in a multiplayer sense. I'm sure it's possible to win as Red, and it's possible to have balanced scenarios, but the disparity is so large that this is extremely difficult - even in an ideal situation, you'll be working significantly harder than the Blue player to keep level. Still, if you're up for the challenge, this is the theory: Imagine a Quick Battle, where the enemy are a US Bradley platoon. These are three squads with attached assets, javelins and the Bradleys themselves. Each element outperforms you in every way. The main threats in -
domfluff reacted to a post in a topic: [scenario] Royal Rumble
-
It really depends, both on the scenario or my mood. Sometimes I feel like you can get a lot out of scenario as a tactical problem, attacking it in varying ways and trying out different ideas. Clearly the latter attempts are easier, even with varied AI plans (even just being familiar with the terrain will help), but when talking about a single player game, I'm not sure that matters. It does mean that "high scores" and the like are pretty meaningless. This is a large reason why multiplayer quick battles are nice - you're doing everything only once, ever, and you can't know what you're figh
-
domfluff reacted to a post in a topic: Community Campaign Created by Multiple Contributors, Historical or Hypothetical
-
What is the learning curve and what to do about it?
domfluff replied to markshot's topic in Combat Mission Shock Force 2
Some brief, unstructured thoughts: Broadly speaking, ATGMs are like better versions of AT Guns. They're similarly hard to see, and they're countered by many of the same things (mortars and HE fire). They're a lot faster to set up and remove, so you can shoot and scoot with them, and probably should. The increased lethality means that you do need to relocate more often. A revealed position can often come under effective mortar fire within 5 minutes (regardless of which side you're talking about). Some US formations with crack FOs and the right equipment can reduce that to more like -
Troops using HUNT do not stop when fired upon
domfluff replied to Bulletpoint's topic in Combat Mission - General Discussion
Sure, so there has definitely been a change. This may have been intentional, or it may have been unintentional. It's not that this is broken, it's that the threshold has been tweaked, and perhaps this has been tweaked to the wrong level. Or not. -
Troops using HUNT do not stop when fired upon
domfluff replied to Bulletpoint's topic in Combat Mission - General Discussion
The behaviour certainly has changed. I ran some tests with CMBN, with a squad under fire from an unspotted SMG at maximum range. The squad stopped moving on the third burst. They will stop moving immediately if they see a target, or if someone actually gets hit, but it takes them a while to react to incoming fire itself. Now, I don't know whether that's strictly a bug. It's observably less sensitive than it used to be, but the functionality does work. It's reasonable to state something like "they aren't behaving as I think they should", rather than "this is broken".