Frederf

https://forum.dcs.world/topic/94816-guide-info-dcs-updater-usage-version-numbers-module-ids/ This post details the process well but I don't know if it's applicable to Steam versions as Steam handles the DLC content through itself normally. I do happen to have a Steam version although I don't use it this way. It looks like modules can be selected for install there. "Manage My 2 DLC"

You can command-line install modules (even though I remember that ability was going away), but without permission normally associated with the automatic process it won't help. I would check https://www.digitalcombatsimulator.com/en/personal/order/ and the licenses area to be sure you have the modules you expect associated with your account. If you're on Steam that might be a different process.

The conversions work both ways so if 21-25 already has L/L near your desired point should have some of the MGRS already ready. Tholozor nailed it, 40RDM6390043600 isn't a valid (or at least preferred primary reference). 40Q... is. It won't work with or without CNVRT highlighted. But it's an interesting point. If i highlight or don't highlight CNVRT before ENTR I can't see any difference. Is there a difference?

Roll channel only has effect when pitch channel is on. And AP has limited authority relative to trimmed input.

Single engine propellers fail flat. Multi engine propellers fail feathered. (in general)

With triggers yeah. On waypoint reach the trigger uses a random to set a switch to order to an other.

I'm trying this, typing in a 6-digit just autofills out to 10 digit with 0s. Visually it looks fine. When I highlight CNVRT and press ENTR I come to a new screen I've never seen before. ENTR I noticed the screen flashes rapidly through something so I went back at 1/64X and did it again. It: Highlights the "21" steerpoint in reverse video, losing the highlight on CNVRT Dehighlights the "21" Moves to the after image shown above

Will RWS or RWS SAM make a tie break difference (all else equal)?

I did a 1.5 minute align (1.4m is the earliest possible) and despite selecting blended in NAV>OPTIONS the HUD shows G1. After ~10 min airborne I got B1 (EAC sticks) but still no transfer alignment. I did an inflight alignment down to 0.8, still unsat. REINIT INS and another in flight align. At all times the INS FOM was 6 which isn't good. INS was "I" status. I feel you have a maximum INS FOM for transfer alignment and I don't know any in-fight way to get it. EGI also shows DEGR on the STAT page. I tried a 3.9min align... FOM 6... ALN UNS I tried a 4.0min align... FOM 1... ALN RDY Maybe in reality there is a way to get working JDAM after a less-than-full align but I can't see how in DCS.

I think eventually GPS will refine your alignment to a sufficient quality and/or you can do an inflight alignment. Can you get EAC switch to stick on? I'm guessing that's the go-no go threshold for JDAM transfer alignment.

Your alignment page says T= 1.6 7.7. Transfer alignment isn't going to transfer until the airplane has an alignment worth transferring. Try it again after a 4.0 0.8 align.

This took me a minute to understand. Agreed, the point of the calibration is to refine the understanding of zero between the HUD and HMCS. The fixed registration marks are projected on the HUD while the moveable alignment marks are projected on the HMCS. The alignment marks must be projected on what the system thinks is the HUD's frame of reference. The roll alignment mark must be "head roll stabilized" or there's no point in the calibration process. A track to demonstrate what such a looks-right-but-is-wrong alignment would look like F-16 HMCS roll alignment.trk

In real life: yes, maybe. SAM has a pronounced dwell time that is distinct from a simple search sweep. At long range the sweep-to-dwell ratio is high and the target may not decide that this constitutes special attention. As the range closes the sweep-to-dwell ratio reduces and the target may get the hint that he has special attention compared to regular search. Priority threat is different from alert level. Even an E-3 scanning you in search will be priority threat if that's the worst thing detected. It would be interesting to see if SAMing F-16 is prioritized above a more distant searching F-16 that would be prioritized below if both were in simple search mode.

I've changed the callsign value but I have heard that this change isn't seen by other clients. Is the player-set callsign propagating over the network? In reality the team STNs can be edited from cockpit but donor STNs can't. They can only come from DTC.

This is the result of enabling GRCV on only COM1

SRS has some limitations. If you GRCV COM1 and then pull the COM2 knob you'll lose the "G" symbol. It's not possible to "G" the radios independently. If you GRCV COM1, COM2, or both then you get "G" on both radios in SRS.

