Ramsay

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.

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.

AFAIK "LTE" is not modelled in DCS's Mi-8. It will however weathercock when the tail is struck by a crosswind, etc. This doesn't mean you can't runout of pedal authority in DCS, just that pedal authority is likely greater than the real. AFAIK Loss of Tail Rotor Effectiveness due to • vortices coming off the main rotor and striking the tail rotor • tail rotor VRS • tail rotor AoA reduction ... is not modelled in any current DCS helicopter.

Not sure what currency you're using. Steam DB shows FC3 released Nov/Dec 2014 @ $40 ($24 (40% discount) for the first week) with a price increased in May 2018 to $50 that effected most modules/currencies* * IIRC ED "standardised" their pricing/exchange rate, rather than price in local currencies i.e. A-10C increased to $60 at the same time. Currently FC3 has a 50% discount in ED's store, so is $25 ($24.99) at the moment. Like other modules, FC3 is updated/maintained to be compatible with changes in DCS's core and improved as time/resources allow.

Yes, but now that INS overfly and offset updates work, there's a good reason to do a position update prior to an attack or landing. It "feels" a good day to be a Mirage owner

I believe so, but I haven't used fast alignment in 2.7, so don't know the details.

Can you post a track, 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

I'm not seeing any difference between the Mirage and A-10C with regards to ATC's ILS. 2.7 has made the ATC active runway and active ILS desync issue worse than 2.5 as 2.7 seems to be more strict on the direction and magnitude of the wind, you now need to have a 3 m/s (5.5 knot) headwind to be sure the ILS and markers are turned on for ATC's active runway. Here I've had to increase a 60° crosswind from 8 knots to 11 knots, to get a 5.5 knot (3m/s) headwind on RWY 07 to trigger DCS's ATC to turn on the ILS. So far I've used the ILS at Senaki and Kobuleti while flying in 2.7

It's not a bug, the functionality of the "NEAR" range switches was changed/corrected sometime ago, unfortunately the manual has never been updated to reflect the change. 1. 150 - 310 kHz 2. 310 - 640 kHz 3. 640 - 1300 kHz. It is no longer possible to set pre-set frequencies in the ME i.e. it's not a feature of the real. See this thread for more detail

Don't let the lack of rudder pedals stop you, if you've flown the Mi-8 using joystick twist, you'll have a good idea of the main issues of having to hold the twist, while making cyclic changes. It takes time/practice to build up a steady wrist and you'll likely always be at a disadvantage compared to someone with rudder pedals when holding a hover but the lack of space for a set of rudder pedals has never held me back from buying/flying a helicopter.

I don't recall a Mi-8/Mi-17 SME saying DCS's VRS wasn't over-modelled who wasn't part of the development team. However the lead dev. (joined ED 2012/13) Aleksandr ‘PilotMi8’ Podvoisky flew the Mi-8TV, Mi-8MT and Mi-8MTV has +1200 hours on the type. With that number of flight hours, all I can do is leave the real life pilots to talk it out.

I haven't found the DCS Mi-8 to be as prone to VRS as you suggest (300 ft/min = 1.5 m/s). The barometric VSI does model instrument lag and it's scale is rather course - making the doppler instrument the preferred reference. Last time I checked (using tacview), the VRS risk zone in DCS was closer to ~3 m/s (600 ft/min) but that was several years ago. IIRC real life pilots have said DCS's Mi-8 is overly susceptible to VRS when compared to the real, so you are right in that regard.

I don't know the details i.e. if it's a DCS API limitation, but the L-39ZA carries both R-3S (rear) and R-60M (limited all aspect) missiles and BOTH give an "all aspect" lock tone, IIRC the dev's said they could only implement one type of seeker logic for the player and had chosen the "all aspect" version, which meant the incorrect logic carried over to the R-3S. The limitation also likely carries over to the AI as I've often been shot from the front in merges, despite give them the older rear aspect R-3S.

• DCS World\Mods\aircraft\NS430\entry.lua The 2D NS430 is enabled by default unless explicitly "disabled" i.e. removing or commenting out with "--" the line ["F-16C_50"] = disabled, ... in entry.lua will allow "LShift+LAlt+B" to call up the 2D NS430 window in the F-16C. Tested DCS 2.5.6.61527 Example edit with line commented out: