Search the Community

Here are some log lines showing player "xvii-Dietrich" in an FW190 bombing a map building. The building is destroyed. The bomb blast also damages the FW 190. Please note that the Target ID number is missing for the statics and buildings. This is evident in the lines where you see "target=" 2021-04-21 08:52:43.086 INFO Scripting: event:targetPilotName=xvii-Dietrich,type=hit,initiatorPilotName=xvii-Dietrich,weapon=SC 500 J,target=FW-190A8,t=777.59,initiatorMissionID=19699,targetMissionID=19699, 2021-04-21 08:52:43.211 INFO Scripting: event:type=hit,initiatorPilotName=xvii-Dietrich,weapon=SC 500 J,target=,t=777.715,initiatorMissionID=19699,targetMissionID=, 2021-04-21 08:52:43.211 INFO Scripting: event:t=777.715,type=dead,initiatorMissionID=, 2021-04-21 08:52:43.212 INFO Scripting: event:type=kill,initiatorPilotName=xvii-Dietrich,weapon=SC 500 J,target=,t=777.715,initiatorMissionID=19699,targetMissionID=, I will break this down a little more: 1. In the following line you can see the the bomb blast hits the FW190. The Target ID is correct (see green text) 2021-04-21 08:52:43.086 INFO Scripting: event:targetPilotName=xvii-Dietrich,type=hit,initiatorPilotName=xvii-Dietrich,weapon=SC 500 J,target=FW-190A8,t=777.59,initiatorMissionID=19699,targetMissionID=19699, 2. In the following line, you can see where the building hit is logged, however the objects ID / type is not known (text is red): 2021-04-21 08:52:43.211 INFO Scripting: event:type=hit,initiatorPilotName=xvii-Dietrich,weapon=SC 500 J,target=,t=777.715,initiatorMissionID=19699,targetMissionID=, 3. In this line you can see where the building is destroyed (killed). once again the objects ID / type is not known (text is red): 2021-04-21 08:52:43.212 INFO Scripting: event:type=kill,initiatorPilotName=xvii-Dietrich,weapon=SC 500 J,target=,t=777.715,initiatorMissionID=19699,targetMissionID=, Having these details properly recorded in the logs is critical for many servers which collect and display statistical information for their players.

Hi everyone, I am reporting 1 bug and 1 possible bug. BUG: After setting up a TGT Code in PB HARM Mode, if you touch Heading Set Switch the TGT number gets scrambled on MFD. POSSIBLE BUG: While trying to use PB MODE in F18 it seems nothing can't stop them. Not even long shots that results in low speeds and impact angles. I've created a mission with several different sams (SA10/SA19/AAA/SA19) at the same spot and seems nothing can stop them. Please see track. Thanks. HARMS.trk

*At least it should be* Hey ED, great work on 2.7 - really well deserved all the praise. Thanks from someone who has invested big into this product. So here's an issue with replays that's easy to create, easy to explain - and therefore (hopefully) easy to fix. (I am using VR, but I suspect trackIR might behave the same - someone might be helpful here and check) Take F18 and take the 9x and go into combat vs AIs using the HMCS. Look at them and uncage and fire until they are dead. Now watch your replay... You are free to look around - but I noticed when in the original flight the helmet display got turned on, back in the replay mode, you are now controlling this in the replay. If you move your head from front to off bore and back, you hear the sound feedback from the IR just as if you were flying live. This means, unless you are looking at the exact spot in the sky at the exact times when the original uncage/lock was made, the replay version of the F18 aircraft is going to try and lockup/fire at whatever you, as replay passenger happen to be looking at. The missile therefore isn't going to lock up / kill the enemy aircraft like it did when you were recording, instead if flies off randomly, perhaps looking for the sun, and now the replay is going to start and desync fast. To fix this, the HMCS system needs to record where the pilot was looking at the time of the recording, and keep those array of variables in sync at all times with the replay, and not override those variables with where the replay persons head happens to be looking. The second issue I dont know why or how it happens, just that it has everything to do with flying fast and low. It has plagued DCS for years, and I tried this again yesterday. It unfortunately makes it impossible to record my favourite style of missions (SEAD & WW). This is high speed, low altitude flying, often well below tree top height, taking on SAMs with dumb bombs or rockets etc, (players who just fire standoff weapons with impunity I find very boring). I watch the replay back, I crash into the first or at the very latest, second low level bit of flying and obviously the entire rest of the mission that I thought recorded is now desynced. This is also easy to reproduce, just take a fast jet and keep it around 400-500 knots and pop up and down as if you are trying to line up a shot with SAMs but then diving down quickly, dodging missiles between trees and residential areas and so forth - the replay will have you crash into something, including an open field. anyways thanks again to all over at ED for your efforts - I hope at least the first issue I post here can be easily fixed.

