backspace340

Wags said that the Hornet and Viper can be donors for each other in response to a Youtube comment on the topic, so sounds like it's a no for the last two questions. I don't think we'll be able to custom create DL flights in the Viper (otherwise Wags would have showed us how), so it'll probably use the mission editor flights like the Hornet does already to determine who your wingmen are in DL.

I wouldn't expect that - Wags didn't show us or explain how the frequency setup worked and, going on past history, that normally means it's not functional. It'll probably be the same as the Hornet's, where it takes the flight setup from the mission editor to create the flights.

Only when the radar didn't have a track - once the radar picked them up, they changed to neutral white squares again. That's what Wags is demonstrating at roughly 4:10 here:

It's because they currently only model the ammo in the gun as HE rounds, and they're incapable of damaging anything more than lightly armored or unarmoured units. It's fairly easy to see - you need almost all your rounds to kill a BMP-1 (if you're lucky), but try and shoot a Roland/SA-6/SA-11/SA-15 and you do no damage. The Harrier can one shot kill all of those.

Your steerpoints won't be in the right place, distance to steerpoints doesn't work properly, and I'd guess that CCRP won't work properly either (though not sure of that last one).

Wags also said somewhere recently that the map fits the current line-up of ED's WW2 planes, so it's probably Europe. His previous hints were that it was ideal for multiplayer and not resource intensive (so sounds like lots of water). My current best guesses are something like these (each square is roughly the same size as Caucasus/Persian Gulf): The exact map shape might be different, but I think that's probably the best mix-up of European conflict areas with lots of water that fit both modern and WW2-era scenarios.

I don't think there is one / I don't think it needs ticking even if there is one. I was playing some older missions at the weekend (from just after release, so before the INS worked) and just putting the switch to stored heading worked every time - just switch it to that and it'll be aligned and say RDY in 90 seconds or so. No need to enter your current lat/long either like people were discussing earlier in the thread (guess that's only for the full alignment, as it was never needed with stored alignment).

I spotted something that seems to be a bug - your first IFF scan of any mission is unreliable, it will only return an IFF result from a small sub-section of the friendlies that are in your scan volume. This one is really easy to reproduce - play the attached mission and press TMS Left once you're in the plane, the first scan only returns one result, press it again and it will return an IFF ping for every plane in the scan volume. Every scan except the first one returns an IFF hit for everyone it should - for some reason that first scan is always deficient. You can restart the mission and you'll see the same behaviour again. Unfortunately, there's something fundamentally broken with track recording on my game (which repairs aren't helping), so I can't attach a track. But I can attach a simple mission - which you just have to launch and press TMS Left to scan a couple of times. I've also recorded the behaviour here: iff.miz

I had the same thing happen on that mission - I solved it by closing the refuelling bay door. Turns out I forgot to switch it off after tanking.

Should be the same - it's carried on dumb pylons/racks with no digital connection to program it, so should need setting on the ground. It might be possible to dynamically adjust HOF in the CBU-105 though.

Really great missions - couple of bits of feedback: In mission 2, you're told to push 10 right, but 10 right is preset to 375.00 which isn't possible to tune on VHF. I looked in the docs and it's meant to be 37.5. In mission 3, the tanker is flying waaay too slowly - it's at M0.5 (200kts!), it should be up at M0.625 or so. It'd be really handy to have the key radio frequencies spelled out in the briefing - having to access the google doc in VR if you misheard/didn't catch it in time or if the radio freq is preset to the wrong frequency is pretty annoying.

From here: https://forums.eagle.ru/showpost.php?p=4079913&postcount=3 The F-4E and AH-1F aren't on the roadmap anymore, they're just hopes for the future.

They changed the HOF to 1500ft because the bomblets were hitting the ground and not detonating - that change has made CCIP much harder. To use them at low alt, put the CCIP pipper on the target and then hold down the pickle button - it'll designate that point for a CCRP drop and perform the CCRP drop after a few seconds.

The in-game IPD is not the same as your physical IPD, it's a setting to adjust the world scale (so items feel bigger/smaller depending on your setting) so things feel the right size for you. They really should have given it a different name, it's too confusing calling it IPD.

The Viper is getting TWS in today's patch according to bignewy and the patch notes BTW, so timelines might be a lot shorter than people are imagining.

Yes when they're asking them to arbitrarily not release a finished feature just so the Hornet can get it first. Whether they release it when it's ready for the Viper or wait till the Hornet's ready to release it for both, you still get TWS in the Hornet on the same day in either scenario - the only difference is if you wait you've held back a feature that people could, in the meantime, be enjoying and finding and reporting the inevitable bugs with in order to not upset Hornet users. Like I said, it doesn't make sense.

That doesn't really make sense - why force Viper users to wait just so Hornet users don't have their feelings hurt? I own both, I just want TWS as soon as possible, I don't care which gets it first - the Hornet is already much more capable from a sensors point of view with fully fleshed out LTWS, MSI and SA pages.

We've had pilots/ground crew describe before that there isn't a huge deal of difference between what we have now in something like the Hornet and what is 'realistic' because the Mode 4/5 codes are loaded by the ground crew and not entered in the cockpit. Even Deka's JF-17 has the Mode 6 (their mode 4/5 equivalent) IFF codes loaded by default based on coalition and not configurable by the pilot - only mode 1/2/3 are configurable, but they're not the primary IFF mode you'd use in combat. You wouldn't expect any other aircraft to match your mode 2/3 code anyway (as they're meant to be unique to your aircraft) so you'd expect every other aircraft to fail a mode 2/3 interrogation, and mode 1 is a two digit code so hardly secure.

You can't see the keyboard in VR. Anyway - you can click the throttles in the F-14, I've never once got anywhere near accidentally clicking them. You're worried about a problem that doesn't exist.

I don't think it's the exact same RWR - seems like the DCS F-15C has the ALR-56C, and our 16CM has the ALR-56M. It's possible the sounds aren't the same between those versions - probably need a resident RWR expert like Beamscanner to tell us.

From Wags' video description: "This is based on a USAF F-16C Block 50 circa 2007 and may be a bit different than you are used to. This is specifically true with the Dogfight mode HUD as it has changed greatly in later years."

Here's one I've been trying to keep as accurate as possible for what's announced / in DCS already: If anyone sees anything wrong, gimme a shout and I'll update it.

Is that a yes for APKWS on the OH-58D then?

If you hold down the pickle button as the CCIP marker passes your target, it will count down and then do a quick CCRP drop on that point. You can use that to do low level CCIP-ish drops even though the horizontal bar never lets you do a proper CCIP drop.

This has been changed to 1500ft, if the A-10C is anything to go by, I'm expecting people to complain cause its too high now... That high in the A-10C and the bomblets drift off the target before they pop.