Ramsay

Please add a non-flying track demonstrating the issue - i.e. a hot start spawn at Kobuleti with a point at 41° 50' 31" N = 41° 50.5' N 41° 47' 52" E = 41° 47.9' E

You should try using Low Terrain textures, even in a simple SP mission, High Terrain textures in Syria use ~24 GB RAM This is Syria's RAM use with Low Terrain, Extreme Visibility and vsync OFF You'll also want to increase the size of the Windows page file to 16 GB or 32 GB, as High Terrain textures plus a complex MP mission can use +50 GB.

TL;DR: You entered the wrong co-ordinates (unless the track played back incorrectly). Detail: Unfortunately the flight didn't play back correctly but before takeoff you seemed to measure position using DMS (Degrees Minutes Seconds) and enter it into the NADIR without converting it to DDM (Degrees Decimal Minutes), also the entered Easting was 3.5' off (likely a simple error or miskey/typo). As you measured in the replay 41° 50' 34" N 41° 47' 51" E As you entered in the replay 41° 50.4' N 41° 44.4 E Testing in DCS Open Beta 2.5.6.59398, I zoomed into the airfield and measured 41° 50' 31" N = 41° 50.5' N 41° 47' 52" E = 41° 47.9' E and had no issues

Tracks record your actions for the whole mission, you can't save a 15 second slice of your flight. Third party tools such as Nvidia's "Shadow Play" can capture game footage. Your issue sounds to be a duplicate of this report -

TL;DR: Does your buddy also own the Huey and the same Campaign ? Detail: Editing paid DLC campaign scripts/triggers is not going to happen - authors need some form of copy protection. In single player - you can copy a DLC mission to "Saved Games\DCS\Missions\...", open it in the ME, change the aircraft, etc. and fly a "protected" mission from the ME. Editing the scripts/triggers is disable, as is saving your changes. I haven't tested the Huey's multi-crew but it looks like if both players own the Huey AND DLC, they should be able to fly a "protected" campaign mission co-operatively. This is me hosting Argo Mission 3 (the co-pilot and gunner slots become available when the pilot takes his slot). Obviously, if your buddy doesn't own both the Huey and the Campaign - copy protection will stop him running the mission. Note: As DLC campaigns are designed to be played in SP, it's possible mission triggers, etc. may break or behave unexpectedly when used with multi-crew. This shouldn't be considered a mission bug as we are playing these missions in an unintended way.

Are you using mouse look in a FC3 aircraft ? In the Su-25T you'll need to switch to "Clickable mouse cockpit mode" - (LAlt + C) to interact with the NS430 2D pop-up, otherwise the mouse scroll wheel acts as a zoom and the NS430 buttons can't be interacted with. If you are having trouble with a different module, please give more detail and perhaps include a short track demonstrating the issue. Tested Su-25T and F-5E, Caucasus map, Open Beta 2.5.6.59398

AFAIK you can create a windows symlink in Windows 10 and redirect the temporary update files to another drive with more space.

In my case (22GB), most of it was Caucasus and Persian Gulf terrain update - at a guess you have the Channel map as well ?

Just finished downloading, no issue here.

Because it's realistic, it may also allow RB to adjust ground friction/engine thrust to give a realistic engine idle taxi, etc. As usual, it's about striking a balance between real life behaviour and "game" mechanics, RB can never please everyone.

Yes

The Harrier's AGM-65F is bugged (both in range and night vision) in the stable version of DCS (2.5.6.55960), it was fixed in the 4th Nov Open Beta patch.

IIRC other users have reported TrackIR micro-stutter when frame rates are above 60 Hz, as a trackIR user - I'm familiar with it but it's easy to differentiate from GPU micro-stutter by testing with TrackIR disabled. I don't know the fine details as my own monitor is a 60Hz large screen TV.

I find Syria a bit of an oddball, with High terrain textures that consume large amounts of RAM and a small draw distance for buildings/trees (compared to the Caucasus map defaults). I started off with high terrain textures but micro-stutter over towns, meant I switched to low to reduce stutters to a minimum. As I found the aggressive Syria draw distance annoying, I used the reduced GPU loading to increase visual range. With DCS running off a M.2 SSD I haven't found the pre-load radius to do much and so look to reduce DCS's RAM footprint. As I normally run with Vsync ON, it's possible it masks potential issues but my experience optimising DCS for a 1050Ti and now the Rift-S have taught me to pay particular attention to texture sizes and memory footprint when trying to avoid micro-stutters. I always find your input useful and obviously YMMV.

