Ramsay

AFAIK Razbam, working with their SME's, hope to include modern/newly introduced weapons such as the AIM-9X and GBU-39 SDB Glide Bombs. ATM they are more of a wish list item than anything else but as the DCS Harrier eventually got APKWS rockets, etc., it is a realistic possibility. Don't expect newer radar, systems, etc. as found on the F-15EX or export variants, just the stores management and GUI changes required to support the newer weapons. What eventually gets implemented in DCS is subject to change and YMMV.

The TPOD should function pretty well by now outside of INS designation/slewing and the TPOD's direction cue on the MPCD i.e. a 12 o'clock "dot" doesn't always mean the TPOD sensor is looking forward. Which mode was the TPOD in (SSS or TPOD HOTAS) as IIRC it's designation/undesignation slave/unslave logic changes depending on mode Do you have a short track or video of the behaviour that's causing problems ? How did the mission/TPOD logic behave when flown during the day - it's what I would do to confirm there's bug rather than pilot error/ loss of SA ?

The 17th Feb pre-order trailer ... https://youtu.be/jIY8eIDUHZU?t=19 Obviously it doesn't mean they'll be available with the initial Early Access release but they are coming at some point. The AGM-130 was shown in the F-15E Pre-order Trailer at 1:16 https://youtu.be/jIY8eIDUHZU?t=76 I agree there's very little chance the AGM-130 will be in the initial EA release.

1. I copied the mission to my "Saved Games\DCS\Missions" folder 2. Opened it in the Mission Editor and selected "Show Hidden Units" on the Unit List

The campaign/mission was created with an earlier version of DCS that allowed the AWACS to spawn at Parking 79, the current version of DCS "forces" it to spawn at Parking 09 which blocks the taxiway for AI aircraft. AFAIK the AWACS only spawns at Parking 79 for ambiance/eye candy and can safely be deleted and/or replaced with a static model without effecting the mission. AWACS at parking 79 replaced with a static model Here the AI flight has passed the static AWACS at parking 79 and C-130 at parking 09 and taken off. After starting up the Mirage the taxiway is clear for player and AI to reach runway and take off. Tested using DCS Open Beta 2.8.2.35759 Mission 08 FINAL - with static AWACS.miz

This Mirage F1 CE E-M diagram was shared on the "DCS Dogfighters" discord https://cdn.discordapp.com/attachments/1044787592794738749/1045083217000145038/Subsonic_Energy_Maneuverability_Diagrams_for_DCS_v202211.pdf

Steam pre-orders can be cancelled up until the actual release/distribution of the DLC - after which it becomes subject to the 2 week/2hr rule.

You are posting in the Gazelle forum, not sure what you mean ??? The base Gazelle Flight Manual is available on the Steam DLC page https://store.steampowered.com/manual/411910 ... but it's quite old (2016) and doesn't include the additional .pdf addendum (found in the DCS folder) that cover the NADIR, SA342L, Mistral and Multicrew - so TBH you are best off looking through Chuck's Guide as it includes using the NADIR, SA342L and Mistral. Polychop are a small team, so aren't very active here but have an active discord channel i.e. if you need further help - I do understand not everyone is happy using discord.

Steam usually updates it's prices/adds products around 18:00 GMT (UK) time, not sure on ED 's store as times have varied.

I'll bump this thread as I came across this DI error while testing. I seems to me that for hot starts on the ground and in the air, the MagVar correction applied to correct the Gyro DI has the wrong sense i.e. it's being subtracted when it should be added and vice versa. I see this when spawning in a 1944 Normandy map (MVar = -11.9°W) The DI should read 110° but instead reads 86° = 98°T - 12° (should be 98 - (-12) = 98 + 12°) https://forum.dcs.world/topic/318891-compass-question/?do=findComment&comment=5147957 ... and on the default 2016 Caucasus map (MVar = +6.6°E) The DI should read ~90° when spawning in but instead reads 103° = 96°T + 7° (should be 96 - (+7) = 96 - 7° = 89°) Tested using DCS Open Beta 2.8.2.35759 using Normandy (21st June 1944) and Caucasus (21st June 2016) maps. Mosquito Spawn DI MagVar and Compass Check, 2016, Caucasus.trk

