MadDog-IC

Found that same reference, but wasn't quite sure where to do the change, so thanks for posting and showing the correct method. Google, for sure best invention of the century ;-) Regards, Ian.

annoying isn't it.

Correct, caused by the map update and addition of collidable trees. Check here for the current status and a post with replacement mission files until it becomes official, as it is going to be quite a while 1-3 months as a questimate until all issues resolved: https://forums.eagle.ru/showthread.php?t=227093 Regards, Ian.

Probably haven't got the correct Microsoft VC++ distro version loaded for it, 2013, 2015 for 1.5 and 2017 for 2.5 I think. https://www.digitalcombatsimulator.com/en/support/faq/556/#1490800 Could also be sound card related as the log ends at about were it tries to init the sound modules. Regards, Ian.

Remove all MODS first (Evident in LOG) (Always a first port of call): Remove MODS folders / files from your "C:\Users\LUAL\Saved Games\DCS.openbeta\Mods/tech/" folder. Run "DCS_updater cleanup" to check for other MODS installed in the original games install path "C:\Program Files\Eagle Dynamics\DCS World OpenBeta" and remove any found. This log exert is an error I haven't seen before, but I would make sure your running DCS with admin privledges. Noticed your running 32gb of ram, but no PAGEFILE, I would recommend you set that to the same amount as your ram (32gb), DCS can be unstable without a pagefile set to 1 to 2 times actual ram size. Lastly run the "DCS_updater.exe repair" function to check the overall integrity of the DCS install itself. Regards, Ian.

I'll state the obvious, but nothing is so simple in DCS, but those symptoms sounds like the CPU or GPU is overheating, then throttling down the speed to stop failure and then after a little time the CPU or GPU cools down and ramps up the speed again, rinse and repeat. Try MSI afterburner or GPU-Z tools to monitor CPU and GPU temps, frequencies and loads whilst game is running under the conditions described. Regards, Ian.

Evidence of MODS in logs (A real mess), your have probably updated DCS with MODS still loaded and it has half stripped out the unauthorized mods leaving a lot of issues, failures on AUTH of .lua files, script errors, missing files and more. As a minimum: You will need to weed out all of the left overs of any MODS or reload them and uninstall properly if you use JGME or other mod manager. Run the "DCS_updater Cleanup" command line to help find and remove error files. Rename your "C:\Users\Jack\Saved Games\DCS.openbeta" folder as a backup and run DCS to recreate a whole new default config install. Run the "DCS_Updater Repair" command line to correct DCS corrupted files that have failed their hash checks. Recreate you configs or by slowly moving back configs and logbooks from you backup. P.S. Tested the "Beach Landing II.miz", loads into ME and runs fine on my DCS Openbeta with out fault. Regards, Ian.

Nice work on that mission, excellent score. Here is a early access christmas present of all of the "Ka-50 GOW campaign" missions, I have just finishing up moving the last of the ground units for all of the missions, there will be future tweaks as there is a lot more to do. https://www.dropbox.com/s/pxv3l8h7rrnd0w4/DCSW%20-%20KA-50%20Campaign%20-%20Georgian%20Oil%20War%20%28Patch%20to%20Game%29%20%28v2.5x%29.zip?dl=0 So to you and indeed every one have a merry christmas and stay safe. Regards, Ian.

No worries, geesh those nvidia drivers are causing some big head aches lately, me included, I am too scared to update them any more as they completely trash my window install. Cheers, Ian.

Currently repairing and refreshing the whole Ka-50 GOW campaign, so I will keep a look out for that issue and if I can reproduce look at getting it fixed. Big issue with all those missions are that a great deal of the FARPS are corrupt with out names and radio frequencies, so the game will not render them, this will create problems and most likely crashes. Attached is a rough draft (not fully completed but with all FARPS fixed) of a corrected version of that mission, try flying it as a single mission and see if you get the same issue. Regards, Ian. ATO-C-P3.4.miz