I've never flown through the delayed solution and not have the bomb come off. I don't think this is a problem. However I have had the bomb come off when it's not supposed to (early or otherwise not in constraints). For slightly early releases it might be the case that the ballistic computation and the actual fall trajectory are not in agreement or the ballistic calculation is fed poor info somehow. This feels like it could be the case as flying around with infinite weapons and targeting things with a delay cue routinely results in variably short (never long) impacts. The logic in these cases seems sound, just that the precision of the calculation is somehow off. On the other hand the bombs (Mk 82) are releasing logically wrong with wide lateral steering errors. If you designate and then fly 3000' to the right of the target firstly the ASL doesn't show any steering back to the left but also the bombs will release when you pass beside the solution (3/9 constraint) instead of not releasing based on 5 mil constraint. Because the ASL doesn't move regardless of your actual alignment I don't know if fixing the ASL movement would cause the constraints to mend themselves as a consequence. Similarly but distinct if you designate and then fly a 360 degree circle (far away, not passing 3/9 of a solution) the bombs will come off with both LGBs and Mk 82s which neither should in those cases. Here's a track of 3 short impacts (slightly short, slightly short, very short) then an intentional lateral aim (release out of constraints) and then a turn away (release out of constraints). F-16 CCIP delay cue.trk

FARP ATC hasn't changed since Black Shark in 2011 as far as I recall.

Ah, yeah a manual long release is something else. I'm a little surprised a PWII will stretch that long under guidance; it might not be realistic. The fins bouncing back and forth at 2Hz drain a lot of energy from the bomb. EDIT: Makes sense he has to get the laser seeker pointed at the laser spot (14 pitch down should be plenty) in order for the guidance to start early. With level releases it doesn't matter if the laser is on early because the bomb is not pointed at the spot enough to see it yet. If you wanted to do that in F-16 I would put PROF1 on CCRP and PROF2 on MAN and toggle from 1 seeing when I should release and actually having release control on 2. That was to do the famous 2 LGBs 3 seconds apart and shift laser between impacts trick. If he wants extra standoff then a medium altitude toss (MAT) delivery is good. Unfortunately the toss cueing and range scale symbology on the CCRP HUD is currently out to lunch. The CCRP math will still do toss/loft releases but the supporting guidance is not in yet. I mean your "throw" of the bomb can be wrong by 1500' (or more) and laser will pull it onto target. If you did not lase then the bomb will hit the ground that far from the target.

