Col. Kernel

I had the error code -13 quite consistently a few days back. It was fixed on my end by clicking "search for extra files after repair" in the DCS Updater and repairing once more. Turned out I had some old reshade .dlls inside the DCS main folder. After deleting those files, OpenXR has worked for me.

+1 on experiencing the CBU-105 dropping long. In my experience about 500 feet in zero wind conditions dropped from 10k or 20k feet.

Seems like something changed in the shaders in the latest Open Beta. After the update to 2.7.7.14727 Open Beta I'm getting this error message when using the (otherwise excellent) VR Shaders mod: I get the same error message with the original Kegetys mod and speed-of-heat's clear water variant as well as the hotfix for 2.7.6.

I think it depends on your Windows user account security settings. Perhaps try launching DCS as administrator. Personally, once I found settings that I liked I just edited ReShadePreset.ini in the \bin folder.

Another observation that I made during takeoff: If you apply roll trim using the trim wheel (on the left panel) instead of the trim hat on the stick, the trim wheel does not reset during takeoff. However, the trim indicator (the gauge next to the trim wheel) resets to zero during the takeoff roll, so that there is a discrepancy between the wheel and the indicator. Once airborne (or perhaps when the gear is up), the trim indicator jumps back to the same non-zero value as before it reset.

You can set system time exactly the same way by overriding the default values with the ICP keypad and pressing ENTR.

When applying roll trim before takeoff (e.g. due to an asymmetric stores load), the roll trim resets/centers during acceleration with the wheels still on the ground. With an asymmetric stores load, this causes the aircraft to roll at lift-off. I've read in the manual, that PITCH trim centers when ground speed exceeds 60 knots, but this is not mentioned for ROLL trim. In fact, the manual says that roll trim should be applied before takeoff in case of asymmetric loads to prevent wing drop. Usual caveats: I've never flown the Viper IRL, nor do I know the inner workings of the FLCS, but I suspect this behavior to be incorrect since it negates the use of roll trim at takeoff. I couldn't find this particular trim behavior reported in the forum, but please ignore, if it already has been reported. 1. Spawn on runway with an asymmetric loadout 2. Set roll trim away from center (using the trim hat on the stick) 3. Advance throttle 4. Takeoff (hopefully) I've attached a short track file (pardon my messy takeoff). It's recorded in VR so the default camera views are a bit wobbly. Press [RAlt]+4 twice, [RAlt]+2 twice and move the camera left to taste in order to see the roll trim wheel reset by itself. Roll trim.trk

Thanks for posting Lace. I also struggled with the MiG-29s and the Sidewinders. The most reliable tactic for me was to stay back in SAM cover and keep the Redfor occupied while having the SAMs take them out. For some reason the Su-25s tended to egress by flying over the Hawk batteries, which most often proved fatal.

I think for some reason that those "Bomb in zone" triggers don't really work for mission goals. Another thing is that it will only test if the bomb is inside the zone at some point - not that the bomb actually hit the runway. As for the latter part, the thread below discusses how to check for runway damage. A bit more involved than what I thought it would be. In any case, the mission scoring isn't crucial, although it is nice to have some built-in battle damage assessment.

Thanks for continuing this enjoyable line of missions Lace. I really like mission 7 because it's so technically demanding due to the low visibility conditions. It takes a lot of precision to line up correctly with the target, and an instrument landing in such low visibility always carries challenges of its own. I've flown it a few times, but never managed to get any points under "Results", even though I've had a good number of hits on the runway. Perhaps I'm being overly confident that they were good hits or perhaps the mission goal triggers aren't working quite right.

You're not doing anything wrong, it's a feature of the mission editor. The list of aircraft is dependent on the task chosen, which can be unfortunate for multi-role aircraft. You might (just might) be able to edit the aircraft in the mission file itself afterwards, but from my experience I would not expect things to work 100%. From the DCS manual (page 124): http://cdn.akamai.steamstatic.com/steam/apps/223750/manuals/ED_GUI_Manual_EN.pdf?t=1509720393

I had those errors in my logs too, when DCS suddenly started crashing. For me it has helped to roll back Windows Update KB4589212, which was installed on my rig earlier this week: https://forums.eagle.ru/topic/270049-windows-woes-random-ctd-fixed-by-rolling-back-win10-update-kb4589212-intel-microcode-update/?tab=comments#comment-4646556

