Shimmergloom667

On October 18, Wags said that DTT for SAM is being worked on: https://forums.eagle.ru/showpost.php?p=4077486&postcount=28 Can we get a confirmation, that it (and Auto SAM) is not yet working? Upon bugging a target in CRM mode, RWS submode, the FCR should enter Auto SAM mode: the Azimuth and Bar settings should stay the the same as the original RWS settings, the TDC should stick to the bugged target. Upon slewing the TDC, the FCR should leave Auto SAM, enabling full TDC control to e.g. bug a secondary SAM target. This is not working correctly right now: upon bugging the first target with TMS up, the radar defaults to 1A / 4B setting (which is the initial track update) which should then grow a bit larger, depending on quality of scan needed to keep the track files updated. The TDC is then not slewable anymore, thus it is not possible to bug a secondary SAM target.

SAM dual target track is not yet implemented. Upon bugging a target in CRM mode, RWS submode, the FCR should enter Auto SAM mode: the Azimuth and Bar settings should stay the the same as the original RWS settings, the TDC should stick to the bugged target. Upon slewing the TDC, the FCR should leave Auto SAM, enabling full TDC control to e.g. bug a secondary SAM target. This is not working correctly right now: upon bugging the first target with TMS up, the radar defaults to 1A / 4B setting, which should expand after the initial bugging. The TDC is then not slewable anymore, thus it is not possible to bug a secondary SAM target. Wags said in an earlier post, that DTT is being worked on: https://forums.eagle.ru/showpost.php?p=4077486&postcount=28

Would you be so kind as to check your information? According to my sources, which I can't post here due to forum rules, upon entering the TWS mode the radar should default to 2A (azimuth 25°) and 3B (3 bar) scan. It should then automatically start building trackfiles from RWS search targets. In DCS it does not and stays at the previous azimuth and bar setting from RWS, also it only starts building trackfiles once you either bug a target pressing TMS up, or bugging all by pressing TMS right (and THEN switches to the correct 2A / 3B scan settings). The track file is attached to this thread I posted on a similar matter: https://forums.eagle.ru/showthread.php?t=256157

Expected behavior: In CRM mode, RWS submode, TWS should be engaged upon long press (>0.8 sec) of TMS right without having to release the TMS switch Observed behavior: TWS engages on release of TMS right long See attached track tws_test.trk

He also acknowledged that AACQ will be worked on in December, so I'm pretty confident we will see it working as intended soon.

Well, so YOU say - all I can say that on Discord, Facebook and reddit people are going nuts for the Thunder. Not really less than for the others you mentioned. That is true. :)

Definitely the best in-depth, no-nonsense Videos out there. And compared to another big youtube DCS channel you actually know what you are talking about :)

It's not yet functional.

What's the problem? Voiceattack has a 4-way bound on my Throttle for TX1, 2, 3 and 5 Vaicom doesn't need specific options set for the Huey on top of that SRS has the same 4-way bound as Voiceattack DCS doesn't need special options set for that, the aforementioned 4-way isn't bound in DCS itself The same 4-way is also push-to-mute in Discord, so I can hang out with the squad in both SRS and Discord (if needed) and I don't transmit over both. Now you just need to activate the radio you want to use in the Huey over it's radio dial. Since it only has one radio, I can only use TX1 for Voicattack / VAICOM. Same with SRS.

With this sort of thread replicating every few days, I have yet to see constuctive criticism. But perhaps me, being very pro-EA as a concept and not in a hurry (I wouldn't mind if the Hornet takes, say: 5 years or longer to be feature complete, others somehow seem to do), is just tired of seeing the same old arguments on the forum, day-after-day. I should get back to bug reports and answering questions about modules that people want to know about.

They know that enough people like the concept of EA and taking part in the development of a product that it will both keep the lights on and enable them to test features with a broad audience. They sure as hell openly acknowledge that this might not be a concept appealing to everyone. I like it, and I will test the new VoIP implementation, even though the squad will stick to SRS until latter stages of the inbuilt VoIP. So: noone is making you buy a thing if you don't want to, and no one is sugarcoating what the EA process really means. If that's not for you (generally speaking): don't take part in it. Sometimes things break, sometimes they don't. Are we backtracking through the last dozen OB updates now and summing up which new stuff broke existing features and which didn't? The pretend radios in our pretend airplanes will work as before, you know all that calling up menus and being able to communicate with the AI. It will also, in good times, get features that are present in a 3rd party product and that no one is taking away from said product, if you like to keep using it. Which product (from ED, not from 3rd party devs) has been taken out of EA incomplete so far?

Of course, BD has already confirmed that he will update the manual.

Yeah, that's probably only you

So much this! Don't like to test the early state? Don't do it. Just like EA modules. Don't like EA? Don't like beta testing? Don't buy it, problem solved.

It is not, the -C is an interceptor. (but probably still good enough)

What is even so surprsing about releasing it in stages? Even given that VoIP is nothing new and probably a lot of existing open-source technologies can be implemented, it still needs to be tailored to the game, and releasing in stages enables them to troubleshoot it along the way. We never know just how long any given feature will take to fully implement, but there's also nothing hinting at a 3rd stage being years away once the initial implementation starts progressing.

Yeah, you sure can talk a lot. Now let's take some time to laugh about that together.

I like how people who obviously have no clue about software development are throwing around opinions on what is "too long" for any given piece of software development. That will sure teach ED!

If a legacy USN /USMC Hornet from around 2005, which is what we have ingame, didn't carry these, then it's 100% correct they are not in game. /thread

There is no numeric counter anymore, only the low / out indication lights.

No, it isn't

Well, to be fair: Razbam has no say on when ED ports beta to stable.

Well, that's exactly what Ramsay just explained: it is in the middle of a major overhaul and needs some kinks ironed out.

We dont. There is no numerical count.

Chiming in with words of support here, too. The Hornet has gotten stuff in EVERY update, some minor, mostly major. It is clearly being communicated that work will continue with increased manpower in the coming weeks. You guys are doing great and I am happy to be part of your EA programs, seeing the modules mature whilst being able to take part in the process through bug reports. Please continue your good work!