WolfhoundCH

This was a known issue in early war Spitfires and Hurricanes, but was fixed in 1941: https://en.wikipedia.org/wiki/Miss_Shilling's_orifice

Even better here in Europe, hopefully drops Friday evening

You got it wrong. He states that they alternated which engine to start first to check on the vacuum pumps. I'm talking about which MAGNETO on either engine to flick up first - before even starting the engine.

Yeah there's a lot missing in that video. Clearing the engines (he mentioned it on the flaps) as well. Compared to that, I still facepalm in the startup video, when he puts an emphasis on how you enable the LEFT magneto switch FIRST! - as if that makes any sort of difference, while other things that were omitted most definitely would!

No reply.. yes please!

I can do that, but I don't see how that disallows me to prefer the thing to be released bug-free rather than too early.

You can only do that on the general Early Access idea, where ED tells you what's included and what's not. Now with the Mossie, I'm Ok with what's included. What I'm talking about is the stuff you don't know until after early access release - how bug-ridden the aircraft is. See how the F-16 came out back in the day So I'd rather not have them release it early due to some sort of pressure, but get rid of most of the bugs.

Or September 15 bc that's the date given on Steam.. Or whenever, bc really, they'll release it when ready. I don't like it either, I'd rather fly that beauty today than tomorrow.. but then, I'd rather fly it feature complete and bugfree, so I can wait.

Geilä Siech! Haha, couldn't resist.. awesome, looking forward to them!

Wasn't an FB Mk.VI but.. oh hell, yes! Are you volunteering to make one? XD

Just chiming in on the topic to show ED that it's not a new or unusual request, yes every WW2 aircraft should get chocks! Sidenote: British accent voicelines please!

Well, yeah.. I was more confused about the 'run the starter' callout for the priming, than the accent.

Check the youtube startup video, you can clearly see the option in the ground crew menu

That's a real pity to hear, I was about to buy it and fly it with my pilot. Wouldn't it be possible to build F-14 campaigns as multiplayer-capable from the start? I mean I guess there are quite a few F-14 solo pilots out there, but for those who fly it as a team, it's a huge bummer, we were looking for some content to play together.

Still didn't work for us tonight.

I love this thing, can't wait to launch AGM-114s with that. Do we need some sort of camera pod for that or can you implement the HF sensor directly to a display?

Resolved with this, misunderstanding: The DDD in the pulse doppler search modes displays returns at azimuth versus rate (closing speed) meaning that by reading only the DDD the RIO can only discern target closing speed and azimuth. The display indicates observed closure rate vs the ground (with own airspeed subtracted) as opposed to relative closure rate. While this means that a target directly ahead, moving directly towards the radar, will show true target airspeed this speed varies with target aspect and radar antenna azimuth. This reason for this is that the radar itself only reads relative airspeed which is then modified by subtracting own airspeed for display on the DDD.

Current open Beta version, in the screenshots I'm in TWS, picture 1 is a closure rate of 1088Kts, picture 2 is 801Kts. According to the DDD-Picture I shared, in Target aspect "beam", the lines all the way to the right of the DDD should be 200Kts apart, so I would expect to see at least that amount of difference between the two screenshots, but they're pretty much the same. Same issue in PD Srch but ofc harder to prove as I don't have a second source to show closure rate.

Didn't record a track but confirm the bug. D Version doesn't handover correctly and H version doesn't lock (but slews correctly). PS: Not always, but sometimes, maybe pilot error but haven't yet found out what I did differently, trying it like Wags on the Video. I mostly have to manually lock the Mavericks in the WPN page TMS up.

Not great for me, I set all my settings so they run smooth on every map even in large scale multiplayer so far, but flying NOE east of the Sea of Galilee into the Golan Heights, without huge cities or anything, I had very slight stuttering almost all the time. Will test in more detail after deleting the shader stuff and cleanup and repair.

As already explained by RePhil, ED broke it long time ago and PC is waiting for ED to release their MultiCrew API (Multicrew for the Huey and Mi-8), then it will be fixed. On the shutdown issue, it doesn't really shut down, it's just not synchronized so for the copilot it seems like it shuts down. The pilot can fly as usual, but all the bugs combined don't make multicrew much sense atm.

Hello rotorheads Many are hyping for the OH-58D Kiowa release by Polychop this year. Be aware that we are already training to fly Attack-Reconnaissance missions in the Gazelle and Ka-50 currently to later get a smooth transition to the Kiowa without needing to start anew with tactics and procedures. Join us now, train hard and become an Attack-Recon pilot, it's just going to get better with the Kiowa. More info here: https://forums.eagle.ru/showthread.php?p=4430959

Absolutely. We start training seriously on the Gazelle, developing tactics that work in DCS and training on the flying style we need for a Scout to work. This combined with flying the Huey on an advanced level should make the transformation to the Kiowa easy when we finally get it.

Just noting that the F-14 is out and seems to work, I'm flying it in multicrew on a daily basis and only rarely encounter issues. Even looking into the front cockpit from the rear seat, everything seems to work.

Yep in my experience, the main issue is desync, very often the copilot doesn't even see the rotor moving.. We also still got issues for the copilot slewing camera controls sideways.. I had to use the rudder to align with that tank :D