Wags

Left on the sight select switch on the collective. Same for pilot and CPG

Without a track or video it’s impossible to know where you are going wrong. But this video should get you started.

Trying to designate an individual contact on the FCR page with the HOCAS cursor while flying at the same time is not recommended and why I did not mention it in my most recent video.

You could slew the HOCAS cursor over the desired target and depress to designate as the NTS. What was the NTS becomes the ANTS.

Changes Coming to Sighting Point/Cursor Slews, Snowplow, and VIP/VRP Logics COMING SOON Dear all, In the next update to Open Beta, you can expect a large number of fixes for the DCS: F-16 Viper. Over the past six months, the F-16 team has been revamping the aircraft's air-to-ground sighting and weapon delivery sub-modes to be more authentic and to address many reported bugs in how the F-16 integrates it's sensors, HOTAS, and targeting logic. Along with the upcoming changes to the datalink within the F-16, this has been a very large task that required our dev team to address many aspects of the F-16 all at once, due to the level of integration such changes would require within the aircraft systems. Understandably, this may seem like a lot of changes, but for the most part very little will actually change within the DCS F-16. These changes are mainly focused on ensuring all the minute details that are required for the F-16 avionics to function are properly implemented to prevent any sort of logic conflicts when using the air-to-ground targeting systems. While the Early Access Guide is still receiving revisions to sufficiently explain how all of these weapon delivery sub-modes are intended to work within DCS F-16, we are including a brief conceptual overview for our Viper players to frame the underlying logic in hopes that it will enhance everyone's understanding of why these updates were necessary; until the Early Access Guide can be updated to reflect these concepts. F-16 Conceptual Overview The F-16 sensors (FCR, TGP, and HTS) drive a singular System-Point-of-Interest (SPI). As such, only one sensor can be in a track mode at any given time. When any sensor enters a track mode, it will cause the other sensors to exit their track mode. For example, if the FCR is in Fixed Target Track (FTT) against a surface target location and the TGP enters POINT track, the FCR will exit FTT. This is because the non-tracking sensors must remain aligned to the tracking sensor to maintain the singular SPI location. If two sensors were in track mode simultaneously, the single SPI logic of the F-16 would be violated. When a sensor enters a track mode (FCR FTT/MTT, TGP AREA/POINT, or HAD designation), this automatically puts DTOS, VIS, or EO-VIS into a post-designate state at the corresponding location. The F-16 A-G master mode includes many weapon delivery sub-modes that may be used, depending on the weapon selected on the SMS page. These sub-modes are categorized as either "Pre-planned" or "Visual" weapon delivery sub-modes. "Pre-planned" sub-modes revolve around the use of steerpoints that have been programmed at pre-planned target locations. These sub-modes include CCRP, LADD, PRE, EO-PRE, and EO-BORE. (PRE is used with AGM-154A, GBU-31/38, CBU-103/105, or GBU-24; EO-PRE and EO-BORE are only used with AGM-65) These sub-modes permit direct sighting options (STP/TGT) or offset aimpoint sighting options (OA1/OA2), as well as the Snowplow sighting method. Sighting points are used to ensure the accuracy of the targeting solution to the target steerpoint prior to weapon release. Offset aimpoints are not targets themselves, but are used to ensure the target location (TGT) is accurately placed for weapon delivery (i.e., due to INU drift in a pre-GPS scenario) The selected sighting point determines where the System-Point-of-Interest (SPI) is placed relative to the steerpoint, which directs all sensors to a singular location. Snowplow permits employing a "Pre-planned" weapon delivery mode when existing steerpoints are not practical, and provides a means to rapidly direct the SPI in front of the aircraft at the Snowplow cursor. If a designation is performed while in Snowplow, the main Navigation cursor is slewed to that location and Snowplow is exited. "Visual" sub-modes are geared toward visually acquiring a target location independently of a pre-planned steerpoint. These sub-modes include CCIP, STRF, DTOS, VIS, and EO-VIS. (VIS is used with AGM-154A, GBU-31/38, CBU-103/105, or GBU-24; EO-VIS is only used with AGM-65) Sighting options are not available in these sub-modes, nor is the Snowplow sighting method. The sighting option rotary and the Snowplow OSB options are removed when these sub-modes are entered. These modes will automatically place the FCR in AGR (Air-to-Ground Ranging) and the mode cannot be changed except for placing it in OVRD/STBY. The TGP (if installed) is automatically slaved to the weapon solution in CCIP or STRF sub-modes. The TGP (if installed) is slaved to the TD Box in DTOS, VIS, or EO-VIS sub-modes, even when these modes are in a pre-designate state. This augments the visual identification of targets and assists in optically locating targets at extended ranges. When a target location is designated in DTOS, VIS, or EO-VIS sub-modes, this also updates the current steerpoint location by moving the Navigation cursor to the same location. This ensures a seamless transition between sub-modes (Example DTOS->CCIP->CCRP) against the same target location in which the SPI is maintained on the target. Visual Initial Point (VIP) and Visual Reference Point (VRP) sub-modes are a means of conducting strikes against pre-planned target locations in CCRP sub-mode while using visual landmarks for final alignment of the targeting solution. These are especially useful when conducting low-level strikes in which the target may not be visible until just prior to weapons release. These sub-modes permit cursor slews to be performed to align the targeting symbology with visual landmarks without affecting the cursor deltas of the main Navigation cursor. VIP adds "IP" as an additional sighting point option that may be selected using TMS Right-Short while the HUD or FCR is SOI, or by pressing the corresponding sighting point rotary at OSB 10 on the FCR or TGP MFD formats. When VIP mode is entered, the sighting point is automatically set to "IP", after which the sighting points may be advanced in a sequence of IP->TGT->OA1->OA2->IP. VRP adds "RP" as an additional sighting point option that may be selected using TMS Right-Short while the HUD or FCR is SOI, or by pressing the corresponding sighting point rotary at OSB 10 on the FCR or TGP MFD formats. When VRP mode is entered, the sighting point is automatically set to "TGT", after which the sighting points may be advanced in a sequence of TGT->OA1->OA2->RP->TGT. These modes allow a single overfly designation of the IP or RP in which the SOI is automatically set to the FCR and the sighting point is set to the TGT. This allows a seamless transition with one button press from the ingress phase into the final attack phase, without the requirement to manually slew the cursor to align the diamond symbol in the HUD with the physical landmark that represents the IP or RP. Changelog: Sighting Points & Cursor Slews Cursor slews are now possible in several different modes that are independently accumulated. As an example, the VIP cursor may be slewed and zeroed independently of the Navigation cursor. If Cursor Zero is pressed and "CZ" remains displayed on the MFD, it is because another cursor still has cursor slews applied. This may be seen when the DTOS/VIS cursor is zeroed back to the FPM, but the main Navigation cursor may still be slewed away from the original steerpoint location. To zero the Navigation cursor, CCRP or CCIP should be entered and then CZ pressed. When cursor slews are applied, Cursor Zero is needed to remove them. For a time, changing the selected steerpoint was erroneously zeroizing the cursor when it should not have been. This has been rectified so that cursor deltas are maintained during steerpoint switching (ie, if the TGP was looking 500 meters west of steerpoint 1, it will be looking 500 meters west of steerpoint 2 if the STPT is advanced from 1 to 2). The TD Box occludes the steerpoint diamond. If they are co-located, which is the case in "Pre-planned" A-G sub-modes like CCRP or LADD, the steerpoint diamond will be hidden by the TD Box. When the steerpoint is slewed using the cursor, the OA1 and OA2 offset aimpoints will always slew with it to maintain their programmed offset distance/direction as entered on the DED DEST page. Pressing Cursor Zero no longer zeros the OA1/OA2 settings. These can only be zeroed by manually editing the RNG value to 0 on the DED DEST page. If the RNG value of OA1 or OA2 is set to 0, the OA triangle symbols will be removed from the HUD/HMCS and will not be available in the sighting point rotary options. OA1 and OA2 will not be available in the sighting point rotary options if FIX or A-CAL are displayed on the DED. When not in VIP or VRP modes, the OA1 or OA2 triangle symbols will not be displayed in the HUD/HMCS if not selected using the sighting point rotary option. When in VIP or VRP modes, both OA triangle symbols (if RNG is not 0) are always displayed along with the IP/RP diamond, TGT TD Box, and PUP circle symbols. Sighting point options are not available if in any "Visual" weapon delivery sub-mode: CCIP, STRF, DTOS, or VIS; or if MARK is displayed on the DED with "HUD" as the marking method. Sighting points may be cycled using TMS Right-Short while the HUD or FCR is SOI (prior to this it was only possible with FCR as SOI). The "Ghost A-G Cursor" (white crosshairs) is now displayed on the HSD at the current sighting point location for all sighting points (including OA1, OA2, IP, and RP). Prior to this it was only displayed when TGT was the selected sighting point. The Azimuth Steering Line will only be referenced to the TGT sighting point location, even if the sighting point is changed to OA1, OA2, IP, or RP. Only the direct sighting point (TGT) can represent the target solution for weapon delivery; offset aimpoints only assist in alignment of the targeting solution. Only one sensor can be in a "track" mode at any given time, since the SPI represents the location to which all aircraft sensors are directed. Entering a track mode in one sensor will cause other sensors to break lock. If FCR enters FTT or MTT, the TGP will exit POINT/AREA track and any HAD designation will be dropped. If the TGP enters POINT or AREA track, the FCR will break FTT/MTT lock and any HAD designation will be dropped. If a threat radar symbol is designated on the HAD, the FCR will break FTT/MTT lock and the TGP will exit POINT/AREA track. If the sighting point is changed, the aircraft sensors will exit their respective tracking modes to prevent cursor slews from being erroneously input into the system. The TGP is automatically slaved to the DTOS/VIS TD box while in pre-designate state. If in DTOS/VIS sub-mode and a sensor is commanded into a track mode, the sub-mode will automatically enter post-designate state at the corresponding sensor track location. (ie, if the TGP is SOI and being slewed in DTOS mode and commanded to POINT track, DTOS will enter post-designate at that location) If in any "Visual" weapon delivery sub-mode (CCIP, STRF, DTOS, or VIS; or if MARK is displayed on the DED with "HUD" as the marking method), the FCR will enter AGR mode and cannot be changed. FCR mode selection page is corrected to prevent manually changing the FCR out of AGR mode without changing the weapon delivery sub-mode. When a laser-guided bomb is selected in SMS, the TGP laser will be inhibited from firing if the sighting point is set to OA1, OA2, IP, or RP. This prevents an LGB from being diverted from the intended target location, which is represented by the direct sighting points of TGT or STP. Snowplow Snowplow is only available while in a "Pre-planned" weapon delivery sub-mode: CCRP, LADD, PRE, EO-PRE, EO-BORE; or if in NAV mode if the FCR is not in an A-A mode. When Snowplow is entered (via OSB 8 on the FCR or TGP MFD formats), the SPI is placed at the location of the Snowplow cursor in a pre-designate state (represented by the TD Box in the HUD). In NAV mode when there is no TD Box and the steerpoint diamond represents the steerpoint location, there will be no HUD symbology corresponding with Snowplow cursor while in a pre-designate state. If TMS Up-Short is pressed while the HUD, FCR, or TGP are SOI, Snowplow is exited via post-designate and the main Navigation cursor is moved to the location of the SPI (represented by the TD Box in A-G master mode or the steerpoint diamond in NAV master mode). If Snowplow is exited from pre-designate by pressing "SP" at OSB 8 on the FCR or TGP MFD formats, the SPI simply returns to the existing location of the main Navigation cursor since a designation was not performed. The Snowplow cursor location is placed in three dimensions by the following. Aircraft Heading: The cursor will remain along the aircraft longitudinal axis and cannot be changed. Range: The cursor will be placed in front of the aircraft at 50% the A-G FCR range. Adjusting the FCR range (even if the FCR is in OVRD or STBY modes, or if the RF switch is in QUIET or SILENT) will move the Snowplow cursor in range. If the FCR is powered OFF on the SNSR PWR panel, the Snowplow cursor is fixed 5 NM in front of the aircraft and cannot be changed. Elevation: The cursor is set to the same elevation as the current steerpoint while in pre-designate. When Snowplow is exited via post-designate, the elevation of the SPI is re-calculated to the terrain elevation. When weight-on-wheels, the cursor is set at the same altitude as the aircraft. VIP/VRP It is no longer possible to enable VIP and VRP for the same steerpoint. Enabling one mode will disable the other if set to the same steerpoint. When VIP or VRP mode is entered, a Cursor Zero is no longer performed to the main Navigation cursor. When an overfly designation is performed in VRP mode, the designation will now designate the location of the RP, not the TGT. Only one overfly designation may be performed of the IP in VIP mode or the RP in VRP mode, using TMS Forward-Short while the HUD is SOI. Cursor slews may still be performed before or after the designation, but VIP and VRP modes must be exited and then re-entered to perform subsequent overfly designations. When entering VIP mode, the EHSI will be directed toward the IP and the Azimuth Steering Line will be to the TGT. When an overfly designation of the IP is performed, the EHSI will switch to the TGT. When entering VRP mode, the EHSI and the Azimuth Steering Line will be to the TGT, even after an overfly designation of the RP is performed.

