MadDog-IC

1) Picture you show is the campaign editor, you can't run a campaign from there. 2) The main menu of Lockon or FC2 should have something like a "Fly mission" or "Fly campaign" menu choice on it to run your missions. 3) If after selecting "Fly Mission" or "Fly Campaign" menus show and you select a mission file and you don't have a button to start the mission, go to the "Graphic / Screen Options Menu" and change the screen resolution to 1024 x 768 or there abouts.

Correct only available up to DCS v2.5.3. Read Here: https://www.digitalcombatsimulator.com/en/support/faq/685/ A good replacement for it is the free A4E: https://github.com/heclak/community-a4e-c Regards, Ian.

This may explain your issue with FOV, it is a server side issue, the Server Admin or mission creator will have to delete the CONFIG/Views folder from within the mission file. Your FOV is over-ridden by the Servers mission config Regards, Ian.

Whilst it is to late now, when saving missions, the safer way is to save regularly and to have multiple versions of saves of the same mission, I save every time to a new indexed named mission file when I have done some substantial changes so that if any thing goes wrong I only loss the last changes and not the whole mission. I assume when you saved often that you just over wrote the same mission file, if so this is frought with danger as you have found out. As to why this happens I can't say definatively, but if the mission editor has a rare issue on saving to disk it will usually create a LUA script error in the DCS.log file and will write a 0 or partial size length corrupt mission file to disk because the script that writes the complete code to the mission files has crashed at some point and didn't complete its job. DCS also has an auto backup feature now, it should backup the mission every 5 mins if enabled so you should see how that works and see if that actually made a backup of your mission. I haven't used it myself yet as I don't do to much mission editing these days. DCS Mission Editor Auto Backup Feature If you haven't run DCS since the issue, you may be able to recover a temp image of the mission file that dcs makes when you run the mission. ie TEMP=C:\Users\YourUSERNAME\AppData\Local\Temp FOLDER I am available to help in anyway I can, but it sounds like there is very little hope of any recovery of a working mission file. Regards, Ian.

Time limit has always been there as far as i know, when I edited the missions sometime back, I adjusted that time limit to give a bit longer as I found it to harsh, it is only for the return trip down the mountain so the casuality doesn't die.

This is what happens if you try to run a mission without owning the Supercarrier DLC, when landing you will not be able to catch the arrester wire either, check your module manager and confirm it is installed. Regards, Ian.

Original mission had "Cloud density of 3" = Light scattered approx, A re-write of that mission had it changed to "Cloud Density of 6" = Med - high cloud cover. I agree It should be changed back to lesser cloud coverage. Regards, Ian.

Corrections already done for all missions in the campaign, the tree removal function is a hit and miss affair, works sometimes and not others, missions may have newer introduced errors due to later patches to DCSW after work and testing was completed. Deployment Campaign corrected for DCSW 2.5 and later Regards, Ian.,

If you or others are so inclined, try my corrected versions of DCSW Campaigns, should work better than the originals, bar any newer issues since I did the work and testing. Deployment and others for DCSW2.5 Regards Ian.

I am missing it also. I think it is gone for good unfortunately.

In the front seat, you have a little lever on the left lower part of the cyclic stick to unfold it, if it is stowed you have no control until it is unstowed.

Stable DCS release: C:\Users\yourname\Saved Games\DCS\Logs\DCS.log Openbeta DCS release: C:\Users\yourname\Saved Games\DCS.openbeta\Logs\DCS.log

I would increase your "Windows Pagefile" to 32GB, so you have 32GB real ram + 32GB virtual ram.(I consider this minimum personally). Nvidia GPU drivers referenced in the crash log, you might have to uninstall them, download and run DDU cleaner and reload fresh drivers. Re-run DCS to see if it fixed crashing with Syria map base missions. Regards, Ian.

You will both need to have a common IP protocol between you, either IPV4 or IPV6 (Long MAC looking address), depending on the Internet provider you have, you may have IPV4 only, IPV6 only, IPV4 over IPV6 or a Dual Stack system with IPV4 and IPV6 together. The ideal is a "Dual Stack protocol setup" that would allow IPV6 connections and fallback to IPV4 connections if needed. If one of you has a IPV4 only setup and the other IPV6 only, the later may have the option of changing their router to allow IPV4 over IPV6 as well, this would allow for you both to connect with the IPV4 protocol. Regards, Ian.

Log is showing problems: Nvidia GPU drivers referenced in the crash log, you should uninstall them, download and run DDU cleaner and reload the fresh drivers. Lua code errors, maybe related to MODS (FRENCHPACK V4.8), suggest uninstalling all MODS if fresh load of GPU drivers doesn't resolve issue. Regards, Ian.

Looking at dxdiag doesn't show any glaring problems, there are logs of "app crashes" and instances that point to "Memory leaks" happening (indicating that software is over running System MEMORY / RAM or using it very poorly by not releasing MEMORY once not used anymore. I have no real pearls of wisdom here, but based on you helpful description above: I would increase your "Windows Pagefile" to 32GB, so you have 32GB real ram + 32GB virtual ram.(I consider this minimum personally). Try lowering the "TEXTURE QUALITY=LOW or MEDIUM" in DCS config, users say the AH-64 model has very "high textures" and this combined with SYRIA (One of the largest maps of DCS) is requiring a huge amount of memory and is causing a huge MEMORY LEAK (This will fill all available system memory your system has no matter how much there is and usually will result in either a crash to desktop or the issue you have). Try running Windows TASK manager or resource manager to monitor what programs are using the most CPU, GPU and MEMORY whilst running DCS and then the mission, memory is the most critical to monitor, I am guessing that it will starve even the windows system. Regards, Ian.

