MadDog-IC

NP, have to go to bed soon. Good luck with it. Could try, but I can't recommend it personally. 5. How to use sfc /scannow - it will inspect and repair all of the important Windows files on your computer, including Windows DLL files. a) open Command Prompt as an administrator b) type the following command: sfc /scannow and then press Enter c) system File Checker will now verify the integrity of every protected operating system file on your computer

Seems more system wide issues, dxdiag isn't working correctly, and obviously DCS, other error reports on "Edge browser" updates failing, Edge Browser crashing. You haven't run out of ram or HDD space have you, can't diagnose with non functioning DXDIAG still. Have you tried running: DxDiag /dontskip /t c:\dxdiag.txt from command line. Have a look at my previous message with the second spoiler about the LUA errors, would try to fix those, they are trying to run some sort of code to do with MOD you removed I am guessing, maybe an export files or something.

@KillerDog Had a second look at the dxdiag.txt you sent and that has a section at the top that said it failed several stages of the diagnostics, didn't notice that before, would explain why details weren't right about graphics cards. Try re-running DXdiag and see if it can complete correctly and upload if you want, read the spoiler for details. Follow with a DCS repair and clean also if dxdiag looks ok.

Looking at your DXdiag.txt: Video card drivers for the Nvidia GTX-1050 and Intel HD GPU's don't have any details about the graphics cards (Amount of Ram, driver capabilities), So me personally would look at doing a fresh install of latest drivers for them as this is not normal. The DCS.log file: Some references to missing Lua files, that seem to be related to Lua5.1 programming language, not sure about what problems these may or may not create. Regards, Ian.

Would help to see your DCS.log file from the saved games directory, but I suspect that its an AI bug that has crept in and you will have to wait for it to be resolved with a future patch. What version of DCS 2.7.??.????? OpenBeta or Stable are your running ??? Mine is more of a later testing version (Would have numerous fixes applied) so the issue your having might have been resolved already (Reason it works here) and would most likely be available in the next "DCS OpenBeta" / DCS Stable patch. Remove all Mods if any installed. Temporarily Backup/Rename your DCS.xxxxxxxx folder in SAVED GAMES and recreate a new one to see if it makes any difference to the missions issue. Restore your backed up DCS.xxxxxxx folder if step 3 didn't make any difference, if step 3 fixed the problems you will have to determine which files in the Backup are the problem by slowly restoring sections of directories/files back into the newly created DCS.xxxxxxx folder. Sorry can't be more helpful. Regards, Ian.

Not seeing the issue with this mission on DCS OB 2.7.11.xxxxx, The wingmen follow like good little wingmen, and respond to formation commands, etc. I didn't play the whole mission, just took off an cruised around issuing orders and watching them form up and go Pincer-right, Pincer-Left. You have any more details of the issue ??? Regards, Ian.

