Ramsay

I've updated the link to the accompanying Krymsk diagram (must have broken when the forums were upgraded). Mission Briefing Unfortunately the 2.5.3 track file doesn't playback correctly all the way to the landing and the weather/lighting is a little different in DCS 2.7.10 but you should be able to hit "ESC" and "take control" none the less.

What RL pilots report aren't subjective "feelings", rather they are objective "observations" - i.e. in RL they'll use 40% throttle (in DCS 60%) to taxi, in a dive DCS picks up too much speed, in a climb DCS bleeds too much speed, at speed "x" they - use left rudder, ball is centered, use right rudder, etc. I forget all the details of the Yak's FM issues and would need to refer back to a none English video and run it's transcript though google again (IIRC he speculated engine torque was over-modelled), however going into such detail would be flogging a dead horse as AFAIK it was reported in both the English and Russian forums and the Yak just doesn't have sufficient priority. There was some tuning done for flaps drag (a couple of years ago), so I'm not sure on it's current status. For the general FM - the main issue I still see is rudder behaviour where with a fixed trim tab "tuned" for a set cruise speed i.e. 210 kph, we should be using left rudder for take off, centered pedals/ball at cruise speed and right rudder when faster but that's not what we see in DCS. Perhaps one day the Yak's rudder trim adjustment will work in special options but I'm guessing that's the best we can hope for.

Possibly but the linked RL Yak-52 pilot's comparison isn't the only one (there are another 2 owners of the real, that say similar things). As a sim pilot, I've never flown a RL Yak-52, so find it's flight model "reasonable", however RL pilot's scan their controls and instruments and note throttle/rpm needed, etc. as more/less throttle, etc. than usual can be an indication of something wrong/missed i.e. gear/flaps not down, etc. Flying in DCS, RL pilots have quickly noticed discrepancies between the Yak-52's real behaviour and DCS. Paraphrasing what one Yak-52 owner/DCS player said, unlike a F-16, etc. with a "civil aircraft" there are a lot more DCS players who have flown the real and ED can't handwave flight model issues away and get a pass. He then praised the DCS Yak-52 for the bits it got right but had bought it mostly to support ED and encourage them to fix it's problems/make similar aircraft. IMHO the DCS Yak-52 has never had the resources for it FM to be finished to a high quality and seems to be mostly running on systems ported from DCS's WWII warbirds, it may keep it cheap but from the comments of RL pilots of the Yak-52, it's been at the expense of accuracy.

Yes, using symbolic links, though aircraft are pretty small and maps take up the most space i.e. Caucasus=15GB, Mariana=13GB (with the largest Syria=60GB) Here I'm using symlinks to put most of DCS's maps on a second 1TB SSD so they don't fill up my 1TB NVMe root drive IIRC you want leave at least 10-25% free space on each drive for performance and longevity

A blade strike i.e. Wags likely hit a tree branch.

They are not, you chose your range source - Nav (distance from waypoint), Auto (radar altitude + LOS angle), manual (as set i.e. 1500m), TADS/Coop (CPG locks and lases target ?) or radar lock (just guessing at this one). Obviously you don't use all five at once as they'd likely give different ranges i.e. the waypoint isn't near the target. In Wags first video (IIRC) he used Nav (distance from WP02) for his first attack run and the TADS/Coop (via George) for his second run.

Sort of, as I understand it ... 1. Place LOS indicator on target 2. Manoeuvre helicopter so I-Beam is horizontally aligned with the 'LOS on Target' indicator 3. Fly straight and adjust pitch/wait until the LOS indicator is within the I-Beam's limits ( I-beam turns from dashed to solid, showing the rocket pods can articulate i.e. track the target's pitch) 4. Wait until within range, (Auto, manual, nav source, TADS or radar) 5. Shoot, adjust, shoot again ...

Yes, it'll be in a future DCS patch (in the same way the western/Cyprus addition was).

There should be a F-5E folder in both locations • CoreMods/aircraft/F-5E for AI and MP aircraft, default liveries, etc. • Mods/aircraft/F-3E for the player cockpit, flight model, default mission files, etc. AFAIK even players who don't own the F-5E should have the CoreMods folder, so it sounds like you have a corrupt DCS install and need to do a "repair" https://www.digitalcombatsimulator.com/en/support/faq/repair/ Note: If running the Steam DCS version, you should instead go into Steam > select "DCS World" properties > Local Files > Verify Integrity of game files ... This is what you should see If you continue to have issues after "repairing" your DCS install, please attach your Saved Games\DCS\Logs\dcs.log file as it may contain important clues to help diagnose the problem.

The MGRS coordinates of WP02 in the video are 37S DA 9694 0433 and the nearest base to that location is the Tal Siman military base i.e. north of Raqqa and part of the Syria map's free eastern expansion. This is a picture of the base/runway without the barriers, tents, vehicles, etc. that Wags placed around it's ramp area. More detail on the eastern expansion of the Syria map is here https://forums.eagle.ru/topic/239806-syria-preview/?do=findComment&comment=4897988

