Ramsay

Thank you for sharing your track file. They show you are using the Easy/Game mode - which is unsupported, hence the broken flight model, etc. You will need to uncheck • Options > Gameplay > Difficulties --> Game Flight Mode ... to fly the Apache.

It was removed as a pre-aligned fast (3 minute ALCM/STH) start up is available by default unless disabled by the mission/server. For players who can't wait 3 minutes or don't want to learn the fast alignment procedure there is always the option to make missions that spawn the player in an already running/aligned aircraft. https://youtu.be/EvoSwROL98Y

Not really as ... • the GPS satellites req'ed for the NS430 to work are only available for mission dates set after March 28th 1994. • the VHF radio isn't modelled The 2D NS430 "pop up" is scalable, so easier to read than the info bar. Currently the displayed airspeed is incorrect (a factor of x1.85) and fixing the NS430 appears to be a low priority - so I can't recommend buying the NS430 ATM. https://forum.dcs.world/topic/316306-incorrect-ground-speed-being-shown-by-ns430/?do=findComment&comment=5121528

There is no way to save edited copy protected missions from the Mission Editor, however they CAN BE LAUNCHED (from the Editor) - so if making simple changes i.e. substituting the player aircraft, and you don't mind re-editing the mission each time you play, it's a work around. For example i've ... • flown a WWII introductory mission using the Gazelle to sightsee / attack German tanks lol • and flew the L-39ZA in a F-86 Sabre Museum Relic mission As noted, mission triggers are often module specific, so don't expect too much, however simple edits can be "fun" provided the still AI spawns, etc.

N1 is replaced by N2 assets for all N1 owners, this is for MP compatibility and SP campaign makers. Disabling the N2 "update" - means high res textures, airfields, railway tracks, etc. for areas outside the boundary of the original N1 map aren't drawn. AFAIK the only way to retain the old version of the Normandy map, is to run an older version DCS i.e. Stable 2.8.1.34667

Unfortunately your track didn't play back correctly, after rearming at Kutaisi, the Harrier flew over the sea (a heading of 236°) instead of towards the target area.

Not AFAIK.

