Ramsay

Both Nevada (+12°E) and Caucasus (+6°E) have easterly magnetic variations, that is, in both regions a magnetic compass will point slightly West of true north and needs a +ve value added to it, to point to true north. MagVar = True - Magnetic i.e. • Batumi RWY 13 MagVar = 126°T - 120°M = +6°E • Nellis RWY 03R MagVar = 40°T - 28°M = +12°E The sign of MagVar is often confused in DCS as we often convert from the F10 map (True) to the cockpit (Magnetic) by subtracting the (positive) MagVar i.e. • Batumi RWY 13 Magnetic = True - MagVar = 126°T - (+6°E) = 126°T - 6° = 120°M With regards to the EHSD bug, it'd be useful if you could include a track demonstrating the problem. IIRC the DCS EHSD should display the course line correctly and heading/course in either Magnetic OR True depending on the chosen Mag/True mode. However it's possible UFC input still takes user input only as a TRUE heading, regardless of the selected compass mode.

Might be you, the A2A update is still WIP and hasn't dropped yet. Without a track, it's hard to know if you're complaining about already known bugs or something else. IMHO it's best to work with what we have and wait for the A2A rework (models different PRF's, radar modes, ground returns and a load of other stuff), it'll drop when it's done/ready.

This old mission still works, it uses Moose to spawn a couple of low skill AI F-5 or L-39 to practice. AWACS is on 251 MHz for bogie dope calls etc.

You could try • Options > VR > Force IPD Distance, to scale the world. ... the higher the setting, the smaller the cockpit looks.

Yes, there are lies, damn lies and statistics. I can't speak about the graph but ED's claims have at times proved to be "selective" and should be verified by SME's. Just because a module is well received (i.e. Huey), it doesn't necessarily mean it's accurate. All I know is that that the Yak's "Options>Special>Rudder trim" adjustment hasn't worked since it's release and I'll judge ED by their actions, not claims.

Yeah, a real life owner passed feedback about the rudder (and landing), a month or so (Aug 2018) after it's open beta release . https://forums.eagle.ru/showthread.php?t=217349 Other than fixing the ADF and a few minor changes i.e. language support; AFAIK nothing else was done/revised. ED simply haven't devoted the resources, choosing to prioritise other projects and put the Yak-52 into maintenance mode i.e. so other updates and lighting changes don't break it.

You can select Russian subtitles and use settings > auto translate > English (or your preferred language). No it's more fundamental stuff. Paraphrasing as best I can (don't speak/read Russian) Testing the rudder - ... and it just goes on and on, but hey - if it looks like a Yak-52 and sounds like a Yak-52, it must be good ? Disclaimer: I enjoy the Yak for what it does but I haven't flown the real or used the DCS Yak-52 as a teaching aid, it does sound it could teach bad habits though.

AFIAK the Mosquito uses air brakes, overnight the air pressure leaks off, so when first starting, chocks need to be used. Once the air pressure has built up (No 1 engine has an air compressor), the air brakes/parking lock, could be used but for run ups, etc. it was common to use chocks. The Spitfire also uses air brakes and a engine driven compressor, although it may be fighter - AFAIK it also requires wheel chocks when first started. Note: I'm not very familiar with either aircraft outside of their "pilot notes" and wartime film footage, so you should check with SME's for definitive answers, etc.

Yes, though like pre-start prop turning, a lot of things in DCS are glossed over / simplified. A "typical" Yak-52 start up Yak-52 cold starting at -3°C The Mosquito will have you calling to the ground crew to work an external "priming" pump to start each engine. I've no experience with aircraft but I've worked with several older engines from the 50's that required fuel squirted into their inlet manifolds as part of a normal starting procedure. IIRC most had a fuel tank above the engine and were gravity feed, but perhaps one of them *might* have used a hand pump (it's a long time ago, so I really can't be sure). Even today, products like "Easy Start" exist to assist cold weather starting

