Ramsay

Unfortunately your track played back correctly on my Open Beta 2.7.0.5118 install i.e. the EHSD is shown in all switch positions. Have you tried cleaning out the "Saved Games\DCS\fxo" and "metashaders2" folders ? Can you share your settings and system specs ?

No issue here in Open Beta 2.7.0.5118, both the 3D model and 2D pop-up (LShift+LAlt+B) are working in a hot started Mi-8 in Syria. Settings to disable the NS430 are found in • Options>Special>NS430 and in the ME • for each player Mi-8 under it's "•••" properties tab. AFAIK the NS430 is enabled by default but some missions, such as those in the "Oilfield" campaign, disable it to force the use of radio navigation, etc. You could perhaps check the NS430 and Mi-8 model files are present and that "DCS World\Mods\aircraft\NS430\bin\NS430.dll" hasn't been blocked/deleted by an anti-virus or similar. • DCS World\Mods\aircraft\NS430 • DCS World\Mods\aircraft\NS430_Mi-8MT

I had the opportunity to install Syria onto my lower spec install, so for info this is what a single hot start Mi-8 looks like DCS Open Beta 2.7.0.5118 System spec. i7 860, 16GB DDR2, GTX 1050ti (1TB SSD for OS, 2TB HD for programs, data and DCS) Syria's RAM footprint was between 13 and 15.5 GB

I haven't tested Syria but have successfully used ILS in the Caucasus map several times. The stable build was missing a number of ILS features that have been fixed in Open Beta, really need to see a short track as "doesn't work" isn't enough info for me to be able to help. Chuck has updated his Mirage Guide so check out page 249 if you haven't already. https://drive.google.com/file/d/1jmp9ueZo9xOPyGzo3YO0AnFYEH-5Iotr/view?usp=sharing There's also this Grim Reapers video https://youtu.be/WDjTH5zI0aA?t=276

It's normal, the gun is powered by bleed air from the engine. The feature was added in DCS 2.5.6.57949 Open Beta, Nov 18 2020 i.e. six months ago. GAU-12 gunpod engine based firing restrictions enabled. https://forums.eagle.ru/topic/170893-dcs-world-25-changelog-and-updates-of-open-beta/?do=findComment&comment=4486087

Would need a short track to see what's happening, as I've had no Mirage specific issues. Note: The ILS director and synthetic runway use ILS, CP/PD (RH/DS)* and QFE, were these setup. *Runway (true) Heading / Desired (glide) Slope

Unfortunately it's a default bind, perhaps it's an inconsistent English --> French translation, as the same stick/mouse buttons are used to fire the mini-gun AND canon/rockets. You can test by arming the L's canon • Master Arm ON • Armament Panel ON • RH pylon SELECTED • HUD gun sight DOWN ... and switching to mouse look (LAlt+C), pressing the left mouse button (SOURIS_BTN1) should fire the canon. If it works, the question becomes - does the HOTAS-X column show for the "minigun" and can you bind a button.

The missing key binding seems to be an indeterminant bug that some players see, it's been suggested on discord that unplugging your throttle (assuming it's a separate device) will allow the "Fire Gun or Rockets" binding to reappear.

I'd need to see a track showing the INS issue, otherwise it'd be just wild guesses. The radar standby bug is known, AFAIK the flashing "P" can be ignored and it's safe to switch the radar to silent or emit.

Are you using DOP mode on the ADI to show the needles for lateral and longitudinal drift, they along with the VVI are the key to easily entering auto-hover. • Ground speed lower than 18 km/h • Roll and pitch lower than 30° • Vertical speed lower than +/- 0.6 hm/min The controls display (RCtrl+Enter) is also handy as it gives instant feedback on when Auto-hover engages and what mode it's in i.e. Collective and Slave https://www.youtube.com/watch?v=Ch_ZRXieGKk&t=154s

The module is WIP and ED have changed how strong the dust cloud appears. This is from a 2.5.6 stream last year. https://www.youtube.com/watch?v=D4RJMfZ0o34&t=2120s

Combined Arms has never been "good" at the best of times, unfortunately AI path finding pretty much broke in 2.5.6.x, with units getting stuck or "lost". AFAIK there's not much campaign makers can do to fix their missions until ED fix the core AI / maps.

Yes, the 10's selector goes up to 12, so you can dial to channel 129

It's a MagVar bug when the EHSD is in magnetic heading mode, UFC data entry is still using true, switching the EHSD mode to TRUE is a work-around until the bug is fixed (or entering the true heading in the UFC).

