REL

Hello, everyone About a month ago I posted this bug report about CCIP Errors in this forum section: A few days ago I came across this Note in the "DCS F-16C Early Access Guide EN" PDF file which made me think of a possible cause of my experience of CCIP Errors (Page 157 - "NAV STATUS DED Page") When I Checked My custom mission neither of the two conditions of a good GPS availability was mat (“USA is one of the countries assigned to the player’s coalition" Or "Unrestricted SATNAV is enabled"): When one of them is true the Viper CCIP is accurate once again - which marks the solution! Another clue is the difference between the info in the "NAV STATUS DED Page" of the two the missions settings versions Degraded GPS precision mission settings - Note the floating TD (Target Designator) Box above the actual target = red smoke base line: Good GPS precision mission settings: I hope my discovery helps anyone who stumbles with this CCIP problem & (@BIGNEWY) prevent ED team wasting their precious time investing this issue!

Hello, everyone I ran some test on CCIP (too many unexpected misses) and wanted to share the following: Basically I used 40c weather with no wind or turbulence and two 30m marked radius with a live tank in the middle as targets for FA-18C & F-16CM while I use CCIP bombing in both platforms. The Hornet CCIP is accurate enough to shack the target & hit inside of the 30m radius (marked with green smoke) While the Viper hits always fall short and well outside 30m target radius (marked with red smoke). * Looks like the F-16 CCIP inaccuracy grows with the mission temperature value (20C hits closer then 40C ). Mission file: #REL - Dead Sherman Range - Nevada.miz .trk files: CCIP Test 2.trkCCIP Test3.trk Videos links: 1. first run 2. second run 3. Third run 4. BDA run Mission details: null null null I hope that's enough data to help ED team to investigate & fix the issue.

Hi Anyone know what this red V mark on the fuel gauge used for?

Hi you can hotfix that yourself by backup & editing "default.lua" file in to DCS World\Mods\aircraft\F-16C\Input\F-16C\keyboard. The change you're looking for is in 101-102 lines: "ANT ELEV Knob - CW" section from 1.0 to 0.1 & "ANT ELEV Knob - CCW" section from -1.0 to -0.1. No effect on multi-player "Integrity Check" as far as I know. Good luck

Hi I see that the F-16 module "FAILURES" Tab in the ME is empty and not containing possible failures unlike other aircrafts, is there any plan to add this feature?

Hey I remember 01 & 02 parking as a hardened aircraft shelter ... Is it a bug?

Yes!

Hey Comrade Doge I would like to know what this "theway Setup 2.0.0.exe" installation file actually do to the original DCS files & How do you fully uninstall it? I want to try it out but need to know what am I getting in to first. Thank you for investing your time & effort to make DCS enjoyable for the community!

thank you for your 2 cents Exorcet but it's a sisyphean work in cases of multiple flights generated by an external auto mission generator. I'm very curious about what ED team point of view on this possible bug though.

Hi Simply use the main menu to set your "External FOV" null or In-cockpit main menu (ESC key when you sit in your cockpit) to set your In-Cockpit FOV for each plane individually.

Hey ED Recently I discovered that destroyed airplanes (some are very tough and hard to destroy) marked with "UNCONTROLLED" checkbox in the mission editor do not register a "Kill" status (Causing a major bummer when flying a OCA/Aircraft sortie). DCS User Manual EN 2020 page 194: UNCONTROLLED. When setting an AI group to a “Takeoff from Ramp” (cold start) waypoint, the Uncontrolled check box can be used to have the AI group appear at their starting location on the ramp, but not begin the spool up sequence until initiated by an AI TASK trigger as set by the START Command in the Triggered Actions of the group. In this case, the group aircraft will appear in the mission in parked configuration and remain as such until triggered to “come alive”. I made a YouTube vid for your convenience HERE. Also see attached files. Please let me know if I can provide more information. DM.BUG.TEST.miz dcs.log

Yes RED .. CCIP with AGR the bomb impact short (see 38-4 pic) CCIP 22,01,05 21;32;10.trk

Hey ED 1. Change the temperature in "Time and whether" tab @ Mission Editor to 38c (see 38-0 pic) 2. Select MK82 in CCIP mode 3. Active Pause when the CCIP Pipper at the bottom of the smoke & pickle 4. The bomb impact short (see 38-2 pic) 5. Repeat the steps with 20c result in reasonable impact (see 20-2 pic) *. Might be a general issue because I tested other modules (F-16C) and on several maps (Nevada & Caucuses) with the same result (reasonable impact @ 20c | short impact @ 38c) More pics & .trk files attached Please let me know if I'm doing something wrong CCIP 22,01,05 15;28;20.trk

AGM-84E SLAM: What do you think?