NineLine

I love Max Afterburners' stuff, but he is very new to DCS, its possible it's a setup issue or something else, I will flag this with the team, but remember we also have a number of SMEs looking at our stuff as well as some FM stuff still in progress. Thanks. 

Based on our roadmap further Link 16 and IDM Functions (after DTC Datalink Functions). Thanks

The Training mission states to go STT but your track shows you staying in RWS/SAM.
You must be in STT and within 30 degrees off the nose or tail of the aircraft and be within around 24 to 24 nm.

We are still updating and tuning some aspects of our radar, once that is complete I will again bug them about the whitepaper. The good news is the discussion and starting of the whitepaper seemed to have led to some improvements which should be coming soon. Thanks all!

It depends, a kill is not guaranteed by no means. I have seen 1 kill a SAM, I have seen it needing 2. If you have a real bad day it kills you (most of my flights). 

Reported, thanks!

I'll take a look.

Thanks for the report, I was able to report the issues with the push to new waypoint, I will report. 

Hey, thanks for the detailed report. This is already reported and I will bump that report with your information as well. Sorry it is taking so long.

Fixed internally coming to a future patch.

Dont tempt me 😄
 
I see LODs for the MIG-29's in the shape folder, am I missing something here?

Did you undesignate? Please supply a track. Thanks. 

It's fixed internally but wasn't merged in time for this latest patch, sorry 

I was able to reproduce internally and will report, thanks all!

All our switch settings are set with discussions with our SME. As well, I just had a look and the battery switch is set to off at cold start for me anyways. Do you have Sync to HOTAS checked and maybe it is set to on with your controls?

Not sure I get the joke? We put a lot of work into the BIT system and most of it works. There still are items to tune and add as stated in that news item.
It's an item we are well aware of, but a rather minor one that we will look at when time and resources allow. In the meantime, we have much more pressing matters for the Hornet.

This is a task we hope to start soon for both AAR and ALE-50. Thanks.

Yeah if you see anything like that send me a track so I can review, we have tuned failures a little, but it isnt released yet, should be next open beta I think.

Yes, this has been reported earlier, key bindings for stuff like the rudder and cyclic are sluggish.

No, we hope to finalize the Viper FM/FLCS next month, and after that, we'll do a complete review of the Hornet FM/FCS.

I talked to the team about how these circles are rendered, and because they are 2D engagement zones, they are a rough estimation for middle altitude of the gun, it can be longer and shorter depending on the altitude of the target it is aiming at. There is not a good way right now to show that in DCS. 

Ok, so it really isnt a bug. 
Orbit is based off a Orbit point, so when you use Push Task it goes back to the last known point, which is the last WP past (or the first WP in the route).
If you use Set Task, it wipes out the set route from the ME, and that spot in time becomes the initial point for the new route and is able to orbit there.
Hope that makes sense.
In my mind, and I haven't tried, would be to set some more WPs in the route so that the AI doesn't travel back so far. Not ideal or perfect, but should make for a little closer to what you want.

Response from the Team
 

This is still fixed internally, but hasnt been updated to release, another reminded sent. Thanks.

Already reported, thanks guys!

Just to follow up on this, the intent is not to allow changes to the load out of flares and chaff at all right now. This is based on real world info and feedback. Thanks.