Ramsay

Correct.

Both the Real F15E and Razbam DCS manuals say the front CMD pinky switch moves vertically - as you say, the switch animation appears to be forward/aft which is wrong. Tested in DCS 2.9.4.53707

The HSI NADIR needle in the SA-342L is broken ATM i.e. it doesn't point to the selected waypoint as it should. https://forum.dcs.world/topic/347051-nadir-waypoint-issues/?do=findComment&comment=5415678 AFAIK the Gazelle's NADIR is working correctly in the M1 and Minigun versions.

@DragonSoulkin Currently there are 3 Gazelle versions that are flyable by the player • SA342M • SA342L • SA342Minigun The 4th (AI only) version - SA342Mistral is kept for backwards compatibility with older missions that used the old Mistral version as an AI opponent. (Players can now load Mistrals on the L and there is no longer the need for a separate version ). Here is an example of the Gazelle's kneeboard folder names that are required to have custom pages in all 3 player flyable versions.

I can confirm the HSI "NADIR Double Arrow" no longer points to the correct WP azimuth. Switching the NADIR's Parameter Selector to TPS/CAP (WP Estimated Time / Heading) - the NADIR's WP heading reads correctly, so the fault is with the HSI needle. F10 Map Overview. I also confirmed the HSI's Waypoint needle was incorrect in a Caucasus Mission with zero wind. As reported here, the NADIR needle bug only appears to effect the SA-342L version.

Below the main panel starter and pump switches are the ALV (hover) and CVS (slaved) lamps which are yellow when armed and green once active/in parameters. The slaved autopilot will try to track the periscope/Viviane sight which moves with helicopter body unless ground stabilized • for the L use the "Periscope Command Box" Stabilization toggle • for the M, the Viviane sight will ground stabilize after it's first manual slew Because of these issues, it's probably best to switch to the co-pilot seat first (with same control/axis settings as the pilot) and setup the Viviane/Periscope, before engaging the Hover and Slave modes. AFAIK the current autopilot Hover and Slave modes are still WIP due to the Gazelle's new/more accurate flight model. Gazelle L Autohover test, 2_9_3.trk

Which manual is that, I don't see a 40,000 ft climb listed in the DCS MB-339A Flight Manual ? Climb rates in the Real MB-339A Instrument and Navigation flight planning section assume a 12 minutes taxi, take-off and level acceleration prior to initiating the climb (i.e. 80 kg fuel burned). Starting with 2x pilots, a clean configuration and full internal fuel (half full wing tip tanks), the RL manual gives a 30,000 ft climb @ 38 NM / 7.5 minutes / 222 kg additional fuel burned. The DCS MB-339A Flight Manual (Page 26) shows a Climb to 30,000ft performance spec. of 7.1 minutes (so is perhaps without filled wing tip tanks). When testing, I found the real MB-339A flight planning tables worked well enough for DCS i.e. climb distance/time +/- 15% and fuel used covered by the 200 kg planning reserve.

"dcs-20240320.log" still has too small of a page file - DCS/Windows is likely running out of memory.

AFAIK not really - as the issue comes from still having a input on the opposite axis (i.e. a slight input on horizontal axis can cause the vertical axis to "stick"). It can be "fixed" by setting a axis dead zone (size depends on how much drift/jitter the other axis has). Here is an example of my Winwing TDC axis setup, which is a compromise for sensitivity vs slew speed - YMMV. Similar thread Re:TPOD slewing https://forum.dcs.world/topic/331645-tdc-slew-axis-horizontal-especially/?do=findComment&comment=5270402

What makes you think you've damaged your MiG-19, when I watch your replay - the ground crew rearm and place/remove wheel chocks as requested. They also acknowledge your repair request with a "copy", AFAIK when there's no repair timer, there's nothing to repair.

I flew for several years using the twist axis of a MS FFB2 Joystick - so flying the Gazelle is possible with your setup. Starting out - it took me around 12-18 hrs of practicing hover taxiing around airfields, etc. to get comfortable coming from the Huey, etc. My son started flying DCS helicopters in the Gazelle, so while it's not the easiest to start out with due to it's sensitive controls, it's certainly possible. Note that different loadouts, fuel weights and versions i.e. M, L, etc. can have an effect on how easy it is to fly. If you haven't already - I suggest starting with air spawns and getting comfortable with it in flight and only then moving on to the more difficult aspects of hovering, take off, etc. that IMHO require time and patience similar to A2A refuelling in fixed wing aircraft (you can sort of "cheat" as a newbie - and use a quick "jump" to get into the air and worry about landings later). Perhaps this tutorial from deephack will help ?

Not sure why things have changed - taking control of your track, I could engage the Autopilot Modes/Lamps, once I reset the Autopilot using the • Autopilot disengage lever (Control Stick paddle switch) Tested DCS Multi-thread Preview 2.9.3.51704 F1EE auto pilot works after AP disengage lever rpt richskinns.trk

