Ned help with IP bombing in multiplayer

[J13 Serenity]

Hi

 

Can anyone tell me why, when my human RIO enters IP to TRG BRG and RNG, it saves on his TID, but on the pilot screen it remains zero. IP bombing is impossible. It deos work in single player though.

Is it a bug or we are doing something wrong?

Thank you

[QuiGon]

It's a bug that exists since the Tomcat got released and is long know, but HB did nothing to fix it so far: https://forums.eagle.ru/showthread.php?t=237903

It's frustrating for me, because I would have so much good use for it in MP. It's especially frustrating, because it seems like they just forgot to sync the IP to TGT data between both players, which should be rather easy to fix, but apparently it's just not important enough to get some attention :(

Edited November 4, 2019 by QuiGon

[J13 Serenity]

Thank you for reply

[IronMike]

Just a silly question: do you guys perform the visual fix on it?

 

 

The IP waypoint itself is only a guide to the visual fixpoint. The RIO then needs to enter bearing and range from it to the real target before the fix and when the fix is done those are used immediately, in effect creating a computer target solution on the real target via the vis fix and the bearing/range.

 

Are you maybe forgetting to perform the visual fix? Or maybe not performing the fix on the right feature?

 

Note, visual fix here does not mean nav fix update.

Edited November 5, 2019 by IronMike

[draconus]

"When the pilot designates the IP visually on the HUD the WCS recalculates the target location using the data set under the IP TO TGT function on the CAP, moves the target diamond to that location and instead displays guidance towards the real target location."

So the pilot just have to press DES button on the visual IP point and then the target get designated instead?

[QuiGon]

Just a silly question: do you guys perform the visual fix on it?

 

 

The IP waypoint itself is only a guide to the visual fixpoint. The RIO then needs to enter bearing and range from it to the real target before the fix and when the fix is done those are used immediately, in effect creating a computer target solution on the real target via the vis fix and the bearing/range.

 

Are you maybe forgetting to perform the visual fix? Or maybe not performing the fix on the right feature?

 

Note, visual fix here does not mean nav fix update.

Yes, of course and it works fine in SP. As soon as I perform the fix on the IP the vertical steer line in the HUD jumps to the actual target. When flying multicrew that doesn't work anymore and nothing happens when the fix is performed. The steer line just stays put. Reason for this seems to be that the IP TO TGT data that the RIO has to enter does not get synced with the pilot. When the RIO enters this data it shows up on his TID, but on the pilots TID repeater all the data keeps being zero. So when the pilot performs the fix his target is on the same location as the IP, because all his IP TO TGT data is zero. The data only gets stored for the RIO, but not for the pilot. I already explained that a while ago in the other thread.

Edited November 5, 2019 by QuiGon

[IronMike]

Yes, of course and it works fine in SP. As soon as I perform the fix on the IP the vertical steer line in the HUD jumps to the actual target. When flying multicrew that doesn't work anymore and nothing happens when the fix is performed. The steer line just stays put. Reason for this seems to be that the IP TO TGT data that the RIO has to enter does not get synced with the pilot. When the RIO enters this data it shows up on his TID, but on the pilots TID repeater all the data keeps being zero. So when the pilot performs the fix his target is on the same location as the IP, because all his IP TO TGT data is zero. The data only gets stored for the RIO, but not for the pilot. I already explained that a while ago in the other thread.

 

 

 

 

I've seen that yes, thanks. Just wanted to be sure. It's very possible that those variables don't get marked correctly for MC sync, we'll try and have a fix soon. Thanks.

[QuiGon]

I've seen that yes, thanks. Just wanted to be sure. It's very possible that those variables don't get marked correctly for MC sync, we'll try and have a fix soon. Thanks.

Yeah, that's exactly how it looks like, which is why I think it should be rather quick and easy to fix and made it a bit frustrating to wait so long for it to get taken care of as it is a feature that I would really like to make some good use of in MP, although it wasn't really used much IRL :)