The file you have dowloaded is a archive file which has multiple compressed files inside of it, you will need to extract those files and place them in the correct directory structure for the logitech X52 software. You will need to download and install a free program such as WinRar to extract the files from the Logitechx52.rar file. You will need to have the Logitech SST software installed (These files don't go into DCS at all and aren't programmed to change the joystick programming, they use the "Logitech profiler" to load the profiles for use and they inturn simulate you pressing the required keyboard and axis commands and sending them to DCS in real time as you fly. Hence at no time do you edit the profiles in the DCS input configuration, but in the Logitech SST and profiler software. Logitech Profiler needs to be running in the windows task bar which will show all the profiles you download when you have them the correct directory. You will need to then place all of the *.pro files from the extracted RAR file and place them into the "c:\Users\Public\Documents\Logitech\X52" folder, or something close to this. You will also have to remember to switch the profiles when ever you change aircraft to fly when in DCS. You should then be able to select the F-16 profile from the Logitech Profiler software in the windows task bar. Fly DCS as normal. Regards, Ian.

@SUHANG Attach the mission to your post so people can have a look at it, to correct any issue they might see with it. Regards, Ian

I could help, but with your mission and using the Syria map is a no go for my setup. At the moment, I am getting single digit frame rates and unplayable delays with most missions and maps. I haven't played with JTAC for a while, but I usually find that letting the "Reaper / Predator" search for the targets with standard "JTAC -a" or "JTAC - Engage Group" might lead to the JTAC just not seeing certain targets, so I use the specific "JTAC - Asssign Group" commands for all the groups you want targeted. Possible causes. Bad AI just has poor eyeball simulation, as is prevalent in Ka-50 and some other helicopters. Line of sight:- Blocked by trees, excessive distance (LOS not that much of an issue with the airborne drones) Type of weather created due to: Time of day, How darkish or overcast it is with clouds casting shadows. Reaper too far from target (Keep distance to targets within 5km), Reaper flying to high (Try keeping altitude between 2-3km), Most of these limitations are because of LOS and max distance of LASER and IR emitters. Make sure the JTAC advanced commands have all the correct callsigns and frequencies set, they are defaulted to "Axeman 1-1, 133mhz, am", regardless of what the REAPER DRONE UNIT is actually designated. (ie: Pontiac 1-1, 30mhz, FM). Few bugs I have seen that are hard to nail down, LOS issues when ground JTAC when it is right next to enemy targets, ie 100m and still doesn't see it. Regards, Ian. A - Test of JTAC Types 1-2-3 in 2.56-4.miz

I had a quick look: I only checked the Ka-50's on both sides in SP by enabling the other flight members as AI and seeing if they showed up in the ABRIS map with their wingman ID's, so that was fine, obviously if playing MP, other human flight members would have to have their Datalink ID set appropriately and the other selector on Wingman to work correctly, also they would only show up when they spawned in as a client which is not always at mission start. I see no glaring issues with the mission as such and was not in a position to fly DCS to test the F-16 and AWACS. You could try toggling the aircrafts task from "Nothing" to "CAS" or some other appropriate behaviour to prep them for engaging, it didn't need to be done to the Ka-50 to work though. This might be relevant also: F-16 datalink issue. Regards, Ian.

That train strafe mission has an over riding config for FOV, delete the CONFIG folder within the mission file itself (*.miz files are just zip files), this will allow you own system settings for max FOV. Regards, Ian.

If you can't wait for an official fix, I have corrected my editions of this campaign and others in the user files site. Maddog-IC v2.7 updates Regards, Ian.

The issues has existed for a long time with the Nalchik Airbase: Supplied track files of just AI 4 ship flight doing a long ferry flight with extra fuel tanks, when they all RTB you will see the problem. Worse If flight is 4 ship with heavy loading (fuel pods and weapons close to max weight). Worse also with 4 ship flight, if any of the AI RTB on bingo fuel, they will never land successfully, as stated they just circle at end of airfield till they crash from no fuel. Worst when other flight groups are holding and landing at Nalchik AFB. In testing, with a simple Mig29 4 ship flight with just 1, 2 or 3 fuel pods mounted and with max internal fuel, not one AI returns because of bingo fuel, they all stay in formation back to base as per the waypoints, flight lead and his wingman will land in pairs ok, but the other two wingman will do the circle dance and keep going to far right or left of the runway and then doing another circle to correct and doing the same mistake each time, when the 3 wingman crashes because of out of full, the 4th wingman will then land successfully. Cheers, Ian. Mig29 Over the Hump - 1 fuel pod & landing ok.trk Mig29 Over the Hump - 2 fuel pod & bad landing ok.trk

If I was to upload the Mission *.Miz file to the server for download. Will all the Custom Sound files be inside the mission *.MIZ file for everyone that downloads it to play? Will they here all of my files for that mission? I don't understand how DCS Mission Editor is working. Thank You for your Help. I need my mind set right. Lol (That's a Joke) Regards, Ian

