Sideburns

Well HB appear to be on the Viggen and did adjust the drag situation recently, the MiG21 however I will concede doesn't appear to be getting much attention.

Latest OB update today "Added a new feature into the payloads panel in the mission editor: Loadout per pylon restriction. The main goal for this feature is to give mission designers more tools to control their mission environment in multiplayer. It will allow the ability to restrict any weapon or other store for a specific pylon on the MP aircraft slot. Feature is WIP and we will adjust and add more functionality to it." Unfortunately doesn't appear to be a MiG21 low speed handling or Viggen speed bug fix yet though.

https://web.archive.org/web/20151025180109/http://www.leatherneck-sim.com/f14 "The F-14 will ship with a completely new DCS Theatre, perfectly suited for the F-14 and Naval Operations of the era. This new theatre will be available separately as well, and will be a great addition to the current fleet of available DCS Modules." So they don't mention GIUK specifically but at the time, 2015, it was strongly rumoured that this was likely to be the North Atlantic, GIUK gap or North Sea area. I don't disagree the Baltics would be more appropriate for the Viggen, and could possibly have been the intentions of this very early theatre announcement. As before note that this theatre pledge was dropped shortly after the initial announcements and before pre-orders were taken, so I don't consider HB beholden to this pledge. I wonder if @Cobra847or a member of the team would be willing to shed light on what the plans were at the time, if not no worries And yes, I'm aware the GIUK and North Sea are separate areas strictly speaking, regardless the point being I would still love the challenge of carrier operations in these regions.

I believe a GIUK map was mentioned very very early in the HB F14 plans, I think it would have worked quite well with the Viggen, F14 and also Sea Harrier modules intended. But to their credit HB did remove this prior to pre-orders (i.e. it was clear we were getting the carrier and F14 variants only) and a dominant part of the GIUK fighting, alongside defending the fleet and surface warfare, would be anti-submarine which of course is not currently well represented currently in DCS. Also suspect they came to the same conclusions w.r.t what the DCS engine could handle and that a GIUK was perhaps too much at the time. Despite this, would really like the challenge of the North Sea's weather and sea states. There are some crazy stories from Sharkey Ward's Sea Harrier book on getting the Sea Harrier operational in the North Sea and the adverse conditions they would fly in.

Also the MiG21 low speed flight model atm for human players is quite generous and has been for some time. Anyway, tips for the F5 (apologies for overlap with existing tips but would like to emphasise them): Speed is life, try to stay above 350 knots and ideally above 400 knots. Turn gently, with the mild LERX like wing on the F5 and small engines it can bleed speed rapidly. I generally leave flaps on auto during turning for best turn performance, but bringing the flaps in can be useful to help regain speed quicker. The gun has a low rate of fire, so you need to practice getting a good track on the target If using missiles, learn to uncage and lead to make them more likely to hit. Gar8 / aim9b is pretty trash but the aim9p and p5 are quite usable.

Yep, but as per the earlier comment you can recalibrate the base to remove this (using the Virpil software)

Yep, thankfully I went straight to centreless cams with the heavier springs and love it.

Have just switched to a Virpil Warbrd base, from a TM Warthog base, tt is a lot nicer to use mostly due to the smoother centre but also you can customise spring force and cams. The spare cams it comes with can remove the centre "dent" which is quite liberating for fine flying. They also have a B-grade store on ebay that can be a handy way of finding stock. Also, using the standard TM stick it is heavier than Virpil offerings so likely to make things off centre. But nothing a calibration can't fix. The TM stick does feel odd with the softer spring that are fitted as standard.

No need to question Bonercat's skills, imply he is ignorant or he's only interested in airquake to try and make a point. I'm pretty sure he is aware of the RWR spike and radar range issues among other non fm bugs. Speaking of ignorant, you might want to check out this mature bug thread on low speed handling. It isn't just the wing rock. I would also recommend anyone liking your post to read the same. What is your opinion of this situation? Do you still endorse the flight model as "fine"? "So, at 0.347M time of the turn has to be 37.5 sec = 9,6°/sec. We have in DCS now 12,9 sec. As I said before - the reason of this fact is over performed G-load!"

While the MiG21 is enjoyable, it is not without some significant and in some cases long standing bugs. I would recommend checking the bugs section for any of the module developers you are interested in, and also any self hosted bug trackers they have, to come to your own conclusion of if these are bugs you are content to live with.

