Jump to content

[NO BUG] Unable to drop bombs in CCIP mode with Waypoint as target


Recommended Posts

Posted

Unable to set CCIP drop mode for waypoint selected as WPDSG, SMS page reflects CCIP mode correctly, HUD displays Auto with CCRP symbology

Version - 2.5.4.28840

Track file attached

 

Method:

1. Create a simple mission with one waypoint and loadout Mk84 and Mk83 Bombs, make waypoint one zero feet (relative adjustment)

2. Fly mission

3. Select AG mode

4. Select waypoint one in the AMPCD

5. Select WPDSG in the AMPCD

6. Select SMS page and Mk84

7. Select fuze Manual > Nose, Efuze > Inst, mode CCIP

 

Expected - CCIP shows as the mode in the SMS page

Expected - CCIP shows as the mode in the HUD

Expected - CCIP HUD symbology

Expected - HUD shows target square over target at waypoint 1

 

Actual - CCIP shows as the mode in the SMS page - PASS

Actual - CCRP shows as the mode in the HUD (Auto) - FAIL

Actual - CCRP HUD symbology - FAIL

Actual - HUD shows target square over target at waypoint 1 - PASS

F18_Target_Bug_CCIP.trk

Windows 10 64 bit | Intel i5-9600k OC 5 Ghz | RTX 2080 |VENGEANCE® LPX 32GB DDR 4 OC 3200

 

Hotas Warthog | Logitech G Flight Rudder Pedals | Track IR 4

Posted

In the Hornet, you can't use CCIP if you set a waypoint as TGT; it automatically switches to CCRP (AUTO). You need to undesignate the target with NWS and then you can use CCIP again. That is how the real aircraft works.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...