Title says it. I can not zoom in and out and change my heads position. The standard setting is way different from the Su-27 one too, not allowing me to see my airbrake and generally anything in the rear hemisphere. J-11_cockpit_broken.trk Another bug that i have been wanting to report for a while is that when you speed up the simulation in a singleplayer mission, while flying a J-11A, you can not slow it down again. Forcing you to restart the mission or finish it at 2x,4x,8x,16x etc. speed. This bug has been in DCS for a while. I cant show this with a track, just speed up the simulation speed in a singleplayer mission and try to decrease it to normal again while flying J-11A.

I was messing around with the Chinese ships yesterday and I noticed that the 52C seems to be able to launch some missiles but when one of the launchers on the rear of the ship fires, the missile immediately explodes, taking nearly half the ships HP.

Not sure if this is bug or feature. I think that the KC-135 Stratotanker does support the frequency range.

A new one (Dedicated Server Crash) 8 Players online. HARMs and Unguided Bombs (MK82,83,84) where released at this time. 2021-04-24 17:49:52.333 ERROR EDOBJECTS: Failed assert `success` at Projects\edObjects\Source\Registry\RegMapStorage.cpp:178 2021-04-24 17:49:52.334 INFO Scripting: event:type=shot,initiatorPilotName=[Bones05] Jeepster,t=6361.195,weapon=AGM-88C,initiatorMissionID=105, 2021-04-24 17:49:52.538 INFO Scripting: event:type=trigger zone,target=,t=6361.401,initiatorMissionID=,targetMissionID=, 2021-04-24 17:49:52.538 INFO SCRIPTING: 8434( 13)/E: EVENT00000.onEvent(WARNING: Could not get EVENTMETA data for event ID=35! Is this an unknown/new DCS event?) 2021-04-24 17:49:53.532 INFO Scripting: event:type=trigger zone,target=,t=6362.401,initiatorMissionID=,targetMissionID=, 2021-04-24 17:49:53.532 INFO SCRIPTING: 8434( 13)/E: EVENT00000.onEvent(WARNING: Could not get EVENTMETA data for event ID=35! Is this an unknown/new DCS event?) 2021-04-24 17:49:53.840 INFO EDCORE: try to write dump information 2021-04-24 17:49:53.855 INFO EDCORE: # -------------- 20210424-174954 -------------- 2021-04-24 17:49:53.858 INFO EDCORE: DCS/2.7.0.5118 (x86_64; Windows NT 10.0.17763) 2021-04-24 17:49:53.861 INFO EDCORE: D:\Program Files\Eagle Dynamics\DCS World OpenBeta Server\bin\Weapons.dll 2021-04-24 17:49:53.864 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 46A2928B 00:00000000 2021-04-24 17:49:53.870 INFO EDCORE: SymInit: Symbol-SearchPath: '.;D:\Program Files\Eagle Dynamics\DCS World OpenBeta Server;D:\Program Files\Eagle Dynamics\DCS World OpenBeta Server\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Adm034Naop86frh3sfwd' 2021-04-24 17:49:53.873 INFO EDCORE: OS-Version: 10.0.17763 () 0x110-0x3 2021-04-24 17:49:55.701 INFO EDCORE: 0x00000000000F928B (Weapons): wWeaponSystemManager::getEmissionModeForTarget + 0x12B 2021-04-24 17:49:55.705 INFO EDCORE: 0x00000000000FA54A (Weapons): wWeaponSystemManager::isRadiatedByRadar + 0x6A 2021-04-24 17:49:55.709 INFO EDCORE: 0x000000000017C8A8 (WeaponBlocks): wDRadioSeeker::isThisMissileRadiatedByTargetRadar + 0xE8 2021-04-24 17:49:55.713 INFO EDCORE: 0x000000000017C75F (WeaponBlocks): wDRadioSeeker::isRadByCurrentTarget + 0xAF 2021-04-24 17:49:55.717 INFO EDCORE: 0x000000000017CF37 (WeaponBlocks): wDRadioSeeker::seekerBlockProc + 0x1E7 2021-04-24 17:49:55.721 INFO EDCORE: 0x000000000017DC70 (WeaponBlocks): wDRadioSeeker::simulate + 0x80 2021-04-24 17:49:55.725 INFO EDCORE: 0x000000000001FD3A (blocksim): wSimulationSystem::simulate + 0x14A 2021-04-24 17:49:55.729 INFO EDCORE: 0x000000000005FB4B (WeaponsBase): wAmmunition::simulate + 0x10B 2021-04-24 17:49:55.734 INFO EDCORE: 0x000000000011237B (Weapons): wAmmunitionDecoy::spawnSnare + 0x7CB 2021-04-24 17:49:55.738 INFO EDCORE: 0x0000000000119348 (Weapons): wAmmunitionSelfHoming::simulate + 0x158 2021-04-24 17:49:55.742 INFO EDCORE: 0x000000000005CBDA (WeaponsBase): wAmmunition::Class + 0x9A 2021-04-24 17:49:55.746 INFO EDCORE: 0x0000000000003AD6 (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x466 2021-04-24 17:49:55.750 INFO EDCORE: 0x0000000000003F3D (World): wSimCalendar::DoActionsUntil + 0x1FD 2021-04-24 17:49:55.754 INFO EDCORE: 0x00000000007E9B02 (DCS): SW + 0x4F9152 2021-04-24 17:49:55.758 INFO EDCORE: 0x00000000007E986E (DCS): SW + 0x4F8EBE 2021-04-24 17:49:55.762 INFO EDCORE: 0x00000000007FF3AB (DCS): SW + 0x50E9FB 2021-04-24 17:49:55.767 INFO EDCORE: 0x00000000007D02A4 (DCS): SW + 0x4DF8F4 2021-04-24 17:49:55.771 INFO EDCORE: 0x00000000007D067D (DCS): SW + 0x4DFCCD 2021-04-24 17:49:55.775 INFO EDCORE: 0x0000000001C2BB59 (DCS): AmdPowerXpressRequestHighPerformance + 0xE40B55 2021-04-24 17:49:55.779 INFO EDCORE: 0x0000000000A067DE (DCS): SW + 0x715E2E 2021-04-24 17:49:55.783 INFO EDCORE: 0x0000000000017974 (KERNEL32): BaseThreadInitThunk + 0x14 2021-04-24 17:49:55.787 INFO EDCORE: 0x000000000005A2F1 (ntdll): RtlUserThreadStart + 0x21 2021-04-24 17:50:04.225 INFO EDCORE: Minidump created. 2021-04-24 17:50:04.288 INFO Lua::Config: stack traceback: dcs.log-20210424-174954.zip dcs.log