With maps like Syria, we are nearing the point where DCS can simulate a modern urban conflict where it becomes worth while to fit a $22,000 guidance kit to a $2,000 rocket to avoid hitting the wrong house/street/troops in contact. As well as removing APKWS from the OH-58D (2017) when simulating older conflicts, I'd like to be able to add it to the AH-64D (~2007) to test it's use when paired with KW and later used as it's replacement. For me, it seems silly to have a OH-58D (2017) and AH-64D (~2007) in a 2021 mission and not allow both to carry APKS rockets when there is no physical reason for them not to. I could understand ED's argument if the APKWS wasn't already in game or their AH-64D licence restricted them to weapons before a certain date. The "date" argument seems silly unless the AH-64D (~2007) "time travelled" to 2021 and wasn't able to rearm when it got here

Unfortunately I don't have the free space for the Syria map on my 16GB install. I can say that in 2.7, Syria appears to use a little less RAM\VRAM (~1 GB), a little more CPU/GPU (~10%) and have smoother frames on my main install but YMMV, so I'd wait for a free play trial or more feedback. Note: Running the map off a SSD (due to NVM space), I find loading times good in SP but some MP servers have been long (Weapons_Training_Freeflight_sy) while others good (4YA_Syria_Capture_Bases_BLUE). The main performance change appears to be in it's Video memory footprint.

I reverted a small footprint install of 2.7 back to Stable 2.5.6.61527, the Mirage has a similar render issue but it occurs far less often (perhaps after a fxo/metashader clean or graphics setting change). In 2.5 stable, changes to Gazelle L's ADI reflection are hard to detect due to the rotating blades/shadows.

I *suspect* it started last year (have daylight screen shots with a strong HUD collimator reflection) but can't be sure as I haven't flown the Mirage that much a night or in low lighting. It looks like the cockpit lighting mask is missing in 2nd and subsequent mission runs/spawn in the *same* mission, switching to a different mission reloads the mask. The Gazelle L's ADI shows the missing mask better than the Mirage The reflections/lighting in the cockpit are brighter due to the missing mask and unobstructed sky and clouds.

I've seen the same thing, workaround is to restart DCS. It's not a metashader or fxo folder issue but may be a DCS render issue of some sort. I'm not sure if it's a fresh issue as 2.5.x would sometimes play differently on a 2nd mission/spawn - BUT IIRC the bright HUD collimator reflection is far more noticeable in 2.7 especially at night. Can't say I've noticed the issue in other modules but that doesn't mean it's not there. Settings

Do you know how to align your INS on PREP 20, etc. or using the Options>Special>M-2000C>"Fast Alignment" option AFAIK the auto-start script is broken ATM.

Page 128 in Razbam's Manual lists the PCN Parameters In the French cockpit the BUT (goal) section has 3 positions Lat/Long, Alt (Altitude) and CP/PD (Cap vrai de piste / pente désirée au but) The equivalent English cockpit WPT (waypoint) section labels are Lat/Long, Alt (Altitude) and RH/DS (Runway Heading / Desired Slope).

There's this one in French AFAIK nothing much has changed with alignment other than than the need to use WP 1-20 for the initial alignment i.e. • enter initial co-ordinates and altitude into PREP 20 • validate to start the alignment • switch to Nav mode once complete

IIRC PCN now requires ground power or the engine running. Not sure why you can't read the LCD as they are usually quite bright - the PCN does have it's own brightness control.

TL;DR: I'm using my MSFFB with • Options>Special>[module]>Trimmer Mode= "default" • Options>Misc>Force Feedback = ON (checked) Both Mi-8 and Huey FFB appear to be working normally with my MS FFB2 i.e. hold offset "Force Trim" positions, both in game and with the physical joystick. Tested in Open Beta 2.7.0.4625 Detail: IIRC • Trimmer Mode = "Joystick without springs and FFB" ... is for free floating joysticks without either center springs OR Force Feedback i.e. for cockpit builders who perhaps use a full size cyclic with it's own trimmer system/brake. Additional Info : Remember to swap DCS's default force axis to match your MS FFB in • Options>Controls>[module]>SideWinder Force Feedback 2 (tab)>FF Tune ... if you haven't already done so. Detail here

Not sure what you're asking for, the campaign's missions were updated at the same time as the 2.7 patch i.e. Mission 2 uses Scattered 7 clouds.