Pyrocumulous

I'm right on the coast about 150 meters from the crashing waves, so constant salt exposure that corrodes everything that is metallic. Pretty much what a real carrier-based HOTAS would be exposed to. I haven't been covering the controls, clearly I should have. I assume you are suggesting dielectric grease; can I just coat the potentiameters and button contacts? I've been just cleaning them with isopropyl alcohol and then reassembling, as I was concerned about grease at least while under warranty. So far, no problem with the main axis on the Warthog HOTAS or Throttle, but issues with the other axes and buttons.

Confirmed that this occurs with GBU-38, GBU-54, GBU-31 on cold start only. CBU-103 and CBU-105 are not affected, which makes sense as they are not GPS-reliant. Track attached. A10C-jdam_align_test.miz a10c-jdam-align.trk

Works great now, thanks @mbucchia

Looking at DLSS in VR reminds me how amazing Quad Views already is.

Can confirm that this error has been resolved in DCS 2.9.0.46801 Open Beta

Is there any particular set of controls (throttle, HOTAS, rudders) that is more corrosion resistant than the Thrustmaster Warthog gear I currently am using? I'm in a highly corrosive environment that's just eating these things up, causing me to lose buttons and axis. These are only 18 months old and I'm getting pretty tired of disassembling to get to some troublesome potentiameter. Being under warranty isn't all that useful, I'd rather everything just always work.

I just completed the initial A-10C training, so could totally be operator error, but in Iron Flag mission 1 I can't get ground crew to respond to calls to remove wheel chocks or refuel/rearm once the jet is started. Prior to start up, Ground Crew responds and does the job. DCS World 2.8.8.43704 OB MT. Tracks in Drive link: https://drive.google.com/file/d/1EXMmHPhAuzmbQIwdLcr4i2WlXPr2Fun1/view?usp=sharing edit / solution: Apparently, one has to activate the intercom on the intercom panel, per page 181 of the manual. I can't seem to get the intercom to work properly, but cracking the canopy open does the job.

I should have been more specific, it's the JTACs in Iran that aren't talking back. FM versus AM would likely explain the radio looking busy, but no audio coming out. Like you say, one doesn't need the JTACs jabbering away.

I can't seem to ever get the JTACs to respond to me, despite being tuned to the proper frequency identified on the kneeboard. I see the proper JTAC listed on the comms menu, and I can do the check-in, but they don't respond. The radio does appear to be busy, but I don't see message text and don't hear anything. I do see this in the DCS.LOG, which seems to match up: 2023-10-05 21:07:46.955 ERROR ED_SOUND (29012): can't load wave: "speech\eng\common\allied flight\usa\1\effects\aircrafts\cockpits\radioclickbefore.wav" 2023-10-05 21:07:46.955 ERROR ED_SOUND (29012): can't load wave: "speech\eng\common\allied flight\usa\1\callsign\devil" 2023-10-05 21:07:46.958 ERROR ED_SOUND (29012): can't load wave: "speech\eng\common\allied flight\usa\1\effects\aircrafts\cockpits\radioclickafter.wav" Example screenshot from STAGE 6 65 perf.miz with clear line-of-site to Bandar Abbas, but I haven't been having success on any the JTACs on any of the missions that I have completed. That's generally not a problem, since the AI wingman is so awful at CAS that I self-assign CAP and SEAD missions, but it's odd.

Makes my head hurt just trying to think about trying to make dynamic missions work! Your explanation above about real-time air defense levels explains what just happened: I "forced" the Jask SA10 to come up by getting out east far enough to get an RWR hit before the Kerman SEAD strike occurred, and then back to Texaco3 for fuel, and then made the low-level SEAD run into Jask, but only got an RWR hit from the SA6 site. I did happen to stumble across the SA10 and destroy it with rockets and guns but it never responded, presumably because the defense level had dropped as a result of the Kerman SEAD strike.

I fixed the Drive sharing permissions and added a similar track for STAGE 7 80 perf.miz with Air Defense at 50-60% on DCS World 2.8.8.43704 OB MT. Devil 1-2 hit the Abu Musa Rapier site but didn't kill it, and then the A-10s destroyed it, which seems to have prevented the Jask S10 from spawning, but not the S6.

On STAGE 6 85 perf.miz with Air Defense at 70-80% on DCS World 2.8.8.43704 OB MT. I've been struggling to get my AI wingman to attack the ground target that I intend, so was experimenting with trying to get him to take out that Bandar Lengeh SA6 but without much luck so I happened to notice in reviewing Tacview that when I give up and take it out for him, the Bandar Abbas SA10 is not present. Here's a couple of Tacview recordings as well as a screenshot that I took to verify that I had correctly set the Air Defense while sitting at 8000' trying to get an RWR hit to locate the site. https://drive.google.com/drive/folders/1Wem6TlvJASldmwB47LhZ4OaGFIYCABRZ?usp=drive_link