No, you are not missing anything I am aware of. Using 1944 and similar airfields - I see DCS reporting a heading/track of approx. 110°M (98°T) with a MagVar = -12°W The default air spawn Mosquito's DI read the WRONG bearing, 86° = 98°-12° was neither the Magnetic or True heading. [Perhaps the Mosquito's spawn logic is subtracting a +MagVar rather than using Magnetic = True - MagVar = 98°T - ( -12°) = 98° + 12° = 110°M ?] I therefore adjusted the DI to read 110°M (not sure why the dial compass was reading 138°M in the picture below - likely I was in accelerated flight or climbing/descending prior to taking the screen shot) Tacview reported the approx. True heading/track of 98°T as given by DCS (F10 map's vertical axis = True North). Note • LCtrl + Y will toggle the DCS cockpit info bar • Setting the DI needs to done flying straight and level as last time I checked, the remote compass was subject to magnet dip (while on the ground) due to the Mosquito being a tail dragger and DCS not modelling the remote compass's gimbal (seems common to all DCS tail draggers with RMIs). Tested DCS Open Beta 2.8.2.35759 using Normandy with mission date 21st June 1944

Can't reproduce, devs likely need a short track file to trace your issue, AFAIK the 90 second ? gyro spin up when first selecting the Laser Maverick(s) is intended but shouldn't effect your 2nd shot unless you deselect/change the selected weapon type. IIRC problems with the search pattern are known (it should search in the area of the target designation but the placement of the scanning "X" on the HUD/weapon page seem somewhat random i.e. can be higher or lower in the HUD field of view). Tested in DCS Open Beta 2.8.2.35759, using an AV-8B air spawn and Caucasus map

I much prefer the Strike Eagle over the F-15C, as it's multi-role and has flown both CAP and strike missions IRL. The F-15E will fit well with DCS "Desert Storm", "Allied Force", "Iraqi Freedom" and "Inherent Resolve" themed missions and am excited to fly Razbam's module as I have lots of nostalgia for MicroProse's 1984 version. With DCS multi-crew, I hope to enjoy flying it both as flight lead and pilot/WSO, so will pre-order 2 copies due to the discount - so the F-15E works from a business/sales perspective as well.

IIRC you'll still need to validate/follow the short "fast" alignment procedure, AFAIK you can't just spawn and go (unless spawning in a hot aircraft).

Some of the training missions need to be updated. Training Mission 1, "Start up from cold and dark" is one of them. • PREP 00 cannot be edited (that is why you are stuck) and SOP is to use WPT (BUT) 20 instead, therefore you'll need to select PREP 20 prior to carrying out the alignment as instructed in the training mission. • There's also no longer the need to enter leading zeros when entering a waypoint's altitude i.e. entering 37 is as good as 00037 now. • As the Mirage now spawns with wheel chocks, at the end of the session, you'll want to ask the ground crew to remove the chocks, prior to releasing the handbrake and getting ready to taxi. With these missing pieces of information, I've completed Training Mission 1 without issue.

Good news for cold war players role playing earlier variants/loadouts, it looks like Razbam have reviewed their decision and are considering adding back the legacy LAU-3 19 rocket pod.

TL;DR: This bug seems to effect all modules tested (Hind, Gazelle and F-5E) - there is zero wind in the supplied track. • It seems the NS430 is doing a double km/h --> knots conversion. Detail: Setting the NS430 to display km/h, and flying at 120 km/h in the Gazelle • it displays 65 km/h i.e. 65 would be correct if it was displaying knots, as 120km / 1.852 km/nm = 64.8nm = ~65 Setting the NS430 to display knots, and flying at a Ground Speed of 135 km/h • it displays 39 knots/h because 135 / 1.852 = 72.894 (correct answer in knots) but divides it again 72.894 / 1.852 = 39.360 = ~39 Tested in DCS Open Beta 2.8.1.34667

The FM has it's flaws i.e. the cyclic control expects a spring centering joystick and IIRC the main rotor is missing dissymmetry of lift effects (changes in pitch and roll as it accelerates forward). If you focus on the cockpit "picture" that frames the horizon (rather than cyclic position), you shouldn't have much of issue as, IRL a pilot makes constant small cyclic adjustments while referencing the outside world. It's just that the DCS Gazelle requires the cyclic to be returned to the center position, while IRL it would be held/trimmed to a center offset to maintain equilibrium in a hover, for forward flight, etc. IIRC PC described the current cyclic sensitivity as correct, but we should expect to displace the cyclic from it's center position during flight once their new FM engine is ported to the Gazelle i.e. at some unknown time after the Kiowa release. Yes, especially when on sale. It's still one of my favourite helicopters despite it's flaws i.e. it's RWR gives good feedback on air threats in a MP environment and hence a sense of danger when flying nap of the earth (to avoid detection) even when nothing much is happening . IIRC the SP Campaign is broken (due to changes in DCS's AI behaviours) and the Gazelle Minigun variant has had problems with firing the gun due to recoding the Module(s) in preparation to unifying the different versions i.e. so you might land at a FARP in an Gazelle "L" and switch weapons, remove doors, etc. IIRC the 3 core variants: M, L and Mistral have been otherwise trouble free.

The Harrier's AWLS is modelled as ILS compatible in DCS, however for unexplained reasons - it doesn't work on the Nevada map i.e. where other modules such as the A-10C or Mirage 2000C can pick up a ILS signal. Some DCS airfields in Syria have ILS issues with all modules but AFAIK Akrotiri RWY28 isn't one of them. I can confirm that Akrotiri RWY 28 ILS isn't working in the AV-8B, while it works for the A-10C Testing the AV-8B's AWLS at Incirlik, RWY 05's ILS works, so the problem at Akrotiri looks to be something for Razbam to solve, rather than a map issue. Given that the real AV-8B AWLS is a microwave landing system (same as the Hornet) and isn't compatible with ILS IRL, IMHO you are best ignoring it and sticking to using TACAN for IFR approaches when needed. Tested DCS Open Beta 2.8.1.34667

Already confirmed as an option. AFAIK remodelling the cockpit is not planned as it would require a lot of work for something of limited use in DCS.

As said, unfortunately the track doesn't replay your actions on the F10 map, so we don't see your F10 map labels, etc. I've taken control of your track and recorded myself entering F10 map CAS labels #TP01 and #TP02 and slaving the DMT to the selected targets - the flying isn't pretty but you might spot something of use. AV-8B ATHS CAS F10 Map labels RShift + RAlt + 8 to receive ATHS message (F10 map label coordinates) Move MPCD line cursor to the desired message Select CAS to open the CAS page Select USE to assign the desired Target Point using the UFC i.e. 1 then ENTER Video of me taking control of your track and assigning F10 map ATHS Labels to the AV-8B's CAS Message List using RShift+RAlt+8 Tested using DCS Open Beta 2.8.1.34667

Yes, due to weight limitations. AFAIK IRL you would setup up a temporary FOB with supply chopper(s) and/or ground units.

IMHO, yes. IIRC Razbam plan to refine certain minor aspects of the FM and add/model additional system failures where they make sense in DCS i.e. hydraulic failure due to combat damage, etc. but AFAIK the core M-2000C updates/fixes are now complete.

TACAN ranging uses integration/reply timing to calculate distance. AFAIK it should be available on most TACAN equipped aircraft i.e. fighter to fighter. Generating TACAN "radials" requires a larger/heavier antenna array, AFAIK it is usually only available from ground stations and larger aircraft. AFAIK the missing DCS A/A TACAN ranging in the F1CE is a general bug effecting multiple (all ?) DCS modules and was introduced some time prior to 2.7 ?

Although the ATHS map markers (#TP01, #TP02, etc.) transfer to the CAS Recall page with "RS+RA+8", they won't be listed on the kneeboard until assigned Target Points. Not sure if it's WIP or an intended behaviour but it is know by Razbam. Tested DCS Open Beta 2.8.0.33006