icuham

I ended up closing Steam out, and restarting, which then caused an auto-update. Now the game launches.

Nothing quarantined and the DCS folder was already an exclusion

Hello, I added the CH-47 today and updated after a couple weeks away. DCS wouldn't boot anymore saying "Important files are damaged, please repair" so I tried a verify in Steam. Same thing. Tried ensuring the DCS folder and the Steam folders are not included under anti-virus, same thing. Here is the log output: === Log opened UTC 2024-08-11 00:57:24 2024-08-11 00:57:24.396 ALERT SECURITYCONTROL (Main): Can't run Steam! 2024-08-11 00:57:24.411 INFO EDCORE (Main): Created boot pool: n:16 2024-08-11 00:57:24.414 INFO APP (Main): Command line: D:\SteamLibrary\steamapps\common\DCSWorld\bin\DCS.exe --force_OpenXR --force_enable_VR 2024-08-11 00:57:24.414 INFO APP (Main): DCS/2.9.7.58923 (x86_64; Windows NT 10.0.19045) 2024-08-11 00:57:24.414 INFO APP (Main): Application revision: 238923 2024-08-11 00:57:24.414 INFO APP (Main): Renderer revision: 25342 2024-08-11 00:57:24.414 INFO APP (Main): Terrain revision: 25357 2024-08-11 00:57:24.414 INFO APP (Main): Build number: 172 2024-08-11 00:57:24.414 INFO APP (Main): CPU cores: 8, threads: 16, System RAM: 65410 MB, Pagefile: 9728 MB === Log closed. What should I try next? Hoping to avoid a complete reinstall. Thanks.

I think I might have worked around it by creating a new shortcut to launch DCS with "bin-mt\DCS.exe --force_enable_VR --force_OpenXR" instead of selecting options in the Steam launch window. Not sure what happened in the last patch to require me to do this to get things on OpenXR again but for now at least it's not crashing, still a black cursor but hopefully that gets fixed sometime I guess. Thanks for the note on the dedicated server, we were doing that previously. Might be time to start again.

@Flappie MT used to be very solid for me but since the last patch I too run ST all the time because there is now an extremely high chance in MT that at some point my VR feed goes black and never comes back. I much prefer MT, but in a 1 hour session I'm almost guaranteed to hit this at least once and I'm usually the game host, so I can't have that level of instability. Game is running fine, so everyone else can continue... but my VR somehow desync's is the best I can describe it. Only on MT, really hoping whatever was introduced in that patch goes back to normal later.

@Dscross It is useful in CSAR! You do you! We have it working in CTLD & CSAR, and we even have paratroops dropping by patching the BRONCO and adding another script. I'll drop my current lua script versions here, but be warned they are modified versions (in multiple ways) for use with squad Liberation missions. The patch to add paratroops to the loadout is too large to share directly in the forum. If you have questions send @ Hammer in the Split-Air discord and I can help you with issues. CSAR.lua CTLD.lua para-spawner.lua

Before I go trying each of these.... Do they all pass IC?

+1 Another vote for an option to change this in the settings

Can you share exactly what you did to change this please? I think a lot of us would like this change.

This approach seems completely different from Laidlaw's description of how they flew in Libya, but it certainly makes sense that different approaches would be used by different operators in different contexts. Night lighting in DCS isn't quite realistic yet, and I'm not sure using FLIR only would be a comfortable or enjoyable experience in VR for extended periods. Many of our friends will simply opt out of that rather than deal with the discomfort in game. ...If so many real Apache pilots also showed preference for NVGs with symbology, why would players prefer an experience without it? I'd rather have a workable solution that players enjoy in the game even if not all Apache pilots employed it. If that's not SDU, then either Laidlaw's solution of a single monocle or fixing the NVG FOV in VR seem like options that would make the experience more enjoyable for a player.

@TalonfoxThis sounds like a decent real life solution where you could see past the NVG edge by looking down, and didn't yet have an SDU available. It seems like IRL the FOV vertically of something like ANVIS should be about 40 degrees. In DCS VR the entire field of view is pretty much full of NVG (ie. >90 degrees in an HP Reverb G2) so with this filled we still have to raise the goggles in DCS to see the MPD video page right? Since you wouldn't have to lift the NVG in real life, the present NVGs in DCS aren't even a sufficient solution without the ability to see past them, imo. If we could see past them (as you can in the Gazelle) then this suggestion is a somewhat more workable solution, but even the US Army seems to have concluded that it could have been better... A note from the report attached above - there was a split opinion in RL pilots about ease of use looking under the NVGs and an overwhelming preference for NVGs with symbology (94.7%): "To further understand the use of MPD displayed flight symbology, pilots were asked to state the ease with which they could view the data while using ANVIS. Recall that pilots wearing the ANVIS system must look below/under the HMD to view the aircraft’s MPD. The responses were nearly evenly split between “Fairly easy,” 12 (31.6%), and “Fairly difficult,” 10 (26.3%). Of the remaining responses, 5 (13.2%) respondents report viewing is “Very easy,” 5 (13.2%) reported a “Neutral” response, 3 (7.9%) reported viewing is “Very difficult,” and 3 (7.9%) reported they did not use symbology, up from two reported on the previous survey question. figure 32 shows the complete results for this survey question." "The U.S. Army countered these problems by allowing the use of NVGs in the AH-64 cockpit while scheduling a modernization of the IHADSS’ infrared imaging system, in essence allowing the AH-64 pilot the “best of both worlds,” image intensification and infrared." <- Just like the 94.7% of pilots above I think most DCS players would like this solution too, especially given that the system was deployed. Might even help us avoid headaches from bright lights in one eye and darkness in the other in game too.