I love this campaign so I went to try it from the beginning with the new clouds in 2.7, but I didn't get very far. I called for ground power on mission 1 in the MiG-15 and there was no response. The F10 map showed Anapa as neutral but the mission editor showed it as red. Huh? Based on this thread I tried adding 10 Russian tanks nearby in the ME. Then Anapa showed up red in-sim and I got a ground crew response. So for some reason, the airfield doesn't seem to have enough red forces around for DCS to consider it properly red. I didn't see any non-red forces around so I'm not sure why, but it seems this mission needs a little help to work again out of the box. I checked the first F-86 mission and the second MiG-15 mission and neither of them had this problem. I also tried creating a minimal test mission from scratch where I just added one cold start red MiG-15 to Anapa, and that worked fine.

JF-17_can_not_be_notched.trk Target is at the slowest possible speed and practically 0 closure speed relative to the ground. No ground clutter or loss of contact. Bug happens within 7-8 nautical miles.

JF-17_infinite track range.trk Tracking a cold target at 100+ nm in TWS, in lookdown mode.

Some ground units seem to be unable to fire/ direct their AA correctly. Video below and link to trk file: https://drive.google.com/file/d/1C8pfJqN-tSNo3UIEryMdXMOkc6-Z4iwD/view?usp=sharing

Hi All, This is my first post on this forum. I've been playing this marvellous game for a long time. About a month ago, began to play A-10C II Tank Killer. Read lots of user guide stuff and watched so many training videos on YouTube. After a while noticed a bug or buggy thing on A10C II. Emergency Wheel Brake works decent when I use only mouse button but it doesn't work if I use keyboard buttons. All my record is on the video which is at bottom.

