ngreenaway

It should be in your savedgame/dcs directory in the mission editor folder Did you just migrate feom open beta to stable or vice versa? Or have both on your machine ?

Its not that I didn't know how, or that I felt it was difficult . Its that Im not interested . Hope you find the answer you're looking for, but I don't know that there is a definitive metric on completion, as everyone will likely weight the inclusion or omission of varios systems differently

I don't typically bother digging into someone's profile when replying , fwiw tge post was similar enough to the typical "which plane should I buy next" message that it was easy to accidentally infer you were looking for advice on a module

A10c would likely fit that bill, but keep in mind its had much more time to mature I would suggest you consider what you'd like to do, or what experience you'd like to have, and fly that. As someone who owns all 4 of those i can say an incomplete plane can still be very enjoyable, as long as it includes the systems that fit the mission profile you'd like to do If dog fighting is what floats your boat, it doesn't matter how complete the hawg is- you're not gonna be very effective , for example

I'm pretty happy with no roadmap . I unironically enjoy a certain degree of opacity

Yea, but how dare you like a thing differently than other people who like that same thing!

there are still back& side lobes to contend with. they dont create tracks for the operators, but might show up on a rwr

Partly correct...and also, partly incorrect. A radar isn't going to detect something that lacks an RCS, however that's not the entire story. Just because a radar can see something , that doesn't mean the system will classify it as a threat or present it to the operators for consideration . Radars by necessity filter out a lot of stuff in order to only present probable targets, otherwise you'd see all kinds of crap -including ground traffic and spurious returns - on the scope and it would be much harder to discern what's engageable. Some of these filters include trajectory and speed. If it doesn't meet thresholds, it may get filtered out or classified as a different type of target. A bomb may come up as an "unknown " slow mover track type. The operator would have little reason to consider it a threat Additionally , the fast mover that delivered the bombs makes for a much more compelling target. RCS makes sense for CIWS like C-RAM, but outside of that I can honestly say that in the 10+ years I spent in air defense, never once did the idea of engaging a dumb bomb with a SAM come up

CE-II armed with......itself

A system will slew when commanded to by the icc. It won't simply pick up an STL arbtrarily. It also won't slew with birds in the air. With targets on scope, whatever is being defended by the STL had better be more important than PTL defended assets If you have access to a hard copy of tm 9-1430-600-10-1 or this: http://link.sfpl.org/portal/Patriot-crew-drills-for-Engagement-Control/DPpVxk7T5NU/ I may be able to point you to appropriate spots

Thats one piece , but theres much more to it. Unfortunately , the icc manual is publicly available but not the ECS one which is one thats really pertinent here. In most cases they are identical , an icc is physically nearly identical to an ecs, so it stands to reason the manuals are as well, however, youre referencing the procedure for the icc to command a battery to change to another target line. The procedure to actually slew a battery is in the battery level manuals which are unclassified , yet not publicly releasable (same with the current icc manual, yet google books has the 1982 edition , if i remember correctly ) There are other considerations which are contained in crew battle drills, site setup , and air defense planning . I wish i still had my reference library , so i could point to exactly which manuals covered what , even if they werent available for others to look at