OP updated.

Dear all, It was jointly decided between RAZBAM and EDSA leadership that the F-15E required additional time to test and address bugs identified by EDSA internal testing/Closed Beta Testing (CBT). Whilst we had an internal milestone goal, it was just that, a goal and that was never a public/official release date to move. The Sinai map release has had nothing to do with this matter. We understand that many of you are very anxious to get your hands on it, particularly those that pre-ordered it. We and RAZBAM simply want to ensure that we deliver an F-15E that lives up to your high expectations. This truly will be the year of the F-15E, F-4E, Sinai map, and more. Kind regards, Wags

Dear Sir, Sniper Advanced Targeting Pod (ATP) is a general term for the Sniper TGP that includes the XR per 4.2+ that is planned. Kind regards, Wags

Dear Sir, As mentioned, there is no time frame for this change. Given we have much higher priorities, it would not be anytime soon. We simply wanted to provide a heads up for all those noting TGP implementation discrepancies earlier. No, not really. When provided with sufficient evidence, we are always open to reconsider implementations. However, in the case of the FM/FLCS, such evidence has not been provided. Let’s keep on topic though, please. Kind regards, Wags

Dear all, If I might stick my nose in on this: We hear you and understand why you wish to retain the currently modeled TGP However, for the following reason, we’ll later (no time frame) adjust it to be an accurate LANTIRN TGP. Due to some incorrectly labeled videos and bad SME feedback, we made an earlier mistake of believing our modeled TGP was a Litening. We were wrong. Despite some initial resistance by us, we eventually agreed with your feedback that we were in fact mostly simulating a LANTIRN TGP. In fact, you all did a great job finding images and references of Block 50s sporting LANTIRN. These partly made us reconsider our stance on this. Thank you. We are doing our very best to model a USAF F-16C Block 50 using 4.2+ OFP. We chose this specifically due to the availability of documentation that we can cite if needed (very important in these times of sensitive information being leaked and resulting investigations). All our available TGP data is limited to LANTIRN and Sniper ATP. Even if we could confidently verify Litening TGP for an OFP 4.2+ F-16C (not secondhand accountings), we have zero reference data for this TGP that we could cite. Anything we put into our simulation must have supporting evidence that we can point to. As mentioned earlier, we still plan to add Sniper ATP. We have good and citable reference data for this, unlike Litening. If at a later point we come across Litening TGP data for OFP 4.2+ or earlier that is complete and citable, we’ll most certainly consider it. Kind regards, Wags

