Ramsay

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)

Note that by default, any Steam desktop shortcut (inc. to bin-mt) launches the Single Thread version. To launch the Multi-thread DCS Preview version without using the Steam GUI - you should change your desktop shortcut to • steam://launch/223750/option1 https://forum.dcs.world/topic/321330-desktop-shortcut-for-mt-version-of-dcs/#comment-5178783

All I did with an old 1.5.7 mission was cycle the loadout to empty and back to rockets and resave. It's apparent in the mission editor when the mission/loadout is fixed as the missing pylon reappears.

How old is the mission, the Rockets and Pod were updated a while ago i.e. to add different types, the missing support arm is a symptom of the loadout not being updated.

Yes (it was the axis mapping that was removed), you'll find it under HOTAS as • "Radar Antenna DOWN" and • "Radar Antenna UP"

GBU-39 is on a "wish list" and may be added with the planned CTU II (2015) update that adds the HMCS, AIM-9X, etc. sometime after early access AFAIK Razbam hope to accurately model Suite 4+ avionics and weapons fairly tightly. Beyond this they wish to include legacy weapons i.e. for 1990 Desert Storm scenarios, and newer weapons/systems that are out of scope of Suite 4. How well this is done depends on the information available from SMEs, etc. for obvious reasons. Adding the GBU-38 to the base game will require cooperation with ED and it's inclusion is subject to change, etc. https://forum.dcs.world/topic/99350-weaponry/?do=findComment&comment=5136643

Having JDAMs in a side by side configuration on stations 2 and 6 is supported in DCS using loadouts with the *-* option, however as in the RL photo, you then can't carry A2A missiles on outer stations 1 and 7. The slanted configuration is chosen when carrying a A2A missile AND 2x JDAM on an adjacent station.

Main changes (from my perspective) are • 19x rocket pods and AIM-9L legacy loadouts are allowed/back as they were used on the AV-8A, etc. and allow players to simulate older mission profiles. • GBU-12 and GBU-38/GBU-54 JDAM have been give ~2015 USMC loadout restrictions ... you can still take 10x GBU-38 but NOT if you ALSO want A2A missiles - in that case, you are limited to carrying 8x GBU-38.

Just received my Orion 2 Throttle and SimApp Pro 1.8.23 seems to work correctly i.e. axis/button tester, calibration and firmware update. The Orion F-16EX joystick Grip and base are working in the SimApp Pro tester (and DCS) but when checking if there's a firmware update - it can't "dial" home (latest version says "retrieving") - other than that, every thing seems to work.

Couldn't reproduce in OB dcs-mt, can you share a short track ? Tested single player, Caucasus map, OB 2.8.3.37556

I see the same testing in Single Player - this Razbam hot fix ... ... fixed the HSI/TACAN/Mag-True indications. Tested with dcs-mt 2.8.3. 37556 at Kutaisi using Kobuleti (X67) and Batumi (X16) TACANs

Nope, you just can't mount a ITER GBU-54 next to the missile (or next to the engine exhaust), there are */* and *\* options for a reason, and that allows you to carry 8x GBU-54 and 2x AIM-9M.

Yes, IIRC it reflects a configuration used at Fort Rucker for training inc. autorotations, etc. (it's also faster/lighter without the MMS).

No, work continues. • Adding the new FN HMP400 Gun Pod(s) requires co-ordination with ED to add the new weapon to the base game. • Last WIP update on their discord was 21st Feb 2023 https://forum.dcs.world/topic/173680-polychop-simulations-discord-comms-for-puplic/

The mission was made before DCS's weather and GFX were updated - unfortunately the new changes don't render fog correctly, hence the "whiteout" conditions that make the visual landing much harder than originally intended. For the ILS localizer to appear in the HUD, you need to be tuned into/receiving Batumi's ILS signal and have WPT 2 selected as that is configured as the "landing" waypoint i.e. is programmed with the Glide Slope's angle and Localizer's True direction. https://forum.dcs.world/topic/292390-ils-landing-and-atc/?do=findComment&comment=4885190

No, this isn't the first time the Huey's lack of performance has been noticed - there's a long thread from Jan 2018* discussing the problem ... ... and promises from ED it would be looked into. However ED's priorities shifted and nothing came of it. * In 2013 when I bought the Huey I noticed issues when trying to use the RL power available hover charts (similar to calculating rotation speeds for fixed wing) but initially put them down to lack of understanding on my part. Lack of power/engine overheating only became a significant issue in 2018 when EGT engine damage was implemented, by then I had a better grasp of the charts and how to read them, so was one of many who reported the mismatch between DCS and RL performance (note some threads/posts have been deleted/lost perhaps due to rule 1.16).