Jayhawk1971

Now that you guys mention it, when it happened to me, I also had launched a VR session from the ME. Mission crashed after startup as well, but in the F-14, on the carrier.

I'm on my usual setup/ device, and I have created an exception for the DCS folder in my firewall. I sometimes do experience a "connection hickup" on my DSL, though, for example websites not loading or YouTube videos getting "stuck" for a couple of seconds. Could that be a reason for a 401 error?

Hi, I had the same problem during my last time playing: 2025-06-03 00:20:02.167 ERROR ASYNCNET (7512): The session has expired (401). Exiting... I ran the logfile through the Discord test-thingy, and it came up with a warning that my GPU driver was causing a problem, I have updated since but have not gotten around to play DCS yet. Still, since others are having the same issue -at exactly the same time - all of a sudden (first time for me ever, and I've been playing DCS for years), and having completely different drivers than most (NVIDIA Quadro), I doubt that issue is driver related. Something must have changed recently that would cause this issue, I presume. Edit: could this be system time related? CMOS battery could be out of juice maybe? dcs.log

Thanks for checking. I actually do wait for the carrier to have its turn finished before doing anything other than setting oxygen, ICS, mils and ammo counter. Oh well, maybe it really is VAICOM interfering somehow. I'll try one more time by starting directly from the ME. It's not that big of a deal, it makes the mission more difficult, but not impossible to finish successfully.

Could someone do me a favor and check this mission again? I need to figure out if the issue I'm having is on my side. My issue is with the A2G part of the mission, and I have had this since the beginning. When nearing Pagan, I experience what the instruments tell me appears to be very high wind speeds. FPM is way to the right of the HUD, and there's a discrepancy with the heading indicator. Also display says wind speeds between 60 and over a 100. Only over Pagan. It sometimes causes LGBs to miss the boat(s), and makes the subsequent strafing very challenging. Incidentally, displayed wind speeds are lower the farther away I get from Pagan. Aliens maybe? Could it be an INS/ alignment problem? I'm waiting for the carrier having finished its turn into the wind before even connecting the power. I'm running vanilla DCS, except for VAICOM. The issue has been persistent for me ever since I got the campaign. None of the many patches/ updates nor multiple slow repairs I've done since have made a difference. I can't find the post anymore, but IIRC someone floated the theory some time ago, that since this mission is under EMCON conditions, the alignment process could be borked? Leaving the power connection on until ready to taxi didn't really do anything, though. Here are some screenshots that I hope can help illustrate the issue. I'm using VR, so the screenshots aren't very good. I would very much appreciate if someone could refly the mission and report back. Back when I first noticed, I did exchange PM's with another DCS user who back then experienced the same issues. Oh, and this is the only mission I am experiencing this, not only in this campaign, but generally.

One major drawback of those being randomized is that, for example, in the RAG part of the "Speed and Angels" campaign, those modifications often change with each loading of a different lesson (or replaying the same lesson), which is somewhat defeating its purpose of adding immersion.

Here's a real-world example for why it is always a good idea to check if your Sidewinder volume knob is up.

Turn your exterior lights on when hooked up to the catapult, that is the launch signal at night. Set the switches on your right console to on prior to taxiing to the catapult (I always switch everything on, bright, flash), but keep exterior lights off via the master lights toggle switch until you are hooked up and ready to go. Once you are ready to launch, use the master toggle to turn lights on. That should initiate the launch sequence.

Exclusively at Toyosu Market - 豊洲市場 - in Tokyo. I mean, where else could you possibly buy a DLC map for DCS?!

"Paco" Chierici, via Reflected's Speed & Angels campaign. It's in the campaign doc for mission 6.

Specifically for the Tomcat, as a rule of thumb, try to not exceed 15 units of AOA when turning, or you'll rapidly lose energy. Pay attention to the audio-visual feedback HB baked into the module, this will give you hints as well regarding your energy state. Don't fly lead/ pure pursuit until you are in a good position to take a shot. Other than that, practice. Learn how to modulate stick input. Your best rate turn in the Tomcat is 307Kts at 6.5g. I'd set up a simple exercise where you try to hit those numbers. You'll develop a feel for that eventually (probably easier IRL, as you don't feel acceleration/ deceleration and g-forces in DCS). FFB stick helps a lot!!

H-34/ S58, the Volkswagen T2 of helicopters....

Don't forget drunken hords of "Ausscheider" with the white sweatshirts.

Yes, and in the F-15E. Both modules are from 3rd party developers though, so my question was whether ED would be starting to implement a similar function for their own modules, starting with the new (and great-looking) new pilot model for the A-10C II.

Is this functional (as in, tinted visual effect in first person view), or strictly cosmetic for external view?

Alpha Jet OV-10A, B (Luftwaffe) SEPECAT Jaguar Dornier DO-28D (also DO-27 until 1980)

I would have absolutely no problem with a "watery" North Atlantic /GIUK map. Recreating the REFORGER part of a Cold War era scenario with the Navy trying to protect convoys headed for Europe from Soviet raids, or liberating Iceland from Soviet occupation would a lot of fun, especially in the form of Reflected/ Baltic Dragon-style SP campaigns. Basically Red Storm Rising/ Hunt for Red October - the map.

Of course I'm not blaming you for asking. From my POV, the more modules, the merrier.

Highly doubtful that ED will ever consider doing niche experimental aircraft like the F-16XL, as the potential market for such modules is probably too small to be financially viable. As has been pointed out by Wags several times in numerous videos/ interviews: modules need to make sense economically for ED to consider making them. The F/A-18E/F would be much more likely, and I suppose it's rather a "when" than an "if". Once ED feels they are no longer creating unnecessary competition for their legacy Hornet module. I for one would very much welcome a whole "DCS: Test Pilot" module, set in an expanded Nevada map (Edwards AFB), where you can fly all relevant X-planes from the late 1940's onward. DCS: Chuck Yeager, if you will. But I suppose that's very niche, and therefore not financially viable. Maybe a 3rd party would be interested, though?

Hopefully this is a "lost in translation" issue, and you didn't really turn off your firewall?! You just need to create an exclusion - a whitelist item - for the DCS folder. Other than that, you better leave your firewall up and running.

Cool with me. Bayxit FTW! An Alpine Republic with Austria and Switzerland would be awesome. Given a choice, I'm sure Baden-Württemberg would join in no time as well. You all would need to call yourselves something other than BRD, though, as it is no longer "Bayern und Restdeutschland".

Very happy with and very much looking forward to the Cold War Germany map! OTOH, a little sad that there's no South Germany planned, so no Fürstenfeldbruck, Memmingen, Lechfeld, Erding....

If I had to make a guess, I'd say HB is aiming for an end of Q2 2026 release, which will get pushed back to the end of Q1 2027. Personally, I'd rather get it in EA later in its development process, with more working features out the door. While it's certainly nice to have a new toy as soon as possible, IMO it can be frustrating when many systems don't yet work as they should, or are still missing completely. Especially if during development some initial features get refined to be more realistic, which will trigger the usual suspects into grabbing their pitchforks yelling that their module is being "nerfed".