MadDog-IC

If you were using my version on the ED website, USER FILE Section (For Flaming Cliffs 3), yes it was a bug. OK, after looking at missions in question, it has become apparent that the DCS Mission editor has most likely corrupted the missions at some stage, it made all the F-4e aircraft a required module and also changed them in missions to A-10c CAS flights instead. After some considerable double checking and redoing flights and loadouts, etc I believe it to be ok, I have re-uploaded Campaign corrections as of 24-10-2018. Regards, Ian.

Have reproduced that missions 3 - 7 require a "F-4E Phantom II module" instead of the default F-4E AI model and have reported. Regards, Ian.

No change in ship speed doing 50+ KPH, but AI planes taking off, don't get that speed added to there initial speed but more like it gets substracted from there initial speed, so it is like 0 or -50 KPH, Where as if the boat is stationary the ai plane gets more speed to take off, no difference on the stats bar of speed, looks the same on take off, so its a wierd one. No change in loadouts either, still same overall take off weight. Checked all missions now, and some AI was most likely light enough to be able to take off under problem conditions, remember one. I even tried taking off in some of the missions with 100 fuel and weapons around the 32000kg mark and I crashed every time, that would be in mission 5 also, so I don't know how you managed that, well done. Mind you I am running an internal DCS test version so that might be different to your stable or beta. Regarding the tankers, they have to be put out of the way in general, other wise they always get shot down, I tried to program them so that they come into the path of you returning back to the carrier, later in the mission, hopefully after you have taken out the objectives. Regards, Ian.

No worries, Thanks for letting me know, I will have to check them all again, mission 10 has the same problem also. ;-( The positioning of the aircraft on the aircraft carrier is fixed internally already, I can now place them in all 3 spots for the players flight of 3 aircraft and have the 4th wingman spawn 2 minutes later on the longer runway, not to say it will stay that way before release. Aircraft taking off from long runway in position 3 can carry a little extra weight, as they can gather more take off speed in the extra distance. The AI su-33 take off is still borked by the boat moving at speed, they only take off if approx 2500-3000kg lighter than they use to be and boat is stopped, so awaiting news/fix on that issue. The amount of fuel is a problem since the PFM came about, as in real life Su-33 they can't take off at maximum weight (33000kg), 30000kg for pos 1 and 2 with (85-90% fuel and weapons) and 32000kg for pos 3 with (96-100% fuel and weapons) is about the best you can get. As for running out of fuel, there is a tanker in missions for resupply, but AI in general is to dumb to break off attacks and refuel when they are bingo. Regards, Ian.

Nothing I can do about that issue with missions 3-7, except put a report in about it (Done that now), only something ED can fix, as far as I know anyway. I could edit and run missions previously on internal testing DCS, but now I can't the same as you guys. I posted campaign up knowing this, but it should work when ED remove the requirement to have the yet to be released "F-4E module" and just use the AI F-4E aircraft as before. Regards, Ian.

Had a look at it, mission wasn't like this originally, a bug seems to have crepted in and the players flight is no longer locking to the carrier as a take off position, it is going to the next available airfield (Batumi) instead. After a bit of testing, this behavior is due to: The players flight having 3 aircraft assigned for take off, but the carrier (Kuznitsov) only allows 2 take off positions now instead of the 3 that it should allow, the game incorrectly automatically moves it to the next available airport that can support 3 plane flight (Batumi). A Work around fix is to: Make the players flight 2 aircraft only. Increase the Players Wingman flight from 1 to 2 aircraft and change its take off start time a minute or two after the actual mission start time. Also noticed: AI Su-33 can't take off with out crashing, Head wind and carrier forward speed no longer help with extra lift and speed. Will report and and try to get these things corrected. Regards, Ian.

Some sort of Directx 11 issue, most likely windows 10 revision your running or graphics card drivers not installed correctly. To Resolve: Use DDU to clean out nvidia drivers and update to a known good version. Update windows 10 or drop back windows 10 to a known good version (there has been a stinker update recently). Regards, Ian.

That only happens if you use the "Prepare mission" option of the Mission Editor, either don't use it or open the mission file with a zip file editor and delete the config folder from within.

Could be that the graphics drivers just requires a larger amount of ram than before, the same as DCS does, that is why the swap file should be large enough so that they can both work, A combined total of 32-48gb of usable ram and swapfile would be my recommendation as heavy dcs missions can easily use up to 32gb by itself and lighter missions up to 16gb, leaving little or nothing for the operating system and drivers. The normal for swapfiles years ago was to have 2.5x you system memory, but things have changed since then, some will argue that you don't need swapfiles now that you have 16gb or 32gb of real ram, others will say it must me this or that, but generally windows works best if you set it high enough yourself, or let windows manage it itself which will increase the limit on the fly if need be. Re putting the swapfile on the SSD drive, that is your decision, me personally, I put it on my games drive which is a hybrid ssd/hdd and not my SSD which is souly for the operating system (Don't want to wear it out any quicker that I have to, all temp directories, DCS missions and configs have all been relocated off the SSD and onto my games SSHD). From the DCS log, this reports your real system ram and the Pagefile - However the pagefile shown is a total of your real ram and the swapfile, so I would like to see your Pagefile setting in DCS log to show 32768MB or 49152MB: 018-09-26 19:49:30.593 INFO DCS: CPU cores: 4, threads: 8, System RAM: 16323 MB, Pagefile: 18323 MB My DCS log with swapfile at 32768MB: 2018-09-19 10:37:58.467 INFO DCS: CPU cores: 4, threads: 8, System RAM: 32637 MB, Pagefile: 65405 MB Regards, Ian.