Correct, the NS430's VHF radios aren't useful/usable. Stick to using the Gazelle's UHF/VHF radios.

It depends, I've enjoyed learning to use the NADIR, etc. and the NS430 offers a chance to do things differently (plus it sort of looks cool) i.e. it's another tool in the Gazelle's toolbox. As the NS430 can't drive the aircraft's native systems/HSI/ADF, ideally the NS430 and NADIR should be used together. However YMMV, especially if not familiar with both. Here the bearing to WP1 is 34°M and is confirmed by the HSI course needle. The NS430 confirms the aircraft is flying a 33°M ground track i.e. heading direct to WP1 but both Desired Track (51°) and Bearing (40°) are showing TRUE/F10 map values instead of their Magnetic equivalents. NS430 Bearing (40°T) - MagVar (6°E) = HSI Course needle (34°M). While annoying that not even the most basic NS430 bugs have been fixed, I still find it easier to scan/read the NS430 than step through NADIR parameters/look down while flying nap of the earth. I own all the NS430 modules but the Gazelle's NS430 is the only one I'm planning to make regular use of, so I guess it's doing something right (ergonomics ?), despite the flaws in the base NS430's logic/programming, YMMV.

The OP used selective jettison. It seems something of the previous Ferry loadout persists after the loadout change - despite both internal systems (PCA and Test Loadout Switch) and 3D model showing correctly. For info. ✔• CAP spawn --> Select "RP" after take off = Jettison center tank correctly leaving 2x Magic II and 2x 530D ✔• Ferry spawn --> rearm as CAP --> Select "530" after take off = Jettison 2x 530D correctly leaving 2x Magic II and center tank • Ferry spawn --> rearm as CAP --> Select "RP" after take off = Jettison center tank AND 2x 530D incorrectly leaving only 2x Magic II ✔• Ferry spawn --> rearm as EMPTY --> rearm as CAP --> Select "RP" after take off = Jettison center tank correctly leaving 2x 530D and 2x Magic II The "Ferry" loadout doesn't seem to differentiate between center and wing tanks (the PCA only shows a single RP option), is this correct ? Tested DCS Open Beta 2.7.10.19473

@oznckr The F10 map ruler measures Vaziani RWY 31's TRUE heading as 315°T. The F-16's HSI and HUD are showing the MAGNETIC heading 309°M This is correct as the Magnetic Variation for that location and date is approx. 6°E MagVar = TRUE - MAGNETIC = 315° - 309° = +6° How to check DCS's MagVar for a particular Date/Location using the F-16C's DED Magnetic = 309°M

I'm hardly a dedicated DCS Gazelle pilot but have used the Garmin GNS430 trainer and used the GNS430 (and similar) in other simulators. Positives The DCS NS430 is a nice dashboard decoration and adds things such as • low resolution moving map, • Direct to, • route cross track error • Imperial measurements (useful when flying in mixed formation) • Holds more than 9 waypoints (unlike the NADIR) Personally, I also find it helps maintain focus when flying nap of earth and avoid CFIG on longer (+1 hr) flights but YMMV. In general, I don't find the NS430 adds much function over that of the Gazelle's base equipment, rather it at best offers alterative ways of achieving the same things. Which is easier depends on how familiar you are with the "Garmin" way of doing things and/or using the Gazelle's native systems. Negatives DCS's NS430 seems to have much less fidelity to the "Real" GNS430, than the NADIR but detailed info on the "Real" NADIR is sparse. The main thing that stop the Gazelle's NS430 from being considered a "serious/high fidelity" module are all inherited from the limited base NS430 module and it's many broken/missing features. • The NS430 isn't integrated with aircraft systems • The NS430 VHF com radios don't work i.e. for ATC • OBS radial adjustment doesn't work i.e. cross track to follow a VOR radial or line up for a runway approach • Desired Track is 6° out on the Caucasus map • The moving map is 6° out (MVAR ?) in Caucasus and Nevada maps (you learn that a WP directly ahead will appear slightly to the right on the map) • The NS430's magnetic bearings = F10 map/True and selecting True adds another error i.e. Batumi RWY 31 which is 300°M/306°T in DCS, reads 304°M/311°T • etc., etc. Because of the above, I only recommend buying the DCS NS430 on sale and warn it's not suitable for learning to use the real GNS430 (IMHO it's best used by players who only have a perfunctory interest in the real GNS430 or those familiar enough with the *real* device not to be confused by the gamified NS430).

DCS Gazelle after hitting powerlines, YMMV. Tested DCS Open Beta 2.7.10.19473

I think the dev's would need to see proof as the only Gazelle main rotor strikes I could find involved lose of control/other major damage. Here a AW139 grazed a cliff face and lost 70-80mm of blade and returned to base with minor vibration. http://aerossurance.com/helicopters/alps-aw139-sar-blade-strike/ here another AW139 struck tree branches and suffered similar tip damage https://www.avfoil.com/helicopter/atsb-releases-preliminary-report-into-aw139-main-rotor-blade-strike/ and here a SA350 struck a bush while hover taxiing, and damaged the main rotor tip caps. https://www.atsb.gov.au/publications/investigation_reports/2017/aair/ao-2017-074/

TL;DR: This is due to a change in how warnings are given for descending through the set barometric altitude. Detail Crossing the Altitude threshold triggers at +1000 ft and -300 ft of the set altitude to warn of breaking an altitude "floor" or potential CFIG (controlled flight into ground). This altitude warning does NOT require the autopilot to be turned on. With the desired altitude set at zero (as in your track), the altitude gong sounds because You spawn at 6,300ft and descend through 1000 ft (0 ft +1000ft) to cruise at ~800 ft. During the low level turn, your altitude momentarily increased to ~1010 ft, before again descending through 1,000 ft to reach your ~800 ft cruising altitude. AFAIK (discord), this new behaviour is intended. Tested DCS Open Beta 2.7.10.19473

A common suggestion is to :- * Type "cmd" in windows search, right click on "Command Prompt" and run as an administrator. sfc scans your registry for errors and dism compares your windows libraries against windows update Comment It's a "health check" and something I often find myself doing when Steam starts acting "funny" (i.e. game updates keeping asking to be installed), after a Windows 10 update.

I think you misunderstand what @Mentos is asking for, the NS430 defaults to Imperial units and there is no way to save NS430 user settings/preferences between flights. The NS430 does not take into account DCS's Options>Gameplay units configuration. Here I have chosen Metric and the L-39 is using Metric instruments (as is the F10 map's ruler, etc.). However the NS430 uses knots, nautical miles and feet until changed via NS430's in game Aux > Units page. Tested DCS Open Beta 2.7.10.19473