AFAIK the pilot's desired SAS attitude and heading is set using the same cyclic button as magnetic brake. The SA342 SAS receives inputs from • Heading - Gyromagnetic compass • Pitch & Roll - Primary ADI • Altitude/Speed Hold sub-modes - Barometric Altitude/IAS from the Air Data Module • Air Speed above/below 90km/h (49 knots) - Badin Switch • Pilot control input - Pitch, Roll and Yaw linkage micro-switches Heading is maintained with the SAS Yaw channel below 90 km/h IAS and switches to using the Roll channel when above 90 km/h IAS A French 1970 SA342 Historic Flight Manual is available from www.alat https://www.alat.fr/documentation-alat-manuels-instruction-techniques-manuels-manuel-equipage-sa342-m-1970.html Section 1.7 describes the Autopilot and starts on page 65.

There's no ETA but IFE Duke posted this on their discord last week So work is in progress.

The Engine shuts down with the FUEL LEVER if the "Starter" switch is in the middle ARRET/OFF position. When in flight - the "Starter" switch should be UP i.e. in the MARCHE/ON/RUN position. Currently the Gazelle spawns with the "Starter" switch in the incorrect ARRET/OFF position, so it needs moving to MARCHE when selecting an air spawned or hot started Gazelle.

Problems firing the 2nd E2 Laser Maverick are usually due not cycling it's cage/uncage button. There seems to be a bug where the 2nd E2 LMav retains the status of the first and is "sort of" uncaged (has good HUD symbology, etc.), but isn't. https://forum.dcs.world/topic/342804-how-to-use-laser-maverick-with-tgp/?do=findComment&comment=5392150

TL;DR: If you want help, rather than just venting your frustration, please start a new thread with a short track/video of your firing procedure. A common error is, after the 1st IR Mav is fired - the system switches to "INS Mode" and SSS Forward Short is required to reselect IRMV to lock/fire the 2nd IR Maverick. Detail: Here is an earlier post I made describing firing IR Mavs and errors to watch out for. https://forum.dcs.world/topic/324103-help-with-ir-mavs/?do=findComment&comment=5199684 This video from Deephack may also help As will Chuck's AV-8B Guide - Part 10 Weapons & Armament - Sections 2.7 and 2.8 https://chucksguides.com/aircraft/dcs/av-8b/

They are, originally the missions worked as intended and Kobuleti's active runway and ILS was RWY 07. DCS's chosen runway direction has become particularly unpredictable when dealing with light head/tail winds (1-6 knot), hence the issue with these older missions. No, the problem with ATC appeared with DCS 2.5.0 but seems to have a very low priority with ED as it's not combat related. There is the promise of an ATC future rework but it seems to be focused on new voice lines, etc. rather than simple functionality. Yes, it's unfortunate players need to learn the mission editor and adjust the wind in a copy of the training mission or create their own versions.

No, it is a real limitation and how the weapons are carried i.e. an example of GBU-12's on one side and AIM-7's on the other over Iraq in 1999.

They did and the asymmetric loadout is valid in DCS.

TL;DR: Correct, the mission loadouts need to be updated to carry the E2/L version. Detail: The AGM-65E cannot be self lased and represents an "earlier" Harrier software/missile combination which could not lase from the launching aircraft. The AV-8B's E2/L variant in DCS represents a newer software/hardware combination (perhaps ~2012 when the centre pylon was wired to accept the TPOD?) that could self lase i.e. switching from TPOD to LMav E2/L didn't switch off the TPOD's laser. https://forum.dcs.world/topic/276694-announcement-regarding-agm-65-maverick-loads/ See Chuck's AV-8B Guide Part 10 "Weapons & Armament" (page 227 and section 2.8, etc.) for more detail of how to employ the AGM-65E and AGM-65E2 variants in DCS. https://chucksguides.com/aircraft/dcs/av-8b/

Not, exactly - IIRC I've always been able to fire the first E2 Laser Maverick, it's the follow Maverick that can have issues i.e. 2nd E2 Laser Maverick appears to have "good" HUD and MFD lock symbology (but it's likely a residual system state from the 1st missile fired) Although the 2nd E2 Laser Maverick's X is steady on both the HUD and MFD, the MFD is missing the LMav's "crosshairs" Cycling the Maverick cage/uncage button fixes the missing MFD LMAV symbology and allows the 2nd LMav to be fired successfully These screenshots were taken over a year ago and AFAIK nothing has changed re: Maverick behaviour. Note: In this case a JTAC "lase" was provided by a CTLD autolase script and YMMV when using the TPOD to self lase.

Read the initial Polychop post.

I was firing IR Mavs yesterday without issue, so it's unlikely to be a bug, can you share a short track file demonstrating the issue.

My understanding is that - • NEW locks generate a warning tone and the identified threat aircraft symbology should flash/blink for 5 seconds on the TEWS. • The previous behaviour, where a circle was drawn on the TEWS aircraft that was locking us up, was unrealistic. I haven't tested this in game.