-
Posts
848 -
Joined
-
Last visited
About Jayhawk1971
- Birthday December 21
Personal Information
-
Flight Simulators
DCS
Recent Profile Visitors
3778 profile views
-
I just used the PDCheck AR-App to get my IPD.
-
F-14 A/B feature follow-up, wish list and beyond
Jayhawk1971 replied to scommander2's topic in DCS: F-14A & B
The one thing that really changed my mind in favor of pilot bodies (even more so in VR) is the working kneeboard we got with the Viper/ Hornet pilot bodies. This has been a huge immersion boost. I hope we'll get this feature with Heatblur pilot bodies as well, and the sooner, the better. -
My guess is ED's next helicopter will be some variant of the Blackhawk. 85%. But, could we get - at least as an AI - The SH-3 Sea King, to help make an 80's Carrier deck a reality? Pretty please? [Public Domain, https://commons.wikimedia.org/w/index.php?curid=18124459]
-
Anytime, Baby! - F-14 Docu-Campaign Announcement
Jayhawk1971 replied to Reflected's topic in Community News
Did you consider including the still classified "temporal anomaly" incident that - allegedly - happened to the USS Nimitz in 1980? Where Tomcats from VF-84 - allegedly - splashed two RJN Mitsubishi Zeros (that looked suspiciously like re-painted T-6 Texans)? Would be a nice Easter egg, especially the narration could potentially be hilarious. -
You got it all wrong! DCS is irrefutable proof that Spheric Earthers are complete conspiracy nuts!
-
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?!
-
Tips for keeping the energy for dogfighting
Jayhawk1971 replied to WildeSau44's topic in DCS: F-14A & B
"Paco" Chierici, via Reflected's Speed & Angels campaign. It's in the campaign doc for mission 6.