• With my first test flight, I saw the bug and was unable to launch the 530D's. • I exited the mission and added another Mirage with 530D and Magics in the ME (may have copy and pasted the aircraft, perhaps that added DB issue to the mission ?) • Sure enough, there was no issue when the Magics were loaded as well. • Watched the track files to see if they played back correctly, they did. • Exited DCS, restarted and checked that the bug was still there (DCS is sometimes "Magical"/frustrating), I was surprised to find the 530D's launched. • Retested the 1st track and took control to make sure I hadn't missed something obvious i.e. hadn't held the trigger long enough or something daft; nope there was definitely a arming/initialisation bug in that track. Uploaded the results/tracks to support your post and help Razbam confirm the issue.

Not sure why, the schematic shows the triple gauge is connected to main fuel line "main". Pumping fuel to the "cylinders" is pumping fuel directly into the inlet manifold, i.e. IRL after each pump stroke the prop is rotated half-a-turn, none of which would show on the triple gauge as line pressure. Whether a cold engine would start if the cylinders hadn't been "primed" is another question but we know the Yak-52 is missing it's failure modes ?

This post has step by step instructions

This is a strange one, I was able to reproduce your bug but it wasn't consistent, retesting after I'd spawned in with magics previously, the 2x 530D loadout initialized fine. I attach two tracks, one showing the bug and another where 2x 530D worked* * I think switching to PIC had no effect as "530" was never blinking in the HUD after master arm was turned on. Tested DCS 2.7.5.10869 M2K with only 530 won't fire missiles track2, 2_7_5_10869.trk M2K with only 530 fires after PIC lock, 2_7_5_10869.trk

Make sure you have the "Historic Filter" in the ME turned OFF (it persists between mission edits, etc.). The F-5E carries older A2A missiles that were likely life expired in DCS's default mission date of 21st June 2016. Using DCS's default date with the "Historic Filter" = ON, only captive training missiles are available. Turning OFF the "Historic Filter", the AIM-9 B, P, P5 and captive training missiles are available in 2016, etc. I suspect this was the OP's original issue and cleaning his saved games folder, reset the "Historic" filter. Tested DCS Open Beta 2.7.5.10869

AFAIK you will need to apply the fix to m2 after installing.

