Ramsay's post in C-101 and NS 430 installation was marked as the answer
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
Ramsay's post in AV-8B : The coordinates at ODU change and run away. was marked as the answer
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
Ramsay's post in Vaziani 31 ILS localizer incorrect was marked as the answer
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 22.214.171.124404 using an A-10C
Ramsay's post in Elevator trim mappings?? was marked as the answer
You'll want to enter "Options>Controls>Yak-52 Sim" and swap DCS's force axis outputs to match the MSFFB2.
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.
Ramsay's post in NS 430 for the HIND? And is the NS430 dead? was marked as the answer
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.