Help with CCIP please.

[Frogfoot1606687865]

Hi, since the final has come out I have been having intermittent problems with CCIP mode (Guns, dumb bombs, you name it). The problem is that dumb bombs sometimes land far short or long,CBU's sometimes fail to separate and cannon rounds get nice tight groupings either short or long of the target, using the CCIP reticule.

 

It seems that the targeting computer is not using the correct altitude in its calculations. I always have one of the group of targets set as SPI so shouldn't the targeting computer use the altitude of the SPI in its calculations?

 

I have read some posts stating that you should create a markpoint near the target and set this as your steerpoint , but I find this hard to believe. I cant understand why you would have do this if the target is already designated as SPI.

 

This occurs with all systems functioning normally, no discernible A/C damage at all. Could this be a mis-configuration on my part.

 

I never had this sort of problem with previous betas. Does anyone have any ideas, and is anyone else noticing this?

Cheers

Tom

Edited March 4, 2011 by Frogfoot

[159th_Viper]

Hi, since the final has come out I have been having intermittent problems with CCIP mode (Guns, dumb bombs, you name it). The problem is that dumb bombs sometimes land far short or long,CBU's sometimes fail to separate and cannon rounds get nice tight groupings either short or long of the target, using the CCIP reticule.

 

It seems that the targeting computer is not using the correct altitude in its calculations. I always have one of the group of targets set as SPI so shouldn't the targeting computer use the altitude of the SPI in its calculations?

 

Have you got a track of the behaviour experienced? Without some form of analysis we unfortunately cannot rely on your description alone in a simulator as complex as this - far too many issue are attributable to user (PEBKAC) errors to attempt reliable troubleshooting without said tracks.

 

 

 

 

I have read some posts stating that you should create a markpoint near the target and set this as your steerpoint , but I find this hard to believe. I cant understand why you would have do this if the target is already designated as SPI.

 

 

You designate the target as a markpoint in order to effectively have any number (6?) of SPI's on hand prior to commencing prosecution of the targets. In other words, you are setting up your SPI's beforehand (PPPPPP principle). Finds particular relevance when dropping multiple JDAM's on specific targets in a particular order.

 

To clarify: You do not end up with 6 SPI's: There is always one SPI - It just means that you can toggle between SPI's almost instantaneously as opposed to designating each SPI one after the other.

Edited March 4, 2011 by 159th_Viper

[Frogfoot1606687865]

Have you got a track of the behaviour experienced? Without some form of analysis we unfortunately cannot rely on your description alone in a simulator as complex as this - far too many issue are attributable to user (PEBKAC) errors to attempt reliable troubleshooting without said tracks.

 

Viper, unfortunatly most of my flights are too long to post tracks. I will attempt to create a short flight to demonstrate the problem.

Tom