Problems with dive toss and Jester

[Typhonus2]

I'm running into situations where Jester won't perform his ground lock prior to DT bombing. I have everything armed, set properly, etc. When I aim the reticle at the area I want locked and press the context menu button, he just says variations of "Unable". Likewise, if I try to pickle without his lock, no tone sounds and bombs don't drop. Master arm is on, bombs are fused, stations are selected and say "Armed", I've set the drag coefficient in the bombing screen, and the UFC knob is set to A/G. Any ideas what I'm missing?

I finally set it to direct and just eyeballed it and everything dropped and hit just fine.

[McVittees]

Did you set the delivery mode to DT in the bombing table?

[WhiskyTango]

I got the same behavior, but setting the DT in the Bombing table call up fixed that. He will confirm by saying "Captured".  Only now my releases are way, way off. In this personal mission I didn't do the Full alignment but instead went with the BATH alignment. Looking through the flight manual now to see what I'm doing wrong. 

 

Edit: My problem is that I don't listen and it tells you everything in the training mission. 

That Bombing call up has to be right, and you have to follow what you told Jester you were going to do...duh. Target Elevation, your anticipated dive angle, speed and your release altitude. 

Pretty awesome really! 

Edited May 23, 2024 by WhiskyTango

[Typhonus2]

I did indeed set the bombing table. As to the rest, I'd clearly seen in the YouTube videos currently passing as training for this that, when doing DT, the only fields that matter in that display are the drag coefficient of the weapon and those that deal with intervals, etc. Angle and such have no effect, as the computer is handling it all. And, when it works, I've had perfect accuracy. And is mostly works.

One difference I've noted is that, when Jester wouldn't lock the ground, the radar range was set to 50 miles. It should have changed down to 10 miles when I set A/G. It's as if he got stuck in some A/A mode. The range seems to only be changeable from the back seat, as I can find no command that does it from the front. Experiments continue, but it thus far seems to rarely reoccur. I assume the problem was me, as it usually is. I'd just like to work out what I'm doing wrong.

[Gunnergolly]

Trying to practice dive tossing, whenever i select bomb type in the"bomb table" weapon drop down menu a yellow warning triangle shows up in the "drag coefficent" line.

If i try and bomb using the direct method instead then changing any parameter within the bomb table also brings up the same yellow warning triangle..... but this time in the pipper depression line... ??.

Please could somebody tell me what i'm doing wrong ??.

 

[_Hoss]

Phester has a mind of his own.

[wired521]

I ran into this as well,

The issue seems to be Jester gets confused when task switching. What I had to do to fix it was:

• Jump in the WSO seat
• Set the radar to A2G manually
• Set the range to 5M manually
• Set the TV/Radar video source to radar Manually

Once I configured all of these items, he would lock on the ground for me as normal. 

 

One other note, when taking just slick bombs and no pave spike he seems fine... I only had todo this when I ran TV guided bombs, a pave spike (for fun), and slicks.

 

[Gunnergolly]

Jester on this occasion seems to be behaving himself, his locking the ground ok when i press the "context menu" key .

The bombing table is not working as described in the manual and a couple of youtube videos that i have seen. .... One of the youtube videos that i watched when the guy selected bomb type it populated the "drag coefficient" line with a value that you could then send to Jester.

I just get a yellow warning triangle instead. 

2 minutes ago, wired521 said:

I ran into this as well,

The issue seems to be Jester gets confused when task switching. What I had to do to fix it was:

• Jump in the WSO seat
• Set the radar to A2G manually
• Set the range to 5M manually
• Set the TV/Radar video source to radar Manually

Once I configured all of these items, he would lock on the ground for me as normal. 

 

One other note, when taking just slick bombs and no pave spike he seems fine... I only had todo this when I ran TV guided bombs, a pave spike (for fun), and slicks.

 

I'll give that a go but he is setting the range to 10 miles and appears to be doing his job...... it's the bomb table that i'm having issues with, it's not coming up with bombing solutions ... see above .. 

[Zabuzard]

Usually that's the case when you entered parameters that do not spit out a valid solutuon.
Crazy example to drive the point: Target altitude above your own. Or too close to the target to find a solution with the entered speed, altitude and angle.

That said, we have seen weird issues on the bombing table caused by Mods interfering with the Phantom. So perhaps you can doublecheck that.

If you can't figure it out, it would be helpful to see a screenshot of what you are entering into the Bombing Tool, so that we can enter the same parameters, run it through the math and tell you what happened :)

[Hodo]

On 5/22/2024 at 6:03 PM, Typhonus2 said:

