Bearfoot

+1

YES! I was on the verge of posting something like this, but then I thought I would experiment to see if I could reliably reproduce it. Never got around to it before you beat me to the punch, but ... YES! On a few ocassions now, Jester JUST KEEPS SWITCHING TO RWS. No idea what was going on. The last time this happened, it was when I launched an Phoenix in STT lock and Jester dropped the lock. Then he went back to RWS and for the love of all that is the 80's, he would not go to TWS and stay there.. I have a button bound to "TWS mode", and me an Jester would go back and forth. Every time I switch to TWS, he goes back to RWS. I tried VLS/PAL and then back to TWS, but nope -- he goes to RWS. Then Itried switching the radar on/off. Same. After a (long) while, I managed to get Jester to to keep in RWS.This time, I didn't get shot down arguing with Jester. The last time, I did. There certainly seems to be a swarm of gremlins infesting the radar system since the last patch

I've noticed this as well, since the last patch. In fact, since the last patch there have so many gremlins in the whole system. TWS dropping lock. Missiles not tracking. TWS not picking up contacts. TWS picking up too many contact. etc. etc. These have been reported in a number of places, as different issues. It's confusing, because there is a lot of overlap in the issues, while at the same time, many seem different. https://forums.eagle.ru/showthread.php?t=281325 https://forums.eagle.ru/showthread.php?t=280902 https://forums.eagle.ru/showthread.php?t=281286 https://forums.eagle.ru/showthread.php?t=281319 https://forums.eagle.ru/showthread.php?t=281346 [EDIT: of course TWS does not lock targets! But you knew very well what the OP meant as much as I did: He meant it's not detecting them or picking them up. ]

Yes! Except in my case it's contacts donated via data link. Yes! And yes again! Presumably related to losing all contacts in TWS. Either way, because of this dropped contact on launch, the next time I launch, the same contact is usually the target. So it gets another Phoenix headed their way. And if again there is this weird IMMEDIATE loss on launch, it repeats. So, without really wanting to, the same contact has multiple (3-4) 54's headed their way, with most (and often all) of them not supported by the radar. So most usually miss.

Just chiming in to agree -- yep, things seem to have gone off in the last update. Targets coming in hot not being picked up in TWS. Phoenixes just flying off on their own adventure, launched on valid targets but no countdown appearing (sometimes up to 3x).

Two questions regarding this: (1) I've noticed that sometimes, with multiple missiles in the air tracking, for e.g., diverging targets, Jester switches to a fatter cone, presumably to keep both targets in view. I used to think that I have lost the missiles due to this being RWS, but then I noticed I still had threat numbers and missile TTI countdowns on the TID, so thought maybe it was still TWS? Do you know if this might be the case? (2) If you can indeed, get "fat cones" in TWS, do you know then how to tell whether Jester is TWS or RWS mode reliably from the TID? Is there any other indicator?

Thanks for this info. Very useful to have it compiled in one place!

I don't have a track (yet), but think this explains some behavior I have seen a LOT! Right after launching a Phoenix, the contact gets dropped. I thought it had something to do with switching from TWS-M to -A on launching the Phoenix. But this analysis makes more sense, as it comes right after the bandit notches.

Sorry if this has been discussed in the 100-odd pages of this thread. But does anyone know what precision guided weapons the model of the Hind DCS is working on will have? Google shows the only one the Mi-24P has is the 9M114/AT-6, which radio-guided through a visual TV system. Is that correct and is that it?

Thank you for these videos! I love the explanation of technique and process and all the other stuff going on. Really insightful and interesting. Are these missions/campaign available for us to try out ourselves?

That's a negative, ghostrider

Yes, but not that in this case, as evidenced by that first shot in the air. To get some more out of the way: - still had Phoenixes on the rails - still had power and all systems intact - still was flying with positive velocity and altitude - still was in the cockpit - and a few others.

I do this ALL the time! But in this case, this was not it -- I got the first missile off.