This is a hard one, lot of speculation on my part, but your log of that mission deviates to mine by the parts in the spoiler, whilst that mission lets me into the cockpit fine (Running slight higher addition of DCS test version) Looks like it could be related to a sound card issue of some sort (Can't play sound or taking too long to find and do it). Missing or corrupt sound files (Missing WAV files maybe related to a MOD, SRS, etc). Left over MOD components that haven't been removed correctly ("ERROR VFS: VFS_open_write:" and "ERROR APP: can't open file"). White Screen and lockup error could be multiple causes, most likely faulty GPU and / or drivers, PSU or any other software or hardware. (Good start is to get the DXDIAG report to get a feel for how you system is operating in general and if there are any captured fault reports). To get DXDIAG report: Use windows search for : dxdiag Click on run dxdiag in search window. Click on bottom tab: Save all information. Choose DESKTOP on left directory list and then the SAVE button. Upload DXDIAG.TXT to forum from your DESKTOP. Excerpt from DCS.log: Check this forum solution for something similar to yours. General diagnosis of White screen lockup Regards, Ian.

Superb, glad you got it sorted. Cheers.

Going to need a dcs.log and dxdiag report to help you out. Regards, Ian.

Awesome, nice to have a win every now and then Thanks for letting me know. Cheers.

Excert from DCS.log looks quite the mess. Shows "Not enough memory resource" errors and "Not enough memory to decompress files" errors. Shows "SECURITYCONTROL: IC fail:" on files, probably due to not decompressing files correctly. Shows a couple of hundred "Key combo skipped" errors, I have never seen before Shows "File write errors" due to files being in use already. Recommended to do: Increase windows pagefile from 9GB to 32-48GB as you only have 16GB of actual ram. Update nvidia drivers to 511.xx as using older set, you may have your own reasons for using them instead. Do a "memory" and "hard drive" test, as faulty RAM or SSD/M.2 drive may be the issue at play. Run Windows file checker "SFC /scannow" to check for corruptions to system. Remove any "MODS" if any installed (Can't see any traces of such). Run DCS repair and cleanup commands, you mentioned that repair didn't work, did you mean it completed correctly but didn't fix issue, or was unable to run at all ??? Regards, Ian.

The two dcs.log files in you original post are corrupt and unusable, you might want to try and recreate, upload and test the new ones can be opened or read. Regards, Ian.

Can only offer generic advice that I would try as there are no glaring issue in the DCS.log. Delete the Syria map files from your install. "L:\SteamLibrary\steamapps\common\DCSWorld\Mods\terrains\Syria\". Run the STEAM "Validate install" option on DCS to check for install errors and to re-download the removed Syria map (Hopefully this will correct any missing or corrupt files / Directories that may have existed). (will download 32-64GB Size of Syria Map). Might pay to increase the windows pagefile from 16gb to 32gb to accomidate the large Syria map. Nvidia GPU drivers referenced in the crash log, you might have to uninstall them, download and run DDU cleaner and reload fresh drivers. Re-run DCS to see if it fixed crashing with Syria map base missions. Regards, Ian.

Hi Dave, I think a great deal of us are getting into our twilight years, if you had clicked on the link mentioning BIGNEWY in my original message it would have indicated on how to do the required steps, but that is no problem, I felt I had better give you some more direct links and easier instructions to follow. Instructions for changing pagefile (input 16384 or 32768): https://mcci.com/support/guides/how-to-change-the-windows-pagefile-size/ Download and install these drivers for your GTX-1060 here: https://www.nvidia.com/Download/driverResults.aspx/187098/en-us Using windows explorer, rename the folder: "C:\Users\user\Saved Games\DCS" to "C:\Users\user\Saved Games\_DCS" or "C:\Users\user\Saved Games\DCS_Backup" and start DCS to recreate a fresh configurations folder and run a mission to see if it resolved your loading issues, if it has you will have to copy over parts from the old backup, such as logbook, inputs for joysticks, etc. (This is the hard part) This is the main DCS problem that needs to be addressed, excerpt from DCS.log showing no permission to access a directory to write a file amongst other issues: If step 3 doesn't resolve the issue with mission loading, I will need to see the new DCS.log file created to see if this same error is occuring or not. If same error is there then it will be more of a hardware or windows system fault that will need to be found and addressed, that will not be easy. You could run DXDiag and send log to see if that contains any clues: Press Windows key on keyboard and type dxdiag.exe and click on that name in the list of results to run it. Click on bottom tab (Save all Information) and create the file on you desktop. Attach that saved file to post in this forum. As you said you re-installed DCS, I have assumed that a DCS clean and repair would be fruitless, you did also mention other issues on your way, what were they ????. Regards, Ian.

Quick look at your DCS.log shows : Your Windows Page files is to low (2gb) and should be set higher (ie 16 - 32gb). Video card drivers quite old (Might pay to get later version). Main issue is Lua code errors that point to the Missioneditor folder, you have permission denied and other failures. The Lua Code issues may be caused by MODS being installed, and the issue of locking up when loading mission is usually because of some issue in the "C:\Users\user\Saved Games\DCS" folder, or loading a mission that may have been edited on a latter (Test) version of editor (You would get a warning on loading that it was made on a later version though). General Help for this issue by Bignewy Regards, Ian.