You can continuous lase a PWII from that speed/height. It's not the best for terminal velocity and crossrange ability but it's not the end of the world. You will hit a stationary target 10/10 times. There is such a thing as a "deliver to miss long" feature in some airplanes with PWII types which will lead to improved terminal energy. By delivering long by a certain amount it expects the PWII to steer steeper as it sees the laser spot. Different airplanes may or may not do this type of delivery. The A-10C for example this feature can be altered with the ORP/BAL setting (although I don't know if it actually does anything in DCS). You could test this in the A-10/F-16/F-18/etc by delivering a PWII without laser and seeing where it hits.

MAN is a backup mode with manual release. If no delay cue in CCIP (pipper in HUD) that's immediate too. I think you are focusing too much on immediate release. If your target location is good then consent to release driving through solution is a good answer. You don't even have to be that accurate with delivery. From high and fast chucking the bomb anywhere within a quarter mile is good enough. It will follow the laser spot. No way were you getting different range from the same bomb in different planes with same parameters. After all you're just throwing a brick out of a moving car. Ford or Chevy is effectively irrelevant.

Setting editor to 15°C 29.923"Hg and from Batumi runway after HMCS calibration (hot runway start isn't perfectly calibrated). Object is an apartment tower north a couple degrees above the horizon. Helmet line of sight is about 45 degrees right of nose. TGP seems to change to very different logic when above the horizon. There's no terrain backdrop to convert a particular line of sight into a specific three dimensional point. I can't put the helmet cue on this building target directly because it's above the horizon. If you try the TGP will say N45 07.770 E34 15.931 which is the X, Z = 0, 0 point on the terrain. This is over 380 miles away in the wrong direction. So to get the helmet TD box on a building while on the ground we have to designate on valid terrain and then slew the box post-designate. By slewing the box as shown I will look at what SPI position is assume on TGP screen. We note the LOS is bad but mostly we care about the L/L/elev. The air conditioner I'm aiming at is at N41 36.818, E41 36.355, 210'. The TGP-listed position is where I first placed the TD box on the ground with the helmet so I could later adjust it to the building top. The elevation seems to be the maximum elevation just as I was slewing above the horizon. So it's no wonder the TGP's LOS doesn't match the helmet's LOS because it's trying to fix parallax at a range of a hundred feet when the target we care about is 0.6nm away. It's really important to consider the difference between lines of sight and points in space. OK try 30°C 30.923"Hg for a radically different weather. Same helmet cue placement, looking at TGP cursor result it's not any different. Symbol alignment can be caused by system altitude errors but in this case I don't think it applies.The TGP is about 8 feet below, 3 feet aft, 2 feet right of the pilot. Unless range is correct the LOS, even if perfectly calibrated parallel, won't convert because of this offset. On the other hand if you TGP SOI and place TGP over a desired point the helmet TD box is not that far off. In my case my TGP shows L/L of N42 40.040 E41 47.767 at 18,707' which is 65nm away but it's in the same LOS as the building. In conclusion the LOS mismatch is due to the helmet or TGP coming up with different points or lines of sight which make harmonization difficult. I don't know if there's an issue or not. Being on the ground and using the helmet/TGP above the horizon to direct the other sensor is a weird case.

Paveway II against a naval target could be conducted via either preplanned or visual modes. Everything air-to-ground in the F-16 falls either under the umbrella of preplanned or visual. From your description it sounds like you want something more akin to a preplanned delivery so we'll start with that first. Preplanned is always in reference to a steerpoint of some kind. In standard employment that would be a permanent destination that is at the rough location of the target with refinement slews via the HUD, radar, or TGP for final targeting. For self-lase LGB delivery the last sensor select would usually be TGP as the pilot would like to have control over the laser spot until impact. CCRP (or LADD which is a slightly modified CCRP) are the typical preplanned modes. Here is a track where the steerpoint 2nm away from the naval target, radar is used to bring the TGP closer, and then TGP used to attack. Release is level at 20,000'.F-16 Frigate LGB 1.trk But you might not have a steerpoint nearby. Thankfully there is another option: a pseudosteerpoint. This is placed in snowplow mode and acts as a temporary steerpoint. The system is placed in SP and the pre-designate point is half the radar range. Turn the airplane until the target is visible, adjust the radar scale until target is roughly in the middle and designate. Then refine and the attack proceeds as before. F-16 Frigate LGB 2.trk If you wanted to attack visually you could use DTOS. The DTOS TD box, post-designate is similar enough to the pseudosteerpoint of CCRP/SP above. Putting the TD box and then using TGP to refine and attack is valid. For some reason I can't see the ship far away so I used the radar to find it, back to visual, designated where the box was, and then finally saw it through TGP. If you can see the ship then putting DTOS box on target visually would be enough. On your computer you may see ship from many miles away and wondering why I'm struggling. F-16 Frigate LGB 3.trk Lastly, CCIP. This is not normally used with self-lase LGB delivery but let's see if it can be made to work. OK, it's very silly but you can is you designate visually with the pipper and then while holding WR to keep the TGP on target you lase. This only works with the delay cue release. I have asked around about TGP divorcing from pipper in CCIP pre-designate and I don't have a clear conclusion. You can't do it in DCS at least. I don't see the value in doing it anyway. DTOS would be the desired mode for a visual attack. F-16 Frigate LGB 4.trk There are lots of issues visible in these tracks if you know where to look but the TGP/LGB integration itself is pretty spot on. Those issues significant to these attacks are with the radar, HUD mostly. There is a significant issue that you should be aware of when moving the TGP with the radar. When you slew radar cursors in a preplanned mode the TGP should follow... it doesn't. What works to "kick" the TGP to the radar cursor is to cycle the sighting point. You can do this hands-on with FCR SOI and TMS right. This is an unfortunate issue and hopefully will be fixed soon.

Ah sorry, F-16 is LOSE.

CH Control Manager is a fine program and is needed for things like turning axis into buttons and similar advanced logic. But for just things like curves, deadzones, and inversion of axes it's not needed and DCS handles these things quite well by itself.