Sinclair_76

The DED is smart enough that it knows to do when you enter an eight digit grid. In other words you can skip the easting and northing 0's.

Thank you so much!

@cfrag Regarding stopGap, awesome module btw. When populating a stopgapped plane in a group of 4 the other 3 planes will not reappear as statics but remain empty. Is it possible to have the not client populated planes within a group te appear? Or is there a spelling mistake in the manual...

It's been a while. But In a older mission which I upgraded with the latest DML modules, this error popped up.

As stated. The BLU-107 in CDIP impacts roughly 30 meters short of intended point of impact. Aircraft was at 350 IAS / 500', well within operating parameters. High speed it seems the shortfall is even more. Test-BLU-107.trk

Running in to some problems I can't wrap my head around. I am trying to set up a simple IADS to get familiar with it and expand later on. What I want to achieve is a SA-2 site (with P-19) that remains silent until the enemy is within kill range and then go active. There is an EW within range as well for, how shall I put it, early warning. Both EW and SAM get recognized by text output. The SA-2 shows as autonomous. do redIADS = SkynetIADS:create('SAADF IADS') redIADS:addSAMSitesByPrefix('SAADF-SAM') redIADS:addEarlyWarningRadarsByPrefix('SAADF-EW') redIADS:addRadioMenu() redIADS:activate() redIADS:getSAMSiteByGroupName('SAADF-SAM-SA2-1'):setActAsEW(false):setEngagementZone(SkynetIADSAbstractRadarElement.GO_LIVE_WHEN_IN_KILL_ZONE) end What am I doing wrong?

I think they can. That's how I imagine the UAF is able to deploy JDAM's.

I made something for that. https://www.digitalcombatsimulator.com/en/files/3320772/

OVRD OSB would fit the need.

I required ECM in automatic mode. Per manual p.158 with the RF switch in either QUIET or SILENT, use of the ECM would have been inhibited. That is the reason I used the FCR ON/OFF switch.

I had the pleasure participating in AMVI's Joint Thunder '23 yesterday evening. As a striker the SPINS require you to turn off the FCR. After our strike (successful I might add ) Our #3 was being engaged by enemy F-18's. The rest of us turned back to support. I switched to MSL Override and turned on the FCR. And the FCR switched on in A/G mode. Toggled the MSL override to get the radar in the correct mode. Track included and easy to replicate with the following steps. 1. Switch A-G master mode 2. Turn off FCR 3. Switch to MSL override 4. Turn on FCR I believe that when turning on the FCR it should default to the present mastermode and not to the one it was in when being switched off. PS #3 survived rdrdflt.trk

Yup. I run a couple of mods. C-130 MAD SAM asset pack High Digit Sams No problems with code 1531.

Most of the time you keep seeing the wings in clouds. Only in the center of thick convective clouds is where you lose sight. And that's with wings with a 35.8 meter span. Iirc this seems to be partially modelled in DCS. It was in 2.5 but I distinctly remember losing sight of my WM in fingertip.

Just to be sure. Is the GBU-12 laser PRF on the kneeboard the same as the TGP laser PRF (DED, LIST,0,5)? The bomb laser PRF can be adjusted in the mission editor and can therefore be different than what you expect. Tested a standard CCRP drop with a GBU-12 and it worked fine for me. Do you have a track file to help you determine what might be the issue?

Today I tested the TGP coordinate generation as well as target of opportunity GBU-38 accuracy and as far as I can tell it has been fixed or am I dreaming? If so was it his patch or another one? I did not see any relevant fixes mentioned.

Maybe not the answers you're looking for. 1: Introduce a higher dead zone in the cursor. or, what I did. 2: I also set button 4 (one of the extra switches on the lowe side of the grip) to cursor enable. I assume that the switch IRL has higher gates which prevent movement on the x/y when even slightly depressed to avoid unintentional switchology.

In the latest BETA and Open versions the penetration of the BLU-97/B was updated. https://www.digitalcombatsimulator.com/en/news/changelog/stable/2.8.4.39731/ https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.8.4.39731/ Weapon. BLU-97/B penetration warhead and damage effect has increased.