Presently, the AH-64 offers the IHADSS or night vision goggles but with NVGs on it's not possible to see any flight and targeting symbology while using the NVGs. The pilot is left with only IHADSS in a single eye, or must constantly switch back and forth between NVGs and IHADSS, which isn't ideal. In real life this has been overcome using a couple of options, at least one of these should be made available in DCS: Option 1: Single NVG monocle for left eye in addition to IHADSS in right eye. This solution is described in "Apaches Over Libya" by Will Laidlaw: "Over my left eye I brought down a single Night Vision Goggle (NVG) tube attached to my helmet. The left eye now had two jobs: look inside at the MPDs and look outside through the NVG. The right eye continued interpreting the HMD symbology with infrared video superimposed from the FLIR mounted on the nose of the aircraft..." This solution would be well implemented if it allows VR users to look 'underneath' the monocle as you can in the SA-342 so that your left eye can read the MFD in the lower view and see an NVG view in the predominant upper view. Option 2: Implement a dual-eye Symbology Display Unit (SDU) This solution is described in "USAARL Report No. 2007-05 Apache Aviator Evaluation of Dual-Technology Night Vision Systems in Operation Iraqi Freedom (OIF) Urban Combat (Master’s Thesis)" By J. Kevin Heinecke (UTSI) Clarence E. Rash (USAARL) Richard Ranaudo (UTSI) Keith L. Hiatt (OCS-FORSCOM) available here: https://www.researchgate.net/publication/290612345_Dual-sensor_use_in_the_AH-64_crew_station_for_urban_combat_in_operation_Iraqi_freedom/link/5b79d098a6fdcc5f8b55a2c5/download "The U.S. Army has temporarily authorized the use of an improved version of NVGs modified for use with a symbology display unit (SDU). The SDU mounts to the pilot’s visor and provides the NVG wearer with full flight symbology representation identical to that provided by the IHADSS. An additional feature of the SDU design is that it allows for line-of-sight acquisition use of the aircraft’s onboard weapons system (U.S. Army Research, Development and Engineering Command, 2005). This system is only authorized for use by units operating in the combat theater and at the discretion of the individual commands." More info is required but this solution seems to offer a dual eye NVG system with the full IHADSS symbology overlaid on the right eye view which may minimize eye strain for VR users in DCS night missions. The same solution of offering a small space to look 'underneath' the goggles to see MFDs may work well here too. Perhaps these could be selected as cockpit options in the specials menu at some point. USAARLTR2008-05.pdf

When an AI AH-64 starts up at night on the Tarawa it's landing light comes on and can be seen reflecting on the water in front of the ship as well as off the deck in front of the helicopter. It should not be visible in front of the ship since the deck is in the way. ApacheLightThruTarawa.mp4

This has happened to me too. When I get stuck in the mud I use the reverse thrusters to rock it back and forth until I get enough momentum to get out. It sounds like I'm joking, but I'm not.

As @Rudel_chw mentioned, A-4 mod was the one I began messing with while trying to understand how to add them myself. The A-4 luas define the gunpod with what seems to be locations for the muzzle and shell ejection. The A-4 also requires a secondary arming panel for the gunpod beyond the "guns" switch so some additional complications there that might mean the HIPEG isn't a good base to start from... I stopped trying to modify things when I realized I would need to add the guns into the MFD logic and couldn't quickly sort out the connection from the MFD to the weapon. Wikipedia, for what it's worth suggests, the A-29 has been equipped with a GIAT M20A1 (The Gazelle in DCS uses a GAIT M621 which appears to the cannon encased in the M20A1 pod, but I couldn't get the CLSID from it's luas, let alone mod the appearance.) as well as M134's experimentally. The M134 can be mounted as an underwing option for the A-29 easily enough but I can't fire it without the MFD integration. I also thought about trying a UPK-23 because it seems like those might be everywhere and an easy test to stand-in for the M20A1 without the M621 CLSID. The MB-339 mod implements an AN-M3 and a DEFA 553 which might be another place to look. I'd be interested in contributing some time to help figure this out too, but I'm not sure where to start with the systems modeling and logic. Would need a hand starting out. UPDATE: I got the MB-339 pods added by importing the gun pod definitions to A-29.lua, allowing WPN_WEAPON_TYPE_IDS.AG_GUN in weapon_system.lua and making a few tweaks to include a mode of continuous fire based on a salvo... first steps.