OP updated.

Updated OP.

Updated OP.

Dear all, A little update on DCS: AH-64D development. We understand that some of you are concerned about the lack of new features. No resources have been taken off the AH-64D, and work continues ahead steadily. Much of this work has focused on bug fixes and tunning. Before we add too many new features, it is very important that we first have a solid foundation to build upon. Additionally, a big push on bug fixes and tuning has been required to avoid player confusion and frustration. Some of the larger bug fixes and tuning that have been underway include: Tuning how George calculates target range. Corrected TEDAC video errors. Adjusted HUD only views. Tuning damage model like flying sans-tail. Adjusted gun fire shake. Fix multi-crew ASE sync. Removed HDU glare. Fix some engine start issues. Tuning LMC. Further improvements to the PERF page. Better IR texture maps. Lesson, input, and tool tip improvements. Fixes to the CMWS flare system. Tuning of SAS collective channel issues and altitude/attitude holds. Fix SAS tones and hold behaviors. Tuning yaw offset. Fix PNVS stutter. More accurate weight calculations. Trim tuning. Multi-crew hold modes sync. Fix hold modes disengagement logic. SAS fixes. Better SAS Collective altitude hold. More realistic slip ball behavior. APU not requiring fuel fix. Fixed various warnings and advisories. Fixed standby indicators. Tuning TADS and NVS relationship. This is to name a few. A great deal of work on this front is ongoing. Although bug fixing and tuning has been our priority, we have certainly been working on new features that are not gated by existing bugs. Some of these include: Option to remove the auxiliary fuel tank for more cannon rounds. Adding the AGM-114L radar-guided Hellfire. Adding the Improved Datalink Modem (IDM) and LB Net. Adding the Fire Control Radar (FCR). Adding the Laser Spot Tracker (LST). Adding animated engine nacelle cooling doors. Wipers removing rain drops. Many of these items are rather complex and take time. Please be patient. Kind regards, Wags

