maths314

If I'm remembering correctly, the radar is supposed to switch from LTWS to TWS if you launch on a target.

coming in 2 - 4 weeks™

Which would be fine, but right now the radar is so basic the radar cone wont even follow the tdc when switching to a narrower scan zone. :doh:

Remember it's not just no mode 4 response and NCTR print, it's any two sources that don't give a response, i.e. 2 F-18 mode 4 interrogates, 1 F-18 and awacs, 1 F-18 IFF and 1 F-16 NCTR, etc... There's also the possibility of someone PLID'ing a track file as hostile or unknown.

I agree that the TWCS throttle isn't exactly ideal, you can fix the stickiness by just using some of this. https://www.amazon.com/Lubricant-Grease-Nyogel-50g Tube/dp/B00W6KWK1Y If you use a different lubricant, make sure it is high viscosity meant for heavy dampening. Edit: After using that 767A lubricant I could AAR on any platform without much trouble both in DCS and BMS

I don't see anything related to not having enough information to do the ATFLIR

I would second the thrustmaster twcs stick, it's the only stick in that price category that uses hall effect sensors. I never had a problem with dead zone drift like other cheap sticks. I eventually upgraded to a warthog years later.

I think what would make most sense is to have an option for mission makers to choose whether players can frag their own packages, but that would require at least some basic DTC implementation. Similar to what a certain F-16 simulator does it.

Consider the possibility that work done on the Viper's capabilities is directly transferable to the hornet considering their similar roles and systems. If that is the case, then the devs moved to the viper might not have delayed say TWS for the hornet at all since they function so similarly, or at least very minimally.

I believe it's a bug if you switch scan width while in spot mode.

You'll get it when it's ready. Someone starts at thread likes this almost every day and I'm getting sick of it.

Can confirm, though I don't have a trackfile yet

Obviously there wasn't going to be anything added to the hornet this week knowing the schedule, so this doesn't make sense. There was no reason for anyone to assume otherwise.

Incorrect, https://forums.eagle.ru/showpost.php?p=3897638&postcount=151 Clearly states last hornet update was May 8th, meaning there shouldn't have been an update on the 22nd.

If you had bothered to read wags' update posts, open beta has been moved to a monthly update schedule.