MadDog-IC

OB 2.5.6 has introduces so many issues in general that ares breaking heaps of missions, this is some of them, will only be fixed when the ED team fix the DCS engine, there is no ME work arounds for it. Regards, Ian.

Yes the trees where patched to clear trees around the FARP (They will appear lighter in color to show the zone that has removed them) as it wasn't possible to find a suitable spot to move it to and there is a convoy that needs to get to the FARP as well that might not if the trees are still there, both the FARP and the other zone clearing trees should remove any trees were the are placed but DCS is notorious for it not initializing those commands on mission start at random. You may remove the Clear Trees -> FARP zone by changing the first trigger in the triggers lists, list light colored trees you show look way to large for the clear zones used in the correction. Happens most when mission is run more than once and or is modified with ME and re run, only solution under these conditions to fix it, is to shut down DCS completely and run mission straight away, and it will most likely remove the trees correctly. Regards, Ian.

Yes I know and agree that the M4 Infantry and Humvee-armoured should work with IR and LASER but they currently don't or didn't last time I tried them a few weeks ago. Cheers, Ian.

Problem is: Your using an "Unarmed Unit - Humvee", needs to be an "Amoured Unit" The best ground units to use for JTAC IR and LASER lasing are the "Stryker" and "Humvee-Tow" with more powerful optical capabilities, the "Humvee-Armoured" doesn't support IR / LASER or is bugged. Corrected mission using Type 2 with IR pointer: https://www.dropbox.com/s/7cfynsdmc6vqw73/%2B%20night%20cas_fixed.miz?dl=0 Regards, Ian.

I would be checking if either of you or your clients have IPV6 enabled or a dual stack system with IPV6 and IPV4 together, with IPV6 as your default protocol, this may cause issues, because client maybe trying to use the IPV6 protocol and IP addresses instead of the IPV4 IP addresses. I had nothing but issues with a slightly misconfigured setup in my router when I went from a IPV4 protocol only, that always worked fine, to a Dual stack system of IPV6 and IPV4 with it defaulting to IPV6 by default. I changed a few other things I didn't understand with IPV6 at the time and made it default to IPV4 and it worked fine again. I believe ED have said that servers will not work with IPV6 address and / or will not at least show up in the server lists. Regards, Ian.

My personal experience is having converted, corrected and then used thousands of those missions from DCS v1.2, 1.5, 2.0, 2.5 that I have never had to redo any missions from scratch and I never would anyway, others experiences may vary however. That being said, yes there have been missions that wouldn't work correctly at times no matter the effort put into getting them working, but that was almost always due to multiple bugs introduced in a major software update to the DCS engine that affected all missions under certain circumstances, these varied issues always have to be identified, reported and ultimately corrected by the "Eagle Dymanics coders", the missions then would work as expected. So the answer to your question in my humble opinion is: No you don't have to rebuild the missions from scratch it should work from previous versions of DCS. However some times it does pay to reload the mission in the newest DCS version and resave them, this has fixed issues in the past, but by the same token the newest DCS version may actually have serious flaws that do damage the mission file (Always keep backups of missions) such is the case with DCS v2.5.6, introducing errors from the mission editor, triggers not functioning correctly to name a couple. What you do have do is report any issues, supplying your DCS log, track files for others to evaluate any errors that may give clues to your issues. Regards, Ian.

Wan't quarantined here, was just made a file of 0k size, deleted and repairing DCS just put the same 0k run.exe back. Regards, Ian.

DCS 2.5.6 did break quite a lot (Triggers and other things), But the F-18 is working as programmed, only a 50% chance of it spawning and helping out. I run the mission twice and the F-18 was there both times. Regards, Ian.

Just reviving the old thread, I have completed all of the "A-10c Single mission set" for DCS 2.55x and they are available on the ED User File section now. https://www.digitalcombatsimulator.com/en/files/?set_filter=Y&arrFilter_pf%5Bfiletype%5D=&arrFilter_pf%5Bgameversion%5D=518&arrFilter_pf%5Bfilelang%5D=&arrFilter_pf%5Baircraft%5D=&arrFilter_DATE_CREATE_1_DAYS_TO_BACK=&CREATED_BY=Maddog-IC&sort_by_order=TIMESTAMP_X_DESC&set_filter=Filter Regards, Ian.

Just change the 19:00.00/1 to 19:00.00/0 instead this means that it will run on the current day as specified in the weather window and not a day later. It is a throw back to the old version of DCS, when you had to use this to make AI Units late start and then be activated by a trigger later on in the mission. Any figure bigger than 0 in the last part of the time field (Day offset) will delay by that many days or until a trigger activate command is issued (Not what you want for a player controlled Unit). Regards, Ian.

