MrDieing

There is no reason to believe we won't. It usually goes up around this time or later. Patience.

And the award of quickest whine after the patch notes dropped but the update is not even live yet goes to

Its called managing expectations, something the DCS community is very bad in. This hype train you mentioned is nothing more but a product of wishlisters in this thread. If the hype train has already left the station with two single lines of ED saying: 'We are working on a new module that is eagerly awaited and will represent a huge milestone' then there will be only one result: dissappointment. So can we all get back to agreeing its going to be a Flanker because it was not in the trailer or are we going to continue screaming Apache for a bit? :D

But what if ED pull a *insert dev name here* and its some aerobatic biplane?

Expected this thread to be half wishlist. Was not dissappointed. Were / are there any clues in the latest DCS 2020 and Beyond video that we know of?

The advertised range of the WMD-7 pod is about 20nm, so talking zoom level and range for target aquisition, yes, its inferior to every other pod, although the LANTIRN (never used it) supposedly also has room for improvement. FLIR imageing is something that seems off though, for unknown reasons the contrasts seem worse in the Jeff then for example the Hog. Maybe ED´s new FLIR imageing will fix this, not sure.

These threads always make me grin a little. Do you really expect a serious answer to this from ED? I mean, sure, you can always ask, but I can already tell you they wont give you an ETA (unless this time for whatever reason they do, Murphy's Law). They will probably say something in the direction of; ''We are working on them and will share news when we have some''.

You can still decide after ED announce the exact meaning of CA integration in a later stage. And if the sale is your argument, there are plenty to come.

Well its up on the store now. https://www.digitalcombatsimulator.com/en/shop/modules/supercarrier/

I really dont understand whats going on in people's heads asking: ''Today is the pre order day, where is it?''. Like as their electrons in their brain of ''Today is January 17th'' and ''Today is the pre-purchase date of DCS: Supercarrier'' have connected is the moment it should be available?

Welcome! And oof, another victim. Your wallet will cry everytime you mention DCS, because it will quickly get addicting and you wouldnt be the first to get the ''Gotta catch 'em all'' virus. Anyways, happy flying and be sure to drop any questions or problems you have down here in the forums.

I understand the confusion and I am a little confused myself aswell, but in the end its pretty simple if you ask me, work needs pay. While it might not have been communicated before, its a pretty logical step if you ask me to include the Kuz in the package, although curious how this exactly is going to play out in MP.

Look at a point on the ground, press a button and the TGP can slave to the point the pilot is looking at, if I am correct.

Did you arm the fuzes?

From their Chirstmas update http://leatherneck-sim.com/2019/12/22/christmas-update/ Finally, an early gift! We have decided to show the very early stages of the Crusader’s cockpit. It is still a work in progress and the version shown in the renders above is strictly for our programmers to start implementing basic systems. Some assemblies may not be modeled 100%. During the course of our research, our team has come upon three modifications within the ‘J’ variant. Our goal is to model the ‘J’ to its fullest, so we have decided on airframes AFC571 and subsequent, that includes a pulse doppler function added to the search, acquisition and track modes of the APQ-124 radar. This will give users the options of using the AIM-9G Sidewinder with the new Sidewinder Extended Acquisition Mode or SEAM, a facility which slews the optics through a search pattern to acquire the target, or allows slaving of the optics to radar!

A taste of your own medicine then. Our MiG-21Bis having the PL-5 is not realistic.

Agreed. Immediately when I saw this was released I fired up the Jeff and within an hour of flying and having this gem of a guide I already learned so much more then 2 weeks of flying without it. Its these guides that allow me to fully enjoy products I am not familiar with. A million times thanks, Chuck!

If you dont want it, dont buy it. If you decide to spit this kind of nonsense on a forum, all you do is make yourself look funny.

I believe ED also lost their original engineer on the A/G radar due to whatever reason. Image an engineer writing up a bunch of code, only to have it left unattended for who knows how long, a new engineer coming in and having to go through the entire thing whilest updating it to latest standards, especially if the previous engineer was writing for version 1.5 or something, while in the meantime we have arrived at 2.5.5

It's called being an internet engineer. Everybody is a professional on the subject because they have valid sources like Wikipedia. Unfortunately you will see a whole lot of these phrases when it comes to missile dynamics and flight models.

As far as I know there is no HOTAS command to quickly change programs. If you press CMBT (at the bottom) on the Left MFCD, or just the CMBT page in the menu, you will go in a sort of a combat preset, where it splits the MFCD into the top half SMS and bottom half Countermeasure settings. It will give you the option to change programs, if you press the OSB next to PROG01, it will then switch to the next etc. You can also click the OSB next to CH (assuming your set program contains Chaff, if it contains Flares it will say FL) to quickly switch to a program that contains the other countermeasure.

Lets see if I can explain it, I'll use program 1 as example. OESP Type means which type of countermeasure the program will launch. So in case of Program 1, only Chaff. Chaff SQ means how many sequences of chaff it will launch, in my case 1. Chaff SI means Sequence Interval, the time between sequences. In the case of program 1 this is not applicable, because there is only 1 sequence. Chaff BQ means how many chaff will launch per sequence. In my case, 4 chaff. Chaff BI means the time between each individual chaff, in my case 0.2 seconds. After that you see the same for Flare, but the program will ignore it because I have set the OESP type to Chaff. So my program 1 will launch 1 time, 4 chaff with 0.2 seconds between each chaff. My program 2 will launch 2 sequences with 1 second in between the sequences, 4 chaff each sequence with 1 second between each chaff.

Known, reported and being fixed.

I'll take that 13 bar setting please.

Known, reported and fixing https://forums.eagle.ru/showthread.php?t=256796