IMHO CPU use looks normal as DCS's performance is mostly limited by a single thread. However, I don't understand why your GPU use is so low ? With Vsync ON - I see perhaps a 78% GPU load but with it off, it's ~98% Low Terrain, Extreme Visibility, Vsync OFF I'm not sure about your micro-stutter if you experience it on *all* maps but for Syria - I find it particularly demanding on RAM, so I use LOW terrain textures (reduces system RAM from 26GB to 17GB in "simple" Syrian missions). Make sure your windows page file is set to at least 16GB min / 16GB max - in your case (Syria) I'd likely test 32GB min / 32GB max as I've seen system RAM reach +50 GB on 64GB systems. Also reduce the pre-load radius (perhaps to 60000m) as Syria is very dense. In MP you should expect reduced performance as it's very dependant on the server, number of players and how busy the mission is with regards to the number of scripts/AI units.

It's hard to be sure as the DCS AV-8B TPOD has been updated to a newer version and it's operation is now similar to the A-10C and Hornet, only AV-8B SME's will know how correct it is. I expect Razbam will still have a few "adjustments" to make/fine tune e.g. the TPOD North compass direction. The main change, if you weren't in the habit of already switching between TDC and HTS (HOTAS Control Mode), is that you now need to "double tap" (less than 0.8 sec) TDC depress to slew the TPOD, otherwise the TPOD will (most likely) slave to INS slews on the EHSD (which may not be what you want). A Grim Reaper video on the TPod changes.

The mission text and audio describe using the HSI's PRMG guidance bars to land at an incompatible ILS equipped runway, that anomaly was removed prior to DCS 1.2.16 (the oldest version I have installed). Here is a youtube video from 21st Jan 2014 of how the HSI's guidance used to work (the bars are visible at 3 min 18 sec).

AFAIK nothing official has been said about the Huey's engine/flight model recently (all emphasis has been about multi-crew). I assume ED's plans/priorities for the Huey have changed with the imminent release of the Mi-24. At a guess, the Huey's improved engine/flight model was a development step towards the AH-1 Cobra which is no longer on ED's roadmap i.e. like the Cobra, it changed to "we hope to someday" after Belsimtek re-joined ED.

No, people complain because the ILS and TACAN bugs are fast approaching their 3 year anniversary, have never been addressed and there's only a vague promise that the ILS bug *may* be fixed at an unspecified time in the future. It's no surprise that some players are hesitant to spend £65 ($80) on another module.

IIRC the HSI worked like that many versions ago (perhaps early on, when DCS first updated to 1.5.x) but the behaviour changed and the mission text/audio has never been updated.

This is described as a difficult landing mission and it is, it's at night, the runway doesn't have PRMG (Russian military ILS) and there is 5 m/s right to left cross wind i.e. In a crosswind of greater than 4-5 m/s, the brake chute is not used as it would make it practically impossible to maintain the aircraft on the runway. You can manually switch from Return (B3B) to Landing (NOC) mode by cycling the navigation mode "1" if needed. As well as monitoring airspeed, radar altitude and the ADI - the HSI gives important guidance in this mission, the thin needle points to waypoint and the double arrow is the required course - when thin needle and course needle line up you are on the runway approach path (you may need to crab a little (nose is a little right of the desired course) due to the 5 m/s crosswind (note: I'm not sure if the HSI's thin needle is visible at night in 2.5.6 ?). A 3° glide slope = 50m per km i.e. at 10km altitude should be no less than 500m AGL and/or 200m AGL at the outer marker. As Beslan lacks PRMG there is no ILS guidance on the HSI, however DCS's FC3 legacy code still provides raw ILS info at the LH side and top of the ADI. You may need to contact Beslan ATC and request landing permission to get the the runway lights turned on. My typical approach to this mission is • overfly Beslan at 2000 m • turn to the downwind leg (274°) and fly outbound • turn to final (94°) at ~20 km • follow instrument guidance / descend to 500 m • while inbound, contact ATC i.e. to turn on the runway lights • follow ILS guidance until visual of runway lights. • correct approach as req'ed and land visually • After touchdown, brake using air and wheel brakes, do not use the chute due to the crosswind. • DH - 200m and not visual, overfly the runway and go-around (you'll likely have to cycle the Nav mode ("1") to get back to landing mode)

I'm not sure what you are asking, kneeboard pages for the A-10C and A-10C II go here :- • "Saved Games\DCS\Kneeboard\A-10C" • "Saved Games\DCS\Kneeboard\A-10C_2" ... as the A-10C and A-10C II startup, etc. are the same I copied my pages from "A-10C" to "A-10C_2"

Perhaps. In you Steam Library > • right click on DCS World > • select Properties > Local Files • Verify integrity of game files Steam will check and replace any corrupt files it finds.

The decimal part of the UHF's frequency doesn't work (when set in the ME) in Open Beta 2.5.6.58125, so perhaps it'll be fixed in the next patch ? Tested using hot and cold starts, UHF Ch 05 = 360.60 MHz (ATC) at Creech AFB, Open Beta 2.5.6.58125

"easy coms" (found in Options>Gameplay) doesn't work with the Yak-52 and needs to be disabled, have you done that ? The default Yak-52 keybinds are \ (# for the UK) = COMM Communication Menu RAlt+\ (# for the UK) = COMM Push to talk