Auranis

+1 on this, I am getting the same error today, same set of circumstances. Steam-only account, 502 error, no saved authorization found. All my modules are disabled.

I recently noticed that while the Mk-20 opens at 1500 feet AGL when released from the Hornet (which is correct per the manual included with the module), the Harrier and Tomcat exhibit slightly different behavior. What seems to happen is that a Mk-20 released from a Harrier or Tomcat will open and release bomblets exactly 1.2 seconds after passing 1500 feet AGL. This tends to result in poor effects on target, especially when the canisters are dropped from high altitudes/steep angles. See attached Tacview ACMI files for documentation. Harrier_Rockeye.zip.acmi Hornet_Rockeye.zip.acmi Tomcat_Rockeye.zip.acmi

Steps to reproduce: Designate target position using WPDSG or sensor designation Arm bombs and select AUTO release mode Start a dive in on the target SCS FWD to select AGR Use TDC to adjust AGR diamond onto the target position Press and hold pickle button until bombs release Expected: Bombs will impact the position overlaid by the AGR diamond Actual: Bombs fall short See attached track files. I think this issue may be related to some of the other issues describing cases where the AGR or TDC diamond are offset from the intended target. It may also be related to issues where CCIP bombs in the Hornet and Viper seems to consistently fall short, as well. AGRBombsShort.trk AGRBombsShort2.trk dcs.log DxDiag20230325.txt

Well, part of the reason I ask is that the ACM switch also disables the RIOs launch button. To me it seems like the loft should be completely disabled, as per Gyrovague's comment there isn't evidence to support it being available. But it's been two years so it seems like some evidence has turned up?