Were do I start, this is not a full time job, but others seem to keep trying to make it that way for me (All volunteered time). I prefer to keep the work flow of repairs happening than reporting on what is updated or not, I spend thousands of hours on these corrections, then more time responding to reported faults in forums, then reporting faults myself to ED and more time checking that the updates have been applied to DCS. Taking into account the jumps from DCS 1.2 to 1.5 and 2.5, I have updated all of the FC3 campaigns at least 2 times and multiple single missions also for all modules, (The campaign update ED never used was the Su-33 Heavy Sky one, this was removed from the module altogether due to not being supported any more, so I spend about a month on it, supplied it and then ED rewrote there own and put it back in as version 2) this is were I notice that FC3 aircraft and the standalone equivalent modules in fact had different content, so I reported that and had some corrected in the Su-27 and F-15 stuff. When I have updated missions, that may need further work by ED for multi language translations, something I can not do myself. This can and does create extra delays to having the update released into DCS for the public, this could be in the order of several days, weeks or months, depending on ED's workload and priorities at the time, sometimes they choose to not use my corrections at all and have developed there own corrected versions of campaigns / missions. So this is why I no longer continually check to see if the updates have been included into the DCS releases and upload the same files to both ED themselves and to the ED user file download section so users have quicker access to working enhanced campaigns, which can also gives me valuable feed back from users if there may be any extra issues. So I will continue to do updates in the same way I already have, not wasting valuable time on double checking if ED have done their part or not, the process is no different for me than any user to figure out if the missions have been updated or not, as by file size and dating comparisons or reported in DCS updates change logs. Regards, Ian.

Yes there are a broken mission and campaigns, some have been fixed and some haven't, it is a matter of man hours and who is going to do it. Speaking for myself I have previously repaired a lot of the older modules missions and campaigns to a working state and continue to actively repair what I can, based on my own preferences and slated work loads in response to reported issues in all DCS english forums and other testing reports. Current active works are: The KA-50 GOW campaign, including all 100 missions to v2.5 standard. The Su-25T single player missions to v2.5 standard. Note: With DCS, very few of the corrections are ever reported in the DCS updates changelogs, so they just usually sneak in under the radar without fan fair. Regards, Ian.

Three previous discussions for getting servers going: https://forums.eagle.ru/showpost.php?p=2200921&postcount=24 https://forums.eagle.ru/showthread.php?t=166405&highlight=server https://forums.eagle.ru/showthread.php?t=127230 Regards, Ian.

Yes this still seems to be a problems with current DCS, I have been re doing all missions again for the new 2.5 caucausas map layout and even AI can't hit targets because guided bombs swerve off target at last moment before impact, seems lock doesn't target the centre mass of bunker, but to the side of it instead. At some stage I will report when I know more about what is happening. Regards, Ian.

Not much to go on, Would need DXdiag report to see what system specs you have. Most likely, system doesn't meet minimum requirements or corrupt drivers of some sort, no init of graphics or sound card shown, so that seems an immediate issue. Try generic DCS repair. Regards, Ian.

Clicking the VISIBLE option will make it so the predator always has line of sight so it can lase and have it orbit directly over top of targets so it never goes out of the max range of the laser. If the Visible option isn't ticked then the predator has to be able to detect the target first and AI can be quite useless at detection at times, especially on lower skill levels, I always use EXCELLENT. I am sure there would be a shared mission doing this already on the forum or ED user download site. https://www.digitalcombatsimulator.com/en/files/3302565/ Cheers, Ian.

Your welcome. You may be able to still run DCS with lower than recommended specs but I can only go on ED recommendations and am not questioning them. Others with lower end graphics cards to yours also had same problem with the later patches making DCS not run on their machines that did so previously. Would try the rebuild of the "Saved Games" mentioned in other post first, exact path for your machine is shown. Clean wipe of only DCS no need to deactivate, if your wiping your operating system (Windows) deactivation needed, changing any hardware, GPU, CPU, M/B Bios, HDD / SSD, RAM best to deactivate all to be on the safe side. When removing DCS you will have to delete the main programs install path and the saved games settings folder other wise the old settings could still ruin the new install. Regards, Ian.

You will have to add a "switch waypoint command -> Orbit waypoint" directly after you escort command at the original start waypoint. You will have to do the same for any other escort commands. Regards, Ian.

