Using the INS for precission bombing

[Zeus67]

Do I get that right?: You can store one offset (BAD) for each waypoint in your flight plan? I know, having an offset for every waypoint doesn't make sense in practical use, but in theory that is how it works?

 

Yes. Each waypoint can have an offset so in theory you can can have an offset saved for each and every waypoint. That rule also includes the RD/TD values.

[Wayc00lio]

Is all this reflected in the manual?

[Zeus67]

Is all this reflected in the manual?

 

Not yet.

[Wayc00lio]

Not yet.

 

Ok, thanks mate.

[FSKRipper]

Just a short question. Before flying over the IP I tried to make an INS correction (extra steerpoint). Is there a way to keep the INS switching automatically to the next waypoint since it will make a correction impossible or has the drift to reach a specific value to allow such a correction?

[Zeus67]

Just a short question. Before flying over the IP I tried to make an INS correction (extra steerpoint). Is there a way to keep the INS switching automatically to the next waypoint since it will make a correction impossible or has the drift to reach a specific value to allow such a correction?

 

You have to disable it by clicking on the ENC button.

 

If the ENC light is on, then it will change waypoints when distance is at or below 1.5 NM.

 

With ENC light off, it will keep the same waypoint so you can do your position update.

 

This works only for NAV mode position update. When you are in Attack mode, the waypoint do not change so you can do a position update anytime you want.

[FSKRipper]

You have to disable it by clicking on the ENC button.

 

If the ENC light is on, then it will change waypoints when distance is at or below 1.5 NM.

 

With ENC light off, it will keep the same waypoint so you can do your position update.

 

This works only for NAV mode position update. When you are in Attack mode, the waypoint do not change so you can do a position update anytime you want.

 

Thanks! :thumbup:

[104th_Cobra]

Good job, guys. I've been waiting for this.

[mia389]

c. ΔAlt is required. ΔAlt = Altitude difference between the IP altitude and the BAD altitude:

+ will add the value to the IP altitude.

- will subtract the value from the IP altitude.

 

The difference for me is 9ft. When I put - 00009 in the left scratpad it changes it to 97

3. Check that both TAS and RS are selected.

 

It will only let me Select TAS or RS.

 

I might need a video

[diditopgun]

1) Many bugs with BAD actualy, but reported.

2) Because it will be available only in the next update.

[mia389]

1) Many bugs with BAD actualy, but reported.

2) Because it will be available only in the next update.

 

I updated my game today, Did the update fix this?

[Whisper]

Has anyone actually been able to use this procedure, is it functionnal? I can't get the indications like described (the diamond for example is still on top of HUD and not bottom), and I can't update the IP position, Ground Designate/INS Position update does nothing.

[diditopgun]

It's still wip.

But for diamond in top of hud, if you are in bombing mode it's normal, and if you are in OBL mode for radar INS position update (still wip too...) it's because your radar is on silence and not emitting.

[diditopgun]

Hi !

 

INS bombing work almost fine now.

 

But 2 problems:

 

RAZBAM side:

_ BAD values in P/0 mode (azimuth and distance) are rounded after insertion. It's a problem to get an accurate target position. Need decimal.

 

ED side:

_ Azimuth value read between ME and F10 map with ruler for a same target have about 1 degree difference (F10 map seems to have the true value). And azimuth number doesn't have numbers after decimal point that is needed for target designation accuracy.

[DArt]

Hi !

 

INS bombing work almost fine now.

 

But 2 problems:

 

RAZBAM side:

_ BAD values in P/0 mode (azimuth and distance) are rounded after insertion. It's a problem to get an accurate target position. Need decimal.

 

ED side:

_ Azimuth value read between ME and F10 map with ruler for a same target have about 1 degree difference (F10 map seems to have the true value). And azimuth number doesn't have numbers after decimal point that is needed for target designation accuracy.

 

+1

Same remarks, need decimals! :)

By the way, it is working well!

[Zeus67]

Hi !

 

INS bombing work almost fine now.

 

But 2 problems:

 

RAZBAM side:

_ BAD values in P/0 mode (azimuth and distance) are rounded after insertion. It's a problem to get an accurate target position. Need decimal.

 

ED side:

_ Azimuth value read between ME and F10 map with ruler for a same target have about 1 degree difference (F10 map seems to have the true value). And azimuth number doesn't have numbers after decimal point that is needed for target designation accuracy.

 

I'll check. Thanks for the heads up.

[Rlaxoxo]

I was busy for a past month someone has a video guide how to utilize Proper INS bombing?

[ZHeN]

I was busy for a past month someone has a video guide how to utilize Proper INS bombing?

 

+1

[kobeshow]

It still does not work properly, or at least not as described in this thread.

 

When approaching the IP:

 

• Selecting PI on the PCA, the diamond does not move to the bottom of the HUD, it only moves if you use ZBI aswell.
  
• Updating the IP position works (gets updated in PCN), but does not move the target cross to new position
  
• After updating the IP BAD/REC/VAL don't turn on in PCN
  

Edited October 2, 2016 by kobeshow

[Azrayen]

Wait for next update.

PI and OBL issue fixed in dev.

[tordillo]

Hi, is there any video tutorial to use the BAD and BUT coordinates?

thanks

[baltic_dragon]

There will be a specific training mission for INS bombing, just finished it - only waiting for the VOs :)

[Doum76]

Stupid question, but how do i get the IP to show on PCA, all i get when i select a weapon is TAS and RS, and i know i'Ve seen it before on my PCA, i don't think it's a bug since other people in the threads has it even though some thing needs to be fixed, bad pilot error i presume. :)

[jojo]

Stupid question, but how do i get the IP to show on PCA, all i get when i select a weapon is TAS and RS, and i know i'Ve seen it before on my PCA, i don't think it's a bug since other people in the threads has it even though some thing needs to be fixed, bad pilot error i presume. :)

 

You need to set up a "BAD" in PCN.

 

So the "DEST" waypoint will be the IP and the "BAD" the target.

[vparez]

@Azrayen,

 

what does TAS and RS stand for exactly in french?