Dudikoff

Same here. I wouldn't even mind if it's some earlier variant with the TID if there's enough info on those.

It does feel slightly overpriced compared to the current TM Warthog price, but e.g. Virpil TM-compatible grip was more than $150 on release IIRC and it's all plastic. I didn't really care about it when it was announced, but it kind of grew on me and I'm seriously considering getting one for the other TM base I have. The Tomcat grip is a bit too basic control wise, so I think this would be a more useful option. Putting that amount towards the Winwing set might be a better investment, but with postage and customs it would add up quite a lot. In this economy? My thought, exactly.

I guess the real throttle on the 29 is not much different (there were diagrams showing its range posted here), but you could adjust the curve so the burners start matches your detent which is not the half of the throttle I guess.

Hmm, the mentioned huge downloads (12 and 16 GB and maybe more) should mean that the VR map optimizations might have made it in the build that's released today (unlike the yesterday's build), but the notes don't mention anything in that regard.

With so many delays, those eventual patch release notes better be reasonably long. :)

Doubt it as the third pylon is attached on the wing before the wingtips, so I guess it actually requires a different (bigger?) wing with an extra attachment point. I'd expect that the throttle A2A control doesn't do anything as it was probably intended for a future modification (3-pylon wing) which never came about on the Ka-50, but was installed on production Ka-52.

It always seemed logical to me it was to offset the TGP weight. The LTS pod is not quite as heavy as the Phoenix (550 lbs according to HOTM page, I guess without the adapter?), but there's also the adapter weight, plus the pod is hanged lower than the Phoenix so I guess it might not be that far off.

But, if you have the AIM-54A missiles on the wing pylons, you still need to have those Phoenix pylons on stations 3 & 6 for coolant then. If I understood correctly, AIM-54C missiles don't require external coolant, so you could carry e.g. two of those on the wing pylons and four Sparrows on the belly (compared to the more standard loadout with two Phoenixes on the belly which nets you 3 Sparrows in total)?

It's called feedback. Customers writing posts on potential ideas and suggestions will not make ED's progress on the F-16CM any slower.

No, it means both groups of BS2 owners (as both BS1+BS2U and BS2 owners are now having only BS2 in the system) will pay the same price which will be noticeably less then the price for people who don't have a BS2 module yet.

They're not. It has its own driver and connects to the PC separately either via USB or Bluetooth. But, without the TM Target compatibility, it's of no use to me, unfortunately.

IMHO, you won't notice any difference in that scenario. But, at least the rigged prices are dropping now, so you won't pay a fortune for that little to no gain in SP as it is. Though, be careful if you're planning to upgrade the system in the near future, since I guess DDR5 is coming this year (in which case, you'd upgrade your system before you got to the point where you'd actually put those 32 GB to good use).

Wait, so what's the problem with that? They (me included) already paid full price for the standalone BS1 and then two-three years later paid again for the upgrade to DCS standard (BS2) when it came out. You couldn't buy the upgrade without owning the BS1 first, AFAIK. Plus, why do you think BS3 will be sold at a full price again to everybody? It will be an upgrade for BS2 owners, for sure.

I'd presume the USAF is not using them on the F-16's, so it wasn't integrated in the WCS. IIRC, they did use them on some B-52s during the Cold War? Edit: I guess they are using them still. https://warisboring.com/transforming-the-b-52-into-a-maritime-patrol-plane/

"The Ka-50 update will consist of new functions such as Igla air-to-air missiles and missile warning systems with infrared missile jamming systems in addition to a substantial graphics overhaul. While new cockpit functions will be part of a paid upgrade, the entirely new and improved cockpit and external model will be available for free. In addition to a graphics overall and new features, we will also take this opportunity to clean up any remaining bugs in the Ka-50." Interesting. I wonder why they didn't make a separate new variant then? It would have been easier for them to protect the new functions (as it would be a new module), while we would have more flexibility with the scenarios since the MAWS variant is a much later development I guess.

Interesting, but rather expensive for only a grip, though at least it's metal. Is this small rotary wheel functioning like an encoder or what? I might consider it when I see how it functions with the Cougar base, since that VKB MCG-TM grip never came about and I need another grip as I have two different bases. Also keeping an eye on that WingWin development, as that package looks rather promising (especially the modular throttle grips and plates) if they can offer it from a Euro located store or something without super inflating the price.

Well, where's the problem exactly? It's called Open Beta for a reason, they don't have to update if the mentioned limitations of the latest Open Beta update would influence the missions they're running. There's still a choice to be had here and nobody loses anything, let's not create a problem where there's none present.

3/3 wrong, not bad.

Real versions, also no. Well, there are those upgraded 47 SM's and 22 SM3's IIRC, but R-77 was never introduced into RuAF operational service and I wouldn't expect RVV-AE (the later export variant) was. There were some recent photos showing some R-77 on some airframes in Syria (like on the Su-35S), but it's not really clear which variant it was (i.e. R-77-1 or Syrian RVV-AE, most likely the former which would mean it did enter some kind of production).

I wasn't speculating on which module it is, it's not really important, 'could be' was aimed at people complaining about not being able to fly their module as a reason behind ED's decision to postpone the update again. The point I was aiming at is that it wouldn't be the first time that some module is out of sync with the latest beta (IIRC, cockpit lighting issues?), so I'd prefer they release the update sooner rather than later and the last 3rd party can sync on whenever they're ready. That way, most of the users win and ED can begin getting more error feedback on the new VR optimizations.

Could be, but they'd still have the option of playing on stable branch servers.

Given the time passed since the last beta patch release, I feel they should have released the open beta branch today and that 3rd party would have waited for the next open beta upgrade window. Certainly better than no updates for yet another week. Hint: Maybe they can still do this on Friday and the late 3rd party can still work till Wednesday?

Technically, Navi is a series of GPU's ranging, like e.g. Navi 10 (which should be in the recently showcased RX5000 series card competing with RTX2070) to Navi 20 (which should be their "high-end" card and compete with RTX2080, but this one has been delayed). But yeah, no competition on the level of 2080Ti for now, it seems.

While we're on the topic, how does the firing of Sparrows and Phoenix missiles work with the pilot trigger in the real F-14? I'm asking as I also saw mention of holding the trigger for several seconds (most recently in that posted F-14 Guide, not sure what they used as a reference), but from my experience, an instant trigger pull is enough and the missile will launch within several seconds. I'd expect that HB's implementation is correct, but would just like to double-check as it differs from some other US airplanes in the game. I guess it could make sense for launching multiple Phoenix missiles relatively quickly, otherwise it would take quite some time to launch e.g. all 6 of them.

I think HB's patches have fallen victim to ED trying to push the VR improvements in the next update which obviously takes time to be properly tested and ironed out. Since I fly the F-14 now almost exclusively, I wish ED handled this in a better way and had a plan B option to just push out urgent module fixes separate from their own complex platform changes.