Ramsay

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.

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