As a minimum, disable or delete the CAS -a statement in WP0 as this tells the AI it can choose any target it wants that suites a CAS attack anywhere on the map (it has magic range and vision detection) and will ignore all flights waypoints and fly directly to the target it deems suitable, which is usually everything but the one you want it to attack, when all CAS targets are eliminated it will return to WP0 and then follow the rest of your waypoints and attack commands. Once the CAS -a statement is disabled the 2 ship flight should fly the waypoints and attack the "GTR Group" you have specified at WP1, it is strange how the two A-10 split up like that, I have no answer why, apart from a bug with DCS. Might want to add the advanced options of "Reaction to threat=Evade Fire" in WP0. Might want to add the advanced options of "Restrict Jettison=on" in WP0. With WP1 make sure it is approx 15km or 7-10 miles from target to allow AI to aim in correctly.

SAM's smaller green ring is most likely minimum range they can fire, Also forgot to mention all SAM units and Radars should be in the same one group (8 units in total). SEAD -a in first waypoint will make the flight fly directly to a valid target anywhere on the map ignoring all other waypoints and when it kills the target / targets will return to the first waypoint and then fly all the other in order (Not what you would normally want it to do), so I disable the default so it looks like SEAD -a -x command and only enable it on a waypoint within range of the target with an advance command "Start Enroute Task=SEAD" or "Search and Engage in Zone" or Search and Engage". I usually change the "Reaction to Threat=Allow Abort mission -a" to "Reaction to Threat=Evade Fire -a" so as the flight can't abort its mission when ever it feels like it, being scanned by radar, fired upon and so forth, instead it will do the SEAD objective and evade any enemy missiles. Add the advanced waypoint option "Restrict Jettison=on" and enable it so that flight will not dump ordinance if threatened and has to do evasive maneuvers. The Default "SEAD -a" and "Allow Abort Mission" options are there to get the AI flight to do its job, but abort if it is in danger, its not necessarily the best way to get the AI to do the job, hence the changes in options etc I recommended. Regards, Ian.

You are probably missing: Radar units will have to be active units not static other wise they will not be emitting a radar signature for your SEAD missile to lock onto. You should have 6 missile units (S-75), a P-19 SR Early Warning Radar and a Fan Song radar system. Your SEAD aircraft should be able to deliver its payload so long as you have the correct SEAD missiles for the job, you have a SEAD command in the first waypoint, or in a SEAD advanced command (Engage in zone or the like) at a waypoint that is placed approx at the same range to the target as your missiles max range. Setting up an SA-2 SAM site (research) There's another radar you need that isn't listed under SA-2. It's the P-19 SR "Flat Face" I think. It's used in both the SA-2 and the SA-3, hence it's loss of the SA-3 designation when the SA-2 system was added to DCS. Radar The S-75 typically uses the P-12 early warning radar (also known by its NATO codename, "Spoon Rest"), which has a range of about 275 km (171 mi). The P-12 provides early detection of incoming aircraft, which are then handed off to the acquisition Fan Song radar. These radars, having a range of about 65 km (40 mi), are used to refine the location, altitude, and speed of the hostile aircraft. The Fan Song system consists of two antennas operating on different frequencies, one providing elevation (altitude) information and the other azimuth (bearing) information. Regimental headquarters also include a Spoon Rest, as well as a Flat Face long-range C-band radar and Side Net height-finder. Information from these radars is sent from the regiment down to the battalion Spoon Rest operators to allow them to coordinate their searches. Earlier S-75 versions used a targeting radar known as Knife Rest, which was replaced in Soviet use, but can still be found in older installations. Site layout Each battalion will typically have six, semi-fixed, single-rail launchers for their V-750 missiles positioned approximately 60 to 100 m (200 to 330 ft) apart from each other in a hexagonal "flower" pattern, with radars and guidance systems placed in the center. It was this unique "flower" shape that led to the sites being easily recognizable in reconnaissance photos. Typically another six missiles are stored on tractor-trailers near the center of the site. Hope that helps. Regards, Ian.

No probs, good to see your up and going again. Cheers, Ian.

