MadDog-IC

I had this issue as soon as the Lot 20 came out, and I reported to ED but they couldn't reproduce it, so nothing was done about it. Regards, Ian.

Log is cleaner, but there are still errors in the log of course, it is difficult to tell which ones to ignore and what might be causing some others. I can see a couple of lua errors still but none the wiser on what causes them. Also DCS can't allocate memory for sound files at the end of the log where it stops recording, so this could mean that the 16gb of ram you have isn't sufficient for the missions you are trying join, I would check that you have a large windows swapfile of at least 16gb set also in Windows 10. Since it was working and now it is not, have you updated DCS and / or Windows 10 at all ??? Not much else I can suggest. Regards, Ian.

I suspect 3rd party MODS might be causing some issues, they are either now incompatible or installed incorrectly and are failing to authenticate with lua code faults. I would suggest you: Remove any 3rd party Mods, can use command line "DCS_Updater.exe cleanup" to scan and check or force removal. Run the classic "DCS_Updater.exe repair" to check for other corruption. After doing steps 1-2 try DCS online and if not working repost log file generated. Exert of Log faults: Regards, Ian.

Discussed in this forum, with a fix supplied from ED, "Autoexec.cfg". https://forums.eagle.ru/showthread.php?t=219093&highlight=autoexec.cfg&page=7 Regards, Ian.

Can confirm that with the "Takeoff-from-Ground" mod installed on my DCS.openbeta does cause the exact same issues you are describing, it would appear it is no longer compatible and needs to be removed. Cheers, Ian.

Looking at your log you have a severe issue with the missioneditor directory and the lua files within, these errors look to be directly linked to your problems. I did a quick test on my system and can not replicate your issues, it works as advertised. I would suggest you: Rename and Backup your "D:\ssd cache\Saved Games\DCS.openalpha" folder and run DCS to recreate to see if it solves your issue, if resolved then recover controls, logbook, etc bit by bit from the backup of your originals. Disable any antivirus or at least exclude DCS from any of the realtime scanning utils so that it can't interfere with updates. Remove any 3rd party Mods, can use command line "DCS_Updater.exe cleanup" to scan and check. Run the classic "DCS_Updater.exe repair" to check for other corruption. Re-try running DCS in mission editor and repost Logs if you think things have changed but still don't work ok. Error Log exert: Regards, Ian.

Ignore these errors, these modules use the newer copy protection that links them directly to your account and no longer use the starforce key protection system. Regards, Ian.

Depends on air frame used: A few mission I fixed with the Fa-18 doing SEAD, did a very poor job of it, I had the same issues you described, I have always had better results with the F-16 and Su-25T being probably the best (Probably depends on long range sensors available on aircraft). Main issue I have is that missiles get borked all the time and cause tracking issues or faulty flight dynamics and or the target turn off their radar, more often missing their targets. Depending on target: Two or more aircraft firing at same time is required to overwelm the targets defenses. Altitude can make a large difference. Type of missile used against a specific target, slow cruise missile will work with some SAMS but not others, the HARM will work better in most instances, some times even firing maverick is better than a HARM, but you do have to get a lot closer for them to fire, so that is why you want multiple aircraft working on the one SAM at same time, and have good countermeasures and manueverability. Some tips for SEAD here: https://forums.eagle.ru/showthread.php?t=181854&highlight=sead Regards, Ian.

Looked at your log file, with the 3rd party mods, they aren't parsing authentications, therefore they aren't loading up (hence the mission module errors), most likely cause is that you have put the files in the MOD folder of the games directory itself, ie d:\Games\DCS World\Mods\ and not the \Saved Games\Dcs\Mods\ where they are required to be these days, so if that is the case, just move them over and try again. Showing errors: How to install MODS: https://forums.eagle.ru/showthread.php?t=190778 Regards, Ian.

Can't speak for other ED team members, but I certainly take notice of all reports on faulty missions, as I am able to help in that area. A lot of issues listed in the forums I already know about, a lot I don't, so it is always helpful when anyone takes the time to list them. With all issues, it is a matter of priorities, all problems can't be fixed instantly and require dedication and man hours to correct. The better the report with clear evidence of the issue is very important. So thank you to Joker and all that contribute to making the DCS flight sim a better product. Regards, Ian.