This might kludge through the crazy prioritization (though HB's promised "Next Launch" request will be ideal), but it does not explain why the Phoenix's did not fire

We are in TWS mode, and we have contacts showing. Contacts all have threat numbers. I command a launch .... and NOTHING. Hold down fire key. Nothing. Hammer fire key. Nothing. Mash and hammer fire key. Nothing. Trying to figure out why. Here are the specifics: (1) Acquired several contacts on TWS-M (azimuth skewed right). (2) Have data link, and some of my unknown contacts (staple on top) are identified by donor as hostile (chevron on bottom). (3) Jester IFF classified one of these has hostile (chevron on top, matching one below). Peversely, this is the furthest contact that's almost 50 degrees off nose, furthest away from and heading on a parallel track, i.e, will not be coming toward me. This gets priority 1). Nice choice. (3) Meanwhile, there are 3 other contacts on my nose (or just off), close, and heading toward me. Fast. Jester has not yet IFF'd, but datalink donor says they are hostile. These are now. They are good (strong) contacts, and definitely through onboard sensor (i.e., not just datalink: staple on top, chevron below). And there is a threat number (2, 3, 4). (4) Press the missile launch trigger. Phoenix away to poor sod minding his own business off in the corner. Ok, no matter, now to focus on the real threats. (6) So I really would like to fire at targets 2, 3, 4. Coming in hot and close. Still unknown on IFF, but (a) strong contacts locally acquired on on-board TWS and (b) datalink calling them hostile. So 3xFox3 Phoenixes away? NO! I cannot! I just cannot get a missile off! No matter what I do. (7) Turn toward threats so directly on my nose. Still in radar cone. Still good contacts. Still have threat numbers. Fox 3 ..... NOPE. I cannot figure out why. Maybe Jester (or the system) only allow launches on targets that are confirmed hostile using onboard IFF? But from some unfortunately friendly kills, I'm pretty sure that I can remember firing on unknown/ambiguous contacts? Maybe somehow the first missile in the air going off to something on my right is preventing a launch to something in front? But all contacts are within the displayed radar scan cone. Anyone have any ideas or insight? EDIT: And, oh yea, for the conclusion of this tale: (8.) An AIM-120C ignores social distancing rules and rams itself into my eye socket. (9) Fin

I've had no issues on multiple drops on land targets in SP with external lasing. Haven't tried any other situation. In issues like this, everyone saying either "Works for me" or "yep, broken too" should probably clarify the full context of the situation --- SP vs MP, human RIO vs Jester, self-designated vs external, moving vs still target, etc. etc. That would really help clear up all the confusion about whether or not it is an issue, and zoom in to the specific aspects. Thing might work in one set of conditions but not another.

Kenapa kamu ingat saya orang puteh? Kamu dan kawan mu dengan "ini bodoh" / "itu bodoh". Macam kanak tanpa adab cuba permainan dewasa tetapi tak faham dasar-dasar. Saya rasa malu untukmu.

It's a shame that the AIM-54/AWG-9 system designers did not have you input during the drawing board phase. Crazy that didn't think of that. ... or maybe the link is just one-way and the aircraft has no way of knowing what the missile is doing? I dunno.

I could be wrong, but as far as the behavior goes, I think this is modeled as per the actual aircraft --- when supporting a Phoenix in flight, you have to stay in TWS-Auto cannot go to TWS Manual. I think that if you need to you can force the support for the missile to break(maybe by going to pilot dogfight modes PAL / VSL and then out again? If so, you should then be able to TWS-M.

+1

Thank you and your team, not just for a wonderful module but also for the clear commitment and passion that motivates your work on it!

You probably need to provide quite a bit more information. E.g., what mission? human cold start, "cheat" cold start? On deck (Stennis? Supercarrier) or land? For the record, I've not had noticed any issues with alignment in any of these scenarios. At least, as far as getting to the point where the TID is on and I'm told "ready to taxi".

IT IS NOT ABOUT REALISM. It is about developer resources. If someone could wave a magic wand and just make it happen: great, I don't care who uses it. If ED decides to do it and this results --- as it will inevitably, due to basic thermodynamic laws of the universe -- in delays to bug fixes, module completion, better AI, etc.: that I do care!

Hi Razor, I agree completely that this should be enjoyed by each indivdidual in whatever way they see fit in the privacy of their own home :) ! I don't think the vote means very much in terms of ED decisions, but in answer to why someone would vote no --- because this would represent an investment of developer resource, effort, and time that should be better spent elsewhere. Like, for e.g., better AI, optimization of performance, bug-fixing, module-completion, better mission generation, dynamic campaign etc.

Easy radio / auto start etc. are about systems management. AAR is about flying. If easy AAR, why not easy BVR? Easy BFM? Easy coordinated turns? Easy formation flying? Why should easy AAR take precedence over easy BVR or BFM? Because some find one boring and the other fun?