equinox137 Posted September 8, 2021 Posted September 8, 2021 (edited) so basically in trying to read through all this, i've come to the conclusion that the targeting pod is of absolutely no use in the Harrier right now. And because of that, you can not use Mav-Es, or at least self-lase, with the Harrier at this point. Is that correct? Edited September 8, 2021 by equinox137 1
Thanatos31 Posted September 8, 2021 Posted September 8, 2021 4 hours ago, equinox137 said: so basically in trying to read through all this, i've come to the conclusion that the targeting pod is of absolutely no use in the Harrier right now. And because of that, you can not use Mav-Es, or at least self-lase, with the Harrier at this point. Is that correct? nope, not as dramatic as you make it appear. it just means you need to spend a few minutes / hours and learning the new flow of how to target with the new E Mav...you can still self lase, just need to incorporate a few different steps. 1 Come fly with us : https://discord.gg/tawdcs TAW CJTF 13 - EU TZ MilSim Squadron Ryzen 5 5600X | 32GB DDR4 3733| ASUS Radeon RX 6700 XT | ASrock B550 Phantom Gaming 4 | HP Reverb G2 | Thrustmaster Warthog Throttle , F16 & F18 grips , TFRP Rudders | Win 10
Krez Posted September 8, 2021 Posted September 8, 2021 10 hours ago, equinox137 said: so basically in trying to read through all this, i've come to the conclusion that the targeting pod is of absolutely no use in the Harrier right now. And because of that, you can not use Mav-Es, or at least self-lase, with the Harrier at this point. Is that correct? The TPOD works just fine and is plenty useful. MAV-E is buddy lase only, like it should be. MAV-E2/L is self or buddy lase. If you have not been keeping up with the changes, it will be like learning it all over again. Procedures and limitations are accurately represented. 4
Rakamora Posted September 9, 2021 Posted September 9, 2021 (edited) Why is mav getting deselected when I go in and out of tpod mode(sss depress) bug or correct as is? Edited September 9, 2021 by Rakamora
Thanatos31 Posted September 10, 2021 Posted September 10, 2021 19 hours ago, Rakamora said: Why is mav getting deselected when I go in and out of tpod mode(sss depress) bug or correct as is? The harrier can only display one "video" feed from a MAV. The TPOD is also a "MAV" for the onboard computer. Hence - its either TPOD feed or MAV feed. Correct. 1 Come fly with us : https://discord.gg/tawdcs TAW CJTF 13 - EU TZ MilSim Squadron Ryzen 5 5600X | 32GB DDR4 3733| ASUS Radeon RX 6700 XT | ASrock B550 Phantom Gaming 4 | HP Reverb G2 | Thrustmaster Warthog Throttle , F16 & F18 grips , TFRP Rudders | Win 10
Vakarian Posted September 10, 2021 Posted September 10, 2021 10 minutes ago, Thanatos31 said: The harrier can only display one "video" feed from a MAV. The TPOD is also a "MAV" for the onboard computer. Hence - its either TPOD feed or MAV feed. Correct. That's not what he asked. You box MAV (still caged) on STRS or EHSD page and you go to find target using TPOD. When you do SS Depress to switch between INS and TPOD designation mode, IRMV gets unboxed so you can't uncage it as soon as you've found the target because you need to go and select MAV first 2
Thanatos31 Posted September 10, 2021 Posted September 10, 2021 ah, thanks ! Come fly with us : https://discord.gg/tawdcs TAW CJTF 13 - EU TZ MilSim Squadron Ryzen 5 5600X | 32GB DDR4 3733| ASUS Radeon RX 6700 XT | ASrock B550 Phantom Gaming 4 | HP Reverb G2 | Thrustmaster Warthog Throttle , F16 & F18 grips , TFRP Rudders | Win 10
HR-Crumble Posted November 24, 2021 Posted November 24, 2021 So how come the 65E self lase was removed?Is it specific to Harrier software as to why because IRL you can self lase from a tpod on the E. Sent from my IN2013 using Tapatalk
Kev2go Posted November 24, 2021 Posted November 24, 2021 On 9/8/2021 at 11:36 AM, Krez said: The TPOD works just fine and is plenty useful. MAV-E is buddy lase only, like it should be. MAV-E2/L is self or buddy lase. If you have not been keeping up with the changes, it will be like learning it all over again. Procedures and limitations are accurately represented. 23 minutes ago, HR-Crumble said: So how come the 65E self lase was removed? Is it specific to Harrier software as to why because IRL you can self lase from a tpod on the E. Sent from my IN2013 using Tapatalk I mean Zeus Does cite a newer documentation..... but the way it seems So with newer software suites in like post 2011? harriers? they dumbed down the features and handicapped things for pilots? dunno why other aircraft dont have these same limitations Build: Windows 10 64 bit Pro Case/Tower: Corsair Graphite 760tm ,Asus Strix Z790 Motherboard, Intel Core i7 12700k ,Corsair Vengeance LPX DDR4 64gb ram (3600 mhz) , (Asus strix oc edition) Nvidia RTX 3080 12gb , Evga g2 850 watt psu, Hardrives ; Samsung 970 EVo, , Samsung evo 860 pro 1 TB SSD, Samsung evo 850 pro 1TB SSD, WD 1TB HDD
Ramsay Posted November 25, 2021 Posted November 25, 2021 (edited) 1 hour ago, HR-Crumble said: Is it specific to Harrier software as to why because IRL you can self lase from a tpod on the E. AFAIK the AGM-65E was an older version which the Harrier couldn't self laze, not sure of the exact reasons. The AGM-65E2 (USAF AGM-65L) is a newer variant developed around ~2012 with a digital semi-active laser seeker and can be self lased. For gameplay reasons the older missile was allowed to be self lased in DCS, now the DCS Harrier has been updated to reflect 2015 specs. both the E and E2 variants are in game. When discussing Harrier capabilities it's important to be specific about the date e.g. Sidearm stock was depleted by ~2000, the TGP was mounted on the wing stations in ~2004 and it was only after ~2012 that the TGP could be mounted on the centerline (same time as the AGM-65E2). If you have evidence of the Harrier self lasing prior to 2012, I'm sure Razbam would be willing to review your feedback. Edited November 25, 2021 by Ramsay i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
HR-Crumble Posted November 26, 2021 Posted November 26, 2021 AFAIK the AGM-65E was an older version which the Harrier couldn't self laze, not sure of the exact reasons. The AGM-65E2 (USAF AGM-65L) is a newer variant developed around ~2012 with a digital semi-active laser seeker and can be self lased. For gameplay reasons the older missile was allowed to be self lased in DCS, now the DCS Harrier has been updated to reflect 2015 specs. both the E and E2 variants are in game. When discussing Harrier capabilities it's important to be specific about the date e.g. Sidearm stock was depleted by ~2000, the TGP was mounted on the wing stations in ~2004 and it was only after ~2012 that the TGP could be mounted on the centerline (same time as the AGM-65E2). If you have evidence of the Harrier self lasing prior to 2012, I'm sure Razbam would be willing to review your feedback.Some great info there thanks!I don't have evidence specific to the Harrier firing an E in self lase mode but I have an AGM-65E document stating it's able to be lased by the firing aircraft itself and it discusses being used on the F/A-18C and AV-8B N/A. Sent from my IN2013 using Tapatalk
Recluse Posted November 26, 2021 Posted November 26, 2021 There is an older thread linked below from when the E2 first came out (and the -F almost went away) that mentioned the E2 has a better seeker and software that allows self-laze. I remember reading that the seeker/software on the E would sometimes lose the laser spot due to its own rocket plume obscuring the own-ship fired laser, which wasn't an issue with the geometry of a buddy lase. The E2 could filter out that interference. I can't find that anywhere, so maybe I imagined it. The link below describes various characteristics of the E2 which probably aid in the Self-Laze capability. In truth, the other DCS platforms (e.g. F/A-18) should probably require the E2 vs. E for self lasing as well https://warisboring.com/the-maverick-missile-is-perfect-for-hitting-fast-moving-vehicles/
HR-Crumble Posted November 26, 2021 Posted November 26, 2021 Here is an excerpt from an official DOD document on the 65E - note the section pertaining to the designator can be the launch aircraft. Under Functional Description. Sent from my IN2013 using Tapatalk
Swift. Posted November 26, 2021 Posted November 26, 2021 6 hours ago, HR-Crumble said: Here is an excerpt from an official DOD document on the 65E - note the section pertaining to the designator can be the launch aircraft. Under Functional Description. Sent from my IN2013 using Tapatalk Can't read the text because it's too blurry, but FWIW I've heard something about hornet not being able to self lase 65Es if it's using Litening but it can if using ATFLIR. So that might explain why we only ever see specific mention of 65L 'adding' self lase capabilities in marine documentation. 476th Discord | 476th Website | Swift Youtube Ryzen 5800x, RTX 4070ti, 64GB, Quest 2
Ghostrider142 Posted March 10, 2022 Posted March 10, 2022 Is this up to date? i7-4770K @3.50GHz; EVGA 1070 8GB Superclocked; 16GB Ram; MSI Z97 Gaming; two Samsung 500GB SSD's in RAID; TrackIR; 32" 2560x1440 Samsung
date7466 Posted August 30, 2023 Posted August 30, 2023 Should AGM65H and AGM65D be able to simultaneously lock two targets, F16 is sufficient
Ramsay Posted August 30, 2023 Posted August 30, 2023 (edited) 3 hours ago, date7466 said: Should AGM65H and AGM65D be able to simultaneously lock two targets AGM-65H and AGM-65D aren't in the USMC AV-8B's inventory, they use AGM-65E/E2 LMAV and AGM-65F IRMAV versions. The RL USMC AV-8B Master Flight Syllabus Guide make no mention of ripple firing Mavericks. AFAIK to quickly fire on two targets (in a modern scenario) - you'd create TOO mark points or target points and switch between them. 3 hours ago, date7466 said: F16 is sufficient I suspect the F-16C's ability to lock separate IRMAV targets per station and ripple fire is an older technique that pre-dates the AV-8B's TPOD (~2004). As said, AFAIK there's no documentation of the AV-8B ripple firing IRMAV's. Edited August 30, 2023 by Ramsay Spelling i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
date7466 Posted August 30, 2023 Posted August 30, 2023 However, it is practical to simultaneously lock two targets before entering range AV8B What's wrong with the inability to launch when the gun pod is often aimed at the target
gulredrel Posted August 30, 2023 Posted August 30, 2023 2 hours ago, date7466 said: AV8B What's wrong with the inability to launch when the gun pod is often aimed at the target Do you mean IR Mavs do not launch, even if crosshairs are collapsed and locked to the target? I also have this happen lately and don't know why. Sometimes re-cage, un-cage SSS FW, slew and TDC depress to lock the same target again works and I'm able to fire. Don't know if it has something to do with launch constraints regarding direction and the position of the seeker looking? But I'm no where near gimbal and pressing the pickle button will only play the beep (Tone selected with the OSB button) but the missile will not come off the rail.
date7466 Posted August 30, 2023 Posted August 30, 2023 34分钟前,gulredrel说: Do you mean IR Mavs do not launch, even if crosshairs are collapsed and locked to the target? I also have this happen lately and don't know why. Sometimes re-cage, un-cage SSS FW, slew and TDC depress to lock the same target again works and I'm able to fire. Don't know if it has something to do with launch constraints regarding direction and the position of the seeker looking? But I'm no where near gimbal and pressing the pickle button will only play the beep (Tone selected with the OSB button) but the missile will not come off the rail. i mean the machine gun pod is often aimed at the target is unable to fire, leaving the target and being able to fire.
Eugel Posted August 30, 2023 Posted August 30, 2023 15 minutes ago, date7466 said: i mean the machine gun pod is often aimed at the target is unable to fire, leaving the target and being able to fire. Check your throttle setting. The gun is powered by bleed air from the engine. If your engine RPM is too low, you can´t fire. 1
gulredrel Posted August 30, 2023 Posted August 30, 2023 Derailing the Mav thread but yes, to fire the gun at least 70% rpm is required down low as the mechanism uses bleed air from the compressor section. At higher altitude rpm must even be higher.
date7466 Posted August 31, 2023 Posted August 31, 2023 12小时前,Eugel说: Check your throttle setting. The gun is powered by bleed air from the engine. If your engine RPM is too low, you can´t fire. Thank you very much. This question has been confusing me for a long time
date7466 Posted August 31, 2023 Posted August 31, 2023 2023/8/30 PM5点28分,Ramsay说: AGM-65H and AGM-65D aren't in the USMC AV-8B's inventory, they use AGM-65E/E2 LMAV and AGM-65F IRMAV versions. The RL USMC AV-8B Master Flight Syllabus Guide make no mention of ripple firing Mavericks. AFAIK to quickly fire on two targets (in a modern scenario) - you'd create TOO mark points or target points and switch between them. I suspect the F-16C's ability to lock separate IRMAV targets per station and ripple fire is an older technique that pre-dates the AV-8B's TPOD (~2004). As said, AFAIK there's no documentation of the AV-8B ripple firing IRMAV's. Shooting two at the same time, why doesn't the hovering machine gun function
Recommended Posts