How effective they are depends on the target and if there are surface winds. AFAIK you should select the Primary fuse in the harrier. I had no issue destroying soft trucks (12 vehicles of a 14 truck line in one pass), zero wind (CCIP Mk-20 Qty 4, Multi 1, 600 ft spacing) Currently AUTO/CCRP ripple bombing is broken in the Harrier and only the first bomb drops, you can use the uncage button to switch to CCIP but that will require you to designate the target/area using the HUD. My initial CCIP testing was from between 8000-1000 ft with weapon release at ~1400 ft AGL (the Mk-20 opens at 1200 ft releasing it's bomblets). Testing higher altitude (10-8,000 ft) CCRP releases, the Mk-20 falls with a much steeper impact angle and the bomblet spread was less, in those tests only a single vehicle was hit/destroyed per bomb.

As above, check out N 51° 23' 45", E 001° 02' 47", there's a line of 3 Army Forts running across the Thames estuary.

Yet that is where Normandy 2.0's Maunsell Army Forts are placed i.e. there are 3 placed in a line across the Thames estuary in the general location of where the real ones are/were. Tested in DCS Open Beta Multi-thread 2.8.4.39313

AFAIK DCS's DL is modelled as a one hop radio link from other fighters (F-16, F-15, etc.) and/or AWACS (E3/E2). IIRC • the DCS DL has a range of ~120 NM (not sure if modelling sat. radios will change this) - IRL intermediate aircraft can "relay" DL packets to/from distant aircraft. • the E3 is also modelled as a Network hub sharing SADL data to/from A-10C • the JF-17 receives data from the E3 and/or other JF-17's but not directly from other L16 aircraft • DCS's BLUFOR/Nato has no ground/sea based EWR/SAM datalink sources. For the FC3 Su-27 • SP: shows everything detected by AWACS, EWR and your AI flight (up to 3 wingmen). • MP: only AWACS and EWR provide a DL Note: I've spent a limited time in the JF-17 and almost none in the Su-27

From reports on Razbam's discord it seems rippling dumb bombs is problematic ATM i.e. it's likely a CCRP bug. Using CCIP instead of Auto/CCRP is said to work without issue i.e. use the uncage button to switch from GAUT to GCIP (tested using Quanty 4, Multi 1, 150ft spacing).

Not sure what you are doing, as both the HSI VAD (TACAN Offset) and the PCN BAD (Waypoint Offset) were working when tested in SP. Cmρ and Cmθ set your desired TACAN Offset i.e. 5.0 NM and 299.0° will create a TACAN offset from Batumi TACAN X16 for lining up on Batumi RWY 13. You'd then use VAD (OFS in the English cockpit) to guide to the offset and TAC to guide to the TACAN beacon. Waypoint offsets are created using the PCN and PREP to add/edit an associated waypoint BAD (offset) which is activated using the PCN "BAD" button. Can you include a short track or video if you are having issues ? Tested using DCS Open Beta Multi-thread 2.8.4.39313 and Caucasus map.

AFAIK the old Normandy 1944 map has been replaced with version "1.5", owners of the old version get improved detailing/textures for the original area, while Normandy 2.0 "upgrade" unlocks the better modelling/textures for London, Paris, additional airfields, etc. Not sure how it looks for DCS standalone installs but for Steam installs - Normandy 1944 is now a 44 GB install with Normandy 2.0 effectively a licence key that "unlocks" the high res textures and new area detail. This is how my install looks after Steam fixed the initial teething issues. Tested Steam DCS Open Beta Multi-thread. Strange AFAIK Normand 1944 should be the same size as Normandy 2.0 for MP/Campaign compatibility, did you switch from Open Beta as "Stable" will still use the old Normandy 1944 "16GB" version until it's updated.

Confirm the same, no idea what has changed but Gravesend has it's runway and taxiways, and London - it's high res textures, railway tracks, etc. Tested using Steam Open Beta Multi-thread 2.8.4.39259

Same here after purchasing the £8.24 Normandy 2.0 Upgrade for Normandy 1944/Channel Map owners. Had a short flight along the Thames from Gravesend using the Gazelle - lots of missing building/church textures and no railway tracks for the trains to run on, etc. Textures for the Houses of Parliament, Tower Bridge and Buckingham Palace appeared when close but lots of minor ones seemed to be missing or different in quality to the video previews of the map. Running Steam file verification ATM but the issue looks widespread for Steam users ? Edit: Steam verified all files as correct. The Normandy install folder has increased in size from ~16 GB to ~43.8 GB after the update.

Once in TPOD DES i.e. after your first designation using the TPOD, you "should" be good but I usually do an extra designation for each additional target point to be sure. Your procedure sounds correct, strange you've started having issues with both JDAM and Maverick TOO. I did find WINC short press detection a little strange with it missing momentary button presses (so I needed to hold WINC down but not so long as to be detected as a long press), however, as I'm new to my Winwing HOTAS, it could easily be a difference in button "action" to my old Saitek throttle.

No, though TOO can be a bit finicky - you need to make sure to Designate each TPOD Target Point (TDC Despress) and start the bomb run with your first Target Point (usually T1), as T0 (the system designation) is usually a copy of it or one of the other Target Points. If the TPOD doesn't slave to the expected Target Point when you designate or step through the Target Points using WINC, you may be starting from the wrong TOO Target Point index (i.e. T0 instead of T1 on the EHSD) or made an error creating the TOO's. Checking that T1, T2, etc. step correctly on the EHSD and the TPOD slaves to the expected targets is one of my last checks before I break away to start my attack run. Attached is a track file of a simple TPOD/TOO JDAM x4 drop on the Caucasus map. See my previous post on using IR Maverick with TPOD. If you'd like further help on either weapon, it'd be helpful to attach a short track file or link a video of what you are doing, otherwise I'm guessing. Tested in DCS Open Beta Multi-thread 2.8.4.38947 AV-8B JDAM TOO Example, 2_8_4_38947.trk

The button was removed as it wasn't correct for our M-2000C version (the lesson hasn't been updated to reflect the change). For info: It used to be on the PCN (Navigation Control Panel) between the PREP and DEST buttons.

Using Razbam's past modules, 2-4 months but the deciding factor will be "when it's ready" Module Pre-order Early Access Pre-order period M-2000C 18 Sept 25 Dec 2015 ~4 months AV-8B N/A 27 Oct 29 Nov 2017 ~2 months MiG-19P None 1 Mar 2019 None

