hein22

I can't elaborate, sorry, rule 1.16. Hornet hotas has many more functions than what you see in public webpages. Each button has functions that won't even be similar to the button's name. That's the way the hornet it's built. Thanks.

You can't currentlyy since DCS has many missing HOTAS functions for the Hornet. They'll come later ED says, but who knows when.

Our hornet IRL has both radar and SA formats showing whatever is set in DATA-A/C subpages of HSI format. The reason why in the radar is not the case is simply a forced bug that ED must have done to be able to live with awacs calls. Obviously it would have been much better to simulate it correctly and let the pilot set true in hsi so he or she can correlate with awacs calls. Afaik though, that bearing setting in hsi never worked correctly so maybe that's another reason why the radar is wrong.

Guys, friendly bumps are getting short :)

I know what dumb bombs are. I'm not saying that they should hit spot on, they should have a random error, based on release parameters that are always different due to human piloting, not the same one over and over again, that is what's wrong in dcs. And it has been acknowledged by ED so...

That was for the stable version update. I HOPE!

I didn't follow this thread for obvious reasons but can we expect the SC for next week? Hoping an answer from ED here. Thanks.

Unfortunately I don't remember the exact video. Last time I said the name or nickname of the pilot he said that he never said such thing so now I'll just stay put.

A fighter pilot on YT said that Hornet pilots are 90% AUTO bombers and above 10k they had spot on results without rippling.

Anything above 10k and the bug appears. It doens't look to exist if you are at 5k for example.

Same as here

Lol xd

Jesus guys, just provide a track and that's all. We'll take a look.

"The code" is where all the nightmares begin :)

I don't think that test represents well the issue at hand. You see, mk84 are so strong that makes you think you did a precise hit, and rippling also contributes to that. Try the same test with just one pickle mk82 more than 10k AGL and let us know. AUTO is broken, since day 1 :(

It'd be nice to see someone from ED confirming if they changed it.

Wags already said in youtube that we will have to do scripting for de-spawn such statics. For me it is absurd, i don't want to get into scripting for such a basic feature of a super module, it would be logical that ED makes a new action for de-spawning static objects in triggers.

It has been like that for ages now. I even forgot about that due to how long it's been since reported. Maybe others have different opinions.

Why would you do an FCS reset or BIT (two different things), before starting the engines?

Last update broke a ton of core things. Basically a lot of things they marked as fixed broke a different aspect of the same category. We are not in a good time for dcs, let's hope the team can solve the issues.

Roger, thanks.

I'm still seeing this issue whenever chinmey smoke is more than 0.

This issue is present not only for awacs but for F/F as well. F/F won't even show in SA but still contributes to the bug. Track attached. F16 in continuous search setting wont show any FF indication on SA but the IFF reacts as if it was a second source of IFF. iff not correct with FF.trk

Sorry, forgot to mention that. Current OB.

Thanks for dropping by BN! Glad to hear you guys could fix it.