Good luck, I hope it works out for you. Swapfile has not increased as of yet, reboot and recheck, keep changing the figure (recommend system managed) and saving until windows insisted that it needs to reboot to implement (If it doesn't ask to reboot, it will not change it or fix it) With video card drivers did you go from a 3xx.xx or earlier version straight to a 399.xx or 411.xx versions by just installing straight over the top of the older version, if so I would recommend, uninstalling graphics drivers once again and running the DDU util software to wipe all traces of Nvidia drivers and associated software for a clean install, disable any antivirus whilst installing drivers. The labels problem is a known bug. List of unusual errors that I don't see very often in log files (some listed multiple times, and I don't know the cause, other than graphics drivers not installed correctly on some systems, which has been happening in resent times with nvidias installers): 2018-09-25 20:45:46.125 ERROR DX11BACKEND: Texture /textures/p51d_damage_main_2.dds is 3d but has depth == 1. 2018-09-25 20:46:03.983 ERROR EDTERRAINGRAPHICS41: VTI loading slice error. ??? 2018-09-25 20:46:23.772 ERROR DX11BACKEND: Can't open texture land_16_57_15.png for texture array at index 456. 2018-09-25 20:51:28.585 ERROR SOUND: invalid source_params(woLA-16799488:aircrafts\engines\rollsroycemerlin\engine): gain Video drivers inplicated due to: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_cad5fc8f5ca41c15\nvwgf2umx.dll 2018-09-25 21:05:05.522 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 2D94BF9E 00:00000000 2018-09-25 21:05:05.525 INFO EDCORE: 00000000 00000000 0000:00000000 2018-09-25 21:05:05.527 INFO EDCORE: 2D94BF9E 6C1DDF80 0000:00000000 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_cad5fc8f5ca41c15\nvwgf2umx.dll OpenAdapter12()+38FE I suspect windows, swapfile and graphics drivers or a general system glitch, coupled with the general instability of DCS itself at the moment, making it difficult for you. A fresh install of DCS will help diagnose whether it is in the Windows system or DCS. Regards, Ian.

Looked at logs, would try: With All logs - Show too little a swapfile - Up your Windows Swapfile to 16 or 32 gb so that you have 16gb of real ram and a minimum of 16gb of virtual ram on hdd / ssd (Highly recommend 32gb swapfile). With 3rd log- Shows crashes in Video drivers, since you have tried uninstall and reloading it, I can't recommend any remedy for this. Try the classic "dcs_updater.exe cleanup" to see if any mods left over in install. Regards, Ian.

I Would be backing up or rename your whole "..\Saved Games\DCS.openbeta" folder and let DCS recreate a new one and then run DCS with that new one just to see if it fixes the load issue, then rebuild it from your backup a little bit at a time to find the problem. Regards, Ian.

This is how it should be done in current DCS 2.5.x versions: https://forums.eagle.ru/showthread.php?t=187155&highlight=6dof

Currently bugged, but work around here: https://forums.eagle.ru/showthread.php?t=215887 Regards, Ian.

Can't give to many words of wisdom, but the following errors standout: Looks like you are running a Dynamically spawning mission script and it is producing several errors, so it might be incompatible now, Run a "DCS_Updater.exe Cleanup" command to check that you have actually removed all mods, try another mission that is similar if possible to see if you get the same results or not. Crash is happening within you graphic card drivers, so might not have installed correctly, try uninstalling and reinstalling or a different version. Best to have any antivirus software deactivated whilst doing this. 2018-09-18 21:42:55.972 ERROR SCRIPTING: MIST|doScheduledFunctions|1005: Error in scheduled function: [string "C:\Users\Steve\AppData\Local\Temp\DCS.openbeta\/~mis000036DA"]:1651: attempt to index local 'myGroup' (a nil value) 2018-09-18 21:43:09.093 ERROR SCRIPTING: MIST|doScheduledFunctions|1019: Error in scheduled function: $1[string "C:\Users\Steve\AppData\Local\Temp\DCS.openbeta\/~mis00000EBF"]:43: attempt to index global '_observer' (a nil value) 2018-09-18 21:43:13.079 INFO SCRIPTING: Dynamic AI group spawn script loaded. 2018-09-18 21:43:13.079 INFO SCRIPTING: Dynamic AI group spawn script running. 2018-09-18 21:51:11.289 INFO EDCORE: try to write dump information 2018-09-18 21:51:11.294 INFO EDCORE: # -------------- 20180918-215111 -------------- 2018-09-18 21:51:11.296 INFO EDCORE: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_adc520364db29861\nvwgf2umx.dll 2018-09-18 21:51:11.298 INFO EDCORE: # C0000005 ACCESS_VIOLATION at CC170D44 00:00000000 Regards, Ian.

Download the updates to that campaign on the "user files" section of ED website, get the patch for 2.5 version, most of you concerns in every mission has long been fixed (3-4 months ago) but is delayed by ED in implementing into DCS because of Multi-language text changes that need to be re-translated, something I can not do, and ED insist I don't touch with google translate. The errors you talk about above, came about because SEAD weapons miss their targets 50-70% time now, compared to a 100% hit success in previous versions of DCS, they are all but useless in general in my opinion, and I am not the only one that thinks so. Had a look at error correction log, and I also corrected the patriot site to make functional in mission 4,9,10. https://www.digitalcombatsimulator.com/en/files/?PER_PAGE=20&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.

This problem doesn't look related to previous users issue as your not getting the same errors in the log he had, but your error log shows a lot of out of memory issues. I take it your not running the latest OB 2.5.3.21444 as it appears more unstable (I suspect it may have a memory leak, which might exasibate your issue by raising the required RAM faster and higher, thus exhausting all of your physical and virtual RAM). Compared to the OB 2.5.2 version you are running, still causes the issue, but just takes longer I would suggest trying: Check your "Windows swap file" settings, and have it set to system managed, if not already so, with 16gb of physical RAM, I would want it to be at least 16 to 32gb of virtual ram. Unlikely to be a video card driver issue, but you never know. Error Log Exert showing Directx errors: 2018-09-16 21:20:11.850 ERROR DX11BACKEND: failed to create structed buffer. Reason: E_OUTOFMEMORY 2018-09-16 21:20:11.850 ERROR DX11BACKEND: CreateShaderResourceView FAILED. Reason: E_INVALIDARG 2018-09-16 21:20:11.854 ERROR DX11BACKEND: failed to create structed buffer. Reason: E_OUTOFMEMORY Regards, Ian.

That is a hard one indeed. Yourself and other VR users: Might pay to have a look at this thread (particularly messages #9 and #10 at the bottom), though not directly related to your issues they might give you some ideas. https://forums.eagle.ru/showthread.php?t=216899 Cheers, Ian.

Having all those third party mods may be complicating issues (Don't get me wrong, they are fine work from their authors) but there is always the possibility of them becoming incompatible in some way with DCS's new code base and cause all sorts of weird effects. I don't have VR and am not willing to load all the third party mods required so can't test under those conditions, but myself and others can't help anyone unless you post the dcs.log files created when the mission works ok in 2D and another when it fails under 3D VR. This goes for all users (@Zoinid, @Wexler and others) trying to get help, every problem has to be treated on a case by case basis, the logs are the only way we get a picture of what is going on with your installs. Regards, Ian.

Fixed a similar problem with another user (was a user mod "takeoff-from-ground mod") that was causing the issue, have a look at the link below, another user offered a replacement to fix issue with 2.5. https://forums.eagle.ru/showthread.php?t=219558 Regards, Ian.

Thanks for the missions, as you know I fixed the main updated one by replacing the faulty missing briefing picture from the previous version. Just noting here for others to know the outcome wasn't related to DCS or VR as such, just a corrupted mission. Cheers, Ian.

Would be hard to tell if SSD is faulty without more in depth diagnosic software (SMART function may or may not report failing SSD), corruption can also be cause by Windows system crashes such as BSOD or sudden uncontrolled reboots, such as faulty power supplies cause. Corruptions to SSD / HDD over time will kill your operation system and other software, especially if it is hardware related, so I would backup system and get a new SSD if you hadn't had any previous unexplained system crashes such as the BSOD or reboots with windows Cheers, Ian.

Can't speak for other modules, but with simple mission with FA-18c AI and creating a new payload of any sort to be saved as new creates that error: dcs - FA-18c Loadout file.txt is with a FA-18c.lua file in the payloads directory. dcs - Fa-18c Loadout missing.txt is with NO FA-18c.lua file in payloads directory. Exert of errors created in Log related to FA-18c, seems to be looking to create an "F/A-18C.lua" or an "F" directory and a "A-18C.lua" file. Regards, Ian. dcs - FA-18c Loadout file.txt dcs - Fa-18c Loadout missing.txt

Try: Disable any antivirus program or at least put DCS directory into the exception list so its files aren't scanned or interfered with during updates. Run check disk on hard drive that has your DCS install on it, to make sure the file structure is error free. Delete the offending files and or directories that can't be moved from the "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\_downloads" directory and try updating again. Run DCS as administrator (Permissions may be interfering and not allowing writes or deletes). Regards, Ian.

Already reported along with the following campaigns, awaiting fix to be applied to release. The A-10c Georgian Hammer and Su-25T Georgain oil war campaigns have similar issues. Regards, Ian.