Comrades in Arms Discussion Board

Full Version: The Debriefing Thread
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
lol, funny one rund. Quite intense tho Big Grin
Winter's bone.

Great mission.  Variable had lead us through the patrol area in a wide line formation with Bravo on his right and Charlie on his left. At the Black Rock we encountered some enemys which were soon overcome by flanking them around the crater. in the process of going around the right flank my squad was attacked from the rear by enemys drawn towards the crater by the sound of shots while we were engaging enemys  at our front. I probably should have had someone check our rear at that moment as we had not cleared the area outside the crater yet. When everyone was patched up and the area cleared our patrol continued to the Wardens Hut.  My squad was tasked to set up  in a defensive position on the south west of the objective from where we didn't see the objective itself. insted we saw that there was heavy fighting to our west and Russian choppers taking off.
We were told by HQ that contact to our camp in the ruins was lost and headed back to it running to investigate. After a short breath cather Alfa went to investigate and draw out enemys, Bravo and charlie following with some distance. Alfa spotted some enemys and set up on them for supressive fire while my squad set up to attack them. When Alfa opened up we shot the enemys we had clear sight of and pushed on to the enemys finding the rest of them killed by Alfas fire.
We then were notified of enemys moving in our direction and were told to defend it. Bravo was tasked with guarding the east, where we roughly set up (I had my bearings a bit wrong in my head so i accidentally set up my men towards NE first until Phantom told me that there was a great position to our east on a big pile of rubble). After a while we retreated back to the main ruin from where we were able to defend our position.
At this point Phantom acted as our combat first aider, ammo bearer and runner keeping us supplied with ammo and FAKs and supplying each of us with a M136 launcher (even getting me a replacement after I used mine on that pesky vehicle in the south east).

I don't generally complain about this, it's a game, mistakes happen to everyone, but you really need to try really hard to not pay attention, to acomplish this. And since same situation happened before, need to write this.


Kore is to our west, and we're trying to take it, to the north there is a big hill (other friendly team is somewhere on the top) and they are engaging enemies close by.


Before we move up on Kore, team leader orders team red to move up the hill to take care of those enemies, that order is repeated multiple times to the team, and then transmitted to the other squad, and repeated one more time to them as well, so you really couldn't miss the order that red team is moving up the hill.


But despite that, as soon as we moved away enough from the team, someone from our own team lights us up, killing me instantly (if I didn't saw the tracers, wouldn't even know it was friendly fire), and trying real hard to kill UnNamed, but he broke line of sight with friendlies, so whoever fired couldn't finish the job.


Team blue had good cover, and we were in the open 200m away with our backs turned to blue, even if we were enemies, we did not pose any threat, plenty of time to check with the others since you're already in cover, or fire a couple of warning shots to see if we return fire.


Don't care really who did it, not even upset, just really surprised, and wish not to witness it again! Big Grin
I JIPed into team red right before that order and I really didn't understand we should move on that hill. I think Alias shared that confusion because he didn't move there as well. I was really surprised when I saw Unnamed on the hill. Now, after reading your post, I realize that we had to go there too. However, when we didn't, the leader didn't correct us, and that encouraged me on thinking that we are in the right place and that it's unnamed that has ventured too far off. Being more clear on the order could have helped, but sure, guys, check your fire especially when firing at a unit with its back at you.
(09-04-2015, 12:43 PM)Gwynbleidd link Wrote:Don't care really who did it, not even upset, just really surprised, and wish not to witness it again! Big Grin

Don't know about your situation, but I actually killed Unnamed for a simple case of miscommunication. I was told friendly forces were moving in from the east. We had been constantly attacked from the south, so I went there and shot a guy that I saw hiding behind a bush, which turns out to be unnamed.

Mind you, this was exactly south of our position, not east.

So yeah, apparently there are communication issues, both in actually listening to it as well as giving precise information.
@Variable, Hm who knows, reading your post it occurs to me, it might even be that bug when it cuts off communication for some people, so the shooter might not be completely guilty.


In any case yeah, guys just please double check before shooting, at least people with their backs turned to you.


@Alwarren, yeah I saw that - it was a lot later than my situation. I just accidentally hovered over you two at that exact moment, and since it was out of context, to me it just looked like you're brutally murdering unsuspecting unnamed Big Grin 

But then you explained it on ts, and I realized what happened.
Well, I have to take the blame for this one.

I heard the order given to team red to climb the hill, but i thought it was the hill infront of us towards the city.
Since Alias and Variable was att said hill, i didn't really think twice when I saw two contacts, facing me, close to the squad we were engaging.

I opened up on Gwyn and moved on to Unnamed, who screamed "friendly fire" and I siezed fire and took the blame and  said I'm sorry
I misinterpreted the location of red team since you were divided, my bad.

If it makes you feel better karma had it's course when McGregor mowed me down with an accurate burst to my forehead Wink

Can't say it won't happen again, but I'll have it in mind
No worries Evans, it was a clear case of miscommunication.
@ evans, at least you were low on ammo and i noticed tracers going over me the wrong direction Big Grin

