electricaltill

Fair enough, thanks for correcting me. Do you think this is a bug? I was just conjecturing reasons it might not be targeting correctly and that was the only thing I could think of. When I attempted this track myself the FLIR started drifting after bomb release, before I had even overflown the target.

It already is - check your axis bindings.

Pilot was getting audible warnings of various kinds, I was seeing the warnings on the screen but no audio warnings. We were using SRS if that makes any difference.

I noticed a few things but I'm not sure which, if any, are the culprit. You didn't use manual attack mode, which you should for LANTIRN. You didn't use nose fusing, which is the correct mode for the mk82 and derivatives. You didn't use automatic lasing, and it didn't look like you manually lased for more than a few seconds after bomb release. Edit: I tried flying in your track and my first attempt it didn't hit either. It might be because you are aiming at a large area of flat contrast - i.e. the side or deck of the ship, and there is not much in the way of distinguishing features the system can use to calculate range. I noticed that the release cue seemed to happen late, and to be off to one side a few degrees, like the system didn't quite know where the target was three-dimensionally. The pod track also drifted somewhat after bomb release. The way I got it to hit was to adjust it back after release (if I'm practicing RIO in single player I fly at <1x speed so I have time to jump back and forth). I think it might just be the visual characteristics of the target you were trying to hit. That's just my wholly non-expert view though, please someone else jump in.

Point track is a contrast lock, so the target has to be different enough from its surroundings for the targeting system to recognise it as a target. You can change the gain and contrast settings to increase the chances of a successful point track (you generally have a better chance in WHOT mode too), but it becomes more difficult the further away you are because this is old camera technology with comparatively limited capabilities. If you're looking at something only a few pixels wide nothing will convince the targeting system to get a point track. That said, as the person above me said you don't need a point track to hit a stationary target.

Oh, I thought it was supposed to say "near."

Oh yes, I was getting confused with the STT mode where it says aspect is for countering different types of countermeasures.

What about the FOV switch, which says FAR/NAR?

I think the aspect switch just affects missile fusing, not target detection.

There are orange thumb wheels on the left side panel, in front of the engine cutoff levers, where you set the frequency (assuming you have simple comms disabled). I don't know the AWACS frequency, though.

Yup, already reported. https://forums.eagle.ru/showthread.php?t=235975 Sadly still happens in 2.5.4.29167.

Another European (novice) RIO here, I will be doing the same.

That is what it does. Have your bindings been reset?

Just had the same thing happen in MP. Going to try same mission in SP.

I see, thank you all.

Was it just a case of the target being static but very hard to spot, so an offset from a known point was used? Or was it for mobile targets, and the offset established after the mission began? If the latter, how? It's easy enough for us to pull up F10 and use the ruler to get the offset information but how was it done in reality?

So I was doing a startup from both positions, Jester disabled. Fine-aligned, spent a while entering all my steer points, target points, etc. Jumped into the front seat, but accidentally reactivated Jester. No instructions, just set him to active. The very first thing he did was to switch off WCS. Why on god's green earth would he do this?? It was aligned! Now we've got to wait another 8 minutes! He also mindlessly enters all the waypoints and target points...which I just finished doing. Please add the following to Jester's code: if(!wcs.isAligned()){ jester.alignWCS(); }else{ jester.gtfo(); } Cheers. :cry:

Are you sure? Because if you set that option to "native," the ABRIS displays in Russian. It should be set to "English."

Options>gameplay>avionics language

Yup, I reported this here, still happening.

That was reported after the unveiling last year, and HB acknowledged it.

Well... we're here to ask HB to change/add things aren't we? :-) Basically a lot of us use modifier buttons to add functions on our HOTAS, and as you say this is hard coded for these particular functions, which is a bit restrictive. In other words pressing S4 left has an A function and B function, depending on the position of the slider on the LANTIRN stick. At the moment when you're binding controls it is impossible not to have the A and B functions on the same button because of this, and I think we should be able to bind them to different buttons if we want to.

Don't worry about it.

Each button on the S4 hat has an A function and a B function. At the moment there is only a single A/B binding, and you use the slider on the LANTIRN joystick to switch between the functions without a visual indication which is selected. If there were separate bindings for the A and B functions I can use a modifier on my HOTAS or just different buttons altogether.

Please can you provide bindings which separate out the two layers of controls for the LANTIRN S4 hat, so that they don't have to be on the same hat? E.g. a set of bindings for the Qxxx controls separate from the gain/level controls. This doesn't have to affect the bindings already there.