Further, Mission Editor presets are coming for all three A-10C radios. Kind regards, Wags

VSR radar mode now in development.

Dear AH-64D virtual pilots, Although the DCS: AH-64D was released with a rich set of features, there are certainly important features that will still be provided during the Early Access period. To help understand what is still planned and the status of each, we’ve created a roadmap to ensure clarity. As with other roadmaps, we will color-code items based on their status: Green – delivered. Blue – in development. Gray – to be developed. Our roadmap features are as follows: Auxiliary Fuel Tank / Gun Ammunition Option AGM-114L Radar-Guided Hellfire Laser Spot Tracker (LST) Improved Flight Model and Stability and Control Augmentation System (SCAS) Improvements (continuing improvements) Datalink Laser Warning Receiver FARM Reports BDA/SHOT Reports Fire Control Radar (FCR). GTM first being developed. AI Damage Model Improvements Priority and No Fire Zone Data Transfer LINK Mode ZOOM C-Scope FCR RMAP Mode FCR Air-to-Air Mode FCR Multicrew Synch TPM FCR Mode After Early Access Continued Flight Model and Flight Control System Tuning Campaign Data Transfer Cartridge Anti-Ice System Radar Frequency Interferometer (RFI) Radar Jammer Selectable Pilot Patches Automatic Pedal-Input Assist Option Kind regards, Wags