In case it can help anyone: In late March my otherwise fairly stable rig suddenly had massive stuttering and random crashes in DCS. I went through the usual process with mods, repairs, removing OC's and what not. I finally figured out that Windows Update had installed a number of update packages around the time the problems had started. Rolling back these updates restored stability. After a month of stability I suddenly started getting random CTDs in DCS (now version 2.7) again earlier this week. Sometimes with an error log, sometimes without a log. The error log would usually show errors relating to video drivers: EDCORE: DCS/2.7.0.5118 (x86_64; Windows NT 10.0.19042) EDCORE: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7d91b2ed40558a26\nvwgf2umx.dll EDCORE: # C0000005 ACCESS_VIOLATION at 6B88A9F3 00:00000000 After going through the first steps of disabling mods etc. I remembered my problems from March and looked for Windows Updates. It turned out that one of the packages from March had been reinstalled. Rolling back that particular update restored stability once again. The update was KB4589212, which apparently is the latest microcode updates for Intel processors, and for some reason does not really work well in DCS for my rig (specs below). Hardly a long term fix, but perhaps rolling back that update can help someone else. Specs: Microsoft Windows 10 Home, 10.0.19042 Build 19042 i7-9700K CPU @ 4.9GHz, 32MB RAM, RTX 2080 (drivers 466.11), HP Reverb G2 Running DCS 2.7.0.5118 Open Beta

Do you by any chance have the "Historical list of units" function enabled in the ME? The wristwatch button at the bottom of the screen.

Well, color me impressed! Thanks for the very solid update! Performance is good... and those clouds... I first loaded an Instant Action mission for the Viper on the Caucasus map. A thin layer of clouds, which looked a bit pixelated and ok-ish, but nothing more. I then loaded up the mission editor and tried a preset for broken clouds. Immediately impressed with the perception of depth of the clouds and I had an enjoyable time zooming around from cloud to cloud. I finally loaded up a preset for overcast and rain and added some wind to the mix. Mind blown! The rain sounds, the claustrophobic cloud layers, and that wonderful relief of finally breaking out of the clouds at 15,000 feet - all amazing! Well done!

Hi Florence. I've been making progress in the campaign and just wanted to provide feedback on what I've experienced so far. I like the campaign and am determined to play it through. I've come to enjoy the repetition in each mission, making it just another day in the office. Mission 3: In mission 4 and mission 8 you kindly provide a hint that you should check/change the laser codes. You could add that hint to mission 3 as well, since that will be the first time that the player encounters the 1687 code in the campaign. I learned the hard way, when playing through mission 3. Mission 4: My wingman, being the usual DCS AI, ran out of fuel over Ar Raqqa. He diverted to the neutral airport at Aleppo - close to the Red faction SAM sites. I noticed that almost all of the SAM sites have ROE weapons hold, except for the southernmost site near Aleppo (N 35 57'19'' E 37 16'1''). Don't know if it's intended or not (I think it's the same in every mission), but my diverting wingman got the SAMs flying. Not so neutral after all... Mission 5: I found it enjoyable and fun. My wingman diverted to Aleppo again. This time he wouldn't land for some reason and ended up ejecting. Mission 6: I found this mission very tricky and struggled to deal enough damage to the group - even if I managed to destroy a vehicle and a few soldiers with every bomb. Finishing off with guns still didn't do it on most attempts, and it took quite a few attempts before I managed to complete it. I don't mind the campaign being difficult, but in this case perhaps it required luck more than skill to complete. My wingman usually baited the MANPADs and on most attempts never made it home. Btw the briefing text says that your armament is 4 GBU-12. However, there are MK-82s loaded and the JTAC check-in also mentions 82s, so the briefing text should probably be updated. Mission 7: Another fun Maverick mission. The volume of the radio messages from the unit under fire was low, so it was a bit of a struggle to hear over the background radio chatter from the other flights. Mission 8: Again the volume of the radio messages (in this case from deep-voiced Blackbeard) was low, so it was hard to hear everything being said. Mission 9: Haven't completed it yet, but on my first try during startup, the medical APC parks right in front of my wingman and prevents him from taxiing. Looking in the mission editor, it's not the AI being wonky - the route ends in front of the hangar.

