Model98

The Texture For AGM-65A Is Actually For AGM-65B . The Difference Between The Two Models Is Mainly The Dual FOV ( Wide/Narrow ) Seeker For -65B as Opposed To -65A Singular Wide FOV . To Visually Identify These Two From Eachother As -65B Is Essentially a Modified -65A The Text " Scene Mag" Short For " Scene Magnification " Is Written Just Behind The Seeker Head of -65B and AGM-65A For F-4E Also Has This Text On It , While It Shouldn't . AGM-65A Maverick

Control Monitor Panel Test Knob Has One Too Many Settings AND Dot Balance Mode Is Also Wrong . “ Dot Bal “ Should Be Springloaded and Jump Back To “ Test 0 Mode “ When Released Which Currently It Doesn’t . between “ Dot Bal “ And “ Test 9 “ There Is a Selectable Position/Mode That Shouldn’t Be There Indicated By Red Circle In Picture Below , The Dimension of Panel Also Must Be Revised on another note , is BIT 0 For Aim Dot and Range Rate Calibration Implemented ? I Cannot Get It To Work and For DSCG BIT The 8 Shades Only Appear When Radar Is In Operate mode .

The Problem Is Specific To GBU-31(V)3 AND (V)4 JDAMs And GBU-24A/B AND B/B LLLGB PAVE Way Bombs That Utilize BLU-109 Penetrator Warhead . Available Fuses In DCS For This Munition Are As Followed : FMU-139 FMU-143 FMU-152 JPF However Based On -34s of F-15E , F-4E , B-52H , NAVY NAVAIRs and etc None of Them Mention FMU-139 For BLU-109 , I Assume That BLU-109 Can Use -139 However Due To How FMU-139 Functions It Has No Use For BLU-109 FMU-139 Has Delayed Action Function BUT It Won't Switch To Delayed Mode Unless It Is In High Drag Mode , On Ground FMU-139 Both Low Drag and High Drag Arming Time and INST/Delayed Action Must Be Set , Choosing "X" For Low Drag Will Dud The Fuse As Soon As It Is Activated By Initiator , It Doesn't Have Any Delayed Action In Low Drag Mode and In Order For FMU-139 To Switch To High Drag Mode To Use Its Delayed Action Is , It Have To Sense Atleast 2.3G's of Deceleration For At least Duration Of 1 Second Indicating Deployment of Retards . However Neither JDAM Nor Paveway Are High Drag Bombs So It Won't Switch To High Drag Mode Thus No Delayed Action Which Defeats The Purpose of BLU-109 . FMU-139 Should Be Removed For BLU-109 Equipped Munitions In DCS The Upper Half Of Face Plate Is For Low Drag Arm Time Settings , as You Can See No Delayed Option Available and The "X" In Picture Is The One Mentioned Earlier , The Lower Half Is High Drag Mode That Has Instant or Delayed Function ( Just For Preventing Any Misunderstanding , The "Interlock" Button In Lower Half As Part of High Drag Function Marked By Red Area Is a Safety Mechanism To Prevent Accidental Use Of 2 Sec Arming / Instant Action For High Drag Mode , The Button Must Be Pressed To Rotate The HD Mode Knob to This Setting .)

The BLU-107s On MER Position or Dimensions Must Be Wrong The Aft Mounted BLU-107s Nose Is Inside Front Mounted BLU-107s Base . There Should Be a Bit of Space Between Them BLU-107/B Durandal Mounted On MER of a USAF F-111

I Reported The BALT STBY Flag Bug In IG To Heatblur and Heatblur Fixed The Issue (And I Thank Heatblur For Quick Fix) but Now Both Cockpits BALT Have Bugged , The 3 Position " Reset-STBY" Switch Will Not Spring Back to Neutral Position and Will Remain On Reset or STBY Front Cockpit BALT Stuck WSO BALT Switch Stuck as well

One Bug That I Have Encountered Since Day One Is , F-4 AI's Nose Wheel Steering Operates In Opposition of Rudder And Out of Sync , When F-4 AI Slightly Rotates Its Nose Wheel To Turn Left , The Rudder Almost Instantly Slams To The Right and Vice Versa Like The Pic Below , This Does NOT Happen With Client F-4s AFAIK And I Didn't Find Any Thread About This Bug So I Made One .

PhantomE

Just to be sure i flew another mission this time facing the 30N6’s Dish No , both Radars that were actively searching ( 64N6 and 96L6 ) interfered the only radar that wasn’t active , The 30N6 Engagement radar even from different angles didn’t cause any interference ( The Line on the left is where 64N6 Is and the one on the right is where 96L6 and 30N6 are )

I don’t think this would be the case but i will give it try since i wasn’t facing the other radar in that site ( the 30N6 ) I believe this is interference as it has been seen before in SAR Images ( irl , MIM-104’s MPQ-53/65 Interfering with Sentinel-1 Radar which both of them work in C-Band and a giant X Appears on the image https://fas.org/publication/an-x-reveals-a-diamond-locating-israeli-patriot-batteries-using-radar-interference/ )

There is a Radar To Radar Interference while In HRM When there is a SAM Active In the area where APG-70 is mapping I really liked this attention to detail that another radar could interfere with HRM Image but here is the nitpicking part ; the radar that was interfering with APG-70 was S-300’s 64N6 Big Bird ( Ive attached both the HRM Image and TPOD Feed , you can see the 96L6E Cheese Board Radar because i’m using SAM Pack Mod , which I believe is re-skin of 64N6 as it shows up as “BB” on RWR Which means 64N6 and even if the modder had in mind that 64N6 and 96L6E Work in different bands which i doubt and utilize that in the mod , still I shouldn’t have any interference because Cheese Board work in C-Band “ APG-70 is a X-Band Radar 64N6 works in S-Band They Are two different bands As far as i know and understand these two cannot interfere with eachother and when i tried to change my radar’s frequency/Channel i still got the Interference I’m enjoying F-15E and as matter fact was very amazed and happy to see this attention to detail hope DCS and Razbam Fix This