Updated.

Dear all, We will explore the option of auto-boresight for the Maverick and HMCS from a cold start. This would also need to be server enforced. When possible, we want to shallow the learning curve for new players. This is a low priority though as we have much bigger fish to fry. On the subject of Maverick boresight: this has been fixed internally and we hope to release in the next update or the one after (limited time for final testing and integration). Kind regards, Wags

Dear Sir, Third party module pre-orders are certainly possible on our eShop and Steam if both publisher and developer agree. Kind regards, Matt

One ARC-210 will be added, RT1, with UHF and VHF functions and related HUD, UFC, STAT page, and COMM changes. This will replace one of the VHF radios. We still need to add the STAT page and UFC function. Once those are done after the team return from holiday, it will enter internal testing. Later, after initial release, we'll add the SATCOM functions. Kind regards, Wags

Dear all, A little update on the A-10C II. In addition to the primary task of addressing existing bugs, most of the A-10C II work is on the ARC-210 radio. We are nearing its completion that includes the radio head, HUD data, UFC functions, and COMM page. The remaining item is the STAT page change. Once that is complete, it will enter internal testing. Following its release, we will then add satellite radio functions. At initial release it will include VHF and UHF function (RT1). Once the ARC-210 is complete and delivered, it will bring the module to a feature complete state based on the listed features here: DCS: A-10C II Tank Killer (digitalcombatsimulator.com) Aside from the ARC-210, we still wish to add a 1st person pilot model, but this would come after the Hornet and Viper pilots are complete. To add DTC functionality to the A-10C II, we are also considering an update to the TADS that would entail changes to the TDL and CHG SET pages. This would allow both SADL and Link 16 data through a gateway. However, this is not a promise and something that would only come after DTC functions for the Viper, Hornet, and AH-64D. Merry Christmas and all the best for 2023, Wags