let me shed some light on this, if i can. i spent 11 years working patriot as a 14E in 4 countries and two states - i worked a variety of positions from fire control operator, system maintainer, and towards the end of my career, a patriot master gunner. I am very familiar with both pac2 and pac3 systems. first and foremost, in an air battle, when you have targets on scope, the radar would never slew during an engagement. in other circumstances, the radar would never slew unless it had been given orders to do so from higher up the kill chain. when it does so, it would do it to a predifined STL. normally this would be done for situations such as providing target coverage for a sister battery in the event of a system failure , pre-planned maintenance down time, et cetera, and then only if the sister battery's defended assets were a higher priority than the ones on the PTL. there are other situations, but its rare. regarding the 100 degree cw and ccw train limit for STL, heres the thing, the radar shelter itself can rotate far more than that. Prior to radiating, one of the duties of the fire control crew is to look out at the van and physically verify that the radar is pointing where it should, because it is possible for the radar (in the event of certain system errors, its conceivable but i never saw it) to be pointing in an unintended direction - including directly back at the ECS. so what then is the true STL train limits? it really is somewhat site specific. let me explain: the system can *not* fire from a launcher outside of radar coverage. normally, launchers are placed in a fan to cover the PTL optimally, +/- a bit . when you slew a radar to one side or the other, inevitably you will have launchers fall out of coverage. if you slew too far to one side or the other , you risk having few , if any, eligible launchers to use. But wait! theres more! it *is* possible to have a remote bank of launchers. these could be attached to a CRG+AMG , or they could even be another sister battery's launchers, however theres certain constraints on what can be used as a remote bank. Along with Hawk interoperability, it was something we had the ability to do but in practice never did during my time. the 50 degree cutoff limit is sort of a nominal thing, its given as if PTL was 0, STL1= 100 & STL2= 260 . its possible, generally theres a greater cutoff zone than that, again, thats something that both mission & site specific. Under no circumstances would the radar slew to track or follow a target. there is a very simple reason for this. i dont believe its information that needs to be protected, but because i cant find an open source reference to explain why, you'll just have to take it on the basis of faith. if you saw the reason, you would understand. as for launchers slewing its a bit complicated and perhaps confusing to someone who's never spent a lot of time with patriot, because the launchers absolutely CAN and DO slew, its part of setup (same with radar) . however, during operation, they only slew when the entire battery is commanded to aim in a different direction, however during normal operations and engagements, they do *not* slew how is it supposed to work? like i said, the launchers never slew, but theyre placed in a fan in front of the radar, with some launchers placed turned slightly to the left or right, some straight ahead. When the engagement command is given, the RWCIU (Radar/weapon control interface unit) compares the azimuth-to-target from the radar and then selects the launcher with the most favorable angle to target. after launch, the missile does its greatest correction to target during the initial turn during this whole process, neither the radar nor the launchers slew at all here's a war-time launch. you dont see the launcher at time of motion, but just prior to launch you can see the launchers are static: https://www.youtube.com/watch?v=K04JaCHIURM of course, this is a pac-3 system, which we cant have with the pac 2 radar in DCS

its true, in many ways the systems dont work as in real life, but i pretty much expect that. theres a lot of specialized info thats either not available, or doesnt make much sense outside of the air defense field. the amount of work needed to get them all right outstrips what we can reasonably expect them to spend on a lower priority such as this . "reasonably well" should be good enough

Really depends on the sam system , and in the one i worked with: how its configured , whether the operators have slow movers filtered out, what the terrain was behind you (its possible to be masked by terrain while completely in the open)

yea, theres a fundamental flaw in that premise. a patriot wouldnt be able to engage a bomb. not all returns are classified and presented to the operator, and for good reason. for ED to allow it would be unrealistic

no, it shouldnt. first, theres only two vehicles used for patriot reload, neither of which is in DCS. theres the GMT, or guided missile transporter, and theres the forklift. units will have a single gmt assigned, and sometimes a forklift..but not always. 1 hour for reload is realistic. if there are more than 4 spare missiles on site, it will take awhile to finish reload one launcher & start reloading another. the GMT would have to go to the holding area, offload spent cans, and load fresh ones before heading out. a forklift on its own isnt very efficient unless missiles are prepositioned next to the launcher. additionally, a site is limited by how many reload crews it can send downrange at one time. could you game the system to exploit loopholes in DCS? yes, if you dont care about realism, sure- its your game Regarding the m818, once upon a time (the only photo i saw of it was from the 70s), the launchers prime mover was a 5-ton bobtail. That may be why you see the m818. I have personally seen a radar being pulled by a highly modified very short wheelbase 5-ton based tug at an airfield once. DCS needs a hemmt bobtail . The m983 is the correct prime mover, and there should be 1 per launcher and 1 additional for the radar (which is mounted on the same trailer)

I tried it twice last night. I'll give it another shot tonight if I get a chance

Trying to play thru mission 1. As I'm moving thru start procedure, some vehicle comes speeding down the apron and hits the front of my aircraft without even slowing. Then the instructor accuses *me* of damaging the aircraft. Can't even start the mission & fail on my own (lack of) merit. Would be nice if this could get fixed so I can actually try this campaign

Nothing, you helped me through it not long after i posted that, works like a charm now

sounds like they did you a favor

Theres a lot of pictures online of this one, i think its an interesting look.. the non-captured ones lack the yellow "V" and star of david, for obvious reasons

Chickenhawk by bob Mason

neither

Well, if and when it gains the letters "ule" and goes from being a mod to a paid module, the sonic boom you hear will be the shekels launching themselves from my wallet in Piktun's direction

I would agree, if you wanna sell off body parts as scrap to get a module..well...theyre yours, you should be able to do what you want with them, but i figgered id pass on the warning. You never can be too careful