Apparently this is what it looks like it in the real thing. The inner target range marker sticks out a far bit and is clearly visible inside the ring. Additionally the super-imposed half-ring that designates 0nm-target range also leaves a stronger shilouette against the ASE ring. In contrast in DCS the range tick seems to be 2-3 pixels long and is ergonomically difficult to pick up: Ergonomically it doesn't make sense to me that the range marker isn't easier to see in our DCS-F/A-18.

Bug: Jester refusing to attempt to switch to P-STT when commanded. Jester will not switch even after responding with "Roger that" or similar phrases. Can I reproduce it 100%: 75-80%, someimes he does it once and it will work, sometimes it never works. Most of the time I am able to (or attempt to) lock 1 single target with P-STT when I tell jester, but he will never be able to do it again, with the same target or another one at futher, similar, or closer range. (NOTE: This seems to mostly be happening in MP, but it has been happening to me in SP aswell). NOTE, I know that P-STT is not supposed to be used at long range, but the point is I atleast want jester to attempt a P-STT lock even if it will fail. This due to the fact that a human rio can try as many times as he wants, why cant jester do the same? (HOWEVER; jester autoswitches to P-STT in close ranges 80% of the time) How to reproduce/ description: Step1: When having a target on TWS or RWS, tell tester to attempt a PD-STT lock on said target. Step2: Tell jester to switch to P-STT Step 3: Jester should just say "roger that", but never attempt said P-STT lock (What he will do most of the time is listen and carry our your order once, but never do it again) Result: Jester will tell you "roger that" but will never attempt a P-STT lock, even if conditions are favourable or not. In practice, he ignores your request. DCS Version: Open beta 2.7.0.5659 System Specs: CPU i5-6600K GPU RX480 8GB 32GB RAM SSD Sabrent Rocket 1TB OS: Win10 Peripherals: Joystick: T.1600M Stick Throttle: T.1600M Throttle Pedals: N/A Others: N/A Headtracker: Custom made Mission File: Happens in any mission (SP or MP) Log: Sorry, don't have Track: See attached file Video (SP in this case): (video might still be processing, sorry for low quality) Mods: I do not use any mods that conflicts or disturbs any module in game. F14Bug2.trk

Hello, I'm new here, but not to DCS World. My father loves DCS World but one thing pretty much takes away his ability to do many missions that require a hot jet. His game, regardless if it's in the air or on the ground hot setting, is ALWAYS cold and dark. For example, we start him in the air for a quick mission, cold and dark jet. Instant action on the catapult??? Cold and dark jet. I was able to help him get setup since his DCS download was incomplete. It didn't even have a Run.exe program. As far as I know it doesn't have an updater.exe but I can check with him. He's reinstalled twice to my knowledge but the problem persists. What do you guys think it is? Should I just tell him to raise a ticket? Or, since my DCS is doing well, just transfer some main files over to him? Thanks everyone, Sabre65

Hello, So, I was experimenting with my F16 Viper, and noticed that in the "Create Fast Misssion" there were objects or icons that are not meant to be there on the F16, such as the IR Deflector and IR/Sand filter options in the Mission Resources. So far, I have only seen this in the "Create Fast Misssion", and no-where else. Any help would be great! (Note: I was able to delete the files from the Gazelle, and that did get rid of it, however in fear I would cause a chain event of unstable-ness, I put them back, and concluded this is a bug) (Second note: Sorry the track is a bit long, I just tried to demonstrate it as best as possible. Also, I forgot to show the Mission Resources, however if I did, the screenshot shows exactly what it would have looked like) DCS F-16 bug.trk

Sometimes, when trying to lock with LHAQ mode, HACQ mode or AACQ mode in the F-18, the radar won't lock to the plane you're looking at/the plane the cursor is placed over, it will instead lock a target which doesn't exist a few degrees to either side, after a few seconds it will unlock him, it doesn't follow any pattern, it happens randomly, sometimes it happens the first time you lock a target, sometimes it happens the 7th, but it can reduce BVR performance. The easiest way to recreate it is to try to lock a target using any of these previously mentioned modes in Hornet's radar, the bug is completely reproducible and I've had it happen a few times already. I'm attaching the track where I reproduce the bug, in this case I'm only able to make it happen with AACQ and LHAQ modes, but in another mission it happened in HACQ too. You can see that in one of the attempts it locks a target around 90nm away, then I zoom in and you can clearly see the enemy degrees away from the lock. As a note I checked the MiG-23 wasn't using chaff, and I've had the same happen with other planes like a Fulcrum. Also I'm attaching the .miz file so you can try and recreate it in the same environment as I did. F-18 LHAQ bug.trk BVR for track file.miz

