captain_dalan
-
Posts
2724 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by captain_dalan
-
Here's an idea.... as people don't read or just chose to ignore the sticky about the F-14D not happening, why not merge all the requests, slap a top post over that thread that says "not happening" and then merge every new request in that thread. Honestly it's becoming not just irritating but also cluttering the threads with the same question over and over again
-
Has anyone measured if they are included in the missile-loadout weight?
-
Maybe there's something peculiar about your setup -
My pleasure. I think this on HB side for now, at least the part with the RWR going silent after a while. I can't be sure though, we are yet to have a confirmation from an official dev or tester member.
-
I hope it works out!
-
So it's not just the 31 then
-
As a divergence from the thread about the AIM-54 and RWR, i made a few tests involving the MiG-31 and the R-33. I tested only 3 planes, the F-14, F-16 and F-18. The initial launch is detected by all RWR's. However, in the F-14 at about 40-45 nautical miles, the alarm switches from being launched on to being locked. Can anyone confirm this behavior? Is it just me? Is it a bug? Or is it working as intended? And if so, why is it so?
-
I have a dedicated HAT on my HOTAS for it. Up-Down switches the between HSI/TID and Left-Right trims rudder. A bit wacky and unrelated setup, but it works if you have an extra HAT
-
I was talking about the R-33 and the MiG-31
-
Just did the same test as before in the F-16 and the F-18. In both planes the RWR starts the launch warning as soon as the bandit fires the missile. It also doesn't stop until the missile hits you or misses you completely. On the other hand, in the F-14A and B, the RWR starts the launch warning as soon as the bandit fires, but around 45 nautical miles it switches back to being locked warning. So this is an F-14 SPECIFIC issue, and quite possibly a BUG! Can anyone else confirm this? Someone from HB or a mod?
-
This could be a feature. Not an expert myself, but interviews with people who flew with or against it, seem to imply simple "check" turns were enough to "break" the TWS "lock".
-
1. That is indeed weird. Never happened to me before but if it's constantly repeating to you, then it's definitely worth investigating. 2. This is why i suspected home on jam. Have you talked to someone from ED about this? Is it a missile feature? This does happen to me as well if i don't take any action after launch. The RWR will go haywire on launch, then go silent, then the missile will hit. However i have zero knowledge on the operational behavior of the MiG-31/R33 weapons system as a whole, or how that translates to DCS. All i know is that it should FOX-1 guided by a PESA, but it wouldn't be the first time DCS engine limitations resulted in wonky feature implementations. I.E. the AI counter-measure-ing the instant you launch at them, despite you launching passive or TWS guided ordnance
-
Just did some tests against the MiG-31. My intent was to test launches from different altitudes in an attempt to correlate launch warning with RWR blind spots. Alas, the AI would not cooperate as desired. Still, all launches were detected. My hypothesis: Either the MiG locked you from a blind spot, or he has lost the lock, but the missile HOJ-ammed you. Were your ECM on during the encounter?
-
No time (on my side) to participate in a squadron, but as an individual and sometimes as one of a pair in MP, i generally prefer the more aggressive approach. Especially when outnumbered. Even against targets with longer sticks. Hit them hard and keep them on the receiving end. Does it conform to any real-life doctrine? I have no idea. Never been a pilot IRL, even less so a military one, but from a tactical perspective, given my platform and mission of choice, this is what makes most sense to me. Maybe the chainsaw would work better for more modern planes, heck if i know. I like to fight where i have the advantage though, and the chainsaw just doesn't seam like its providing enough of that in this case. Just my (arbitrary small integer of) cents here. But if you have a cooperative likeminded individuals to fly with, why not experiment and share the results? Tell us what works better in CAP, Fighter sweep or Intercepts?
-
Jester speed callouts in ACM...what triggers it?
captain_dalan replied to Ryano4242's topic in DCS: F-14A & B
Ooh, that would be neat for all the demo teams out there! Speed calls on demand! -
I actually got my AI wingman to engage with multiple Phoenix shots here: But the trick is tell him to engage at long distance. He actually goes FOX-3, launches two times and scores 1 hit. Left to its own devices though, the AI will just fly to the target until 30 miles or so before engaging. I know, these things are best conducted in controlled conditions and my as many players-testers as possible
-
A pleasure!
-
That indeed should be so. I usually get a launch warning from a 31, the R-33 being FOX-1 and all that, but there were instances when i didn't and always attributed this the PESA nature of the radar. Has anyone discussed this with ED? Their patches never mention the 31, yet the behavior does vary from time to time. I've never dropped the issue as my statistic sample is too small to make any rational deduction on what is going on.
-
This one is more difficult to judge. If the AI uses the same rules as human controlled F-14, then the missile could go active extremely close to you and by then you were belly up. How far away was that F-14 that engaged you? By new or old i meant, what F-14 was used by the AI. Discussing with some fellow mission creators, i confirmed that if the AI is using the HB F-14 as opposed to the old ED F-14, the former would refuse to engage on it's own until very close. We are talkin 20 something NM range for medium altitudes, and 30-ish NM for high altitude shots. Even done AI VS AI experiments of ED F-14 VS HB F-14, MiG-31 VS HB F-14, MiG-31 VS ED F-14 and F-15 VS HB F-14, it was the same in all scenarios. The only workaround is the use the AI as a wingman to a human player and let the player order the AI engage at long range. How do you get the HB F-14 to engage at longer ranges when controlled by the AI?
-
But if you see in the left side of the screen an F-14B is smacked in the nose by an R-33. So it was a MiG that shot him
-
But is this a bug or a feature? Maybe this is exactly how the AWG9 should behave.
-
Weird, are those AI F-14's the old or the new F-14's? Cause the new ones? Cause the new ones won't engage till well inside 30NM. As for the R-33, this one most certainly showed on my RWR:
-
Amen
-
-
Good catch, yeah Pilot Lock-on Mode is what i had in mind, PAL is what i typed! .