IIRC Polychop (or perhaps one their KW SME's) said they'd like to see flechettes but it might be of limited use in game. It's not clear how easy it'd be to add a realistic flechette warhead in DCS as a sudden "cloud" of flechettes might degrade performance or cause lag spikes in MP i.e. the M255 (~2500 x 28-grain (1.8 g)) and the M255E1 (~1180 x 60-grain (3.8 g)), and that's without considering DCS's limited damage modelling for ground units, perhaps ED could model a cloud of flechettes to be similar to flack damage ? I don't think we'll hear anything official from Polychop until the dev's have a working solution and are certain they will be added.

See this thread for potential fixes for Mission 2 - specifically changing the C-130 landing WP to a min altitude flyover point. There also fixes to OPF missions 3, 9 and 14 by snakedoctor here - https://www.digitalcombatsimulator.com/en/files/3312575/

Yes, I tested in the current DCS version. Main point to recreate the issue is to have a AV-8B that hasn't had the TPOD loaded or turned on. It's specific to when Sensor Select "double tap" is used to display the TPOD page and it hasn't been opened previously i.e via MPCD Menu > TGP > STBY > OPER This is a fresh mission If at any time previous, I had called up the TPOD page on the MPCD, the TPOD would have been initialised and would have worked normally. AV-8B TPOD Initialisation Bug rpt Dave62ndFF (with Fast Forward to bug), 2_7_5_10869.trk

Like you, I find many tracks play back correctly or where they don't have a reasonable explanation. In the case of FM tweaks and version changes, obviously as the track records the player's input, older tracks aren't "corrupted", rather the aircraft doesn't behave as originally recorded. For example, I have a older AV-8B track (2.7.4 from July) where I air spawned, went active pause, used the TPOD to TOO several trucks, unpaused to get closer (14 --> 5) and fired off several APKWS. The track plays near perfect, except in flying closer to the targets, the heading was now ~14° off (likely due to the AFC changes) and I'm shooting at open fields. (For Info: The APKWS still hit their targets thanks to their wide FOV). In the case of DCS 2.7.5.10869, the AV-8B's tracks sort of work and sort of don't i.e. repeating the APKWS mission and re-recording it. On the TPOD only the first truck was point locked correctly, for the rest the TPOD was slightly right of where it actually was (so 9/10 APKWS missed). The same was true for the landing at Kobuleti, it was replicated perfectly (faults and all), except for the final approach's alignment and touch down which was to the right of the runway centerline and ended up in the grass. This was a ~13 minute track with approx. 8½ minutes of it spent in active pause. I'm not sure that track desync over time is what is being reported, there are other reason why certain modules break tracks • the F-14 simply does not record player interactions with Jester's GUI "Wheel" (AFAIK keyboard short cuts are recorded) • the Gazelle has very little stick deflection (controls indictor very near zero) so tracks quickly desync or don't respect the players previous input • the Huey assumes no ffb (tracks need ffb turned off to play correctly) • MP tracks may call server scripts, so play perfectly until the server changes the mission or updates it. These are not random issues and shouldn't be coloured as such. I've watched a Mirage 2000C, 1 hour 40 min track, from the 4YA PvE Syria server (with ~32 players plus AI units) recorded in Open Beta 2.7.5.10869 that played correctly all the way through, so this certainly isn't effecting all modules.

I'd say yes but you'll be using keyboard assignments for a lot of stuff i.e. TDC slew, depress/designate, etc., etc. If you haven't already, I suggest setting up your controls and testing the free Su-25T for a couple of hours before dropping the cash to buy the Harrier.

Although the DCS Mi-24P models torque and weather cocking, and it is possible to run out of pedal authority, AFAIK it does NOT model LTE due main rotor vortices or tail rotor VRS due to crosswinds etc. This is an abridged version, for further detail check out page 147 - FAA-H-8083-21A, Helicopter Flying Handbook 2012

Yeah, I see the same (Grenade + 12.7 fire together). AFAIK mission loadouts are saved with mission file, so • Instant Action>Mi-24P>Syria>Weapons Range ... was created with a incorrect loadout or (more likely ?) loadouts and the weapons system are still WIP. Tested DCS Open Beta 2.7.5.10869 • DCS World\Mods\aircraft\Mi-24P\Missions\QuickStart\Mi-24P_SYR_IA_Weapons_Range.miz, 11/08/2021, 4,564 KB

As SnuggleFairy said, it is NOT the default loadout, this is what the default looks like. Your version has added the GUV-1 AP30 to stations 2 + 5. If still uncertain you've edited the default loadout, you can remove any customisations by deleting • Saved Games\DCS\MissionEditor\UnitPayloads\Mi-24P.lua (only created/exists for user loadouts and edits) There's a similar default loadout with 4x GUV-1 AP30 + 4x ATGM, perhaps you're thinking of that one ?

Not sure about the other elements like the radio, etc. but turning the MPCD exports on and off is assignable (unbound by default) This is how the default "HUD only" view (LAlt+F1) looks with MPCD exports turned off: At a guess, "HUD only" view is expected to be used with a home cockpit/large screen and the MPCDs, radio elements, etc. repositioned to fit on secondary or tertiary screens. Tested DCS Open Beta 2.7.5.10869

TL;DR: • The main/tail rotors, have fixed speeds (unless rotor RPM falls due to load) • Increasing collective, increases the pitch of the main rotor's blades, increasing the rotation torque • This has to be compensated for by increasing the pitch of the tail rotor's blades, this is done using the anti-torque (rudder) pedals. Detail: The tail rotor is connected to the main rotor gearbox (not the engine) and like the main rotor, has a fixed speed (unless rotor RPM falls due to load). Increasing collective, increases the pitch/loading of the main rotor's blades, this would cause the Main Rotor RPM to drop, so the engine governor responds by increasing power to maintain the SAME rotor RPM. The increased pitch of the main rotor's blades also increase the rotation torque to be compensated for. As the tail rotor turns at a fixed RPM, increasing the tail rotor thrust has to be done by increasing the pitch of the tail rotor's blades. This is done by changing the position of the anti-torque (rudder) pedals.