Title is self-explanatory. Just curious about this topic, since a while back Gyrovague said that lofting would be disabled for Sparrows generally (link: https://www.reddit.com/r/hoggit/comments/fmezjy/comment/fl8clnq/?utm_source=share&utm_medium=web2x&context=3 ), however it appears this was not done for the MH and now the P. Currently the pilot can disable lofting by flipping up the ACM cover, but the RIO has no equivalent ability. Thanks for taking the time to read.

I discovered an interesting issue with using the Air-to-Ground Radar on Persian Gulf, in both the Hornet and the Viper. If you designate a target using MAP mode, the target designator diamond is offset significantly from the designated point. Interestingly, if you use it as your bomb aim point, your bombs hit the target. Conversely, it seems that selecting AGR and putting the diamond over the target will result in a miss. This issue appears to only affect the Persian Gulf map. I could not replicate it on Marianas, Caucasus, or Syria. See below screenshots and attached trackfile. In this example, I designate a C-130 parked on the ramp at Al Dhafra, then switch to FTT. When I roll in to attack, the TD diamond is completely off the ramp. I make my AUTO attack run on the diamond and score hits on the intended target. TDIssueAlDhafra.trk

Steps to reproduce: Start "Beyond Visual Range" Instant Action Mission on Persian Gulf Order JESTER to set TGTS to Large Acquire MiG-29 group as single trackfile, fire single 54C at 40NM Crank. At some point the target trackfile splits into two as the radar resolves the second MiG-29. Expected: 54 will activate once getting within 13NM of the target trackfile, regardless of which aircraft is actually targeted by the missile. Actual: 54 never activates. It appears to be going after the other aircraft than the target trackfile. See attached ingame and tacview screenshots. Notes: I reproduced this issue a few times, and failed a few times. It seems to only happen when the target being followed by the missile (DCS game logic) differs from the trackfile under attack in the F-14 module. AIM54_test.trk

Bump. Can confirm that the AIM-7M on the Tomcat is still lofting.

High Digit SAMs (HDS) is a simple, IC-compliant asset pack for DCS that adds more air defense systems to the game, both modern and historical. The pack is intended for use in a PVE environment, and offers a variety of assets which perform somewhat differently from their DCS analogues. Our hope is to provide assets that provide enhanced realism and gameplay variety from those included in the base game. HDS is supported by Skynet IADS by Waldair, for additional challenge and mission diversity. Mod Authors: @Auranis (original mod author: S-300PS, S-300PMU1, 5V55RUD, 5V23, 5V27, HQ-2, 9K317 Buk-M1-2) ERO (all custom 3D models) @Hextopia (SON-9 Fire Can AAA Director & KS-19 AAA Gun) @LetMePickThat (S-300PMU2, S-300V, S-300VM and Polyana-D4M1) How to Install Download the latest release from the GitHub repository, Extract and copy the Mods folder into your C:\Username\Saved Games\DCS folder, or use OVGME to install the files there. Currently featured systems: S-300PMU-1 (SA-20A Gargoyle) Complex This upgraded version of the S-300 added ABM capability and the long range 48N6 missile to the advanced S-300 complex. All components labelled as SA-20A in the mission editor. On top of the 48N6-equipped TELs, the complex can also accommodate launchers for the legacy 5V55RUD missiles. The S-300PMU1 includes a truck-mounted 30N6 radar than can be used in place of the mast-mounted variant. S-300PMU-2 (SA-20B Gargoyle) Complex This incremental upgrade from the S-300PMU-1 features improved ABM capability and increased range. All components labelled as SA-20B in the mission editor. S-300PS (SA-10B Grumble) Complex This variant of the SA-10 is a remake of the S-300PS included with DCS. The version from the mod features improved guidance and kinematics, as well as a brand-new set of 3D models by ERO. All components labelled as SA-10B in the mission editor. S-300V (SA-12 Gladiator/Giant) Complex The S-300V is a tracked, mobile area defense SAM with a particular focus on countering tactical ballistic missiles. It was specifically designed to protect Soviet Army HQs from Pershing II and Lance nuclear strikes near the frontline. The system features both the long-range 9M82 missile and the shorter-ranged 9M83 round. S-300VM (SA-23 Gladiator/Giant) Complex This upgraded variant of the S-300V features Track-Via-Missile guidance and the extremely capable 9M82M anti-ballistic missile, in addition to the 9M83M missile, all on a tracked chassis. Unlike the S-300V, the S-300VM saw some success on the export market, with batteries sold to Venezuela, Egypt and India. All components labelled as SA-23 in the mission editor, complete with custom 3D models. 5V55RUD Missile for the S-300PS (SA-10c), S-300PMU1 (SA-20A) and S-300PMU2 (SA-20B) systems This upgraded missile has improved guidance from the original 5V55R, increasing its effective range vs. aircraft significantly, up to 90km. Available in the mission editor via the dedicated SA-10 (5V55RUD) launchers. Can be used with either the SA-20A/B or SA-10B complexes. 9K317 Buk-M1-2 (SA-17 Grizzly) Transporter/Erector/Launcher and Radar, 9A310M1-2 This upgraded Buk TELAR carries a more capable radar, and fires the 9M317 missiles, which is longer-ranged and more agile than the original 9M38 Buk missile. This variant has an improved ability to defend itself from anti-radiation missiles. V-759/5V23 Missile for S-75 (SA-2) Complex This late-production missile for the SA-2 has an improved warhead, maneuverability and G-tolerance compared to previous versions, and was widely exported in the 1970s. Note: The DCS version of the SA-2 is able to maneuver at up to 17G at the time of this writing. The V-759 is modeled with a 6-G limit; the historical missile could pull up to 9G, which will be simulated when an advanced flight model is created. Add to your SA-2 complex by selecting the launcher for the V-759 in the mission editor. V-601P/5V27 Missile for S-125 (SA-3) Complex This upgraded missile for the SA-3 features a number of improvements to the guidance and rocket motor. Note: This version performs much more closely to the historical SA-3 than the DCS version, and as such it is generally much less dangerous to face. Add to your SA-3 complex by selecting the launcher for the V-601P in the mission editor. HQ-2 Missile This Chinese-developed copy of the S-75 makes several upgrades to its performance, particularly guidance, overload capability and kinematic performance. Note: Associated radar systems not included until we can figure out a way to add RWR symbology without breaking IC. Add to your SA-2 complex by selecting the HQ-2 launcher in the mission editor, available to China, Iran, and CJTF Red. 9K338 Igla-S (SA-24) MANPADS The 9K338 system features significant kinematic and countermeasure resistance improvements from the previous 9K38 Igla. It fires the 9M342 missile which has an average speed of 650 meters per second. Selectable in the mission editor as the SAM SA-24 Igla-S. 9K34 Strela-3 (SA-14) MANPADS The 9K34 system was a major improvement over the previous 9K32 Strela-2, featuring a limited all-aspect engagement capability and improved fusing. It saw service around the world from the late 1970s onward. Selectable in the mission editor as the SAM SA-14 Strela-3. SON-9 Fire Can AAA Director with KS-19 AAA Gun The SON-9/KS-19 combination was a potent Soviet heavy AAA system with radar guidance. Selectable in the mission editor as: AAA SON-9 Fire Can, AAA 100mm KS-19. Currently using 3D models from the Silkworm radar and Flak 18. Polyana-D4M1 C2 Vehicle This wheeled command vehicle is perfect for Skynet users to use as a node for their IADS. A manual describing how all units are to be used, including examples of site layout, can be found below. If you have any question or suggestion, please do not hesitate. Feedback is welcome! HDSM_S300_Variants_Explained.pdf

This is exactly what I'm trying to do, and it doesn't work for me. I tried it first using a client slot, and then again using a player slot after re-installing the F-14 module. The waypoints did not transfer in either case. I attached tracks from both attempts. Is there anyone out there who can get it to work? CAINS.trk CAINS2.trk

@Naquaii Sorry for the bump, just want to make sure you see the above comment.

Thanks for your replies @Naquaii! It seems to say exactly that here: http://heatblur.se/F-14Manual/general.html#steering Either this is not implemented, the implementation is broken, or I'm missing a step somewhere, because I cannot replicate this behavior in the current DCS open beta. Only the DLWP1, DLWP2, DLWP3, DLFP, DLST, and DLHB will be loaded by link. The rest *must* be manually entered, even with the CAINS/WAYPT switch set on the deck to perform a CV alignment. Edit: Does having Aircraft Stored Heading set in the mission editor make a difference on loading the waypoints via link?

Hello all, Just a brief question here regarding the datalinked waypoints (DLWP1-3, DLFP, DLST, DLHB). Currently their behavior in the sim is to function simply as marks on the TID, they can be hooked for the purposes of performing a datalink fix but there is no other way to interact with them, and destination vectors are not available for them. I was curious as to whether anyone at Heatblur or otherwise had any info pertaining as to whether this is the behavior in the real jet, and/or if the behavior will be changed in the sim at all in the future. Personally, I'd quite like to have some ability to either get destination vectors directly from them, or to import them into the nav computer. Heatblur's F-14 manual says that destination vectors are available for datalinked waypoints, but I don't see any details on how to access them. Thanks for reading

Saw this issue messing around with the F-14, but it may affect other modules as well. The problem: ripple dropping the Mk-82 Snakeye in level flight has a pretty high chance of one or more bombs exploding in midair, possibly caused by collision with another bomb. Test parameters: Speed: ~400 knots Altitude: ~600ft MSL Standard temp/pressure, no wind 14 bomb ripple, 50ms interval snakeye_ripple.trk

Did my own test which confirms this result. AIM54-Test2.trk