Ramsay

Normandy 2.0 is "keyless", so doesn't have a CD key. What does the Steam DLC manager show is installed ? This is how it looks for me Normandy 2 is listed in the Mission Editor as "Normandy" and maintains compatibility for owners who haven't upgraded (they miss out on high detail London/Paris textures, etc.). Were you expecting to see "Normandy 2.0" listed separately or can you not access Normandy at all ? The original "Normandy 1944" (AKA 1.5) area, now has the same detailing and textures as Normandy 2.0 You will only notice the difference after upgrading to 2.0 when flying/spawning outside the original boundaries i.e. Gravesend after upgrading to 2.0. is more detailed. This is a good "before" and "after" post demonstrating a successful Normandy 2.0 Licence "Upgrade"

This is from discord but note PC are endeavoring to get reference images/diagrams of the real and what we have *may* change (the current sight is based off the UK version). I haven't tested the reticles myself.

We really need a short track or video of what you are doing - have you checked out Chuck's AV-8B Guide to see if you've missed anything obvious ? https://chucksguides.com/aircraft/dcs/av-8b/ You are likely doing something wrong as lasing and dropping GBU-12's was trouble free. Tested using GBU-12's in DCS Open Beta Multi-thread 2.8.5.40170

No, there are L, M and Mini-gun variants. The old L and Mistral variants are now combined in the new "L" version and are now determined by their "loadout" The new "L" can also carry HOT missiles or FN HMP400 .50 cal gun pods. The "M" is the only version with a night vision camera and laser range finder, so still has an important role in night missions, etc.

My understanding is that shared buttons/keys between pilot and co-pilot are improved but the copilot needs to press buttons (i.e. for NADIR data entry) at a slower/steady pace than normal (i.e. press/hold/release) to avoid multicrew network desync on keydown/keyup "events". How much control Polychop have over sync issues and how much is on ED/DCS is unknown, so we'll need to wait for the update before forming an opinion. IMHO, your loss - I find the Gazelle's positives outway it's negatives most of the time but you're always entitled to your opinion, however as PC have clearly put a lot of work into this "FREE" update - it seems poor manners to throw shade on the update before even trying it. YMMV.

The trouble is the old flight model has been broken for a while, just because people adjusted to it's faults (the engine has been under performing since DCS 1.5.6) , didn't make it "right". IMHO once ED have fine tuned engine, transmission and torque output to realistic figures and the DCS Huey can pass a realistic "hover check" at different altitudes and weights, they will have a much stronger foundation to tune the flight model (if that is their plan).

It's a complete module, however as it's been heavily reworked to meet AdA requirements, some of the training and campaign missions still need to be updated. IMHO although it's not the most competitive for PvP, it's one of the best DCS modules available.

However it doesn't match the diagrams, etc. found in the 2002 Tac Manual Vol 1. AFAIK Razbam are consulting with SME's to confirm the correct ASL behaviour.

The ASL likely displaces from the designation diamond by a fixed amount when it's correcting for wind. That's not what we see in DCS where the distance between ASL and target diamond changes with the FPM/aircraft heading.

It can be flown as a single person from the front. AFAIK you only "need" to enter the WSO's seat to turn on the TGP, laser, counter measure program and similar. Initially the EA module won't support multi-crew 100% (still WIP) or have an AI WSO, though it's planned to add one later in development.

That was my understanding as well but I'm no SME when it comes to OFP H6.2

Negative, Auto doesn't work ATM i.e. as it only triggers the first release pulse (sometimes 2) and only one (or 2) bomb drops out of a stick of 6, etc. So • AUTO QTY 6, MULTI 6, INT 15 (x10) will drop all 6 bombs at once while • AUTO QTY 6, MULTI 1, INT 15 (x10) only drops the first (and sometimes second ?) bomb of a stick of 6 AFAIK Razbam are aware of the bug via discord but are focused on the Strike Eagle ATM. Interval spacing does work but requires a "fudge" factor i.e. I use INT 15 x10 for 130' (40m) target spacing As CCIP ripples are working, they can be used to confirm if the release settings, spacing, etc, are correct but only when the Reflected Cue isn't in the HUD. Tested using Mk-82, Mk-82 Snakeye and Mk-20 Rockeyes, DCS Open Beta Multi-thread 2.8.5.40170

I believe how the fall line is drawn in the HUD is a separate issue (design choice? ) to the auto release pulse failing to increment i.e. auto used to work.