I've been noticing that if destroy a SA6 and then sneak up to the SA10, it's not present. Is that intended or is that a bug?

Nice work, that’s no small task!

Minor issue, but Devil 3 CAP F appears to have callsign Devil 11 and 12 in STAGE 6 85 perf.miz I'm impressed and shocked that despite the number of permutations, this is the only mismatch that I've noticed. Well done!

Tested in DCS 2.8.8.43704 Open Beta MT and ST, pancake-mode and PimaxXR, all exhibit the same behavior: setup a bomb (CBU-99, MK-20, Mk-82 all tested) in the F/A-18C Hornet with interval release, then select 82P TALD while in A/G Mode. Instantaneous crash every time in my experience. Setting up the bomb in single release or multiple (non-interval) mode does not cause a crash. Similarly, entering A/G mode once TALD is already selected does not cause a crash. TALD-test.mizdcs-TALD_crash_example.log

I am experiencing the same error, causing DCS to crash and leaving this at the end of the log: ERROR ED_SOUND (24252): can't load wave: "speech\eng\common\wingman\1\effects\aircrafts\cockpits\radioclickbefore.wav" ERROR ED_SOUND (24252): can't load wave: "speech\eng\common\wingman\1\effects\aircrafts\cockpits\radioclickafter.wav" Every time it happens, I am selecting TALD in the FA-18C Hornet. Full / slow repair made, no mods. DCS World 2.8.8.43704 OB MT, PimaxXR

You are correct, I see it listed under Group for each aircraft on the F10 map. E.g. "DEVIL 4 CAS H" It's also buried in the message history, but F10 is certainly the easier way to verify prior to launch. Still super easy to accidentally RTB a flight when I go too rapidly on the Push commands, but that appears to be resolved by just counting at least 5-seconds after the prior flight confirms command on radio.

Sometimes either I mess up or one (or more) of my flights go on the wrong objective, or perhaps something goes wrong in the F10 menu. Not sure. Either way, is there a way to see what orders were actually applied early in the mission. It's frustrating to realize after flying the entire mission that Devil 3 was off on some suicide mission all by themselves. It's obvious in Tacview after the fact, because I can see their tasking right there in the label for each aircraft. Brilliant campaign, well done!

Thanks @ChillNGand @BIGNEWY, removing Tacca's NVG mod resolved the crash. Glad that fixed it, unfortunatly that mod fixes the square-artifact issue in NVG when using Quad-Views-Foveated

Two pointers are appearing in VR right eye, and only one in left eye when in single threaded mode. The one that appears to be smaller in the right eye is the "real" one that that actually does things, but big one does nothing. Only the big non-functional pointer appears in the left eye. This is with DCS 2.8.8.43704 Open Beta ST with PimaxXR. I have no idea if this is new, as I always play in MT, but I am trying to figure out a weird but unrelated AV-8B bug.

This is a weird one, and doesn't seem like it could be mission related, but I have not been able to recreate it in custom missions so perhaps? In Mission 10 part 2, as I acquire the first waypoint, when I double-tap the Sensor Select Switch to enter Targeting Pod HOTAS mode it usually crashes DCS World. This is with 2.8.8.43704 OB MT. I flew all of the previous missions on a previous DCS version, but never had a single crash. Only mod is Tacca's NVG mod. Running VR through PimaxXR.

Not mission breaking by any stretch. Great mission, looking forward to Part 2! Tacview-20230814-115811-DCS-Kerman Mission 10A FINAL.zip.acmi

Before switching to the RTX 4090, I used a Radeon RX 6800XT. No real complaints, and it can handle Reverb G2 resolutions at a reasonable frame rate, and the RTX 4090 is definitely more than is needed for the Reverb. Radeon RX 6950XT is pretty excellent bang for you buck at this point. That said, there are some good reasons that nearly all VR is on nVidia GPUs. Radeon doesn't support foveated rendering at this time, and that would be a no-go for me if specifically building for VR. Lack of VRSS support means that at this time Radeon is not compatible with Varjo headsets, and hasn't been compatible with Pimax. I believe DLSS is on the roadmap for DCS World, which also is Nvidia-only. Another option to consider is RTX 3090 ti, particularly on the used market.

This question is in regards to the update on lens options for the Pimax Crystal: https://pimax.com/crystal-notice/ A glass 35ppd lens is the standard. My understanding is that we have the choice of either an additional polycarbonate 42ppd lens or a glass "wide FOV lens." Frustrating that we don't know what "wide FOV" really is, nor an option of glass for the 42ppd. Strictly for DCS World, what are your thoughts on what is ideal? Do you think it depends on flying modern jets with radar versus the warbirds? I've been flying with Reverb G2. and I am definitely looking forward to the higher resolution and larger sweetspot for spotting aircraft. Should the polycarbonate versus glass be a factor? I believe that I could eventually acquire all three, but for now, trying to figure out which option to select.