hein22

That's the attitude!

Imagine a mission with a wind coming from the south east, and the CSG is going from the east and into the gulf. IRL the carrier will change course for recovery if the wind is too strong. But how will we do in DCS to accomplish this? That was my question. Thanks ED for taking a look at this.

I need a new Supercarrier video, urgently. I can't wait until wednesday. Please Wags, please.

It isn't. I posted above saying that after some tests I found this was already fixed.

No need, PPLI is also updating each 12 seconds.

Santi, It is for all Link16, I'm flying at this very second and PPLI also updates each 12 seconds, which according to this hornet pilot isn't right.

There are papers that have been shared here and there that suggest that Link16 has 300ms update rate. Here is a link of one of them, the others are more confidential I think. Anyway, I am pretty sure ED knows this already, it's a matter of how they wish to simulate things and what engine limitation there is. I honestly don't think this will change, seems like one of those sensitive things that ED is not open to external sources. In my humble opinion it is worth looking. https://drive.google.com/file/d/1eaxwaWtnvefME32qajM3r6Wla8tDhHr1/view

The update rate is not correct, it is currently 12 seconds which is crazy. I think he refers about something that went on today in youtube, I don't know if it is even something that I should talk about here, given current rules. But a fighter pilot suggested that 12 seconds isn't correct, and that measuring link16 is seconds in absurd, too long. I'm really confused about how things work in this community to be honest.

You didn't experience what?

I'm talking about the new option that ws shown in the EA Guide of the supercarrier. The one you mention is the Hidden on Planner.

Holy thread revival Batman! Bignewy, I saw many posts saying that I should change registry for the new path. Has anything changed since you posted that?

Bump. Does anyone know a workaround for this?

Bump

Roger. It would wise IMHO if ED simulate automatic interrogation (the whole beam) like it was ON in the AZ/EL page. Forget about L&S interrogation, we want auto :). Then when the page gets implemented they can roll it back and let the page control it. This would be like many other things currently that are not implemented but have a simplified state.

Again, with a track we might prove to ED that we are in front of a bug. Without one is going to be difficult.

A track would help us help you.

Ok, nevermind. The bug exists, both of them. OP's testing was not bullet proof since the active seeker of the amraam played a role there, but tested with LTWS midcourse guidance and the HUD magically updates and the missile is guided.

Actually this might have something to do with the extrapolation. In terms that the missile is first sent to the extrapolated place and then it switched to pitbull. But it was never going to guide if it had been outside active range. Hope ED can give light to us.

That's why a track is better. A video means nothing, you even have an error at the end so who knows what is going on in that mission. In both tracks I saw everything is fine. Again, if Santi says he could reproduce then be happy. No one cares what I say, I was just coming here to help.

Yes correct. Your target was already turning when you intentionally lost radar contact, so the extrapolation did its magic. I don't know why Santi could reproduce but for me OB is fine. What's important is that if there was a bug it is fixed, and if there was no bug then we're fine.

Exactly that. Meaning no disrespect obviously. But was kind of dissapointed when I read the guide. My opinion only. Air boss station will need player to interact, and that's what I'm saying, the carrier should have an easy logic that can be made by ED with no effort. They code NASA stuff I imagine they can code a simple logic for this.

I just saw the track and in current OB cannot reproduce. Working fine here.

That video has the camera all messed up, can't see clearly.

Santi, I just saw your Edit. What bug did you reproduce? I tested it 4 times last night and in current OB the extrapolation works fine.

There is no wrongly memory feature. The other bug report was wrong like we pointed out with Santi. Extrapolation is the reason. This bug report is serious, and may very well be a bug.