I got a strange behaviour on my dedicated server. Whichever mission I choose in the list, it is the "mission 1" (according to the numbering of mission list in optionsServer.lua) that is launched. (Look at the current mission on server details, and the one which is tagged as running in the server list...) If I modify myself the [1] mission in the list, to change the mission, the behaviour is the same. I cannot either remove line in the mission list. I can only add... I have fully reinstall the server, including the saved games, top start with a clean setup -> same behaviour. Everything was OK in last OB.

Seem's to be some slight audio glitches with the Mi-8 in 2.7 examples being the trimmer sounding funky and Rockets launching sounding weird (from inside cockpit). Only seems to be some sounds not them all, easily replicable just hop into the hip free flight and trim it. You will know what i mean

Recently I bought the Syria map because I was looking for map in the Middle East. It worked fine for a few hours, then it crashed. Which for me is normal. Had a super high density mission going on and just restarted the mission. When I restarted I was doing a gun run in the A-10C and then my game froze and then crashed. Tested this with Caucasus map and didn't happen. So I tried this again in Syria and happened over and over again. The only thing I noticed that was wrong on my computer was that the CPU and GPU utilization would drop whenever DCS froze and then leading to a crash. Happens around 890 feet. Otherwise playing the Map is fine. Just wonder if anyone has also had this problem and if they did, how could it be fixed. Here Is my most recent log. And has crashed my Computer twice now. Specs: AMD FX 6300 Nvidia GeForce GTX 1050ti 16GB of ram 500 Watt Power Supply 930gb SSD dcs.log-20210407-045848.zip