How the seeker is slaved - depends on the mode and what (if anything) is already designated i.e. HSI Waypoint, TOO, TPOD point track, etc. In IRMV mode, TDC depress commands the IR seeker to attempt a "lock", I don't think you were doing anything wrong but were perhaps in the wrong "mode" (can't be sure without a track file or video).

TL;DR: To fire the IRMav - make sure you have used SSS UP to cycle to IRMV mode (Top left of MFD can say TPOD, INS, IRMV, etc.) before slewing, locking or firing the IRMav. Detail: There are some peculiarities when using the TPOD with IRMAV's as the TPOD video is treated as a weapon "feed", hence why selecting the TPOD deselects the IRMAV's, etc. 1. Master Arm ON, A/G Mode, TPOD on RH MFD, HSI or Stores page on LH MFD 2. SSS "double tap" to enter HTS (TPOD) mode if not already in it. 3. Slew TPOD cursor to target and designate (SSS left short changes FOV, SSS aft cycle point track, etc., SSS right short cycles hot/cold polarity) 4. Select/ensure IRMV is boxed on the LH MFD HSI or Stores page 5. Uncaging the IRMAV should give you the IRMAV video feed on the RH MFD but you will still be in TPOD control mode for slewing, etc. 6. Cycle SSS UP short, to enter IRMV mode (Note: you may need to adjust the MFD gain, contrast, etc. ) 7. You can now slew/lock the IRMAV seeker with the TDC 8. After firing your first IRMav, the MFD Stores page is displayed - from here you can either • uncage a second IRMav and slew it's seeker to a nearby target OR • use SSS "double tap" to reopen the TPOD page for damage assessment. Note: Re-selecting the TPOD, deselects the IRMav(s) as a weapon, so they will need selecting on the Stores or HSI page again when you wish to employ one. Tested DCS Multi-thread Open Beta 2.8.4.38947

AFAIK the more powerful Astazou XIV engine provides additional power when operating in hot climates, high altitudes, etc. but is of limited benefit near sea level or in temperate climates where the limiting factor will likely be Max torque. This is a quote comparing civilian 341 and 342 helicopters http://www.aviafora.com/forums/forum/helicopter-fora/gazelles/343-shrieking-gazelles?p=985#post985

1. Looking at your track and the options it uses - Unrestricted GPS isn't set, so this isn't an error when flying a Russian L-39C with NS430 • Russian aircraft do not have access to western GPS satellites (in DCS) unless Unrestricted SATNAV is enabled in DCS\Options\Gameplay or enforced in the Mission Editor. DCS\Options\Gameplay "Unrestricted GPS" enforced in the Mission Editor 2. This is a known issue with the Multi-thread preview build and effects all modules that use the NS430. 3. IIRC it's caused by one of the GFX settings, I don't recall the details, so you might need to experiment a bit. Tested using Single Thread Open Beta 2.8.3.38090

AFAIK the default "snapviews" are saved automatically (per aircraft) provided you have • Options>Misc>User Snap-View Saving enabled. No, each set of snapview settings are saved per aircraft i.e. the default camera positions in the AV-8B are different to the F/A-18C, A-10C, etc., etc. However it's worth making a copy of • Saved Games\DCS\Config\View\SnapViews.lua ... in case you wish to revert back to a previous default (can also be done by deleting or editing the "AV8BNA" section in SnapViews.lua Creating and saving SnapViews for the Harrier is no different to other DCS aircraft (it's a default core feature of DCS), useful key commands are LWin+ Num 1 ... Num 9 = Glance look at SnapView (i.e. when not in SnapView mode) RCtrl+ Num 0 = Toggle SnapViews On/Off Num 1 ... Num 9 = Switch to saved SnapView (in SnapView mode) RAlt+ Num 0 = Save current view to last viewed SnapView So the work flow might be • Adjust the camera position/FoV to the view you wish to save as a "SnapView" • Use "LWin+Num#" to glance at the SnapView you want to adjust/replace. • Use "RAlt+Num 0" to save the current view to the previous "SnapView" • Check the change to "LWin+Num#" has taken. Helpful links are https://www.airgoons.com/w/DCS_Reference/Snap_Views and this youtube video (although I'm sure there are others)