Vähäkylä

Any news on this? Anyone got the link still?

I don't think the HMS Invincible has any CIWS in this year model in DCS.

It does not show any geographical features, simply airports and waypoints.

Making any kind of naval combat or SAM combat is a huge pain in the butt currently. The controls are lackluster and frustrating for ship control, and require players to figure out work arounds. I want to order the ship to fire at particular ships, not just at a group. I want to tell the ship to do evasive maneuvers.

Now we got the Colossus-class carrier for Argentina, the two Chilean Condell-class frigates, and the Leander's from the Royal Navy that are free with South Atlantic Asset pack. I don't think any of the Leanders from the UK side come with any CIWS. The two Condell class ones do come with a CIWS, but the Colossus-class carrier does not.

This should be part of the module. The script looks neat.

This feature, even if just used on the ramp, with typing in the coordinates for it, is very important to the module's useability. Right now it is not possible to use the Sea Eagle in any kind of dynamic environment that is not a purely preplanned and scripted .miz prepared by you.

Resurrecting because it'd be nice to get more callsigns for all units. Using legacy vanilla units, I run out of specific callsigns very quick.

Here is the new video detailing how the campaign works.

As the patch popped up, I tried to hop into the playable F1 EE and set the country for Ecuador, but was not able to get Ecuador skins still, sadly.

The ingame map that integrates with the South Atlantic DCS map: https://www.google.com/maps/d/u/0/viewer?mid=1RHYRehltgtfH02o6Yn9JgBmaHt2XqZs&ll=-50.27184644770649%2C-59.893140458910224&z=7