Hello, I've posted on this topic before didn't have the time to test it but now I've. Last time I wrote this (Under that I would put the test results and other people experience with this issue.) : " I would add later this day a video of this. The basic idea is: - 80% of the time the missile won't show on RWR and you would just die. - The time it does show on RWR it usually shows about 0.5 seconds before impact and very rarely it will show 3-4 second before impact. - Also a F-14 will not show on the RWR when it locks you for most of the time, it will maybe blip in RWR twice or a bit more but that's it. (Tests have been done on the Viper [F-16] but a Hornet [F-18] player that I fly with also confirmed that the Phoenix doesn't show on RWR). *I would try to add a video of this happening when I'm home, around 6-4 hours from when this is posted* " On this post I got the response of IronMIKE, he said this; " Thank you. If this is happening on the RWR of another module, it is likely an oversight on their side and would have to be addressed with them, please. " Before posting my first topic about the issue I've contacted NineLine on the ED Discord he responded by telling me this: " You may need to report this to HB " Because of that I'm trying to figure out to who should I reach out about this problem. My first test were in a Viper [F-16] and in the F-15, did it on single player when the A.I got these following settings, Enemy fighter- Ace, 1 AIM-54C-MK47, at 35,000 feet with speeds of mach 1.0 . In that test the Viper didn't got the results that I looked for it immediately started warning of a incoming missile the moment the A.I launched, but the F-15 did got the result that I looked for. In this track file you can see the F-15 not getting any warning of a incoming missile: F-15 AIM-54 test bug prood.trk I had a track file of that happening to me but I don't remember which day it was and each track file is at least 2 hours. Also I asked around to see if some players also experienced the same thing, I got some of my buddies to confirm that this has happened to them after the latest update but like me they have lots of file that each one is at least 1 hour long, I've also asked around in the ED's discord, a user named FzK#4325 told me the same thing, he flies the F-14 and he didn't have a track file for me but he did have a Tacview recording. he said the it had happened to him 3 times in the mission he flew, it may seem like he was defending but he said the he is cranking right after he shots everytime, by the Tacview we can see the he engages a bandit then he foxes and start cranking, not getting any RWR warning and then he just dies. Is own word (can be found is ED's discord): Das Feuer — Today at 4:54 AM is anyone experiencing AIM-54 not showing on RWR or showing just half a second before impact FzK — Today at 5:02 AM I am [5:02 AM] Got killed [5:02 AM] By phoenixes FzK — Today at 5:02 AM With no warning [5:02 AM] 3 times no warning just death [5:03 AM] It annoyed me so much Das Feuer — Today at 5:03 AM Can you just confirm that you weren't in the blind area of RWR and not got killed by a IR missile please FzK — Today at 5:03 AM I watched the tacview [5:03 AM] And he was dead ahead of me [5:03 AM] Phoenix to the face Das Feuer — Today at 5:03 AM and can you please tell me which airframe were you using? Das Feuer — Today at 5:04 AM I would like if can send it to me FzK — Today at 5:05 AM At first I was shocked like what killed me hehe [5:05 AM] Silent phoenixes [5:05 AM] That’s dangerous(edited) @FzK Another F14 Das Feuer — Today at 5:05 AM Copy if you can send me the Tacview file it would mean a lot FzK — Today at 5:05 AM It is a tacview from PGAW Would U mind If i clip it?(edited) [5:05 AM] Via video FzK — Today at 5:05 AM Because it is 3hours long Das Feuer — Today at 5:05 AM it's better to send me the whole file @Das Feuer it's better to send me the whole file FzK — Today at 5:06 AM I’ll do that and give ya a time stamp then Das Feuer — Today at 5:06 AM copy thanks FzK — Today at 5:07 AM So give me about 20minutes [5:07 AM] And I’ll send it in your dm’s Das Feuer — Today at 5:07 AM yup no problem thank you By this we can learn that he is probably telling the truth. Here we can see the Tacview: (wasn't able to add the Tacview you are welcome to DM me in discord I will send it to you.) look for him (SHARK 1-3|FzK) at 30:55. Hope someone can give me a answer to this, if help is needed I've no problem helping out. My discord is the same as username here look for me in ED's discord.

Hi, I'm really enjoying the Anton at the moment. Part of the joy of flying in VR is having the ability to turn on the pilot body in cockpit. Despite trying with the default key and even changing it to another, no pilot seems to appear. Has the Anton still not got a pilot model? Thanks

All the information below is public and posted by ED. The R-27R in DCS has a 20% energy reserve compared to EDs real-life Su-27 DLZ simulator at all altitudes. The R-27ER does not. It is noticable that the difference between the graph from the manual and the DLZ in the real Su-27 is always 20%, no matter which R-27 variant or what altitude. What this means is that either all the documents are wrong, and the DCS R-27R is overperforming by about 10%, or the R-27ER is underperforming by about 10%. I could not find the DLZ values for 5 and 10km for the R-27ER, but the difference between the diagram and DCS is the biggest at low altitude. Hit condition is target speed+150 m/s. Uncut version of the documents below: Tracks: ER_ingame_1km.trk R_ingame_1km.trk R_ingame_10km.trk DLZ simulator proof:

This selector should accept 10 positions but currently you only have 9, so they are not properly displayed and the arrow ends up in middle positions Trying to select 18 degrees (3 clicks) This can be solved by changing: elements["AC-TEMP-KNOB-PTR"] = multiposition_switch(_("Temperature Selector, 5/10/15/18/20/22/24/30/35/40/50"), devices.ECS_INTERFACE, ecs_commands.Temperature, 146, 11, 1/9, false, 0.0, anim_speed_default, false) to elements["AC-TEMP-KNOB-PTR"] = multiposition_switch(_("Temperature Selector, 5/10/15/18/20/22/24/30/35/40/50"), devices.ECS_INTERFACE, ecs_commands.Temperature, 146, 11, 1/10, false, 0.0, anim_speed_default, false) In the file ....\Mods\aircraft\Mi-24P\Cockpit\Scripts\clickabledata.lua (line 150) After the fix: @BIGNEWY Sorry, this should have been posted to the bugs section but I messed it up

Hello all. For a few months now, I have had this issue with my game where about 5/6ths of the display will randomly start to flash in and out. The most times it has happened is either in the F-16 or the F-86, but I think it could be with almost all aircraft. Here is a reference of what I'm describing: These are my settings (The resolution is currently 1366x768 due to the nature of my monitor, but changing it to 1080 does not solve the problem and flashing will continue): My current specifications are: - Intel Core i5 4670K CPU @ 3.40GHz - NVIDIA GeForce GTX 980 4GB (Video drivers up to date) - 16GB DDR4 RAM - SAMSUNG 1TB SSD (DCS Install Location)