If you are using CCRP, the release parameters are very tight (IIRC +/-5 mil ) and the flight path marker needs to be on (or very close to) the azimuth steering line when the release cue reaches the FPM (otherwise the bomb(s) won't drop). Release angle 45° gives you the cues for a "optional" 45° loft and instead of a single release cue, we now get a release "staple" and 2 cues that look a lot like the "in range" cue for dropping GPS guided JDAMs, etc. but that work differently (it's changed from the LGB and dumb bomb HUD illustrations in the official manual and Chuck's Guide). • prior to line reaching FPM and top of staple - depress and hold weapon consent/release • top of staple - FPM flashes --> time to start climbing (mil power, smooth 4G pullup) @ 45°, keeping the FPM on the azimuth steering line (AFAIK actioning the climb is optional and the system will release the bomb(s) regardless - provided pickle button is held and FPM is kept on the ASL) • once the system calculates the release will hit the target - bomb(s) auto release, FPM flashes a second time (this may or may not be near the bottom of the staple - which is the release cue for level fight) Wags Loft Video also applies to CCRP LGBs, etc. weapons releases. IIRC the release parameters for dropping LGBs, etc. used to be more permissive but ED received info that SOP was to use tighter release constraints (perhaps to avoid collateral damage, etc.). In the DCS A-10C, we have the option to change release constraints i.e. to the 3-9 line - unfortunately we don't get that (menu?) in the F-16C.

CCIP ripple is working but for now, you must avoid the CCIP -> Auto conversion i.e. dropping while HUD has the CCIP Reflected Cue (horizontal line) symbology. Tested using Open Beta Multi-thread 2.8.5.40170 Mk-82SE, QTY 6, MULTI 1, INT 15 (x10) You can enter 100' using the ODU and the mechanical counter will display 10 (x10). Only one bomb dropping out of a stick of 6, is typical of the current Auto/CCRP bug when using CCIP while the CCIP Reflected Cue is displayed.

There's an issue with CCRP/Auto ATM, are you sure the CCIP mode isn't converting to Auto during your attack i.e. when the "real" CCIP impact point is below the nose of the aircraft at time of bomb release ? Can you share a short track or video ?

The 3D cockpit NS430 is working - only the 2D popup (LShift+LAlt+B) doesn't work/appear in VR. Tested using Steam Open Beta Multi-thread 2.8.4.39731 with the Gazelle and Mi-8, Syria with Oculus Rift S

That looks like SIT-ALAT, the GPS based French equivalent of NATO's Blue Force Tracker.

Correct, AFAIK it's planned to model the L with APX 334 Athos gyrostabilized binoculars (2x levels of magnification and no laser range finder) i.e. the L cockpit will lose the Viviane "TV". The "binocular" view may be "similar" to this Ferranti ? sight from Episode 6 of "Flying Soldiers" (a 1997 UK documentary). https://youtu.be/X-ap3xTgJjk?t=923 AFAIK work on the L's Athos sight is still at an early stage and subject to change.

The RMI doesn't work correctly on the ground i.e. as part of a taxi/pre-flight check, however once airborne and in level/unaccelerated flight - they can be used/adjusted to match the magnetic compass. Setting the remote magnetic compass while on the ground does not work reliably i.e. setting a compass heading and then taxiing to face 4 known compass directions or a known runway direction can have upto +/-20° of error. AFAIK IRL the magnetic, RMI and gyro compass are adjusted/checked i.e. during the taxi, etc. to match each other prior to take off. I suspect the RMI compass gimbal isn't modelled as it reads correctly in level flight but if that's so, it seems to be a low priority for ED (effects most/all tail draggers with a RMI).

Thanks for providing a track file (it helps greatly with questions like these). You are spawning in with an unarmed Harrier, as you have no weapons, DCS removes the JTAC option from the F10 menu. If you were to equip the Harrier with weapons you would be able to call the JTAC and find if they have suitable targets. The other aircraft you tested have their cannon at the least, so still get the JTAC as a radio contact i.e. in the case of the Hornet it has 600 rounds of ammunition.

TL;DR: Working fine for me, at a guess - you're pressing the VAL button which lights at the end of the alignment process, rather than simply selecting NAV mode. I suspect the button lighting has been improved/become more noticeable. Detail: ACLM/STH Example • Select ACLM/STH - (orange ALN lamp flashing, VAL button lit) • Check Co-ordinates, etc. Match kneeboard (optional) • Click on VAL button to confirm starting alignment (orange ALN lamp steady, VAL button unlit) • Switch mode to STS (status) - watch status count down from 100 --> 0 • At Status=0: ALN lamp goes out, green PRE lamp flashes, VAL button lights. Important: DO NOT PRESS THE VAL BUTTON - THIS RESETS THE ALIGNMENT AND STARTS IT AGAIN • Move the Selector to NAV (PRE lamp goes out, ADI flag clears) • Switch mode to N (normal) - co-ordinates, etc. display as normal If you still have alignment issues - please share a track or video of your startup. Video of ACLM/STH procedure Tested DCS Open Beta Multi-thread Preview 2.8.4.39731

AFAIK - yes. The APG-70 auto-acquisition modes were demonstrated in this WIP video

ALCM/STH should work for most missions - unless the mission is set to look for a particular switch, mission trigger, etc. or it's been disallowed in the Mission Editor. The only way to be sure would be to try it. Note that ALCM/STH alignment has a higher INS drift rate and therefore A2G can be less accurate, however there is an option to disable Gyro Drift in • Options>Special>M-2000C>Simulation: Disable Gyro Drift ... if the mission doesn't enforce it.

The latest version(s) of Chuck's AV-8B Guide has the updated ATHS Target Point F10 map format So it looks like you'll want to update your current copy to the latest version (6th Feb 2023). https://chucksguides.com/aircraft/dcs/av-8b/ Note that when imported, • initially the target points will only appear on the CAS message list • Target Points are only listed on the kneeboard AFTER the received "message" has been given a Target Point i.e. message list -> message detail -> use -> ODU T1, T2, etc.