Jump to content

vetacon

Members
  • Posts

    103
  • Joined

  • Last visited

Posts posted by vetacon

  1. Just stumbled across this Paper Tiger. Your campaigns all rock (loved Montebourg and currently loving Scottish Corridor).

    You mentioned the possibility of doing a German Campaign for Market Garden. That would be cool, but I'd love to see a Brit campaign around the 6th Airborne's attempts to get into Arnhem, the battles round the bridge and the defensive actions around the Oosterbeek perimeter. I think the size of these actions and the force compositions (predominantly infantry) would be perfect for the type of stuff you design. Any interest in that sort of thing?

    Anyway, that's an entirely selfish request as I'm particularly interested in Arnhem and have visited a couple of times. I'm sure whatever you design will be incredible - I would never have expected to get as much enjoyment as I have from the infantry slogs of the Cotentin and Epsom. Testament to your design skills and, of course, the game itself.

    Looking forward to the Road to Carpiquet.

    Cheers

  2. I downloaded CW about 10 days ago, having not picked up CMBN for several months for a variety of non-game-related reasons.

    I've had no problems with it at all on my iMac, and must have put it an average of two to three hours per day on it since I bought it.

    I hadn't realised there'd been lots of Mac issues so don't know whether I'm an outlier, but I haven't regretted it at all.

  3. I've mentioned this before and was just wondering if it is being looked at by Steve and the team. The screenshot below shows a trooper who has somehow ended up apx 500 metres away from his squad (even though the game's in its early turns and the rest of the squad has only moved apx 100m from its start point).

    He's also some distance off the map edge, though that is incidental to the main issue.

    Happens to me relatively frequently - I've now seen it three times in about 10 games played. Is this something that's fixable?

    Thanks

    PS The blacked out bits are to hide intel from my PBEM opponent!

    x8Rdi.jpg

  4. I clearly must take greater care when posting these days...:)

    What i meant to say was that in this test, that was so extremely limited in time and space that it probably should be considered irrelevant, all 60 fire missions landed on target. In no way does this invalidate the observations of all previous and following posters.

    I would, however hazard to voice the opinion that in this particular test, insignificant as it may be, the off-board mortars were almost ridiculously accurate.

    Cheers,

    M.

    The OP used the term ridiculous, not me - I don't agree with it. The point I was making is that when someone is reporting behaviour within the game that is unusual, it doesn't really matter that other people haven't seen it. The people who are reporting it still have a valid issue.

    I've had a couple of times where the fire for effect order is given and the rounds are landing several hundred meters off target. I've even tried doing a mission adjustment and that didn't help. In the third battle of Task Force Raff, where this had occurred, I cancelled the mission, chose an area about a hundred meters to the right (it was an area fire mission) and the spotting and fire mission went fine.

    I haven't played a huge number of games but would saying where I have had a problem represents at most 10% of missions.

    It may be as some have suggested visibility issues for the spotter team.

    Chris

    I have also seen accurate fire mission much more than I've seen inaccurate ones, but i'd still like to understand why a spotter would call for fire-for-effect when he hasn't seen any spotting rounds land on target; after all why bother with spotting rounds if the mission just goes ahead whether they're hitting the target or not. If it's to reflect the occasional incompetence of spotter or whoever's commanding the battery then that's fine. It would just be good to hear from someone "in the know" if that actually is what's happening.

  5. Oh, that seems to be the order of the day, these days (cough cough).

    Anyhow: I set up a platoon HQ, company HQ and FO (all regular/normal at Elite difficulty) firing off board 60mm, 81mm and 107 mm mortars (all regular).

    Perfect conditions, perfect visibility.

    And fired and fired and fired (that would be some 20 missions per unit).

    Result: Not once was the fire for effect off target.

    That is in fact better than I would have thought possible in WW2.

    M.

    Not quite sure why this is relevant. Are you saying the behaviour that people are reporting is made up?

  6. Design, I believe. Spotting rounds are very inaccurate (unless you get lucky). But, the spotter has to be able to see where they land in order to send corrections to the firing unit. Otherwise the next round will fall somewhere similar to the first one. If none of them are spotted, then fire for effect is eventually called where the last spotting round fell.

    In bocage scenarios this is a big problem, since thakns to the hedges almost everywhere is out of line of sight of the spotter; a spotter in one hedgerow trying to call in a mission on another hedgerow isn't going to have a high success rate unless one of the spotting rounds happens to fall in the field between them, which isn't guaranteed.

    Whether there are additional possibilities for mis-aimed missions to simulate mistakes by the spotter I don't know.

    As a rule, get your spotters where they can see the target and as much area around the target as possible. And yes, off map artillery in heavy bocage maps is not massively useful. And aggravated by the current tendency of scenarios to be 1 hour long with the artillery arriving 5 minutes in so you can't use it for a pre-planned barrage.

    I know nothing of military procedure, but the principle of the spotter calling fire for effect when he knows none of the spotting rounds have landed on target seems deeply flawed. Does this really happen IRL?

    Can't help thinking if I were calling for artillery on a target, the last thing I'd be doing is saying "yeah go for it" when I knew that no spotting rounds had yet found the target.

  7. I have had precisely the same issue - I know exactly where you mean. I tried about 5 or 6 times to get a half squad through it, including setting waypoints directly either side. Most frustrating...

    Bizarrely though, I think the other half of that squad actually made it through the same gap a few turns earlier - I am not certain of this, as I wasn't monitoring them closely, but they made it into the orchard safely and I'm sure they'd have been cut to pieces if they'd taken the alternative route into it (i.e. running through the adjacent field, round the corner of the hedgerow and back into the orchard).

    It's a really great campaign and I don't blame Paper Tiger (the designer) for this at all - seems to be just a weird bug.

    I have saves.

  8. "Adjust mission" is not meant to be used by the player during spotting; it is there to switch to an entirely new target without having to start the call for fire over from scratch. Observation and correction of spotting rounds is handled automatically between the spotter and the firing unit, assuming that the spotter can see the spotting round impacts (if not there is nothing you can do but cancel the mission).

    OK - I get it thanks. I thought I'd read somewhere that 'adjust fire' was the correct response to spotting round falling miles away - obviously it isn't.

    So the only answer to the situation where you see the spotting rounds falling in the wrong place but still hear the "fire for effect" command, is to cancel the mission and start again? If so, that brings me back to the question, why is the spotter saying FFE when he doesn't see the spotting rounds landing on the target?

    Thanks for the responses.

  9. Hoping some of these might merit some further investigation by the BFC team. I should add before I start that I'm really enjoying the game, notwithstanding these issues.

    1 I'm using very short cover arcs frequently when I want my troops not to engage the enemy but to have more visual awareness than they would under the hide command. From time to time these cover arcs are being overridden to engage targets of opportunity - I'm reasonably certain they are not responding to being fired on (I play WeGo and go over each turn numerous times), but are just arbitrarily ignoring the command. It doesn't happen often but I've seen it a few times, and it's somewhat irksome. Is this a bug or is this expected behaviour?

    2 I'm playing a game in which a Sherman with LOS for a flank shot on a Panther has fired two HE shells at the Panther (both of which hit!). It has plenty of AP ammo for its main gun - is this a bug?

    3 Finally I've had a couple of occasions where a member of a squad or team has become separated by a massive distance from the rest of the squad / team, even though they began in the same place as the rest of the team and were not under fire at any point during the move. In one case a rifleman had somehow got himself to the other end of the map than his squad - I heard firing coming from a part of the battlefield where there was no action taking place, and suddenly I spotted him running through a wheatfield getting shot at by an MG. Weird. Anyone else seen this?

    I probably have saves for most of these.

    Any help / observations much appreciated.

    Thanks

  10. I'm getting some weird aiming issues as well. In one game (in the Road to Montebourg campaign), my Company commander called in an off map arty strike from 3 / 400 yards away and it landed bang on target. Later, using the same asset, a platoon commander, around 150 yds from his target calls in a strike - the spotting rounds falls apx. 200 metres away so I adjust, then the spotting rounds for the adjusted mission are equally far from the target, just in a different spot. The platoon commander has LOS to the target the whole time and isn't under fire - surely he wouldn't proceed with the fire-for-effect command until he sees the spotting rounds hitting the target.

    Any ideas anyone? I have save games.

  11. Are you basing this on the red Xs in the command chain display or on the absence of c2 link icons (mouth and/or eye icon) on a selected mortar?

    No - I'm basing it on the fact that the Company HQ was standing next to the three mortars at the back of the map, none of whom had been or were under fire (thus all 'OK') and the mortars were shown as being out of contact when the Co HQ called up the artillery dialogue.

×
×
  • Create New...