Jump to content

Recommended Posts

Posted

I came across something puzzling the other day. I’m not very familiar with Tacview, but I did a test mission with the aim-54s. I shot the missiles from various distances at various targets to test the enhancements of 2.5.5. 50, 60, 70, 80nm shots. What’s surprising is viewing it on Tacview is about ten miles short of what I thought I was shooting in range to target. Is this normal for Tacview? Or is there something really wrong?

 

I’m sure I shot at those distances, because the data readout was showing it as well as the dashed 20nm scale backed up the readouts as well.

 

 

Sent from my iPad using Tapatalk Pro

Win 10, AMD FX9590/water cooled, 32GB RAM, 250GB SSD system, 1TB SSD (DCS installed), 2TB HD, Warthog HOTAS, MFG rudders, Track IR 5, LG Ultrawide, Logitech Speakers w/sub, Fans, Case, cell phone, wallet, keys.....printer

Posted

Radar mileage

 

Here's an example. I launch missile approximately 60 miles according to radar display. Nothing less.

 

 

 

attachment.php?attachmentid=211728&stc=1&d=1560200817

 

As you can see here, Tacview is saying the target is less.

 

5d2fa34d60434b17033d5412be875f6e.jpg

Win 10, AMD FX9590/water cooled, 32GB RAM, 250GB SSD system, 1TB SSD (DCS installed), 2TB HD, Warthog HOTAS, MFG rudders, Track IR 5, LG Ultrawide, Logitech Speakers w/sub, Fans, Case, cell phone, wallet, keys.....printer

Posted

Maybe tacview is giving you ground distance and the radar is providing slant range? Depending on the altitude difference, this could be quite significant.

 

 

 

A second thought is that the AWG-9 has some relative uncertainty in determining the distance. In this case it is about 8% which seems to be quite a lot though

Posted (edited)

Radar mileage

 

Here's another test at 80nm? launch.

 

 

attachment.php?attachmentid=211738&stc=1&d=1560219971

 

 

b6549e46be4329d2f5ff0eaf230fc239.jpg

 

 

Then:

 

 

attachment.php?attachmentid=211739&stc=1&d=1560219976

 

e68616257cdbc51d51db3d65d735d0fc.jpg

Screen_190610_211622.thumb.jpg.74adae8f64c70ca29f1c3a2d953765bf.jpg

Screen_190610_211639.thumb.jpg.501b78ccd6eacc4950f133623feaa533.jpg

Edited by Eagle7907

Win 10, AMD FX9590/water cooled, 32GB RAM, 250GB SSD system, 1TB SSD (DCS installed), 2TB HD, Warthog HOTAS, MFG rudders, Track IR 5, LG Ultrawide, Logitech Speakers w/sub, Fans, Case, cell phone, wallet, keys.....printer

Posted

closing speed is kinda high and it takes about 3-5 seconds after pressing trigger to feed AIM54 with all needed data and lauch, so if you are shooting at fast closing target at 60nm, in reality, you are shooting at +- 55nm

Posted
closing speed is kinda high and it takes about 3-5 seconds after pressing trigger to feed AIM54 with all needed data and lauch, so if you are shooting at fast closing target at 60nm, in reality, you are shooting at +- 55nm

 

 

 

Umm, I don't think so. The picture is taken right after I heard the release of the missile (countdown on TID), but before the sound of hearing the turbulence from the missile. Both pictures are from the same exact moment in time. Last I checked this isn't the space shuttle.

 

 

Sent from my iPad using Tapatalk Pro

Win 10, AMD FX9590/water cooled, 32GB RAM, 250GB SSD system, 1TB SSD (DCS installed), 2TB HD, Warthog HOTAS, MFG rudders, Track IR 5, LG Ultrawide, Logitech Speakers w/sub, Fans, Case, cell phone, wallet, keys.....printer

  • Recently Browsing   0 members

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