Jump to content

Ramsay

Members
  • Posts

    3618
  • Joined

  • Last visited

1 Follower

About Ramsay

  • Birthday 12/05/1958

Personal Information

  • Flight Simulators
    DCS World
    MSFS 2020
    Arma 3
    Falcon BMS 4.33
    Kerbal Space Program
  • Location
    UK
  • Occupation
    Retired

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. There's no ETA but IFE Duke posted this on their discord last week So work is in progress.
  3. 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.
  4. 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
  5. 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/
  6. 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.
  7. 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.
  8. They did and the asymmetric loadout is valid in DCS.
  9. 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/
  10. 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.
  11. 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.
  12. 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.
  13. The Razbam F-15E discord was/is full of RWR discussion about the changes, AFAIK from the SME replies, the new behaviour is correct i.e. matches the real.
  14. Following SME feedback, new A/A contacts in search (Nails) have no "new guy" tone.
×
×
  • Create New...