F14 is a great module, full of stuff to learn. I'd suggest learning to fly it first, then A2A and then A2G stuff. 1) As hinted before, airframe is unforgiving and will kill you if you handle it roughly. But flown well (smoothly) it is a difficult airframe to beat in BVR or BFM. Also has incredible endurance (~240 knots for endurance, ~330 knots sustained corner speed) and speed. 2) The AIM54 is incredible, the AWG9 can also be great but has its limitation for low closure targets particularly over land. 3) Human RIO is better than Jester, the F14 is a lot more enjoyable if you pair up with someone. Alternatively why not try being a RIO yourself, you can load up a single player mission and switch seats to have a quick go. 4) Don't forget it can also do air to ground precision strike, and the adm141 drones can be fun to assist with SEAD/DEAD situations. The LANTIRN functionality really requires another joystick, you can map a modifier switch in DCS to switch between A2A and A2G button asignments and use a single joystick for both.

Seeing a lot of people "gaming" the system and shooting down incoming missiles, is this intended by ED?

1 year anniversary Any update on this? The MiG21's low speed handling still seems generous.

These were the settings, it does matter which variant of bomb you use and if you are dropping singly or in pairs.

Also affects the Viggen. weapons and pylon drag is wonky and enables a higher top speed compared to a naked aircraft by 200kph.

Has been discussed many times, try the search function

I've always considered this situation an unfortunate balance of bugs. We appreciate your efforts trying to balance @Alpenwolf, thank you for trying suggestions. If there is a RIP here it is the MiG21's broken RWR lock indications to others and radar overperformance issues that have been seemingly ignored since formally posted months ago (and there are earlier comments on these issues also ignored or overlooked). Most players are blissfully unaware of these MiG21 advantages as it is not as obvious in game or in tacview as the Viggen's speed bug. The availability of the unrealistic ASP pipper, that tracks targets, is also questionable. In the mean time the F5 has RWR functionality missing and the jet nozzle scheduling bug are still present. The Viggen speed and damage issues have shown improvement with the recent patches and show some hope of being resolved (and also HB were fairly honest and didn't say the recent patched fixed the issue, but were tweaks they could do while busy finishing the F14 and Forrestal).

Can confirm it is.

Reported, and also there is an IC breaking hotfix available

Great news, that video is such a good teaser. Looking forward to the outcome.

Anyone retested since the patch given "Updates to sidewinder pylon drag coefficients."? I did a quick test (standard ME parameters for Caucasus, 10-20m above sea level): 1580kph for a Viggen spawned in without weapons 1450kph for x-tank and rb24j/rb74 1540kph for x-tank jettison but retaining rb24j/rb74 1710kph for an x-tank and rb24j/74 fire off, pylon retain 1630kph for an x-tank and rb24j/74 fire off and pylon jettison Still too quick it seems, odd behaviour with the pylon jettison slowing the jet down.

Can also confirm this is an issue for me

This was posted on the discord and apparently works? So the actual procedure is: 1. Designate a target using any sensor. 2. Press UFC TOO button 3. An options menu will appear in the ODU: WPT, MRK, TGT (TGT will be selected by default) 4. Select TGT. 0 will be shown in the UFC scratchpad indicating T0. 5. Enter any number between 1 to 10 and click Enter (Just press enter, entering a number will not work -> it will still just increment by one) 6. The Designation coordinates will be stored in the selected targetpoint. 6.5 Press UFC TOO button AGAIN or wait till the TOO function disappears from the UFC automatically: (Otherwise things will NOT WORK, it will just set the next target point to the location you designated previously -> All your Target Points will be on the same spot) 7. Repeat until you have filled all 10 targetpoints 8. Do an absolute JDAM release. Tell me if that works for you guys or if it is just me doing something wrong. I'm guessing this feature is still a work in progress.

As per the other thread I personally paid for the AV8b(NA) as advertised and with the fuller range of weapons it carried over its operational lifespan, not a specific model. Why not leave it to the users and mission makers to decide which year they are simulating / flying?

The F16 is a fun jet but buyer beware, the dev team are mostly working on the F18 atm (after we were initially told F16 and F18 would not interfere with each other's development pre F16 release) which means the F16 has had slower then expected development and also that the feature list for the F16 is "dynamic", the sniper pod and AGM-154c have been dropped recently.