WolfhoundCH

I didn't fly the Mosquito for a while, being annoyed by getting a smoking left engine every single time for no reason at all. Now we received a few updates recently, I'm really surprised that this bug still isn't fixed. Is there any update on it? Other than that, I almost feel she's finished, performing well and fun to fly.

Any chance for this to read the data that is currently set on the F-16? For example, I use DICE to set CMS, and the default radio presets are mostly OK, I just want to change a small thing.. how do I do this? Further, I expect that radio presets are overwritten by the mission settings? Other than that, I'll use it for the MFDs which was annoying af so good job.

People, do you realize we are talking about Pulse-Doppler radar? Ground clutter is no effect because the aircraft (as long as it's not notching) has a clearly distinct closure gate compared to ground. The only place where we should get a ground penalty is pulse, and there only if an aircraft is close to the ground. And not just "5° nose down = penalty. That's not how radar works. The FCR nerf really made the BVR king the BVR loser now, and there is public data stating differently. I was at angels 40, locking a hot target at Angels 38, so no ground clutter even close, didn't work until 35nm.. how am I supposed to launch an AMRAAM at 45nm?

Considering that there were numerous accounts of runway excursions on take-offs, I do feel like this probably isn't realistic. Also, leading with the left engine even slightly doesn't help, quite the contrary.

Also to simulate engine failures to train single engine handling and landings.

Thanks, I always forget how great VA is, I mostly use it to get buttons to work that I can't reach well with my mouse in VR, especially in helos. If any others have the issue that the flaps don't work, I had to use 0.5s for the flap lock, otherwise the flap down didn't register.

I use the friction slider on the Warthog for prop pitch, with buttons that modify which prop I'm changing (or both). Before I feather, I go into low RPM on the affected engine, then switch to the working engine, so nothing should change the prop pitch.

I still can't do it properly. Sometimes it feathers, just to automatically unfeather a min later, on low speeds. Often enough it doesn't feather at all.

Yep, additionally if there was an option to automatically remove the flaps + gear locking levers. IRL it's easy and doable with one hand, just remove the lock and flaps down / gear up. With the Warthog for example, it's not doable at all with the standard flaps switch and a button for the gear so you have to use the mouse every time, and that sucks.

Weird, I don't have this issue, is it with coldstart or hotstart aircraft? Also I think the gyro compass doesn't drift, which is understandable that it's not simulated, but would be cool.

Ok, thanks. I'll test some more.

First test (no trackfile available): Coldstart aircraft, takeoff, gear up, then: - Throttle starboard engine: Idle - RPM starboard engine: Fully back - Feathering: Push Nothing happened, the engine didn't fully feather, and the feathering pushbutton stuck pushed in, couldn't pull it out again (as stated in the manual). Second test (Trackfile attached): Instant action "Free Flight" Channel - Throttle starboard engine: Idle - RPM starboard engine: Fully back - Starboard Feathering Pushbutton: Push - When engine stopped: starboard fuel cock: Off, starboard magnetos: Off Step I forgot: starboard radiator was kept open. Now the prop feathered properly, the engine stopped, all perfect. Until after a while, the engine started windmilling again at relatively high RPM, thus producing too much drag, so I had to get fuel and magnetos back on. Trackfile: https://drive.google.com/file/d/1c427g56ZAtA7yIzj3hPTzS05CXFuaOVV/view?usp=sharing

100% agreed. I'd even keep it out for gun strafing and bombing.. better to get use to angles and stuff and use "the force" than needing to lean over like that and use a sight that blocks important instruments.

Rift S, RTX3070, 7800k Mosquito in channel, mostly fine but some stuttering once in a while (and once it went on for like 4s and I almost crashed due to it).

I bet IRL they'd remove the circuit breaker for that thing if possible XD

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