|
Aivlis -> RE: Operation Reclaimed Might v0.95 (12/10/2015 10:56:59 AM)
|
Ok, let's try another take at feedback. The Losses and Expenditures log is now lost, so take my word that I only lost the Fencer E to the I-HAWK in an incredibly lucky shot, while wiping almost everything on the map save for a few secondary targets around Raqqa (turns out it's almost out of range for the Frogfoots and totally out for the Hinds, I cannot into measuring distances, apparently). Score was 415 (Triumph) if I recall correctly, mainly because I avoided previous mistakes like tangoing with MANPADS in anything but Su-24s at afterburner speed.
Some more detailed feedback:
0. Cruise missile mission is still not launching... maybe it has something to do with the WRA? I have tried tampering with the fire rules and can't get them to launch, maybe a bug report is in order.
1. Civilian ships are set to 0 knots, manually.
2. Civilian side needs to have it's "Collective Responsibility" flag unchecked, and the Russian side needs to lose the "Can Auto-track Civilians" flag so the player can't immediately tell if a unit is a target or not.
3. I appreciate you adding in a Civilian and Turkish side, but as of now they don't add much, as they are totally out of the theater of operations. I was suggesting something more along the lines of having unidentified civilian or third-party neutral units near the strike zones, encouraging target identification (is that an IS technical on the road to Idlib, or is it Ahmed taking his radishes to the market?; are the radar contacts near Raqqa MiG-21s or did the US forget to inform us they'd be flying in the area?).
4. The Scud detected event tells you what the unit is even if you don't have a positive ID, consider construing this as SIGINT/SF on the ground/Syrian intelligence sources being able to use your new partial data to fully ID the TEL for you based on what they already know (maybe with a small delay), or something along those lines. If you want, you can then use this LUA line to set the Scud to "Auto-Detectable"
quote:
ScenEdit_SetUnit({side="Islamic State", name="Whatever_your_Scud_is_named", Autodetectable="yes"})
5. Good job on finding there was a thunderstorm that night, but reading the METARs for Aleppo and Basel International (no, the IS isn't kind enough to publish METARs for Raqqa) I found there were only scattered (3-4 okas) to broken (5-7 okas) clouds all over the place, with cloud base at 2000 to 2500 ft. AGL. Consider dropping the cloud layer to light or breaking it into two so the Fullbacks have to descend into the threat range of older SAMs to lase, but have some space left to release.
6. Minor: Hind loadout should maybe be the one without a troop compliment, unless you want them modelling readiness for a CSAR mission.
7. Minor: all the Fencer Ds share "White #" callsigns, even different models. Not sure if this is intentional, but it gets confusing at times.
I think that's all I had written yesterday. Overall I think it's looking good; you can polish some last bits and release it, or broaden it in depth by adding further events, like having strikes on the C^3 centers affect the IS response (see Baloogan's videos for some ideas on that, if you haven't already); off the top of my head I can think of the MiGs being vectored toward your aircraft if the Comms centers aren't taken out first and foremost, or having a chance that the SAMs in a given site will panic and turn their radars on if bombs start falling on nearby units (this can be good or bad, depending on how careful the player was with their bombing run and SEAD mission planning).
I hope you find this useful.
|
|
|
|
