hein22

Thanks for your suggestion. I suggest you read the thread after searching and not take only the title. That was me replying to that thread you linked. Which by the way, has nothing to do with this bug report, two different animals. Thanks for your effort though.

+1 I also would like to know if this is correct or not.

Also noticed that TUC in TWS doesn't interrogate either.

Oh so the island refers to the bridge? I didn't know. Thanks!

According to supercarrier FAQ, populated island crew will be included at EA. What is it exactly? I mean, animated deck crew for launches and static placed in ME are already mentioned. But this populated thing is mentioned apart. So what could it be?

Well, if there is indeed a bug it won't be because of that. Extrapolation should be easy for the radar to do and continue to update the aspect. The other report you made, that is definitely a bug. This one I'm not that sure. Let's see what ED says, they will know.

What makes you think is a bug? I'm not sure, maybe it is correct.

In the mission editor section of the guide there is a picture that shows a new option HIDDEN ON MFD. Any ideas what can it do?

Nevermind, I just read (carefully now) and it was described clearly. I was just being stupid at the moment of reading the first time. Thanks for your help.

So 33 knots from the bow and 6 knots from starboard?

So reading Wags supercarrier guide that he just posted I found something that I personally thought was going to be approached differently. First, we are still obligated to set the carrier waypoints so it goes into the wind. I thought the supercarrier was going to include a smart logic to do it by itself in case wind changes or the ship's route doesn't match the wind, but at the moment of launch or recovery it would automatically switch. Second, BRC. It would have been nice that ED included a BRC small window that showed the BRC based on the MVAR coded into the game at the specific location the ship is at, rather than having us calculating it ourselves. It says that we can also check the LSO station but not during early access.

In the guide Wags just uploaded it is mentioned the number in the center of the ship symbol in the LSO screen displays wind over deck, and S or P to either side is for the axial direction. What is the 6 in the screenshot in the manual?

I tried GBU 31 with wind and it was as inaccurate as the 38. Curious.

Santi, I noticed that you can only designate with HUD if you previously had a TGT before. If you start a mission and try to do it it won't let you. Bug? Most sure. Also if you touch the TGP after designating with HUD, then HUD movement won't move TGP like you confirmed it should. Hope it helps.

With ingame vsync on I see too much input latency and sometimes when it gets lower than 60 it gets worse. That's why I was looking for a different approach. I don't really get what is trackir stutter... Stutter is within an image, don't really understand what people mean by trackir stutter. Saw the videos but still don't see anything but FPS stutter.

Thanks for your answer.

While in LTWS any L&S or DT2 will (like IRL) automatically interrogate that specific trackfile. The same doesn't happen in TWS and L&S/DT2 are not interrogated unless you manually do it. Does anyone know if this is correct behaviour?

Thank you Santi. Apologies for not making a clear bug report at first hand, sometimes I get a little lazy.

As promised, attached one track showing there is no notch and that if you don't switch L&S and DT2 the bug doesn't appear. Second track shows targets separated by more than 5nm, no notch and immediately after switching L&S and DT2 the midcourse guidance shuts off. Easy to reproduce, let me know if I can help in any way. Thanks. ltws midcourse DT2 no notch.trk ltws midcourse DT2 no notch and more separation.trk

Santi, thanks. I did same test and same issue was present. Will attach a track shortly. As for the notching, negative. I tested that mission 15 times and there is no notch at all. I will provide two tracks, one showing that if I don't change DT2 and L&S there is no notch. And the other one separating targets.

Is there one? The reports from last year were all discarded by ED saying "Not a Bug" so I assumed there was none. In fact, when ED says something like that I tend to say "ok, then there is no bug". So now I'm confused: Do we have an accuracy bug in JDAMs in DCS World?? Sorry for the continuous appearances here. ED must hate me for sure by now :)

Sorry I didn't catch what you meant. Can you rephrase please? I'm really interested in knowing about this. Thanks.

Despite not agreeing with you (https://forums.eagle.ru/showthread.php?t=268214), even if you're right this bug report could translate into TWS when it is fixed. So I still think ED could benefit from taking a look at this. Thanks.

What about only fast?

Oh yeah, that's has nothing to do with the lack of accuracy of JDAMs in windy conditions IMHO. Only ED know.