[REPORTED] F/A 18 LGB won't switch from CCIP to Auto?

[Gierasimov]

Try selecting CCIP mode and then switch by selecting AUTO. It works but a bit bugged.

[Gierasimov]

And it is already reported I should add

 

https://forums.eagle.ru/showpost.php?p=3887078&postcount=19

[imacken]

Try selecting CCIP mode and then switch by selecting AUTO. It works but a bit bugged.

 

Great! Thanks a lot, that worked.

Now, the ASL doesn't appear in Auto mode unless the WP is target designated. Is that a bug, or is that correct?

[Jak525]

Great! Thanks a lot, that worked.

Now, the ASL doesn't appear in Auto mode unless the WP is target designated. Is that a bug, or is that correct?

This is correct. WPDESG just uses the waypoint as any other sensor e.g. targeting pod to make an A/G designation (the "TGT").

[imacken]

This is correct. WPDESG just uses the waypoint as any other sensor e.g. targeting pod to make an A/G designation (the "TGT").

 

Now, I'm confused. Why would that be the case for laser guided bombs? Also, what if the target isn't a WP?

[Jak525]

Now, I'm confused. Why would that be the case for laser guided bombs? Also, what if the target isn't a WP?

Basically the WPDSG function is just another way of designating an A/G TGT, in this case via a waypoint. The bomb does not care if the TGT is based off a waypoint or a targeting pod or whatever. When it's not a TGT the WP does not matter to the A/G systems, it's just for navigation.

[imacken]

Basically the WPDSG function is just another way of designating an A/G TGT, in this case via a waypoint. The bomb does not care if the TGT is based off a waypoint or a targeting pod or whatever. When it's not a TGT the WP does not matter to the A/G systems, it's just for navigation.

 

I understand all that, but my question still stands, what if the target is not a WP? Also, why doesn't the bomb take its target from the laser? Why does it need a (target designated) WP to get the ASL up?

Edited May 15, 2019 by imacken

[Jak525]

I understand all that, but my question still stands, what if the target is not a WP? Also, why doesn't the bomb take its target from the laser? Why does it need a (target designated) WP to get the ASL up?

 

1) Then you'll need to designate another way such as via the HUD when a bomb is selected (TDC depress with TDC assigned to HUD) or, when it's out, the TGP and later A/G radar etc.

2) The laser is for the bomb's guidance, the aircraft itself doesn't see it. Operationally, using an LGB is the same as a dumb bomb, minus entering the code.

3) Because the ASL appears only when an A/G TGT is designated because AUTO bombing mode uses the A/G TGT.

[backspace340]

I understand all that, but my question still stands, what if the target is not a WP? Also, why doesn't the bomb take its target from the laser? Why does it need a (target designated) WP to get the ASL up?

 

The Hornet does not have an in-built laser spot tracker - it has *no* idea where the laser is. It can only target an AUTO drop on a TGT, you have two ways of designating a TGT currently, either turn a waypoint into a TGT or use the ball and chain on the HUD. Without a TGT it can't create an ASL as it has no idea what you're trying to drop on.

 

The bomb can take the target from the laser - but the bombs aren't wired into the plane, they sit on the same dumb pylons as Mk82s, so the seeker can't tell the plane where the laser is. You can CCIP drop in the rough area of a lazed target and the bomb will track, but the only way to get an ASL near the target is to either WPDSG so you get a TGT or use the ball and chain.

[TheBamse]

Edit: Ninja:d :)

 

First of all there's no data link on the BRU that carries GBU-1x's so there's no way to use the bomb as a sensor to feed the targeting computer with a solution. Second, the laser isn't always on prior to pickle, it will most likely only be active some seconds prior to impact so it's not a good way to get a firing solution.

 

You don't _need_ a WP but you need a target of some sort that the aircraft can feed to the targeting computer. Without AG radar or TGP, we only have waypoints and the currently hard to use HUD-designation and I'd go for creating a WP any day of the week out of those two options :)

Edited May 15, 2019 by TheBamse
Haiii-ya!

[imacken]

Thanks, that makes sense. I guess I'm just used to having a TGP!

[lecd64]

Couldn't change bomb release mode from CCIP to AUTO in Wags's video

 

I noticed that the bomb release mode doesn't change from CCIP to AUTO in Wags' latest video at 0:45. Is it normal?

Here is the video:

[falcon_120]

Make sure of the following:

 

1-In the store page in the left DDI go to Mode and select AUTO

2-Once you find your target in the FLIR, and with the FLIR as Sensor of interest (Denoted by the little diamond on the top right corner) press TDC Depress (Same button used to track a target with your Radar)

3-You are ready to blow stuff up.

[Wesjet]

GBU12 - Stuck in CCIP

 

I have noticed an issue when setting up my GBU-12s initially.

Typically this is in MP with a cold start, but I was able to reproduce in SP with a Air Start.

 

1) Select GBU12 (default mode is CCIP)

2) Select Mode

3) Try to select AUTO

4) Nothing Happens

 

Work-Around:

5) Select Mode

6) Select FD (Or another mode)

7) Select Mode Again

8 ) Select Auto

9) Profile changes to AUTO.

 

Track & Mission Attached.

 

Edit: Also Noted that this is visible in Wag's training video with the GBU-16s.

LGB Testing.miz

GBU12-Stuck-CCIP.trk

Edited August 2, 2019 by Tiburtius

[lecd64]

Thanks falcon_120. I mean the Mode doesn't change from CCIP to AUTO after your first step, which can been seen in the Wags video. It might be a bug I think.

[Eagle7907]

Thanks falcon_120. I mean the Mode doesn't change from CCIP to AUTO after your first step, which can been seen in the Wags video. It might be a bug I think.

 

 

Yep I noticed this too. After you select AUTO from the menu, it doesn't change. It remains CCIP. :dunno:

[KTFBGB]

It remains in CCIP until a target is designated. Then you Change back and forth.

[Eagle7907]

It remains in CCIP until a target is designated. Then you Change back and forth.

 

 

Right. But shouldn't you be able to tell the jet you want to do an AUTO release before designation? I don't really know if this is correct as is or something wrong. I don't have the docs to show it is correct or not. In the video the OP provides it doesn't change, but Wags still makes the motion to select AUTO.:dunno:

Edited August 2, 2019 by Eagle7907

[KTFBGB]

Right. But shouldn't you be able to tell the jet you want to do an AUTO release before designation? I don't really know if this is correct as is or something wrong. I don't have the docs to show it is correct or not. In the video the OP provides it doesn't change, but Wags still makes the motion to select AUTO.:dunno:

 

Ok to that I have no idea if that’s modeled correctly or not.

[Rockrend]

I’m not sure if this bug has been fixed or not...

 

See the following thread - https://forums.eagle.ru/showthread.php?t=238829

[Rockrend]

This has been a problem for some time.

 

See - https://forums.eagle.ru/showthread.php?t=238829

[Cyborg71]

Same problem. Mode button needs a click on the ccip mode (despite showing ccip) then selecting Auto before a change occurs.

 

Can't imagine thats required IRL.

[BIGNEWY]

threads merged.

 

This is reported to the team

 

Thanks