Grinch

I would imagine that's a bug as the Normandy has a Mk41 vertical launching system (only plausible thing I can think of). The current version is 1.2.6. Unless there's a good reason you want to play the version that you are, I recommend patching.

Wags, can we expect this iterative process to remain as free patches or should we expect it to cost money similar to the Blackshark 2 upgrade?

Eno, I'm sure you're aware that this isn't strictly a CA issue. This happens quite frequently with groups that are simply moving along assigned routes, especially when assigned "on road" and when reacting to enemy fire--even with no CA control.

People are probably voting no because they realize that producing this module would require assets devoted to a product that would be better utilized on something they would enjoy more. Would you rather have a T-2 Buckeye or an Mi-24 Hind? Polls probably would have been useful there too. Having a poll with just a "Yes" isn't much of a poll.

Anything that has PGM capabilities and can punch coordinates in after start up. It's rough designing maps for eastern bloc forces that aren't stupid easy to find targets.

The proper answer is: we don't know. Fire support coordination nuances are largely not in game, such a Free Fire Areas (FFAs), Fire Support Coordinating Lines, and your frequently heard term "kill boxes." Coordination with JTACs, FACs, FAC(A) / AFAC is required for Close Air Support (CAS). The necessity for CAS procedures (i.e. 9 lines) is based primarily on the enemy's proximity to ground forces. Depending on the location of forces involved in the mission, it might not even be considered CAS. In these cases, the tactical mission is called Deep Air Strike (DAS) or air interdiction and the procedures change dramatically. Generally speaking, before even contacting a JTAC directly, you would be routed through various air officers before and get an AO update or two before getting passed over to a JTAC. During these conversations, you would get routing information, air threat information, friendly air traffic info, and your assigned holding position and altitude block. What does this all mean in game? It means it's not simulated. I usually just hit the assigned target at the assigned way point, and if I have fuel and ordnance left over, I contact a JTAC to see if he has any work for me. Unless of course the mission has me tasked to directly support a JTAC, in which case I'll contact him before doing whatever.

What's your bandwidth estimate without voice comms, per person?

So here's my suggestion for F10 view modes. There needs to be another F10 view mode option (like fog of war) that allows the ground commander to see enemy units and target them based on intelligence, surveillance, and reconnaissance assets. This same F10 view doesn't give a fog of war view to non ground commanders. The purpose behind this is to prevent pilots from using F10 to spot helicopters, other aircraft, or ground targets. Without fog of war, combined arms is more or less a waste. There's no happy, middle ground.

Half off might be worth it if you're using it in multiplayer. Full price: a resounding no. It's nifty, but I don't think its full potential is even close to being achieved.

Any of the ED testers out there have any input?

Yes. The map was built on a separate computer, moved to the server, renamed, and the trigger updated to reflect the renamed file (and therefore saved in ME on the server).

So here are a couple bugs I've never seen before. I have a MP mission that is set to load the same mission after 5 hours via trigger. Upon reset, all static units (SAMs, ground forces, etc.) do not spawn at all. Only groups with waypoints upon mission start spawn and begin their routes. If the map is loaded manually, everything spawns as it should by mission design. Continuing the trend of weirdness, some units that are supposed to spawn later after triggers are initiated, spawn upon start. For example, an AWACS that is set to spawn after a certain condition is met, spawns at start without that trigger being met. It appears on the F10 map, moves, but cannot be reached via the radio commands. Anyone seen this stuff before?

This makes me wonder if "bang-bang" guidance is modeled. ED Testers? Edit: Nevermind, I can go watch a LGB in F6.

I would imagine a multi-million dollar pod would take all of these into account and do some basic trig to give you the yard stick measurement.

To follow up on Atalia's post, final attack headings are also imperative if using any sort of laser, whether it's IR, such as an IZLID for marking targets, or a PRF-coded laser. In these cases, JTACs/FACs, will bring the aircraft over their left or right shoulders to ensure ordnance isn't dropped on the friendly end of the beam. This is referred to as a laser basket. On a related laser safety side note: notice that the AI JTACs at night will actually 'snake' the IR pointer, and give the brevity code for it over comms. This is an actual technique and the end that wiggles is the target.