Ok... I took a F-16 up in the air with a similar setup as on the ground but simplified. Four emitters aligned at 0° / -60° / -65° / -90° (true). Aligned at give angles from steerpoint 1. The F-16 was spawned in the air at 25.000' due south (true) from steerpoint 1. So it had to fly 348° magnetic. Once at steerpoint 1 I active freezed DCS to obtain static results. Again the -65° and -90° are not registered by the HTS and the 0° and -60° (+- 2° (ref 298°) at some points) are registered. All 4 emitters are seen by the AN/ALR-56M. This again demonstrates that the HTS scans only +- 60°. Now for your (@skywalker22) experiment I can only guess. But once the HTS establishes a track or ellips it will remember that even though the HTS reached it's scan limits. So it will remain displayed on the HAD but the ellips will probably not be refined. A emitter will only turn green if no emission has been detected for 2 minutes (per manual p. 286) and be removed after 4. So if you build a track/ellips it will remain visible for up to 4 minutes even while out of scan limits. Hence the "....even behind. " Miz and track file included for verification and duplication. EDIT I added a second track file in which I mainted active freeze at stpt 1 for 10 minutes to verify scan limits. The HTS only tracks the 0 and -60° emitters nothing else during the 10 minutes. After the 10 minutes I unfreezed and turned right at heading 003° to get the -60° emitter at -75° active freeze again and see what happens. After 2 minutes the -75° emitter turned green (stale) and after 4 min it disappeared. RWR showing all 4 emitters. Reaffirming that the scan limits for the HTS are +-60° or 120° in total. TEST-HTS-FOV-AIR.miz Test-HTS-FOV-AIR.trkTest-HTS-FOV-AIR2.trk

As mentioned in this chat: The HTS FOV according Aerospace Power Journal Summer 2002 p11 (https://www.airuniversity.af.edu/Portals/10/ASPJ/journals/Volume-16_Issue-1-4/sum02.pdf) is 180° forward sector. Although the HTS variant described is not the R7 (but the R5?). It does not seem realistic to not have the ability to maintain standoff in a more modern version. As anything less than 90° requires the platform to fly towards the target/threat at some angle. After testing the HTS FOV within DCS I came to the conclusion it is 120°, 60° left and right. Test setup: A HTS mounted F-16, hot on ground, with 11 Clam Shells (for elevation guaranteeing LOS) at 360° / +-30° / +- 60° / +- 65° / +- 75° / +- 90° After selecting a radar on the HAD I cycled (with TMS right) through the various emitters and it looped through the 360° / 030° / 060° / 300° / 330°, ignoring the other emitters. At the same time the AN/ALR-56M shows all 11 emitters. Demonstrating the HTS only sees 120°. Track replay as well as miz included for verification. Nevada because I needed as flat terrain and large LOS as possible. EDIT: since my bug report has been merged. The HTS in DCS has the wrong FOV. Test-HTS-FOV.trk TEST-HTS-FOV.miz

Not automatic but pilot intent. You set TGP to SOI. It makes sense as well. For example you're tracking a target with your TGP. To maintain SA you DMS to HAD. If switching MFD to HAD would automatically switch SOI as well you would have lost your target. So it doesn't. Now reset the example to the beginning. Still tracking target with the TGP. To maintain SA you switch to DMS and realize a pop up bandit is transitioning to your six and you want to engage asap and switch to Digfight Override. At that moment FCR has become SOI by automatic priorization.

If the wind is more than 8 m/s you need to account for wind drift. Especially on narrow groupings, ie columns or arty positions. So aim slightly uowind or lower the burst height.

That's the AMASE pod for certain. To be complete this helicopter is having it's rotor tracked and balanced. The camera to track the blades is mounted on the front part of the left EFAB.

Tracks are considered suspect. Further explained in the DCS F-16 Manual from page 262. Or page 239 for TWS. I am not sure on the mechanics but as I understand a C² element (AEW or GCI) is needed to id datalink tracks as hostile instead of suspect.

Realistic Battle Damage Assessment is lacking within DCS. Is that something that could be included? Have BDA report by friendly units within vicinity of destroyed target?

Wait for the SEC light to extinguish before advancing the throttle to idle.