Best solution, post your mission here so we can have a look at what might be wrong in it. Might be that in the starting waypoint time of the units used, the day is set in the future. ie 19:00.00/1 (The last digit is the day to start 0=straight away, Greater than 0=days in the future to start unit) Regards, Ian.

@All, whilst I would recommend you guys log a support ticket with ED for these issues as it is past my pay grade ;-(. Myself or someone else may be able to assist more if you could post your: - DCS.log file (Previous ones showing serious issues, but unknown why) - DCS Autoupdatelog.txt from: ie (d:\Games\DCS World 2 OpenBeta\) - DXDIAG.txt report (Win + R keys -> type in DXDIAG -> Save all info to file and post) Issues may be related to: - Anti-virus interference with files / directories (Locking and Quarentining), including spyware scanners, bit defender and others. - Windows 10 updates. - Faulty hardware, such as SSD, HDD, Memory. - Corrupted SSD / HDD directory structures. (Run Scandisk on all partitions) - Not running DCS as administrator. Regards, Ian.

Have a look at my post here about the deployment missions here: https://forums.eagle.ru/showthread.php?t=265852 DCS 2.5.6 may have introduced new bugs also. Regards, Ian.

In the mean time here is an unofficial version with quite a lot of the errors corrected (Still work in progress), I have forgotten where I was up to with them, the later missions I think still need work. Feel free to try them out, DCS 2.5.6 maybe causing extra issues, as the were tested under 2.5.5. https://www.digitalcombatsimulator.com/en/files/?set_filter=Y&arrFilter_pf%5Bfiletype%5D=&arrFilter_pf%5Bgameversion%5D=518&arrFilter_pf%5Bfilelang%5D=&arrFilter_pf%5Baircraft%5D=&arrFilter_DATE_CREATE_1_DAYS_TO_BACK=&CREATED_BY=Maddog-IC&sort_by_order=TIMESTAMP_X_DESC&set_filter=Filter Regards, Ian.

Most common reason for this issue: The directory structure gets changed in a patch for were the campaign files reside or the name of the files themselves are changed, this creates the problem because the logbook.lua records the name and directory of the mission you were up to within the campaign and it can no longer find the missions because of the changes. To fix it and regain your status as before, you would need to edit the paths and names for the mission within the logbook.lua file to match then new paths and names of missions in the DCS directory structure. ie: https://forums.eagle.ru/showthread.php?t=261917&highlight=lost+campaign+progress https://forums.eagle.ru/showthread.php?t=148303&highlight=lost+campaign+progress Regards, Ian.

Your issue is more a new bug problem in latest 2.5.6 patch, but FYI. Bare in mind that there are 100 mission in the GOW campaign, 3 variations for each Stage, so there are 3 x mission1, 3 x missions 2 and so on, you are given a random mission out of the three each time you play, so Stage 1 mission 1 may be faulty, but on a replay you may get Stage 1 Mission 2 or 3 which play fine. Either way, the Ka-50 GOW campaign and any missions based on the caucasas map is busted in some way, based on my corrections that I have posted on the USER download site, there are still issues to address that I already know about, but it is such a big task to fix and test 100 missions that I needed to take a break from them. I fixed the glaring problems like mission instantly crashing because FARPS not rendering in game, but not scoring or campaign progressing issues, as they require extensive testing. I will up take more corrections when and if I get re-invigorated once again to devote a month of 8 hour days to the KA-50 GOW campaign. Regards, Ian.

I am not sure what is happening, just thought I would mention this, but I have only had this happen when I was in DCS ME and put my computer into sleep mode, hour later returned to bring the computer out of sleep mode and was greeted with that IP has changed message and DCS closed down. So for normal users of DCS it might be related to very quick drop out and reconnection with the flow of data. Regards, Ian.

You do have the required support vehicles at the farp, fuel truck, APU / Transport vehicle and command vehicle. (You can't repair, refuel or request ATC with out them) Regards, Ian.

Solution to try: https://forums.eagle.ru/showthread.php?t=202214 Regards, Ian.

Antivirus interfering with false positive: https://forums.eagle.ru/showthread.php?t=264465&highlight=World.dll https://forums.eagle.ru/showthread.php?t=264566 or Corrupt directory / file structure: Run Chkdsk on HDD for errors. Regards, Ian.

Here is extract from your DCSlog.txt that shows the start of your issues, as I suspected DCS can't create the temp files: It is showing that DCS can't create the temp files it needs to run the missions correctly. Run windows chkdsk on all of your hdd /ssd drives to check for directory corruption or failing drives. The drives you have show some very small partition sizes, but C: drive seems to have enough empty space to work, so suspect corruption of Directory and files. Depending on you antivirus solution, you should disable it completely or whitelist the DCS directories as not to scan on updating (Known issues with Kaspersky, Windows Bit Defender, Mcafee, MalwareBytes), they will delete files from your download as the get false positives, ruining the DCS install, (Suspect this is happening also). If you have infact done a complete fresh install of DCS and deleted the ../Saved Games/ folders as well and guaranteed a default install with no customizations. Then once steps 1-3 are complete, run "DCS_updater.exe repair" and Clean function, to verify your games files and re-download any missing or corrupt files for you. If using steam you need to verify local cached files. (Virus scanners must be disabled from scanning) and (HDD / SSD must be checked for files structure and free space errors before doing this part 4.) Once you know you HDD / SSD pass their checks and are functioning correctly, DCS is set to all defaults and verified as missing no files, Anti-virus progams are disabled and not interfering, you can then run DCS normally and re-test if this has fixed the issue. If the problem continues, resend the new dcslog.txt to see if things have changed or not, if not I would have "BIGNEWY" try and help or log a ticket with ED support directly. Should get a copy of your Autoupdatelog.txt from the DCS root directory also to see what happened when downloading updates, see if it had issues trying to save some files. Regards,Ian.

Reasons are most likely: Can't run or edit official DLC from Mission Editor as it is encrypted. Own missions you create will have the DictKey issue if: The mission can't be saved completly without creating a lua script error or run from the temporary directory due to permission settings on folder / file or it is set to read only. There is corruptions with the directory structure on SSD / HDD (Run Chkdsk to correct). Hard drive is full, so can't create temp files and or the new mission file. Mission file is in use or opened somewhere else whilst you are trying to save mission to HDD. [*]Installed DCS into default directory c:\Program Files\....., not using run as administrator mode in Win8.1 or Win10, those default directories are more restricted by operating system. May have to run DCS.exe as Administrator mode. (I install in something like c:\Games\DCS\...) [*]System specs of your computer aren't good enough for DCS to run correctly. Will need a look at your DCS.log when tried to save missions for some clues, post DXDIAG.txt log or tell us you systems specs. Regards, Ian.

Looking into the issue: The issue is with the Line of sight (LOS) not highlighting when correctly within parameters and no possible way of being blocked by terrain, trees, etc. In the mission "Midnight train to Georgia" the AFAC is an aircraft at 5000m in the air so there is no obstruction to targets, However the distance that it is from the target (Over 20km) could also be to far. I have an edited version of that mission that I fixed in DCSW v1.2.16 years ago by moving the AFAC aircraft closer to the targets (Within the default <5km range) and it works perfectly fine with JTAC calls and targeting and shows no issues with LOS warnings. Port that mission into DCSW v2.5.x and it instantly shows all red warnings on LOS in the AFAC targeting commands, but fly the mission and the JTAC calls still work correctly and allocate targets to you. The mission your playing and most likely all the A-10c Single missions are going to be broken in some way, I know because I fixed them years ago. Can't commit to a time frame to fix them as they need even more work to correct the DCSW 2.5 map changes with trees in way and multi language additions. About other JTAC missions, some have the unit in position straight away, so you can call them before even leaving the runway, other have the aircraft flying to the Area of Ops, so they will not be transmitting targets until they get there. The JTAC (Ground Units) or AFAC (Aircraft) doesn't use or need reports from other aircraft or AWACS to operate, they are a standalone unit with the ability to find and designate targets themselves or in the ME you can specify what targets you wish designated and by what means, WP, Laser, IR pointer. UPDATE: Fixed versions of all A-10C Single missions available here now: https://www.digitalcombatsimulator.com/en/files/?set_filter=Y&arrFilter_pf%5Bfiletype%5D=&arrFilter_pf%5Bgameversion%5D=518&arrFilter_pf%5Bfilelang%5D=&arrFilter_pf%5Baircraft%5D=&arrFilter_DATE_CREATE_1_DAYS_TO_BACK=&CREATED_BY=Maddog-IC&sort_by_order=TIMESTAMP_X_DESC&set_filter=Filter May have some new issues under DCS 2.56 as they broke a lot of things with that patch. Regards, Ian.

Some time ago when the updater didn't work at all for me, I did notice the autoupdatelog.txt had errors of no connections to torrent clients in it with invalid IP numbers or the like, so I was very suspicious then. Thanks for the detailed report, might give that program ago sometime. Cheers, Ian.

Same very slow torrenting: Downloaded at 50KB-500KB/sec with a 50mbit FTTP link (5.0MB/sec capable). Took 21 hours to get the 17gb patch, but upload approx 3-4 times faster to other torrenters. Net result used 40GB download / uploaded. (Not good on a limited 100GB / month plan that counts uploads and downloads), I only had 43GB remaining before patching DCS Openbeta and 3GB after. Worst update speed ever, torrent give priority to uploading and not downloading:mad:. Regards, Ian.