Think I made it work. Used the previous non-crashing dxgi.dll (after reading Brainfreeze's reply) and now the new settings for radius and SingleImage turn up in the menu. The sharpening wasn't right at first, but switching SingleImage off made it work. The new radius setting works too - confirmed by setting it to a very low value. So far the performance improvement is minimal (with the default radius of 0.5). The previous version had a frametime impact of about 0.8ms - this one about 0.6-0.7 in the same scenario, so could be measurement error.

Looks promising, but I haven't been able to make it work so far either. Like zildag found, the new dxgi.dll crashes DCS on startup.

Windows Update installed some system updates (KB4589212, KB4601154, KB5001567) around the 20th-21st March on my rig, which led to stutters in DCS VR. The stutters disappeared when I rolled back the updates. As impalor suggests, try looking at the update history. In a different sim, there has also been quite a few reports on degrading performance in VR with some of the latest NVIDIA drivers

@Sr. Thanks for letting us know about this. This is really awesome! I've dialed back the color saturation and the overall contrast to 1, so I presume I just use the sharpening filter. In my usual benchmark (Viper "Ready on the ramp" in Caucasus) I notice about 0.8ms increase in frametimes. I've dialed back SteamVR SS to 90%, which more than compensates for the performance loss (on my rig and in that setting) and still leaves me with a better image overall. It's really noticeable on high contrast areas/textures on medium to long distances. The Syrian terrain from +10,000 feet looks so much better now - especially the increased contrast and detail in the city areas. Great find!

+1 from me too. I've been playing the 1987 Nordkapp missions by Lace for the Viper and they have really ignited my interest in an Arctic map. Would work well for different eras and plenty of scope for carrier options etc. Seems like the Falklands map will bring South American fjords, but the Norwegian and Russian ones would be a great addition to DCS.

I have been experiencing this as well. Starting from February (perhaps January) this year: The mission editor/mission planner has become really laggy in VR. Noticeable when zooming in or out on the map, even in missions with few units. I've experienced near crashes and crashes to desktop using the F10 map when flying in single player missions. Usually after the mission has been running for some time. I just flew an hour-long mission in VR on the Syria map in the Viper. I used the F10 map after about 25 minutes into the mission without any issues. When I opened the F10 map again after about 1 hour and 20 minutes, the sim froze for about 10 seconds and I lost the image in my headset. The WMR portal lost connection to the headset and the frame time in SteamVR shot through the roof. After about a minute or so, the frames stabilized, but I could never get the image back in the headset. Had a hair-rising experience landing the Viper in VR without the headset I've saved the DCS.log from the session and I'm happy to send it over, if it might be of any help. From the looks of it, there aren't many clues in the log file though. i7-9700K, 32 GB RAM RTX 2080 Reverb G2 Windows 10, build 19042

Thanks for your quick response Florence. There's no need to rush with a new release for my sake. I managed to get the right coordinates in the end. So just a suggestion in case you at some point make a new release. Rather than indefinitely, perhaps the option to repeat could be there until you ask the JTAC for the remarks. Regarding the taxi issue, I was cleared to taxi by the ATC, but my wingman refused to move until the Globemaster had parked. Still not quite sure what was happening with the AI, but it happened consistently each time I flew the mission. Of course there's only so much that you as a mission designer can do with the DCS AI, but I just wanted to let you know that it is a bit quirky in that mission. Now I'm looking forward to flying mission 4. Edit: Oh wow, you're quick. Thanks for the update!

Thanks for the updated version @Florence201. Have tried out mission 3 and hit a few bumps on the road. There seems to be an AI/ATC conflict at Incirlik between the landing C-17 Globemaster and my wingman. If the Globemaster lands, my wingman only starts taxiing once the Globemaster has reached the parking position after a few minutes. Which means I'll have to wait for my wingman to taxi to the runway. One the other hand, if I start taxiing early, the Globemaster aborts landing and circles the runway instead. I've flown the mission a few times and on one occasion, the Globemaster got stuck on the runway, which meant that my wingman got stuck in the hangar and refused to taxi. While AI traffic adds to the atmosphere, it's apparently a bit too much to handle for the DCS ATC. Perhaps consider skipping the landing Globemaster. Don't know if and how it's connected to the changes regarding ATC and taxiing aircraft that you mention above under version 1.2 I was very pleased that you added the option to repeat the JTAC 9-line, since there's a lot of information to cope with. However, it is only possible to repeat it once and the second time the text only shows for 10 seconds (compared to 35 seconds the first time). Since it takes a while to type in the coordinates in Long/Lat (at least for my fat fingers), it would be helpful to add the option to repeat indefinitely and also have the text show for a bit longer.

Just flew the first two missions and had a blast. Thanks for creating and sharing this campaign. It's evident that a lot of hard work went into creating it and I look forward to flying the remaining missions. A few observations from mission 2 (I'm flying version 1.2 of the campaign): Mission 2 requires the Civil Aircraft Mod (but neither mission 1 nor mission 3 do). You might want to include a link to that mod in your description - or modify whatever modded unit is in the mission, if this wasn't planned. During my attack run I got a lua script error about a CASEngagementZone. See the image below. Thanks again!