EGG

I meant to post back here (I thought I had done) to say that the problem was CG-NAT on my ISP also. Once that was removed it was a lot easier to get in. And similar to krakovv I hadn't had the problem with other multiplayer games also.

I was more querying the launch modes which apply for those radar functions. I should have used Pitbull rather than 'Maddog', but I'm going by the conversation here: https://forums.eagle.ru/showthread.php?t=238762 Reading it a bit more, it sounds like PD-STT is meant to launch in pure SARH, but at least at the time of that thread it wasn't implemented and was waiting on the new missile API/TWS-A. So launching in PD-STT will still erroneously give an active missile.

Thanks, I'll have a look

Hi I'm trying to unravel two things. Predominantly I've flown the F-14 as pilot, but figuring out how the radar/lantirn work has been a joint task between me and my RIO. If you're losing a track on the TID in TWS due to notching are your options at that point: a) quickly switching to P-STT or PD-STT? b) hitting the Track-Hold button? We're finding when targeting say an AWACS flying in a circle, it will just disappear for periods of time as it flies in a circle. I would have thought notching the AWG-9 would have taken a bit more effort than a lazy A-50 circle? Second question is on the AIM-54, I understand that currently it behaves "like the AIM-120", but 90% of posts tend to drift towards talking about how it should behave, rather than how it does under the current missile code. Does this mean that: 1) It's presently accepting course-corrections for it's full flightpath 2) It never ordinarily cuts over to Pitbull on it's own seeker 3) If lock is lost on the AWG-9, it will go Pitbull? 3) P-STT and PD-STT are meant to be Maddog and SARH respectively, is this the case or are they also ARH? If you're in TWS, have fired and swap to STT, will that alter the missile guidance?

In my case if it was Firewall rules (Windows or router) it would be applying 100% of the time. But sometimes I can get in and sometimes I can't. A couple of people (one here, and one on PM) have mentioned the problem goes away if they use a VPN, so I'll try this next time I see the issue.

Oh sorry, maybe I've been looking at old documentation. I had thought only the DCS E-2D was currently enabled for Link-4A and the E-3C wasn't. I'll have to remind my (human) RIO to turn it on next time.

Link-4A being the AWACS datalink, rather than fighter-fighter. It appears to be more commonly referred to in technical manuals as TADIL-C. Hunting around on the internet I can find a variety of references that suggest both the E-3A and E-3C supported TADIL-C at various points of their lives. I'm unsure what can be posted here, but one document is the Congress hearings from 1977 when Iran was requesting a purchase of the E-3A which notes out what would have been specified on the Iranian E-3 vs the US version.

Curious, how would TWS-A work if there are multiple launches and multiple targets? Does it try to factor all of them in, or just target #1?

So it appears to be linked to other internet activity. I'm on a 50mbit connection, but if there's a slow rate download going on (around 100kb/s) then it will have much more trouble syncing. I'm surprised it takes this little to destabilize it, the other day I was playing AoE II multiplayer while the 16Gb HD pack accidentally downloaded in the background without me really noticing.

Symptoms About 2-3 weeks ago I started having issues connecting to MP servers, specifically with the game stalling on the Clouds screen with "Please Wait" shown below. Sometimes I can connect, sometimes I'll try again the next hour or day and I can't. However the success rate on connecting seems to be dropping from 70% to about 20%. Tonight I've tried and failed to connect to GAW, 104th, BlueFlag, TTI-Aus. All Caucasus maps. The last message in DCS.log when it stalls on this screen is: 2019-11-05 14:26:20.663 INFO Dispatcher: loadMission Done: Сontrol passed to the player And if it succeeds it will write: 2019-11-05 14:26:20.663 INFO Dispatcher: loadMission Done: Сontrol passed to the player 2019-11-05 14:26:20.663 INFO NET: sync seems good, telling server we are ready 2019-11-05 14:26:20.924 INFO NET: MsgClientInit(serverTime=49622.171759, modelTime=4996.565039) 2019-11-05 14:26:20.924 INFO NET: local time=47.924837, offset=49574.418087, error=0.005100, samples=16 2019-11-05 14:26:20.924 INFO NET: scheduled start at 47.748644 2019-11-05 14:26:20.924 INFO NET: MsgClientRun (then more stuff) What I've tried I've tried repairing DCS, no change. I've also tried completely reinstalling DCS (and removing all files and \Saved Game\ data) without SRS/Tacview, still the same however. No mods are installed. What I've ruled out DCS is Open Beta on an M.2 NVMe, 64Gb RAM. It can load singleplayer lightning fast and has no trouble with FPS. I'd previously been playing DCS MP for about 2 years and built a new PC maybe a month ago. My ping is around 110 to Aus and 240-270 to US servers. No wireless on local networking. No firewall messages. Anyone have any ideas? It makes it difficult to hook up with a wingman when I'm unable to connect.

Any reviews or thoughts on the stick?

Just to bring this thread back up I found someone had uploaded a decent video of the three possible BK90 dispersal patterns: https://www.youtube.com/watch?v=Zg0W4AjpQd0

I've had this happen to me about three times in multiplayer. I'm still not certain if it's visual or it's actually stuck. Raising/lowering it 3 times didn't fix it. Taxing and take-off were pretty mild? I'm sure a Viggen QFI would have been horrified, but there were no bad thumps.

This was the last post I saw on the BK90 approach altitude: https://forums.eagle.ru/showthread.php?t=230957

Interesting to read this, it seems there was effectively an F-8J 'early' and F-8J 'late'. It's from the crusader organization website, so I assume the writer is an ex-pilot and the text has been eyeballed by many other ex-pilots. https://www.f8crusader.org/history.htm