i never noticed that we were being shot from the back before and almost thought i had understood something wrong when i noticed i was alone on that hill.... the missonformation with the south could even have resulted from me telling our leader i was closing in on bravo from the east, i was too busy shooting enemys in the city that didnt like me moving on the hill, unfortunately i had already used my green smoke before so i was unable to mark my position again for bravo

unfortunatly when i tried i was still out of shouting distance from bravo (i had noticed gunfire close from me that sounded like one of our guns), i should probably have swithed to chanel 2 to communicate with them directly
(09-04-2015, 06:19 PM)Evans link Wrote:If it makes you feel better karma had it's course when McGregor mowed me down with an accurate burst to my forehead Wink


Damn, how many ff accidents were there in this mission? Big Grin

Anyway, all good Evans!
(09-04-2015, 08:19 PM)Phantom link Wrote:This is why I drove way ahead... didn't want to wreck the car like last time
-video-
-video-
(09-05-2015, 11:45 PM)rundll.exe link Wrote:Yeah, you didn't really have a choice there.
The point was, you moved the car from the base before we even fully assembled. I wasn't ready, so took me a while to catch up, (I didn't even see you anymore after the start...)  Next time, don't move when not ordered, even if we restarted the mission with the same orders.
(09-06-2015, 08:19 AM)McGregor link Wrote:I was under the same impression
That was a chain of mistakes.
1. As rund says, the lead vehicle on point should wait for an 'advance' order.
2. Once moving, driver on point should make sure he's being followed. Use your rear view mirrors or ask the guys at the back to confirm visual contact with the second vehicle.
3. If eye contact is lost with the lead vehicle, lead driver should be ordered to stop, convoy should regroup before moving forward.

Touch base guys, touch base Smile
Lost Squad

the mission went nice and Smooth.
I was almost about to turn south again when I finally made contact with the lost squad in the extreme NE of the map.
since the ground team reported that they were undetected yet and had only spotted a single hostile squad yet I decided to risk landing without firesupport. The boarding went quite well with only a little incoming fire and we were soon air borne.
just to almost crash....  turns out the search light  is reflected by the windshield even though there is  a partition between the cockpit and the rest of the cabin. I had a white screen for some moments  and noticed that even though we had not crashed and i had pulled back on the cyclic a bit we were dangerously low over the tree tops.
I guess this is the same problem as with reflections on rifle sights even though you can clearly see your own shadow over the whole thing or the reflected moon light we once had on the HUD of a chopper on a lost squad Altis run.
co07 liberation campaign mission 1


Took out all the comm towers with alwarren's artillery support and explosives, second task never ticked, so calling it complete.
Campaign: Pulsate Ion Conspiracies - Shadows of Thirsky

With the benefit of hindsight, I think it would have been better if I'd given the sniper team all our explosives when both teams first met near the 3 Grads, as they were probably ideally suited to sneaking up on undefended Grads and blowing them up, whilst Alpha concentrated on RPG'ing the Shilkas. We didn't start with many RPGs and it took three hits to destroy the first Shilka but we encountered quite a few enemy RPG to the west of the runway and on our way back to our starting point, so whilst we were shooting them and gathering their RPGs the Sniper team would have had something more interesting to do (their spotting and marking targets was vital to the mission though).

Ultimately it may be that the RHS armour bugs make this mission too difficult though.
One thing from last couple nights missions:

Squad/teamleaders/grenadiers: If illumination flares for UBL's (GP-25 for Russian stuff/M203 for US) are available, use them when in contact with enemy if light conditions are poor!

We have had couple of missions now taking place at night with no nvgs. In last nights airbase capture mission I had hard time spotting targets, and it wasn't the foliage this time. I have crappy monitor and not-so-good vid card and playing with gamma feels a bit of cheating. Sure, you can make a guess with muzzle flashes/tracers, but if flares are there, use them.  RHS flares are already pretty good, and now we have serverside add-on to make 'em even better.

Airfield capture mission was pretty epic although 9 Shilkas is almost two AD battalions worth of hardware . Well funded insurgents have all the toys : )  Maybe few less Shilkas might have been better. Solid lead Variable/leachy, unfortunately Shilka shredded team blue badly and I watched bulk of mission from the sky. I liked the sense of combined arms operation, great ambient lightshow and illusion of player team being a part in a bigger machine.

In episode4, the 6-shilka mission, we had NVG's but with rain/nvg mod it might have been better to use flares in some firefights.  Otherwise the mission premise  was good. Simple objectives, close to target. It was fun and solid leading doveman. However it would have been better with..say.. 3 Shilkas, and maybe one patrolling AA-specialist team to send the message about AA- threat home. Like doveman pointed out,  we had to rely for battlefield capture tools and 6 Shilkas is a lot.  Current bug/feature of RHS didn't help either.  In RL Shilka has quite thin armour and it should not survive 3-4 rpg7vs and 1-2 RPG-26s : ) (Or then we just missed and won't admit it. Bit like "Yeah, don't worry guys, the chopper is definetely unarmed - kaboom")Â