Jump to content

Recommended Posts

Posted

A question about bullseye calls for ground targets.

 

In a previous patch ( I believe it was 1.1.1.1) there was a user mod that fixed problems that apparently resulted from magnetic variation not being incorporated into bullseye calls -- as a recall "SPEED" was responsible for this. This worked beautifully until the game was patched to DCS world 1.2.0 and since then the fix hasn't worked. So my question is - does this remain an unresolved issue, or am I improperly setting up the CDU (i.e. is there a place to take magnetic variation into account) to accurately calculate bullseye offset calls from an AFAC or AWACS?

 

If anyone would be willing to weigh in on this I'd appreciate it.

I used to find these calls incredibly useful for finding threats, but for now they are only noise.

 

Any help or insight would be appreciated. :book:

Posted
Still useful, to me. Just entered an armor tally at bulls 55 for 7, entered into cdu, aimed tgp at new markpoint, bingo, armor right where it was called out.

 

Hmmmm... ok I'll have to try again. Tried it last night after the 1.2.1 patch and ended up looking onto a hillside ~ 1.5 clicks off target. Bullseye was approx 10 away from target.

 

I'll give it another try.

  • 1 month later...
Posted

I noticed the same problem! I place enemy units at bulls 74 for 35 at a mission waypoint. Friendly AI calls them correctly at bulls 74 for 35, but when I hook the waypoint, it shows in my TAD as bulls 68 for 35. Off by several miles.

i5-2500K @4.2 GHz | 16GB RAM | GTX460s in SLI | 1TB HDD (internal) | 1TB HDD (external via eSATA) for FRAPS recording | Thrustmaster Warthog HOTAS | Saitek Pro Flight Combat Rudder Pedals | TrackIR5 | 50" LG monitor

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...