I'm running into situations where Jester won't perform his ground lock prior to DT bombing. I have everything armed, set properly, etc. When I aim the reticle at the area I want locked and press the context menu button, he just says variations of "Unable". Likewise, if I try to pickle without his lock, no tone sounds and bombs don't drop. Master arm is on, bombs are fused, stations are selected and say "Armed", I've set the drag coefficient in the bombing screen, and the UFC knob is set to A/G. Any ideas what I'm missing?

I finally set it to direct and just eyeballed it and everything dropped and hit just fine.

make sure gun sight is not caged or standby.  Has to be in A-G mode for him to lock anything

 

[Zabuzard]

Might sound obvious, but make sure you put the Delivery Mode selector into DT. That is also what commands Jester to go 5nm boresight and primes him for the locking.

[Tom Kazansky]

18 hours ago, wired521 said:

I ran into this as well,

The issue seems to be Jester gets confused when task switching. What I had to do to fix it was:

• Jump in the WSO seat
• Set the radar to A2G manually
• Set the range to 5M manually
• Set the TV/Radar video source to radar Manually

Once I configured all of these items, he would lock on the ground for me as normal. 

 

same here. Maybe I misused the "Jester Context Action" key before I tried to get an A2G lock, but I saw it once (in the backseat), that Jester's video source was off, and not "Radar". I switched it to Radar manually, and everything worked fine.

 

[Zabuzard]

I believe I might have found the cause of this. When you switch the delivery mode to DT, you usually switch through TGT FIND. Now, when you do that too fast, Jester will run into an issue where he sets the DSCG knob to TV for TGT FIND and then skipping the subsequent action to set it to Radar because, at the time of enqueuing the actions, the knob was in Radar already.

Ill prepare a fix for this

[Zabuzard]

Hopefully fixed in the next patch

[DaveDewhurst]

On 5/27/2024 at 9:20 AM, Zabuzard said:

I believe I might have found the cause of this. When you switch the delivery mode to DT, you usually switch through TGT FIND. Now, when you do that too fast, Jester will run into an issue where he sets the DSCG knob to TV for TGT FIND and then skipping the subsequent action to set it to Radar because, at the time of enqueuing the actions, the knob was in Radar already.

Ill prepare a fix for this

Oddly I started a thread on this earlier in the week. I posted that switching the knob sometimes didn't update the radar if you did it too fast. I left it to go and get a track of the issue and couldn't reproduce it so I deleted the post. Glad I'm not going mad.

[Coenraad]

I only enter DT and bomb type on the sheet and leave everything else blank. And it still hits right on. 

Seems DT does not need alt and dive info etc. 

 

[Gianky]

Indeed, it doesn't.

The only thing the aircraft needs to know is the drag coefficient.

[Zabuzard]

The drag coefficient depends on the altitude and speed at release point though.

If you are planning to hit a small target dead on with a single dumb bomb, you better properly enter the full attack profile and fly it accordingly.

It is just that Dive Toss, by nature of being a dive attack, is more forgiving than other modes. Smaller altitude and speed differences wont have much of an effect if you are diving in steep angles.

However, if you are flying more extreme parameters such as high altitude or low dive angles, you definitely will miss your targets if you are using a drag coefficient for 4k ft, 400 TAS, 50° but then release from 10k ft, 500 TAS at 20°.

[LindaBrownie]

On 5/24/2024 at 1:29 PM, Gunnergolly said:

Trying to practice dive tossing, whenever i select bomb type in the"bomb table" weapon drop down menu a yellow warning triangle shows up in the "drag coefficent" line.

If i try and bomb using the direct method instead then changing any parameter within the bomb table also brings up the same yellow warning triangle..... but this time in the pipper depression line... ??.

Please could somebody tell me what i'm doing wrong ??.

 

For Dive Toss, set target altitude to 10ft to populate a drag coefficient.

I was setting DT and inputting the bomb type on the Bomb Table and my releases were way off until I realised that setting just those two does not populate the Drag Coefficient.

Flicking target altitude to 10ft seems to force the Drag Coefficient to populate and then my releases were on target.

[Gunnergolly]

On 5/25/2024 at 9:02 AM, Zabuzard said:

Usually that's the case when you entered parameters that do not spit out a valid solutuon.
Crazy example to drive the point: Target altitude above your own. Or too close to the target to find a solution with the entered speed, altitude and angle.

That said, we have seen weird issues on the bombing table caused by Mods interfering with the Phantom. So perhaps you can doublecheck that.

If you can't figure it out, it would be helpful to see a screenshot of what you are entering into the Bombing Tool, so that we can enter the same parameters, run it through the math and tell you what happened








 

Yeah you were right i was inputting parameters that could not provide a solution..... as soon as i increased the "run in" speed parameter from the default value to something like 450kts..... it then calculated a drag coefficient for me.

Thanks for your reply ...