I would have a guess that an antivirus program (Avast, Windows Defender or other) is locking the file in question and not allowing it to be accessed (ACCESO DENEGADO or Access Denied) in log. Solution: Add an exception for the DCS directory to the list of directories not to be scanned by your antivirus program or disable your virus scanner whilst doing any DCS update. Check the directory "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\_downloads\Mods/aircraft/A-10C_2/bin/Cockpit_A10C_2.dll" to see if the "Cockpit_A10C_2.dll file even exists, if not, your antivirus may have moved it into a quarantine area, if is is there delete it and rerun the DCS_updater. Still not fixed, recheck you update log to see if your getting the same error message as listed below or any new type of error and re-post. In that BIN directory there needs to be 4 DLL files, A10.dll, Cockpit_A10C.dll, Cockpit_A10C_2.dll and Cockpit_A10Common.dll. Your DCS log exert: 00016.094 ERROR: UNPACK_FAIL: (3552)->[FileError: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\_downloads\Mods/aircraft/A-10C_2/bin/Cockpit_A10C_2.dll: (5) Acceso denegado. ] C:\Program Files\Eagle Dynamics\DCS World OpenBeta\_downloads\Mods/aircraft/A-10C_2/bin/Cockpit_A10C_2.dll 00017.242 STATUS: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\_downloads\Mods/aircraft/A-10C_2/bin/Cockpit_A10C_2.dll: (5) Acceso denegado. Regards, Ian.

Thanks, much appreciated, good to see them still working, I apologize about the radio voice, I was feeling sassy that day and I can't even try to do a russian imitation. Coodos to you for your F-15 training missions, I haven't tried them as yet (I don't fly much these days), but others have them in high regards, so well done. Regards, Ian.

Eric963 is on the money, usually coming from the wrong direction, he will yell ABORT ABORT if you are flying directly towards the JTAC and would or could fly over him to the target, you must always approach with ingress and egress directions JTAC gives you in compass headings, this will guarantee you fly perpendicular to the JTAC's position (from his Left or Right at a 90 degress intersection) so you can't accidently drop bombs on the JTAC causing friendly fire. Regards, Ian.

Good to know, I just tested it in OB after update and all worked fine here.

Moving Zone: Most likely you made the moving zone to small, the zone centers on the middle of the carrier with the diameter having to be the real total length of the carrier (1092 Feet), and not just fit over the mission editor picture of the ship. Speed detection: Should be fine so long as ship is doing 50 knots and the trigger to detect speed is also in knots (not KPH or MPH) and less than 50. I can't test this at the moment to test if any faults with triggers have been introduced with patches. Wiki: USS Theodore Roosevelt (CVN-71) is the fourth Nimitz-class, nuclear-powered, aircraft carrier ... Length: Overall: 1,092 feet (332.8 m); Regards, Ian.

I compared my original Campaign mission files to the ones on the ED download site and it looks like I stuffed up when I uploaded the file set, I put the original non Super Carrier missions in the archive instead. I have re-uploaded the correct Campaign mission set now, so re-download the Su-33 campaign and all should be good. Thank you for bringing this to my attention, can't believe that 400 others that downloaded the campaign didn't leave a comment mentioning any problems with the Super carriers (KUZNETSOV) not being present. Kind regards, Ian.

Hi there, glad you are getting some use from my work. Not sure why your having that issue, works here with new KUZNETSOV (2017) model: I know that some mods interfered with the supercarriers module, can't remember what their names or issues were (one issue was either the Supercarriers wouldn't display at all or may only show the older models), you should check the DCS.log for errors or post to me and I can have a look at it. Check that you don't have the little clock icon enabled at the bottom of the Mission editor screen (Only shows Units based on time Period, so as missions are in 2011, the 2017 version of KUZNETSOV may not show). Why supercarrier may be missing Re: Mission Editing In general you can change the ships with little to no issues, you will need to re-snap the flights to their respective take off positions on the deck. You may have to change the ships speed back to 59kph. Can't see any reason that it would break any triggers. Regards, Ian.