Dear all, Merry Christmas and all the best for 2023! As the team prepares for some well-earned time off, here is where we are with the Hornet: Highest priority is on bug fixing. This includes, but it not limited to issues with the Harpoon, SLAM, and SLAM-ER behaviors, ASE dot behavior, etc. We are performing a ground up review of and refactoring of the Hornet flight model and flight control system. This also includes a large update to the landing gear model. New and improved pilot model. Once this is complete, we’ll do the same for the Viper. Refactoring the radar for more accurate performance. Once this is complete, we’ll do the same for the Viper. We’ve updated the ALR-67 to include new functions and symbols. Following the next Open Beta, tasks include: IAM loft cues. New bomb fuzes like DSU-33 and JPF. MUMI page and DTC. This will follow the Viper DTE page and DTC. A review of MSI functions based on available data for the version we are modeling. Please note that the above are just the highlights is certainly not 100% inclusive of all planned work. Kind regards, Wags

Dear all, Merry Christmas and all the best for 2023! As the team prepares for some well-earned time off, here is where we are with the Viper: Highest priority is on bug fixing. The alternate gear handle and arresting hook tasks are complete and currently undergoing internal testing. You should see both in the next Open Beta update. We’ve done a lot of work on the ALR-56M RWR and added new functions, audio, and symbols. After the next update, the final big ALR-56M task will be the Handoff function that is currently being gated by the PRF audio tones. Adjusting AIFF and ROE Tree logic. New bomb fuzes like DSU-33 and JPF. Following the next Open Beta, tasks include: Tuning air-to-air performance including look-down and search to bug target delay. This will follow the refactoring of the Hornet radar. Air-to-Air datalink assignment functions. Digital Maneuver Cue (DMC) and Loft indications. IAM loft cue. Further work on Link 16 and adding air-to-air target assignments. A 1st person pilot model that will follow the new Hornet pilot model. Radar Velocity Search mode. Further out are items that include: ALE-50 towed decoy (first need new rope physics). Sniper ATP. Data Transfer Equipment (DTE) page and functions. We will start with the MPD, LINK16, and COMM sub-pages. Please note that the above are just the highlights is certainly not 100% inclusive of all planned work. Kind regards, Wags

Performance (PERF) Page tutorial added by BradMick in first post.