Ramsay

TL;DR: It'll be done when it's done, PC have they said they want it *mostly* feature complete. Detail: Last date I heard was 2021 and PC wouldn't be more specific until the module had at least been sent/met Bell's approval process.

No, I just did a quick sanity check with the default time and weather.

I confirm there's a large (~10°) error in the AV-8B's EHSD ground track on the Normandy map when using magnetic bearings. Switching MapM to TRUE is boxed fixed it for 21 June 2016 (MV = W 0.7° both historically and in the A-10C). The magnetic variation (both historically and as measured by the AV-8B) is not large enough to cause the error.

No issue here going to page 5 of the Open Beta change logs and searching (Ctrl+F) for the word "Syria" https://forums.eagle.ru/topic/170893-dcs-world-25-changelog-and-updates-of-open-beta/?do=findComment&comment=4392356 DCS 2.5.6.53756 Open Beta, 2020-08-18 DCS 2.5.6.54046 Open Beta, 2020-08-26 DCS 2.5.6.57264 Open Beta, 2020-11-04 DCS 2.5.6.57949 Open Beta, 2020-11-18 Not including the addition of numerous "Quick Start" Syria missions, etc. by other dev's

AFAIK it is caused by the size of the antenna (and supporting guy wires) "collision" box and is a DCS "world" issue, rather than JF-17 issue i.e. it effects other modules/targeting pods. IRL it's common for TGP's to "lock" onto the wrong (brightest/darkest) contrast and they often have ways to offset their laser designator to the compensate. While the lock/laser designation issues we see with guy wires are not totally realistic, they are IMHO analogous to RL TGP problems. It's possible ED's FLIR improvements will change things for the better but we'll have to wait and see.

Only one pair of NDB's will be active at any one time, which pair depends on the active runway i.e. ATC/wind direction. The different letter suffix are their morse ID's, so *you* the pilot can confirm the correct runway/beacon is active i.e. • 289kHz RWY 22 outer marker = RK = ".-. -.-" • 289kHz RWY 04 outer marker = DG = "-.. --." From a game play perspective, mission winds are setup so ATC has the correct runway/NBD's active, so it's not something you'll usually need to worry about outside of dynamic weather or mission making (DCS's 2.5.x ATC can desync the active runway and NDB for light (1-3 knots) headwinds i.e. ATC will say to use RWY 04 but activates the NDB's for RWY 22).

As it's not allowed on these forums to compare DCS's helicopters to those in other sims, you *may* not have all the information when saying ED's "helos are universally praised". IMHO ED's helicopter FM's are good but not without their flaws e.g. the huey's collective and pitch/roll cross coupling is reversed, available power is wrong, LTE is missing so it's twice as stable (+40kts) in an adverse crosswind than RL, etc. While it's good ED plan to maintain their FM quality in the M-24, I would have liked ED to take the opportunity to iterate on their previous FM's and improve on them - I fear this is a "new team" that's been given a "quality standard" and told to work within existing limitations. How well this conservative/production line approach works will mostly depend the amount/quality of SME feedback that ED have available, rather than FM limitations i.e. most DCS players seem content with the existing FM's and either "buy" into ED's hype or at least except the limitations. I just don't find ED's conservative approach as "exciting" as PC's unproven Hummingbird FM that potentially models LTE, etc. YMMV

