Ramsay

Took me a while to workout what I "think" is going on ...


• Strangely the mission has "no weather" set (usually seen in older missions that haven't been updated), which means the night sky (stars/moon and clouds) aren't rendered and (some?) ambient lighting effects get broken.
• Spawning directly on the runway at Batumi doesn't give many visual clues
• It takes a while (time acceleration) for the NavFLIR to oversaturate.
• Gamma=3.5, SSS, SSLR and SSAO don't help but aren't the root cause, rather it seems to mainly be the missing weather and poor location.

Have you tried a Install Repair ? Which mission/module are you testing this in ?
A quick test using Open Beta with the Gazelle 342L and F-15E in Single Player showed no issue using LALT+Left Mouse button.

The Bullseye is bugged on the Sinai map.
 

That is because the Airport Info gives the approx. location of RWY 25's threshold, NOT  the location of the runway centre / symbol
You don't, MGRS is Easting followed by Northing - the OP's Easting is approx 1.3 km "off" because they measured the co-ordinates of the runway centre/Airport symbol, NOT RWY 25's threshold.
• Runway Centre /  Airport Symbol is at the edge of grid square KM 91 72
• RWY 25's threshold is in grid square KM 93 72

Yes, for example the DCS MV in Normandy depends on the mission date and is 'W -7.6°' in 1944 and 'W -0.3°' in 2019
 

DCS uses a database of values and years, I don't know the detailed mechanics but for example there's MagVar data in "DCS World/Data/MagVar/2015, etc." (WMM-2015, 12/15/2014)
 

No, it also depends on location i.e. the MagVar at Batumi (E +6.0°) is different to Anapa (E +6.5°) for June 2011
 

 
• Aircraft Systems True North = F10 ruler
• Magnetic Heading (i.e. the A-10C magnetic backup compass) = True North/F10 map - local MagVar
 
• FC3 aircraft i.e. Su-25T, simpler system model uses True North (F10 map) for all their systems.
 
Note: the F10 map ruler seems to round readings down, so 6.8° = 6° and it's not uncommon to find a heading error of +/- 2° between map measurements and cockpit but the source of errors greater than that should be sort.
 

 
Yes, see the above.
 
In game MV's measured using the A-10C CDU, DCS 2.5.4.28840 Open Beta

While the DCS NS430's operation/3D model is based off that of a Garmin GNS 430, do not expect the NS430 to be a realistic simulation of the "real" unit or to be able to use Garmin's operating instructions.
This Grim Reapers video helps set expectations for it's use in DCS and explains how to enter User Waypoints, naming limitations, etc. @20:25
Note: the NS430 has a number of reported single player and multiplayer bugs that are awaiting attention from ED.

Primary (max 8 ) allows messages and reports to be sent through the TSD i.e. present position, threats, points, etc.
Team (max 16) allows messages and reports to be sent through the COM Page i.e. threat list, waypoint list, etc.
Wags data link video @3:12
Using the COM page to send/receive mission data @4:29
 

Yes.
The RL F-15E Flight Manual (1993) gives the "basic weight" plus crew as
• Without CFTs = 33,500 lbs
• With CFTs = 37,500 lbs
(to the nearest 500 lbs)

AFAIK the GBU-28 should  not be available - it's a mission bug.
https://forum.dcs.world/topic/328735-gbu-28-malfunctions-in-mission-bombing-range-demo/?do=findComment&comment=5245103
 

Normandy 2.0 is "keyless", so doesn't have a CD key.
What does the Steam DLC manager show is installed ?
This is how it looks for me

 
Normandy 2 is listed in the Mission Editor as "Normandy" and maintains compatibility for owners who haven't upgraded (they miss out on high detail London/Paris textures, etc.). Were you expecting to see "Normandy 2.0" listed separately or can you not access Normandy at all ?

The original "Normandy 1944" (AKA 1.5) area, now has the same detailing and textures as Normandy 2.0
You will only notice the difference after upgrading to 2.0 when flying/spawning outside the original boundaries i.e. Gravesend after upgrading to 2.0. is more detailed.

This is a good "before" and "after" post demonstrating a successful Normandy 2.0  Licence "Upgrade"
 

This Mirage F1 CE E-M diagram was shared on the "DCS Dogfighters" discord

 

https://cdn.discordapp.com/attachments/1044787592794738749/1045083217000145038/Subsonic_Energy_Maneuverability_Diagrams_for_DCS_v202211.pdf

AFAIK the NS430 2D popup shouldn't require an additional purchase to work in the EB.
To enable the 3D NS430 cockpit instrument in the EB requires an additional purchase/module manager download 
https://www.digitalcombatsimulator.com/en/shop/modules/ns430_c-101eb/

Your waypoint co-ordinates were rejected - they are invalid i.e. seconds were greater than 59.
• N 42° 24' 86"
• E 041° 34' 72"
I'm not sure what exactly you are trying to do as I can't read the TPOD co-ordinates in the low res 480p video but if you are copying the TPOD's co-ordinates, they are in a different format "Degrees Decimal Minutes" to the EHSD's waypoint Lat/Long data entry which expects "Degrees Minutes Seconds".
This video might help if you're attacking targets of opportunity i.e. stuff spotted using the TPOD

Engine Oil Temperature ?

2kts isn't enough to keep ATC's active runway and ILS directions in sync (2.5.x bug).
 
In your mission ATC's active runway is 31 but the ILS direction is set for 13.
 
You can either ignore ATC's directions and land on 13 using ILS or increase wind speed to 6 kts toward 125°T so both ATC and ILS will use 31.
 
Tested in 2.5.6.47404 using an A-10C

TL;DR:
You'll want to enter "Options>Controls>Yak-52 Sim" and swap DCS's force axis outputs to match the MSFFB2.
 

 
Detail
It doesn't matter if you adjust the pitch trim with mouse, keyboard or an external trim wheel - when using "Options>Misc>Force Feedback", a FFB joystick will (try to) move to match the in game stick.
 
Unfortunately MSFFB2's force axis assignments don't follow Microsoft's own DirectInput FFB API, a force output on the y-axis (pitch)- actually changes the sticks physical x-position (roll).
 
By default, DCS follows the DirectInput FFB API as set by Microsoft and used by third parties such as Logitech, etc., the "FFB Tune>Swap axis" check box, swaps the x and y FORCE OUTPUT to be compatible with the MS FFB2 and/or other "non-standard" FFB implementations.
 
 

The NS430 2D "popup" works with the Hind already.
 
Press LShift+LAlt+B and test.
 

 
Eventually the Mi-24P will likely be added to "Options>Special>NS430" and you'll be able to disable the NS430 but until then, by default "LShift+LAlt+B" will always be available to call up the 2D NS430 if both  modules have been installed.
 
 
Support is not discontinued but the NS430 seems to have a low priority and very little (if any) resources devoted to it.
 
Realistically the best you can hope for is an updated entry.lua, etc. to add the Mi-24P to "Options>Special>NS430" so the NS430 can be disabled if desired.