AFAIK none of those should have inverted slewing, TDC left should not slew to the right, except perhaps for slews on the EHSD map in "north up" when the aircraft is flying south i.e. HUD movement might be inverted when EHSD is SOI or vice versa (IIRC these were the only "inverted" slews that used to occur). How DCS's AV-8B behaviour is coded is something only the dev's know. AFAIK the sensors (HUD LOS, DMT TV, IRMAV) are independent, however they can be slaved to the INS designation made by another sensor and the system/LOS designation they make is an INS one i.e. you might make a system designation using the HUD/FPM (or EHSD) and then sweeten the INS designation using the DMT TV followed by a final IRMAV slew/designation.

No issue contacting the ground crew and asking them to remove the ladders, rearm, etc., I'm guessing you've missed something ? Placed an invisible "Helicopter" FARP with a selection of appropriate "service" vehicles for radio/ATC, rearming and fuelling (fire truck is cosmetic IIRC) and all worked as expected. Tested DCS Open Beta 2.7.10.19473

There are two "Approved for public release; distribution unlimited" reports from 1979 that I can think of that match your description. • A-10 GAU-8 (6 passes) Low Angle Firings Versus Individual Soviet Tanks, 36722041.pdf • A-10 GAU-8 (10 passes) Low Angle Firings Versus Simulated Soviet Tank Company, a522397.pdf

Yes, this is an air spawn and uses active pause, I • Lase 1st truck, • Fire BRM-1 (laser timer displays), destroy tuck, • wait 3 minutes to avoid over heating (LSR still blinks as it's ranging), • repeat for a 2nd truck • wait 3 minutes to avoid over heating (LSR still blinks as it's ranging), the laser fails after ~12:30 minutes (LSR stops ranging/blinking) just as I'm getting ready to fire at 3rd truck. • I fire a BRM-1 but the MFD's LSD laser timer doesn't display, the missile misses, as does a second (just to make sure). Track recorded/tested using DCS Open Beta 2.7.10.19402 JF-17 Laser fails after 12 minutes, 2_7_10_19402.trk

The initial report is over 12 months old, IIRC the devs thought the issue (IRMAV slewing) resolved and the report moved to the "Resolved section". However after the Gen 3 TPOD update, there was a major regression inverting INS slewing across multiple systems i.e. EHSD, IRMav, etc. AFAIK the bug is under investigation - i.e. • should slews on the EHSD move relative to to track-up or north-up or change depending on mode, • should HUD/IRMAV slews be relative to the aircraft's track/nose ... either way the current INS slew behaviour is inconsistent to how it worked previously with slews to left - moving right, etc. While using the TPOD to designate targets works well in TPOD mode (sensor select double tap), slewing the system designation in INS mode is inverted and INS/System designation is used in many ways i.e. EHSD, HUD designation/slews, IRMav, DMT TV, etc. You should note that the AV-8B isn't always be equipped with a TPOD and prior to ~2002, system designations (INS) was done via EHSD, DMT, IRMAV and HUD, as the TPOD wasn't available. Even when TPOD equipped, a common reason to use the IRMAV seeker in INS mode is to slew to near by targets and ripple fire several mavericks, one after the other.