Why is my CCIP all messed up , and why bombs fall so much short of target?

[hreich]

Please if somebody know why is this happening?  - Please check video and tell me how to fix this error on my CCIP*

 

[Vampyre]

Two ways to fix that.

1  Set your INS Selector Switch from NAV to IFE and it will be constantly updated. It's not realistic to the real jet but it works.

2  Go to the SUPT page on the AMPCD and select HSI (PB2). Auto start will have the page up already. Change your input from INS to GPS by selecting PB6 and then selecting the GPS selection which is PB9. GPS will keep your position constantly updated.

Edit: This assumes you have completed your INS alignment properly. Your CCIP pipper is directly influenced by your INS Alignment. If you dont have the INS Selector Switch in either NAV (with GPS input selected) or IFE the CCIP pipper will be erroneous.

Edited April 6 by Vampyre

[AndyJWest]

Given the angle of the display impact line, I'm not surprised you are missing. I'd find a mission where you don't have a crosswind. Or at least bomb into wind. And then concentrate on using the proper technique, which is to place the velocity vector beyond the target, align the impact line with the target, and pickle as the CCIP impact cross walks up over the target. 

Having said that, cluster bombs have often been problematic in DCS, with issues both with aiming and with fusing. If you are new to CCIP, conventional low-drag iron bombs are easier to get consistent results with.

 

 

[zika1234]

Its mk20 bombs

Sent from my Pixel 7a using Tapatalk

[Czar66]

4 hours ago, hreich said:

Please if somebody know why is this happening?  - Please check video and tell me how to fix this error on my CCIP*

 

No way that's a valid CCIP cue given your velocity vector is not giving out a heavy cross wind component.

Align your INS properly.

[hreich]

This is mission - from the launch from carrier....Cant figure how to fix error on ccip mode? Can somebody check mission for me?

1989-CAS.miz

[Muchocracker]

Your INS isnt aligned properly. Use the CV selection on the knob then move it all the way over to IFA when it's finished. 

[hreich]

4 hours ago, Muchocracker said:

Your INS isnt aligned properly. Use the CV selection on the knob then move it all the way over to IFA when it's finished. 

Is this doable from mission editor, or do I have to sit on cat launch and wait 10+ minutes while it alligns properly?

[Muchocracker]

30 minutes ago, hreich said:

Is this doable from mission editor, or do I have to sit on cat launch and wait 10+ minutes while it alligns properly?

It's only pre-aligned on hot start. It has to be aligned when going from cold start. Use stored heading to shorten the alignment to 90 seconds. The chucks guide that's linked in the top of the main hornet forum page has the steps. 

Edited April 7 by Muchocracker

[zika1234]

It.looks.like when doing auto startup, AI is doing stored heading procedure


I dont remember that up untill now i needed to do the stored heading procedure. I was always first switching to cv than waiting to alignment than after timer switching to ifa...

Sent from my Pixel 7a using Tapatalk

[Phantom711]

@zika1234

You don‘t need to do a stored heading alignment, it‘s just faster as far as I know.

[MissionCMDR]

I just flew this mission a couple times and received the same result as you did with your jets. I tried a bunch of things but could not get the reticle to "hang freely" it follows the orientation of the plane and then sticks there.

Brand new unit placed, from cold and dark, nothing else changed, CCIP works fine.  It's unique to the jets you created. Could try starting from the ramp?

Cool mission btw, I liked what I played.

Edited April 9 by MissionCMDR
Ramp suggestion

[zika1234]

Tried today again, will post track replay, same problem again after takeoff and few minutes of flight -- ccip borked again

Sent from my Pixel 7a using Tapatalk

[hreich]

Here's replay with manual startup - did i messed up something ...At around 15:01 i switch nav dial to CV and select std HDG...At 15:06 i switch to IFA and lost "auto" option for waypoints (seq is tere, but no auto)...then back to NAV and "auto" option for waypoints is availabale again. but CCIP is borked

HR_continueCAS.trk

Edited April 9 by hreich

[MissionCMDR]

Uncheck Unrestricted SatNav in the mission options. The issue appears to be corrected.  -Nope, seemed fine low alt, once up to a decent height it was all screwed up again.

Remove your waypoints from the main flight just leave EPLRS on. The CCIP reticle acts normally now...so I will test in VR now

Edited April 9 by MissionCMDR
Additional suggestion

[hreich]

Sorry, don't understand this -->  "Remove your waypoints from the main flight just leave EPLRS on. " ?

 

[MissionCMDR]

you have the aircraft setup to attack the BTR's under the waypoint actions tab, remove those.

Your wind settings are fairly high (I lowered the wind turbulence by alot to 0.2), and will contribute to our problem, as the CCIP reticle is uncaged and according to wind data.

mission runs perfect out of the box now, I will give it a proper run possibly later this evening.

Edited April 9 by MissionCMDR

[MissionCMDR]

12 minutes ago, hreich said:

Sorry, don't understand this -->  "Remove your waypoints from the main flight just leave EPLRS on. " ?

 

Could probably leave them, personally I never really put those types of waypoint actions into a client/player slot, I was just trying to eliminate some possible factors.

The wind thing needs changing, as the settings are too high, and most likely the actual root cause of the issue.

[hreich]

Ok, lowered winds...will check again

Edited April 9 by hreich

[MissionCMDR]

Ignore me, it was still happening with your jets, so I deleted and recreated them, and the issue was more or less gone. I bombed one set of 3 before eating a MANPAD

I am not sure what it could be at this point as the default alignment for a hot start should be accurate.

I haven't experienced this before, but then again I haven't used the cluster munitions really at all up to now, so maybe it's different with them? *shrug* I dunno...

Alignment of something that was supposed to be automatic, is problematic getting ready to launch off CAT1