witness_me

stand-off munitions can and are engaged by surface to air weapons, typically though you wouldn't use a patriot for a bomb, rather you'd shoot down the airplane long before it gets within the 8-mile range required to lob a gen1 paveway for example if somehow you end up with an airplane right on top of you dumping bombs or an incoming artillery round etc, the munition would then typically be engaged by a point defence system, e.g. a centurion or a mantis or pantsir etc

a mate has gathered data for detection ranges for all SAMs, airplanes etc for all modules and created some kneeboard illustrations for me you can place an awacs in an empty map and fly towards it, once you see your rwr light up hit f10 and check the range

you're in luck! you can buy your own unlimited supply of sd10s for just 79.99$ !!! :thumbup: here: https://www.digitalcombatsimulator.com/en/shop/modules/thunder/

145-150nm i think - more than the range of the missile

same here - they just seem to fly to random places? we came up with a story about how it's all ecm lol ok about the LD10's - it might actually be a bug/exploit :P but here goes anyway - if you lob ld10's at one (we set them to expert a.i. not sure it matters) quite often they'll turn their radar off, well sometimes they drop to the deck and take about half an hour to turn their radar back on again :P sometimes they even stay on the deck or something like 8k ft till a server restart...

i try to keep it realistic so about 80nm or less when launched at ground skimming mode or 105 for high altitude (or less)

i was under the impression oap mode should work regardless of the munition type equipped? maybe not right now because it's EA, but oap can normally be used for navigation, dumb munitions etc

i'm one of those people - i've noticed the same behaviour against 120 c's in all my modules or even against 54's, it's intermittent and since it's already reported to bignewy i'm not all that fussed. People have been reporting rwr issues about every module with every missile combination lately - check Coxy's thread for example without a tacview file nobody can tell what's going on a good test would be to get an f18 side by side with a jf17, headed towards another pair of f18/jf17's and lob an aim120c at the same time you lob an sd-10, straight at them in mad dog mode even when i'm looking at my own tracks, whenever i "think" i got a late warning (i'm not recording videos of my flights so can't tell for sure), i'm never sure if it's an actual dcs issue or not as based on heatblur's analysis of how rwr's work there's all sorts of factors like radar strength, angle of approach, altitude of approaching missile, existing radar noise, when and under which conditions the missile would turn on it's radar etc etc :confused: another thing to note: if you get shot at close range, a missile might be doing 2-2.5K kts. That's 4.2K ft/sec or 1.3Km/sec

i don't think they have a progressive zoom apart from wide/nar fov - never seen it mentioned anywhere ietther - e.g. chuck's guides or youtube etc they're pretty annoying to aim as well, esp when you need to make a 2nd pass etc :P

:megalol:

hey i think i might know why i'm not getting this bug anymore then - it doesn't seem to happen if you're exporting your mfcd's more reasons as to why mfcd exporting is a must have :P

p.s. you only need an unobstructed line of sight to the missile's rear end during the terminal guidance stage, for the first part of the flight it doesn't matter i typically use akg's for early warning / long range radars, if these go down you can get rid of anything else in terms of SAM sites etc using LD10s from well outside their range. The akg's are also good for static targets and/or ships but they're not difficult to shoot down

send a couple of ld10's towards the awacs if you have an opening or a couple of akg if people actually bother protecting it. The akg's can be shot down but hey that's their purpose, an early warning radar is a top priority target you can guess how far it is/approximate vector, based on when you see it in the rwr (fly as high as you can) otherwise try to find some sneaky approach it should take quite a bit for interceptors to get to you - the akg has a range of about 120nm

haven't tried this myself, but in "real life" it needs an unobstructed LOS, if it works with the airplane behind a mountain it's a bug/exploit

the active waypoint can be whatever you have selected as active :P typically a waypoint from the FP-A (flight plan A) waypoints Loopback has mentioned in the past: "SPI logic implemented: radar、WMD、HUD designator in point/area track mode, will set SPI for WCS. these 3 'sensors' are exclusive, any one of them set SPI, will command the other 2 to break lock. if none of these 3 sensors set SPI, you current wpt became SPI(default UFCP page, line 1, number right) wpt#40 is reserved for WCS SPI. if there is SPI set in WCS, WCS will rewrite wpt#40 coords."

search for T3 (T3_Forward / Down /Backward) the text is "T3_Forward: Speed Brake On"

@AeriaGloria i was referring to this: http://himg2.huanqiu.com/attachment2010/2012/1126/20121126090921886.jpg :bye_3:

you can see s1/s2 in the first screenshot, mms (master mode switch?) is T1 (forward/centre/backward for a/a, nav, a/g modes respectively) axis setup here (t6 antenna elevation is also used to zoom in/out the tgp):

the rwr's are busted in multiplayer for pretty much every aircraft. ED is looking into it e.g.: https://forums.eagle.ru/showthread.php?p=4155871#post4155871

it seems PAF purchased the cm 400 akg though, which has gps+image recognition guidance (similar to a tomahawk, only much faster - apparently during terminal guidance it can hit 5.5mach) - maybe DEKA can introduce it at some point as a fire and forget standoff weapon :pilotfly:

aviation week in an article re the zhuhai 2010 expo mention it only has ins navigation, so it's no good for long range precision strikes, hence the mitl terminal guidance there are other cruise missiles with radar guidance and/or gps, but i don't think PAF procured any of those

didn't notice a difference in fps - there shouldn't be a difference really, i definitely recommend exporting the mfcd's to another monitor if you can - it's a game changer not having to change views on your main screen (trackir or not), doesn't even have to be some decent monitor - whatever you can get your hands on would work just fine and if it's some trash monitor from 10yrs ago it'll probably be closer to the real thing than something new :P

they should be - here's my thog settings for the jeff, hopefully they'll save you some time - some things are set to axis's (tdc movement, radar antenna/pod zoom etc)

hey Tiger - have you tried disabling the automatic transition to the next waypoint when you're in proximity of the current waypoint? if you're within some distance from a waypoint the jeff by default will automatically move to the next one (i think it's around 2nm?) auto: manual:

this was a little while ago, so 2 weeks from now i guess? :P