Firstly: From you DCS.log in the spoiler below, the graphics card shown doesn't meet minimum specifications to run DCS, and has too little onboard VRAM most likely. DCS Minimum system requirements (LOW graphics settings): OS 64-bit Windows 7/8/10; DirectX11; CPU: Intel Core i3 at 2.8 GHz or AMD FX; RAM: 8 GB (16 GB for heavy missions); Free hard disk space: 60 GB; Discrete video card NVIDIA GeForce GTX 760 / AMD R9 280X or better. Secondly: These errors in the spoilter below indicate a user mod (upuaut's - Addon Tents, Watchtower, UH-1-Cargo) is still loaded as entry.lua config files are still trying to load some tent textures that don't exist in the mod, whilst I have installed those same mods and get the same error messages, mod appears to function ok, but I would uninstall all those mods from the tech folder temporarly whilst trying to diagnose all the other issues. Thirdly: This extract points to more issues, your normal DCS openbeta saved user data from "c:/users/2die4/saved games/dcs.openbeta/" but your trying to load textures from "c:/users/2die4/saved games/dcs/textures/", I assume that is another install of say DCS Stable, but the folder or files don't exist any way. Forthly: Left the worst for last - exert from dcs.log file in spoiler below, this is your main issue now and the hardest to diagnose. It is apparent now that a "DCS_updater.exe cleanup" will never fix your issues as any modified and incompatible files that reside in your "SAVED GAMES" folder are most likely the culprit and are never touched by that command, it is up to the user to figure out and remove or replace said problem files when and if they become incompatible with DCS new code. I would backup and rename your complete "c:/users/2die4/saved games/dcs.openbeta" folder and let DCS recreate a new one, thus ruling out any stray code. See if it corrects your immediate issues and show me a new DCS.log, if so then rebuilt your controls and logbook, etc from the backup file a bit at a time, leaving any MOD stuff till last. If none of the above fixes any thing, a total wipe and reload is recommended. Regards, Ian.

There was a MOD that modified the statics.lua, I think it was so the AV-8na or viggen could take off from the ground that become incompatible with latest DCS revisions and caused the same error that is showing in your log. Either way, if you haven't any MODS, I would backup / rename your "C:\Users\Wolf\Saved Games\DCS.openbeta" folder and let DCS recreate it, See if it corrects your immediate issue, if so then rebuilt your controls and logbook, etc from the backup a bit at a time. Also do a DCS_update.exe cleanup command to check for installed and or remove MODS. P.S. @OH-ZEE - post a current log with the mods removed. Regards, Ian.

Sorry got a bit confused with that first post, I am so used to doing testing with AI, just flown it myself as human pilot, you need to use the radio to call the fellows over to embark using ALT+\ or one of the other 3 radio set key command then F7-F1-F1 keys, they will load into your craft, but can't get others into AI wingmen choppers. Cheers, Ian.

In the process of doing it. Cheers, Ian.

I have considered it broken for quite a while, but some here have reported they have it working. After a little testing of the embark and disembark commands, the "Binding to Transport" option seems to be the broken part: Using only one chopper in the flight and one set of troops: If you set it up correctly with: Troops #001 embark command -> "Vehicle Group=Uh-1h" and "Binding to Transport=Pilot #001" pointing to the correct units, which you have then the chopper will land, but not pick up any troops and sit there indefinitely, the troops will also just stay where they are. If you set it up incorrectly with: Troops #001 embark command -> "Vehicle Group=Uh-1h" and "Binding to Transport=" , then the chopper will land, pick up any troops and take off, the troops will embark the chopper and disembark at other waypoint when set to. Using 2-4 choppers in flight and multiple troops dispersed to embark each chopper in the flight: If you set it up correctly with: Troops #001 embark command -> "Vehicle Group=Uh-1h" and "Binding to Transport=Pilot #001", Troops #002 embark command -> "Vehicle Group=Uh-1h" and "Binding to Transport=Pilot #002", Troops #003 embark command -> "Vehicle Group=Uh-1h" and "Binding to Transport=Pilot #003" pointing to the correct units, then the chopper will land, but not pick up any troops and sit there indefinitely, the troops will also just stay where they are. The above work around for single flight of chopper (#2) will not work, as lead will load up but non of his wingmen can, so they remain grounded indefinitely. Regards, Ian. Test - UH-1H embark and disembark (No Binding to Transport).trk Test - UH-1H embark and disembark (Not working).trk

Sounds like you may be running different versions and or revisions of DCS, they can have incompatible networking code, ie stable can talk to stable, and openbeta can talk to openbeta, but not necessarily stable to openbeta. One of you may be running the "Stable" version and the other "Openbeta", also make sure you are also running the save revision number, just update to latest to be sure. Regards, Ian.