Here is one after action review from the prologue mission of dropping SBS team to the HMS Agincourt in the Atlantic, enabling the Arma 3 mission on the Goose Green map. Ascot 1 - Op. Guinea Pig after action report: A/C status Ascot1-1, systems fault, aborted, A/C down while maintenance diagnoses fault. Time to resolution should be ok for next mission. Ascot1-2, 1-3, no concerns. Ascot was to proceed to a specified drop point in the ocean, and deliver SBS with cargo to the waiting submarine before turning back to pick up parts. Pre drop, Ascot 1-1 had a malfunction requiring immediate mission abort and RTB. Due to effective planning, the SBS mission can proceed with 1/2 cargo modules delivered. Mission control passed to Breaky in Ascot 1-2, and proceeded without issue. Since all Hercules were carrying only minimum fuel reserves, excess capacity was available to haul the payload slated for Ascot 1-1. There were no concerns with cruise or landing in IMC. Communication with ground stations was congested, but effective even with multiple airports on the same frequency. Also, Ascot 1 flight worked out some kinks with the autopilot modes, transitions, and cut out conditions. This assisted navigation, with all planes within visual range when IFR conditions lifted, with 0.7 nm spacing. The drop precision was ok, with AP issues leading to reversion to manual flight, and visual drop. As mentioned, IMC approach procedures were good, with landings at El Calafate and Puerto Santa Cruz performed by the numbers. Due to the manual drop, it was close enough to be retrieved, but could have been closer; most practice was done to master dropping at parameters on autopilot. Communication of package status was hindered by not having a concise summary of codes in a handy location. AP glitches and unfamiliarity caused manual flight until the system could be engaged again. At points, the package frequency was overloaded, leading to messages being delayed until a gap in traffic could be found. Going forward, the ABM team should split separate areas of responsibility onto different frequencies at their discretion. Due to Hercules AP concerns, a second waypoint shall be placed >2NM past any precision drops along the same flight path. Radios should be preprogrammed with UHF channels to allow quick switching as they are controlled from the FMC, and require focus inside the cockpit for several seconds to switch frequencies. Frequency transitions should be performed while autopilot can be engaged to avoid flight path deviations. Flight time was also not as planned, due to a slower speed than used in the planning; recommended speeds are approximately 170 KIAS in climb phases, and 230 KIAS in cruise, unless escorts are assigned. Cruise with escorts should be approximately 260 KIAS. Finally, flight control transfer methods should be disabled until investigation of the systems fault on Ascot 1-1 has been concluded. -------------------------- And another AAR from the escorts. Venom 1 was completely successful in all objectives, though admittedly, we didn't really have to do much aside from fly near Ascot and look pretty. Since BARCAP didn't <profanity> up, we had plenty of opportunity to look real fucking pretty. There were some adjustments that had to be made to our flight path since the clouds were so thick. Namely, the clouds were so thick that we really didn't care to go below 15000. What went well: My flight as a whole did a great job keeping formation both on each other and with Ascot. The new air battle managers were very quick to respond to my calls. The Panthers intimidated the enemy sufficiently that we didn't really have to do anything but admire the view. The last-minute decision to add wing tanks was an excellent one, single centerline would not have left sufficient margin if a scrap did occur. What went less than well: At one point during the flight datalink coverage was lacking, and I called for a declare ("ABM, is this guy hostile?") using Bullseye coordinates. The ABM misunderstood and looked for my callout in BRAA relative to me. While it was quickly cleared up, it did take some time to sort. When entering the clouds during landing, we were flying in too close a formation. At one point, Venom 1-2 conducted a maneuver that forced me into evasive to avoid a collision. Later review determined that we passed within 150 ft of each other. Venom 1-3 was running the majority of the flight with airbrakes out. This caused undue fuel expenditure and difficulty with formation keeping. Landing was somewhat of a clusterfuck, as there was a bit of a communication breakdown there. While I will admit there were some missed directions from the ATC within my flight, I did need to conduct some approach resolution on my own to conduct a safe landing as a result of misdirections from the ATC (the most "expedited" descent you're getting out of me in IMC is 10-15 degrees nose down in my expensive jet). https://i.imgur.com/HjwkEy1.mp4 What can improve: During portions of the flight, we noticed our datalink dropping off for extended periods. This made it a little challenging to know where Ascot was during portions of the flight where they were below cloud cover (we chose to stay above clouds for fuel economy). Petitioning command to shore up coverage in the AOO, as if the PLA discovers this gap in radar/DL coverage, they might exploit it to slip aircraft in undetected. I would have preferred the ILS side of the runway in those conditions. While I recognize that we opted not to use it due the wind forcing wild corrections to stay on target, it would have been useful to have as a reference point before the runway was in sight. The weather. Seriously, that super secret commando team better be setting up some of those weather controlling lasers I keep reading about on the internet. https://i.imgur.com/kExBe6m.mp4 The Arma 3 mission is set up like this: Some signals traffic and regional intelligence from our friends at MI6. The Falklands, or Malvinas, have long been used as a shipping port, a safe harbor, and a waystation for exploration and international shipping. They're about 300 miles east of the Patagonian coast, and have been inhabited by Europeans ever since the 1600s. They might have had settlements before that, likely Fuegians from Patagonia if anyone, but were not inhabited when European claims on them were asserted. The UK had visited it prior but laid its first claim in 1764. It reasserted it more forcefully in 1833, and ever since the Falklands has been inhabited by mostly European-descent Falkland Islanders, populations ranging from 500 to 5000 with ebbs and flows. In addition, is has, or had, RAF Mount Pleasant, an airbase of the South Atlantic for the Royal Air Force. Now, the PLAAF controls it, and PLAN uses Port Stanley as a base. Goose Green is a small town that sits on an isthmus, connecting the main island of East Falklands to the uninhabited part known as Lafonia. This narrow isthmus is not only the only road and thoroughfare between these two major portions, but it also divides a small sound that is the ocean cut between them. For as long as there has been shipping, the Choiseul Sound has been used as a safe anchoring point for cargo ships and military vessels waiting for more favorable winds, warmer weather, or for the storm to pass. For the past 400 years, this has not changed. This same sound is now a shelter for the PLAN mobility sealift fleet, waiting for their turn in the clogged up Port Stanley, unable to accept as many ships as are arriving from Africa. Thus, they sail to Choiseul Sound to wait for their turn. MI6 is also passing along this whatsapp message from a Chinese sailor sent from a cellular network in the Falklands. --------------- And another historical newspaper from two months before the game events was made:

So, it's kind of hard to figure out here where to start. I will do my best. I'm sure many of you are familiar with goons from www.somethingawful.com, the older era of the internet. In any case, the goons, of Eve and WoW and many other game-fame, will try blending in forums-based RPG, DCS World, and Arma 3 to a big grog-style wargame that blends simulation and planning between many mediums. "Narrative driven wargaming" is a term that some have used. In any case, I intend to copy here the main plot events and intelligence briefings to make it so that if there's people here who wish to follow along can see a very different way of playing DCS. Where does it start? Well, the world's in a world war. It's sparked partly by events of 2008 Georgian War, which we played in our alternate universe and I will make a post that shows what it entailed, as well as the 1990 Arab-Israeli War, a conflict in our alternate timeline. The main plot starting point can be read here: https://www.airgoons.com/hype/TheLongAfternoonWar.html It's a long read, but will get you to the mood. That's the starting point. Story telling wise, it's hard to get a good enemy into South America, so extensive writing had to be made to tenuously support such a scenario. Anyway, here we are! A few months before the events of the first game day, there's a news article blurb: Lord Stimperor posted: Time for the first intel briefing given at the CSAD to Air Force commanders. [b]Date:[/b] February 10, 2010 [b]Concerning:[/b] PLAN and PLAAF forces at Islas Malvinas and Tierra del Fuego. Briefing Focus: Islas Malvinas (that some call the "Falklands") Listen up, as we all know, the Chinese Navy has captured Puerto Williams and Ushuia, and is currently spreading its forces to the rest of Tierra del Fuego. While there are not many major cities nor airports, the situation is very grim. The intel briefing for Tierra del Fuego will be at a later moment, but first, let's discuss the current situation of People's Liberation Army Air Force resupply. The distance from the current PLAN logistics hub, Cape Town, South Africa, to Tierra del Fuego is 4100 nautical miles. That is an immense distance, and far beyond the capabilities of any PLAAF air asset. Currently, as far as we know, the PLAN has taken control of all the ports in South Africa and Namibia. These are used for island hopping logistics where the latest PLAN island seizures; Saint Helena, Edinburgh of the Seven Seas, South Georgia and now Malvinas, are used to sustain this immediate sealift. Using this island hopping logistics chain, each leg is roughly 1500 nautical miles long. Their attack submarine fleet is hard at work protecting this, but they have also had their shipping sunk. Some 40 cargo ships are currently en-route to the Malvinas, and possibly as many as 15 have already been unloaded. Most of these ships are at Blanco Bay, waiting to get into Port Stanley at East Malvinas. Their cargo is unloaded and either trucked to former-RAF Mount Pleasant, or in the case of jets; trucked to Stanley Airfield and flown to Mount Pleasant. This is is where they are combat fitted and conduct patrols between the Malvinas and Tierra del Fuego. When the PLAN landed at Puerto Williams and Ushuia, they had relative few airplanes providing overwatch. We believe this to be due to the difficulty sealift and the slow speed of unloading. This means that at the start of our operations on the 20th, ten days now, we are not yet against the full PLAAF airpower. Let's look at the satellite photos offered by the USSOUTHCOM: Here we can see the ships waiting in line to get into Port Stanley. Visible are also several Type 052 destroyers providing air defence. Red arrow is the route they take on trucks to Stanley Airfield. The mainstay of the PLAAF fleet is the J-7G, seen here getting unloaded from the cargo ship. The number of cranes and the throughput of their lifts is the current limiting factor. Expect the PLAN to prioritize shipping in better port facilities as soon as they are able. Also seen is a HQ-7 mobile SAM unit. The flight from Stanley to Mount Pleasant is only 30 nautical miles and we've detected a daily ferry operation by the PLAAF. Here's a latest flyover of PLAAF Mount Pleasant: A daily increasing number of J-7Gs, two J-11s, and two H-6s are there currently. In addition, a large number of shipping containers are arriving via truck from Port Stanley. Now let's focus on something else. As you all know, the seas at the Malvinas can be especially cruel and demanding. As Port Stanley has a limited capacity of accepting ships, the PLAN has had issues with the large number of ships, including their civilian merchant fleet used for this sea lift. Just like for the past centuries, ships seek shelter at Choiseul Sound, between Isla Soledad (Main part of East Falklands/Malvinas) and the southern, mainly uninhabited Lafonia. These are conneted by a narrow isthmus known as Goose Green that also has a small settlement on it. To the east of Goose Green, are various natural bays and coves that offer safe anchoring for the large number of ships. This place also has Type 052 destroyers there. THIS CONCLUDES THE INTEL BRIEF LADIES AND GENTLEMEN ------------------ Hypothetically, if we had eyes everywhere, this is what it would look like to watch some PLAAF J-7Gs depart Stanley to Mount Pleasant. ----------------------------------------- Aight, intel briefing. Get ready. In real life gametime, this weekend, on the 30th of September, we will fly a DCS mission at the usual goon time, 2000 UTC. It represents the in-game time of 0900hrs, 11 February, 2010. This is a secret mission. You are to take the cargo GROOMSMEN from El Calafate, Comandante Armando Tola International Airport. It's in Santa Cruz Province, Argentina. This cargo is to be brought to a specific location over the Atlantic Sea. After you have delivered GROOMSMEN, you will turn around and either land at Rio Gallegos or Puerto San Julian on your way back to El Calafate. This will depend on the choice made. After cargo pickup you will fly to El Calafate and it will be mission complete. Available for this mission you have: ASCOT 1: 4x C-130 cargo aircraft VENOM 1: 2x F-16C from Chilean Air Force Venom 2: 2x F-16C from Chilean Air Force Signup looks like this: nullnull We will get the final weather forecast soon, but it is currently bad weather over the province with low lying fog, broken clouds, and moderate precipitation. It is not a good flying weather. The flying weather is not made better by the PLAAF patrols that have been sighted over the South Atlantic. We are currently monitoring the hostile invasion force in Tierra del Fuego, but do not assess that to be a risk to this operation. Nevertheless, we've assigned the escort flights to this. The PLAAF has some patrols around the Malvinas, and there are sporadic airplanes flying low over Tierra del Fuego. The PLAAF is unlikely to initiate contact, and so are we. Stay well within the FLOT during the mission. The two proposed waypoints are as follows: RESOLUTION JAGUAR (Fetch the F-5 parts) RESOLUTION GUINEA PIG (Fetch the Su-25T parts) We have this signal intercept from South Atlantic that we are currently waiting more information on: https://drive.google.com/file/d/1QaZxuhpLDQFNv1sQnblPmUJTW2HKV5DH/view?usp=sharing Sign up and see you in the skies! Vahakyla fucked around with this message at 21:53 on Sep 26, 2

Thanks so much! Appreciate the quick turn-around. Thanks for your efforts!

Would it be possible to fix this? I love the 2112 Squadron's skins on the CE but I prefer the EE, and we'll be using the plane in our big MP campaign, too! You can see in the video that they have wrong skins, sadly. I realize this is likely because the CE was released first and the skins were on it, but it'd be neat to have the other countries to get their skins on the EE, too! In practice that now means that this dope skin: Is only on the wrong plane!

I find this mod to be simply stellar. DCS needs more female voices. I've listened to plenty of military aviation radio and there's been times when there are no male voices on the net at all, and DCS is still very dude heavy.

Ok so we have narrowed this down somewhat. There's two major clues that are the likely culprit. In a trackfile, C-130s that are AI are dropping paratroopers. These appear as MK77 in the trackfile. They went through the ground, and kept falling to the infinity. Does DCS have some culling mechanic for when objects go too far? This picture shows them far below the earth altitude. Second, found this message of the Hercules mod that is used on our server that has same exact issue, though I am not sure if there was a shootdown at the exact same moment.

Did they drop them?

Server was running a mission file that has been used before several times, so it should not be anything added to it by the mission makers, and leads me to believe it could be the patch. Dedicated server, running OpenBeta. Map was Syria. No player admits to using any kind of retarded bombs at the time of the crash, either. I've attached the log for one client computer, but if there's value in server log, I'll get it later, too. dcs.log

When I load into the game, sometimes my screen gets stuck while loading into cockpit, sometimes it happens in the menu. The game itself does not crash, but SteamVR does with error -203. This leaves the 2d desktop repeater stuck in one view, running at some 2fps or so, never truly recovering. Problem is that DCS didn't crash, meaning it essentially does not log it as a crash either for analysing a log. Only solution I have found to this is to reinstall DCS, reinstall SRS, and reinstall SteamVR and WMR. I don't know which one of those helps. Then it seems to work until DCS patches again, and we're back into the steamvr hell. Reverb G2 gen1. 11700K 32GB 3200mhz 3080ti Game on a NVME. Here's the bit of DCS Log. I played on Growling Sidewinder, then logged off, went to the main menu. I adjusted some control settings and bam, -203 Steam VR crash: 2022-02-01 00:54:16.550 ERROR SOUND: render time = 0.010639s exceeded allowed slice of 0.010000s 2022-02-01 00:54:25.492 DEBUG LuaGUI: --- onChatMessage--- Slmod- PVP KILL: "viper" scored a victory against "Spoon" with AIM-120C-5! 1 2022-02-01 00:54:25.566 DEBUG LuaGUI: --- onChatMessage--- BLUE player Cobra 1-1 disconnected nil 2022-02-01 00:54:25.566 DEBUG LuaGUI: ----onPlayerDisconnect--- 39 0 2022-02-01 00:54:40.801 INFO NET: Current ping: 133.3ms 2022-02-01 00:54:49.782 DEBUG LuaGUI: --- onChatMessage--- Slmod- PVP KILL: "Spoon" scored a victory against "viper" with AIM-120C-5! 1 2022-02-01 00:55:10.811 INFO NET: Current ping: 131.7ms 2022-02-01 00:55:16.833 DEBUG LuaGUI: --- onChatMessage--- BLUE player BiggestGeese disconnected nil 2022-02-01 00:55:16.833 DEBUG LuaGUI: ----onPlayerDisconnect--- 3 0 2022-02-01 00:55:16.987 DEBUG LuaGUI: --- onChatMessage--- RED player FUPA 1-1 | UncleTouchy disconnected nil 2022-02-01 00:55:16.988 DEBUG LuaGUI: ----onPlayerDisconnect--- 20 0 2022-02-01 00:55:26.919 ERROR SOUND: invalid source_params(woLA-16781832:aircrafts/engines/rearclosehighpower): gain 2022-02-01 00:55:40.829 INFO NET: Current ping: 131.6ms 2022-02-01 00:55:51.460 DEBUG LuaGUI: --- onChatMessage--- RED player laocoon died nil 2022-02-01 00:55:51.460 DEBUG LuaGUI: --- onChatMessage--- RED player Eagle 1-2 | Cheems in JF-17 killed RED player laocoon in F-16C_50 with SD-10 nil 2022-02-01 00:56:01.359 ERROR SOUND: invalid source_params(woLA-17244957:aircrafts/engines/rearclosehighpower): gain 2022-02-01 00:56:03.004 ERROR SOUND: invalid source_params(woLA-17244957:aircrafts/engines/afterburnerrearclose): gain 2022-02-01 00:56:03.004 ERROR SOUND: invalid source_params(woLA-17244957:aircrafts/engines/heavy_rear_afterburner_crackle): gain 2022-02-01 00:56:03.004 ERROR SOUND: invalid source_params(woLA-17244957:aircrafts/engines/afterburnerrearclose): gain 2022-02-01 00:56:08.731 INFO NET: disconnected: 0 2022-02-01 00:56:08.740 INFO NET: disconnected from server 2022-02-01 00:56:08.740 INFO NET: client has stopped 2022-02-01 00:56:09.750 INFO Dispatcher: Stop 2022-02-01 00:56:09.750 DEBUG LuaGUI: ----onNetDisconnect--- 0 false 2022-02-01 00:56:09.752 DEBUG LuaGUI: ----onSimulationStop--- true Thats okay 0 2022-02-01 00:56:09.752 DEBUG LuaGUI: ----DCS.isMultiplayer()--- false 2022-02-01 00:56:09.752 DEBUG LuaGUI: removing C:\Users\KALLE-~1\AppData\Local\Temp\DCS\tempMission.miz 2022-02-01 00:56:09.809 DEBUG LuaGUI: ---- openReturnScreen= multiplayer 2022-02-01 00:56:17.411 INFO Config: netview stopped 2022-02-01 00:56:17.757 INFO TERRAIN: lSystem::CleanScenes() 2022-02-01 00:56:17.825 INFO VISUALIZER: StopSimulation 2022-02-01 00:56:17.866 INFO VISUALIZER: Stopped collection of statistic. 2022-02-01 00:56:17.919 DEBUG LuaGUI: --- onChatMessage--- Mission is over. nil 2022-02-01 00:56:18.674 INFO EDCORE: (dDispatcher)enterToState_:3 2022-02-01 00:56:18.674 DEBUG LuaGUI: --onShowIntermission-GAMEGUI--- 2022-02-01 00:56:19.400 INFO NET: client has started 2022-02-01 00:56:19.400 INFO NET: Using LEDBAT for UDP congestion control. 2022-02-01 00:56:23.633 INFO NET: got 1289 servers from the master. 2022-02-01 00:56:37.250 ERROR NET: dropped serverinfo(92.41.62.63:10308): unknown request id 2022-02-01 00:57:27.308 INFO NET: client has stopped 2022-02-01 00:57:27.310 INFO APP: Screen: MainMenu 2022-02-01 00:57:29.288 INFO APP: Screen: Settings 2022-02-01 00:57:31.584 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/keyboard/Keyboard.lua' 2022-02-01 00:57:31.588 DEBUG LuaGUI: Input: File[./Config/Input/UiLayer/keyboard/default.lua] opened successfully! 2022-02-01 00:57:31.591 DEBUG LuaGUI: Input: File[C:\Users\Kalle-Erik\Saved Games\DCS\Config/Input/UiLayer/keyboard/Keyboard.diff.lua] opened successfully! 2022-02-01 00:57:31.591 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/keyboard/Keyboard.diff.lua' 2022-02-01 00:57:31.591 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/joystick/Throttle - HOTAS Warthog.lua' 2022-02-01 00:57:31.591 DEBUG LuaGUI: Input: File[./Config/Input/UiLayer/joystick/default.lua] opened successfully! 2022-02-01 00:57:31.593 DEBUG LuaGUI: Input: File[C:\Users\Kalle-Erik\Saved Games\DCS\Config/Input/UiLayer/joystick/Throttle - HOTAS Warthog {45502A90-B986-11eb-8008-444553540000}.diff.lua] opened successfully! 2022-02-01 00:57:31.593 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/joystick/Throttle - HOTAS Warthog.diff.lua' 2022-02-01 00:57:31.593 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/joystick/Joystick - HOTAS Warthog.lua' 2022-02-01 00:57:31.593 DEBUG LuaGUI: Input: File[./Config/Input/UiLayer/joystick/default.lua] opened successfully! 2022-02-01 00:57:31.594 DEBUG LuaGUI: Input: can't open 'C:\Users\Kalle-Erik\Saved Games\DCS\Config/Input/UiLayer/joystick/Joystick - HOTAS Warthog {BCFD8BD0-B974-11eb-800D-444553540000}.diff.lua' 2022-02-01 00:57:31.594 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/joystick/Joystick - HOTAS Warthog.diff.lua' 2022-02-01 00:57:31.594 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/joystick/F16 MFD 1.lua' 2022-02-01 00:57:31.594 DEBUG LuaGUI: Input: File[./Config/Input/UiLayer/joystick/default.lua] opened successfully! 2022-02-01 00:57:31.595 DEBUG LuaGUI: Input: can't open 'C:\Users\Kalle-Erik\Saved Games\DCS\Config/Input/UiLayer/joystick/F16 MFD 1 {946FE750-B986-11eb-800A-444553540000}.diff.lua' 2022-02-01 00:57:31.595 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/joystick/F16 MFD 1.diff.lua' 2022-02-01 00:57:31.595 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/joystick/Saitek Pro Flight Combat Rudder Pedals.lua' 2022-02-01 00:57:31.595 DEBUG LuaGUI: Input: File[./Config/Input/UiLayer/joystick/default.lua] opened successfully! 2022-02-01 00:57:31.596 DEBUG LuaGUI: Input: can't open 'C:\Users\Kalle-Erik\Saved Games\DCS\Config/Input/UiLayer/joystick/Saitek Pro Flight Combat Rudder Pedals {455051A0-B986-11eb-8009-444553540000}.diff.lua' 2022-02-01 00:57:31.596 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/joystick/Saitek Pro Flight Combat Rudder Pedals.diff.lua' 2022-02-01 00:57:31.596 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/joystick/F16 MFD 2.lua' 2022-02-01 00:57:31.596 DEBUG LuaGUI: Input: File[./Config/Input/UiLayer/joystick/default.lua] opened successfully! 2022-02-01 00:57:31.597 DEBUG LuaGUI: Input: can't open 'C:\Users\Kalle-Erik\Saved Games\DCS\Config/Input/UiLayer/joystick/F16 MFD 2 {BCFD3DB0-B974-11eb-8008-444553540000}.diff.lua' 2022-02-01 00:57:31.597 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/joystick/F16 MFD 2.diff.lua' 2022-02-01 00:57:31.597 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/mouse/Mouse.lua' 2022-02-01 00:57:31.597 DEBUG LuaGUI: Input: File[./Config/Input/UiLayer/mouse/default.lua] opened successfully! 2022-02-01 00:57:31.598 DEBUG LuaGUI: Input: can't open 'C:\Users\Kalle-Erik\Saved Games\DCS\Config/Input/UiLayer/mouse/Mouse.diff.lua' 2022-02-01 00:57:31.598 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/mouse/Mouse.diff.lua' 2022-02-01 00:57:31.598 DEBUG LuaGUI: Input: can't open 'C:\Users\Kalle-Erik\Saved Games\DCS\Config/Input/UiLayer//modifiers.lua' 2022-02-01 00:57:31.598 DEBUG LuaGUI: Input: can't open 'C:\Users\Kalle-Erik\Saved Games\DCS\Config/Input//modifiers.lua' 2022-02-01 00:57:31.598 DEBUG LuaGUI: Input: File[./Config/Input/UiLayer/modifiers.lua] opened successfully! 2022-02-01 00:57:31.599 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/keyboard/Keyboard.lua' 2022-02-01 00:57:31.599 DEBUG LuaGUI: Input: File[./Config/Input/UiLayer/keyboard/default.lua] opened successfully! 2022-02-01 00:57:31.600 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/joystick/Throttle - HOTAS Warthog.lua' 2022-02-01 00:57:31.600 DEBUG LuaGUI: Input: File[./Config/Input/UiLayer/joystick/default.lua] opened successfully! 2022-02-01 00:57:31.601 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/joystick/Joystick - HOTAS Warthog.lua' 2022-02-01 00:57:31.601 DEBUG LuaGUI: Input: File[./Config/Input/UiLayer/joystick/default.lua] opened successfully! 2022-02-01 00:57:31.603 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/joystick/F16 MFD 1.lua' 2022-02-01 00:57:31.603 DEBUG LuaGUI: Input: File[./Config/Input/UiLayer/joystick/default.lua] opened successfully! 2022-02-01 00:57:31.604 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/joystick/Saitek Pro Flight Combat Rudder Pedals.lua' 2022-02-01 00:57:31.604 DEBUG LuaGUI: Input: File[./Config/Input/UiLayer/joystick/default.lua] opened successfully! 2022-02-01 00:57:31.606 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/joystick/F16 MFD 2.lua' 2022-02-01 00:57:31.606 DEBUG LuaGUI: Input: File[./Config/Input/UiLayer/joystick/default.lua] opened successfully! 2022-02-01 00:57:31.607 DEBUG LuaGUI: Input: can't open './Config/Input/UiLayer/mouse/Mouse.lua' 2022-02-01 00:57:31.607 DEBUG LuaGUI: Input: File[./Config/Input/UiLayer/mouse/default.lua] opened successfully!

I just received mine, and I tried it out on DCS with the F-16, UH-1, and the F-14. I have not altered the settings at all, and I use mine in a USB mode. I'm using SimShaker for Aviators. The default vibration on a level flight in 1G is pretty significant. What settings alters that? In addition, I don't really feel the touchdown on a runway at all, since the default vibration is high enough. While flying, I changed the "engine rumble/piston beat" to 1 instead of 50, and no apparent effect.

Is this problem related to Reverb G2 seizing SteamVR, and Cliffhouse launching while DCS crashes as SteamVR is hung? The headset never truly dies, it just shows a frozen DCS image then cliffhouse, and it seems SteamVR hanging is teh cause of the crash. Seems to be most produced by having a SteamVR notification popping up, or calling the Action Menu up.

While I'm definitely interested about this one for DCS, does it work in MSFS2020 too?

I figured out the problem. You have to go to Windows MR dev settings and headset settings, and disable "pause simulation on freeze" and other similar options that make the game freeze when headset has hiccups. This happens even when headset is unplugged, as long as WMR apps remain installed.

I have tried the game on two different SSDs. At this point I have spent thousands on updating every single piece of hardware I own so that I can fly DCS. Yet, I can't. And the problem could be a part of an unknown problem experience by many users, with no known solution. Pretty damn depressing idea.