Funny, that more or less summarises PC's initial responses when receiving FM feedback from RL helicopter pilots i.e. they had flown the "wrong type" of helicopter/gazelle and DCS's gazelle was 'special'. In the case of DCS's helicopters - there are control response and stability tests done on the real aircraft i.e. that reveal missing effects like LTE due to adverse crosswind or an AoA gauge that RL pilots use to determine when the helicopter (Mi-8) will go light on it's wheels/skids, that don't match up in DCS. AFAIK ED have implied they don't see the need to "needlessly" improve their flight modelling over and above that seen in the Ka-50/UH-1/Mi-8 which is fair enough (as they've been pretty well received), however it's also why I'm more excited by PC's Kiowa than the Mi-24 which promises "more of the same" which IMHO is both a good and bad thing.

You should be able to download the appropriate version of F-86F from the command line while in the "DCS World\bin" directory of your 1.2.16 DCS install, the command is • DCS_Updater.exe install F-86F from the windows command prompt or • .\DCS_Updater.exe install F-86F from PowerShell. See this thread for more detail, DCS versions, Module names, etc.

Sales occur approx. every 3 months or so (Spring, Summer, Autumn and Christmas/New Year). https://steamdb.info/app/249310/ Individual modules rarely go on sale separately apart from an initial "pre-order" discount and then occasional "package" bundles i.e. the Hornet + Persian Gulf Map (40% discount), Helicopter Bundle (Mi-8, Huey, Ka-50 and Gazelle - 65% discount). A break to this pattern are ED's recent Early Access discounts for the P-47, Channel Map and Syria Map - where the incomplete EA module continues to be offered at a discounted price (20% discount) for a short while after release (until more feature complete/bug free).

The TELSON 8 Inductive Rocket System fitted to our SA342 L is said to be "Combat Proven" since 2009 (Afghanistan, Libya, Mali, etc.) and have been in service for 10 years - which puts it in service no sooner than 1999 (more likely early 2000's as the literature looks to date from ~2012). There are pictures of Gazelles fitted with a traditional SNEB rocket pod but it's not clear which Gazelle variant it was and/or the date. It certainly wasn't our Gazelle with it's digital pod. The 20mm GAIT M621 Canon is harder to date as the canon dates from 1973 with a possible service date in the late 70's. I couldn't find a service date for the helicopter mount but a naval variant entered service in 1988. Obviously there nothing stopping players/mission designers using the DCS SA342 L as a place holder/substitute in earlier conflicts.

It usually happens when you haven't setup the weapon profile/auto-lase correctly. I see you setting up auto-lase in the profile but am not sure it "took" correctly i.e. was loaded to the current weapon profile. Unfortunately as it's a MP track, I can't take "control" and check the profile after it failed.

I think the HUD's current ILS guidance is bugged/inaccurate and should behave more like this https://forums.eagle.ru/topic/144961-hud-bugs-since-launch-all-related-to-fpm-amp-pitch-ladder/?do=findComment&comment=3214446

@Q3ark The Syria map was "released" on DCS 2.5.6 stable on the 9th October 2020 The map itself is in Early Access, with plans to include Cyprus and receive further optimisation. AFAIK, it's not known when the map will be considered "complete" and moved out of it's "Early Access" status.

@mikestanley464 DCS is on 2.5.6 now, 2.0 is a depreciated version (from 2017) used to run early versions of the Nevada map. Is there a particular reason why you want to install 2.0, rather than 2.5.6 which supports multiple maps ? https://www.digitalcombatsimulator.com/en/downloads/world/

Yes. The integration of the NS430 into 3rd party cockpits requires those dev's to create a 3D NS430 model and/or re-work their existing cockpit to "Fit" the NS430. These 3D "cockpit fitting kits" are sold for ~$6 each and while not particularly good value, do allow VR use and the dev's to recover their costs. The functionality (or not) of the NS430 is entirely determined by ED's base NS430 and hasn't changed significantly since release. If looking for a detailed or full functioning representation of a Garmin GNS 430, you will need to look elsewhere. https://steamcommunity.com/profiles/76561198018615750/recommended/933980?snr=1_5_9__402

@esequiel What was the wind strength and direction, there is a long standing 2.5.x issue with ATC Active and ILS runways desyncing for light headwinds (1-6 kts) ?

@sergkar That is correct, neither the C-101EB, C-101CC or Gazelle NS430 3D Cockpit kits are available on Steam. The "All-in-one" NS430 Module sold on Steam includes the base 2D "popup" and 3D cockpit integration for the L-39 and Mi-8 (all made by ED/Belsimtek). It does NOT include addons created by 3rd party developers. The base 2D "popup" works with the C-101 and Gazelle but is not compatible with VR. It's unknown when or if 3rd party NS430 addons will be made available on Steam.

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.

@R0NiN TL;DR: I wouldn't expect the KW to be released soon, although it's FM seems almost complete, there seems to be a lot of work required to "finalise" the module to a level Polychop are comfortable with. Detail: Polychop have said they are cautious when discussing WIP features as the DCS community can often react with unrealistic expectations or negativity (sometimes both at the same time), which in turn prevent/distract the dev's from actually working on the module (so they prefer to stay quite unless there is something to "show"). AFAIK • System wise they are working on adding the moving map, refining how the MFD menus work, RWR, AI co-pilot, etc. • Art wise they are adding/refining the 3D pilot/co-pilot models and external lights (WIP screenshots were shared 2 weeks ago). • Audio is WIP with some elements missing and others requiring re-recording/sampling. • A basic damage model has still to be added (it will be expanded after release). • The intention is to release as "complete" and bug free KW module as possible, so the dev's aren't "firefighting" to support both modules and time and resources are available to rework the Gazelle FM as promised. Although unrelated to the KW, the Gazelle FM was again heavily criticised on discord, necessitating the dev's to investigate (the player: flew inverted, engine died, auto-rotated while inverted, then normalised their orientation to complete an auto-rotation landing - using it as an example of an unrealistic FM). The dev's responded (as such criticism undermines the KW) at length, explaining how the KW's "hummingbird" FM compares to the Bell 407 in another sim, etc. and what the Gazelle FM does/does not model and what might change once it's reworked. While it's good to see the Gazelle getting attention and Polychop ensuring lessons learned are carried forward to the KW, such investigations (while necessary) do divert time and focus from the KW's development. When Polychop go "silent" I take it as a good sign they are free from community "drama" and able to focus on their personal lives and KW development - no more, no less.

I only had a symptom like that when I forgot to swap DCS's FFB force axis for a MS FFB2 Sidewinder Joystick i.e. adjusting pitch trim was causing the physical stick to move to the left/right and aircraft to roll. • What does the trim wheel in the cockpit do ? • What does DCS's control indicator show (RCtrl+Enter) ? • What is your physical stick/yoke doing (is it spring centered or FFB) ?

There are 2 Gazelle NS430 Cockpit versions available on the ED Store • The 3D Gazelle Cockpit "fitting kit" on it's own (i.e. for owners who already have the base 2D NS430) - $2.99 (reduced from $5.99) https://www.digitalcombatsimulator.com/en/shop/modules/ns430_sa342/ • A Gazelle Bundle that includes the 3D Gazelle Cockpit "fitting kit" with a copy of "base" 2D NS430 (i.e. if you don't already own the base NS430, etc.) - $14.99 https://www.digitalcombatsimulator.com/en/shop/bundles/ns430_and_ns430_sa342_bundle/

You may need to prompt steam to start the download • Steam>Library>Downloads or • Steam>Library>DCS World Steam Edition --> Right Side Bar > Manage My DLC Alternatively exit out of Steam and restart it. Note you'll *likely* need to be running DCS Open Beta to "see" the Rising Squall Campaign. • Steam>Library>DCS World Steam Edition>Properties>Betas --> "openbeta - Public beta versions" The current DCS Open Beta version is 2.5.6.60966

IIRC "Error code 500" is windows time and date not synchronised.

IRL the AV-8B's AWLS and Hornet's ICLS are the same thing. When the LHD-1 Wasp's AWLS was certified in 1999, it was certified using F/A-18A's and simulated landing approaches. SME's say AWLS was rarely used and TACAN was the preferred/only Case 3 method. It's not clear if the Tarawa was fitted with the equipment/radar/aerials necessary for AWLS. Edit - to answer your question TL;DR: Gameplay. Detail: When the AV-8B was released, ICLS wasn't modelled in DCS, I'd *guess* that, as AWLS wasn't used much IRL, Razbam decided to model it as an ILS to give it a "function" in DCS and add a gameplay element. While I agree with your sentiment, IMHO removing a gameplay element would not sit well with a large portion of the community/existing owners i.e. I held a poll and of the few that responded, there was a 6:4 split in favour of removing AWLS=ILS. Modelling AWLS realistically ... • wouldn't necessarily add AWLS to the Tarawa i.e. pictures don't show it having AWLS equipment • would remove "AWLS/ILS" from airbases • requires the removal and/or reworking of training missions including voice lines. • might require dev time to create a portable AN/TPN-30B unit to add a TACAN/ICLS beacon to land bases, via the ME It's a lot of rework, for very little reward and likely a lot of complaints from those that didn't care or didn't want it. IMHO Razbam should move on (but perhaps explain their AWLS logic/choices better) and continue focusing on getting the AV-8B complete and of "finished" quality.