It is a hard one for sure, what I am saying is still relevant, I updated my previous post to be more clear and added the VR failure message to the spoiler, so please re-read. You appear to have at least 3 separate issues: VR interface in DCS failing to run. MissionEditor .lua file corruptions. Persian Golf Map security failure and map not loading. Could be that VR interface failure is causing a snowball effect and creating the other two problems, this would be logical, as you say you can run the same senario with a montor instead of VR and it doesn't have these issues (A dcs.log of the same missions run on a monitor setup would be helpful to compare against the VR based one) Don't focus on PG map so much and look for relevancy: I don't have VR I don't know what is normal for the dcs.log to have in it when working correctly, but I do see a failure to init the DCS WebGui which I have never seen in anyone else's logs. I am trying to fix the two other issues (MissionEditor .lua config file failure) and (PG Map security failure), by ruling them out of the equation, so by taking the complete DCS configuration directory back to default, that is one thing less I know isn't causing the issue and so on. In your "C:\Users\HomerSimpson\Saved Games" directory, try renaming the whole "DCS" folder temporarily to "_DCS" and let it recreate a new one to test with, run dcs again and save a new log file. (If it works, you will have to move directories back one at a time and retest to see what may have broken it. Not necessarily. May be so, but if PG runs fine when not running VR, then the issue must be something to do with the VR setup or files associated with it (Is there any software or firmware updates for your VR setup available at the support sight). Very difficult to fix if no one can't reproduce, but as I said in other post I have a security issue with the Harrier module that has no reason for failing but does, I am running it in a test version of DCS that is pretty much no mods or anything fancy such as VR. Regards, Ian.

Nice work, thanks for the feedback. Regards, Ian.

Problem is most likely: In your "C:\Users\HomerSimpson\Saved Games\DCS" directory, try renaming the "MissionEditor" folder temporarily and let it recreate a new one to test with, run dcs again and save a new log file. or In your "C:\Users\HomerSimpson\Saved Games" directory, try renaming the whole "DCS" folder temporarily and let it recreate a new one to test with, run dcs again and save a new log file. (If it works, you will have to move directories back one at a time and retest to see what may have broken it. The Persian Gulf Map module isn't passing authorization, it doesn't use the key system so ignore that error message, but is directly linked to your account, so there is still something amiss there also. May need to be deleted and reinstalled again. The VR system may be causing some interference to the security system, I suspect this as I see a failure of the DCS WebGui because of "no webserver running" in the log files. Other thing that causes a module security to fail is the presence of livery, cockpit and other mods in your E:\DCS World\ install directories and not the "C:\Users\HomerSimpson\Saved Games\DCS" directory structure, but as you done fresh install this is unlikely. My own system is similar to yours I am guessing, I have win8.1 with 32gb of ram, and I have a module security failure with the AV-8 Harrier module, it is linked to my account fine, but it fails every time, early on dcs would lockup and not run at all until I disabled the module completely, now dcs runs fine with it enabled, but I can't fly it when I go into a mission designed for it, it just shows an AI flying it. Disable any virus scanner as maybe interfering with software installs ??? Repost new dcs.log file of current effort running DCS. Regards, Ian.

Glad I could help, great to hear you are back in action, thanks for letting me know what might have fixed it. Re: The PG map, this map is using the new copy protection system that doesn't use serial numbers any more, but is directly linked to your account, ED is in the process of moving some of the older modules over to the newer system, and new releases I suppose will be in the newer system, but at the moment there is a mixture of the two systems. Regards, Ian.

Can see some issues with the M2000 cockpit and liveries (Missing files), but major problem seems to be with an export lua file for a simshaker. Exert from logs (unusual errors): No real ideas on how you might fix this: Except disable the export script for simshaker and any other third party mods to see if it corrects problem. Run the "..\bin\DCS_updater.exe cleanup" to check for third party mods. Run the "..\bin\DCS_updater.exe repair" to verify your install is ok. Regards, Ian.

There is an issue with the first two radios, in that the power on switches don't work, but if you use the frequency knob (Use the Middle mouse wheel) on the first one and turn it to the right, the radio turns on also, the second radio, you have to turn the frequency knob to the left and then right to turn on the radio. This has been reported. Regards, Ian.

How about a command line "DCS_Updater.exe cleanup" to check for some installed mod files you may have missed ???. You get the options to remove, keep, Backup anything that doesn't come with the game by default. My guess would be: If the problem is in the Mission Editor, then the solution is usually to recreate your "Saved Games\DCS.xxxx\MissionEditor" folder where the payloads, weather, logbooks are kept (Yes I know that you tried the whole saved games folder). Would need to try and get a dcs.log of when you try to run and it crashes or when you try to re save a mission. Regards, Ian.

Can't help you too much, if at all as I don't have VR, but for anyone to help, we are going to need two copies of your dcs.log, one when it works (Monitor) and one when it didn't (VR), use the same mission as that way we can compare results at least. Are the other user missions that work in VR in PG map also with same Fa-18 Hornet as players Aircraft ??? or other maps. Regards, Ian.

The zip file seems corrupts, can't get any data from it.

Looking at your log: You may have a MOD installed as your getting script errors, and I don't recognize the "Pak-Fa" module, so uninstall it or do a DCS_updater clean command to remove any third party mods. Your graphics card is being disconnected during play instigating a directx crash, have you recently updated the driver or windows 10, pays to disable antivirus when updating as may interfere with driver and DCS updates particulary. Regards, Ian

You could do it with the Recorded Track files intro system that is used in some missions. An example of these are in: The A-10c Introduction training mission. The Su-25t single mission - Presents. The technique to produce a Mission with a Track intro: Regards, Ian.

I tried the UH-1H Training mission Startup tonight, and the "SPACE BAR" was working ok, make sure you only press the "SPACE BAR" after the voice over has finished playing and then press for a second or two for it to be recognized. (It is checked for in the triggers that have a command that has "Wait for user response" in its name). The only issue I had was powering on the first two radios, the power buttons are mixed up with the frequency knob (I will report as a fault): To turn on the AN/ARN-82 you have to turn the frequency knob to the right one click forward with the middle mouse button wheel instead of the correct method of one right mouse click. To turn on the AN/ARC-134 you have turn the frequency knob to the left once and then to the right once using the middle mouse button wheel instead of the correct method of one right mouse click. Regards, Ian.

Cold war warrior, isn't on my list of repairs and I haven't had anything to do with it, not to say that others aren't looking into issues. Regards, Ian.

Has been reported for Su-25T (Georgian Oil War), Su-27 (Fortress Mozdok), A-10c (Georgian Hammer). In the mean time, you can use these corrected versions. Regards, Ian. DCSW - Fixed Campaign Intro's (Patch to Game 2.5x).zip

Sorry I missed this reply, but I posted the error when I last mentioned it being reported and provided the solution files to fix the issues, but it could take weeks to be put into a release to the public, I have no control on that side of things. Regards, Ian.