Jayhawk1971

Yeah, was about to pounce on a 1TB NVMe, now I'm looking at a 2TB.

On the one hand, really glad to get a Sinai map. On the other hand, kinda sad that it's a separate map from Syria, and by a different developer. I was hoping that some time in the future, the "Syria" map could grow to include eastern Egypt, western Saudi and Iraq. Oh well. Maybe, hopefully, I'll live long enough (singularity?) to witness the great-grandchildren of the current ED devs implementing the whole world as a single map.

Would it be possible in a future update to make the setting module-specific rather than "global", so that each value for each individual aircraft is being "remembered" by DCS? In other words, move the slider from the VR tab to the respective module tab in the GUI? That way, users could set the individual values once (for the respective airframe) and not have to change (and remember) settings every time they switch modules.

I've found the thread. This looks quite promising! Apparently he also wants to add FFB rudders? Thanks for the heads-up, that project went completely under my radar.

Logitech G940 HOTAS. Was always going to replace it, now I'm glad I didn't. Especially with the Apache: I have zero trimming issues thanks to FFB. If I had any mechanical skills whatsoever, I would try to fit an extension to it. Alas, I don't dare to.

Odd. Did you compare your logfiles if there's any difference? Would be interesting if they look differently. I'll try the mission again tomorrow and see if it works for me then. Maybe ED snuck a stealth patch in?

Interesting. Did you do anything differently, or change anything (DCS version, drivers)?

Hi, I, too, am now plagued by freezing/ crashing issues. VR user. Mission freezes (with the "waiting..." message displayed) right when "things start to get interesting", as in it seems a major mission trigger event is happening (spawning of many assets?). I'm on the most recent OB patch. Here follow mission spoilers: Log file attached. dcs.log

I meant what Puck said right before that "Phoenix to Sparrow" story, at 22:40. When asked whether the excessive tests revealed new data about the missile's envelope, he answered that their "charts were generally pessimistic...which was good", which I interpret as "the missile performed better than anticipated".

Yep, lots of little gems in there, like the "Phoenix needed altitude, Sparrow needed speed" line.

From the "10 Percent True" Podcast interview with "Puck" Howe on the Tomcat. From the timecode I've "marked" onwards, he talks about the difference between AWG-9 and APG-71, the Phoenix engagement envelope, which is interesting regarding the actual timelines they used. Also he mentions that the Navy had to get rid of all those Phoenix missile stockpiles at the end of the Tomcat's lifespan , and they did it via massive live-fire exercises. He mentions that it turned out their estimates were too conservative, that the missile performed better than anticipated. Listen to the whole thing anyway, as this interview is very in-depth and interesting.

It'll take a while to get used to zero curves on this module at first, but it will pay off in the long run. Just practice flying around in freeflight and get used to the very direct input. I've found that trying to keep the VVI needle centered is good practice. The Tomcat handles like a warbird (think F-86), so it needs a light touch and lots of trimming. Literally two fingers on the stick (I mounted the stick center, and rest my right elbow on my lap while steering with two fingers and the thumb on the trim button). Admittedly, the force-feedback stick is helping a lot with the trimming. In that case, here's what I'd do: try to lineup as early as possible, and "stab forward" with the refueling probe. If you miss, back off a couple of feet and try again. If you see you're moving vertically on the basket, don't chase it. Also, maybe something in this video might help:

I use zero curves, deadzone of 1 or 2 on all axis (with a Logitech G940, no extension). AAR in the Tomcat is not an issue for me, at all. Easiest of the bunch, IMO. For me, the Hornet's too sensitive pitch axis makes refueling harder (not impossible, just less fun). Disclaimer: switching to VR helped immensely. It turned AAR from a dreaded chore to something I actually quite enjoy now. Still, even in 2D it's not impossible, just a little bit harder. Autopilot or other "shortcuts" will not help you. If/once you are able to fly a stable close formation with the tanker, ignoring other "input" once you are in formation (like airspeed, VVI), you'll find AAR not that hard. Find one or two distinct features on the tanker and try to make it/them "stick" to a point of reference on your aircraft (canopy frame, for example). If you can do that comfortably, apply the same principle to actual refueling. Every tanker in DCS has a certain frame of reference to help you line up with the basket. Also, if you switch to A2A HUD, use the right degree number next to the pitch ladder and overlay that with the refueling hose. That'll put you pretty much in the ballpark lineup-wise. Trimming helps a lot. Other than that, keep practicing. Sooner or later it'll "click" for you. Some people say not to focus on the basket, rather to keep it in your peripheral vision. Other's claim the opposite. Whatever you do, do not chase the basket. Take a "stab" at it (quite literally), if you miss, back off and try again. Once you're connected, don't get excited (which I found to be the hardest part ) and stick to formation flying.

Still impatiently waiting for the Nimble Archer F-14A campaign...

Since the most recent campaign I've purchased (Hornet-related) seems to be kinda broken until the next patch, I've decided to once again jump into Zone 5. This time around, though, I'm using the "Maverick and Goose" skin, for maximum realism . Sacrilege? Maybe. But damn fun! Now if I only could get my hands on good Iceman/Slider, Hollywood/Wolfman and ?*/Sundown skins. Edit: *according to the "Top Gun Wiki", Sundown's (LTJG Marcus Williams) pilot was Lieutenant Charles "Chipper" Piper

Did you get Jay as well? Can't wait for this campaign! Seriously, it's very, very hard to wait for this. BTW, on an unrelated note, did you read "Goodbye, Mickey Mouse" by Len Deighton, and if so, how about a Mustang campaign inspired by the book? Who, knows, this might actually push me over the brink into WW2-DCS (got the Mustang, but so far have held off on WW2 stuff - maps and assets - mostly due to lack of SSD space.)

Including Meagan, according to the F-14 Tomcast.

Didn't work for me, unfortunately. I've tried taking off immediately, tried waiting for Blade to hook up and launched as soon as his lights turned on, tried letting him launch before me..... all from Cat 2 and using F10 instead of spacebar. Followed departure briefing to the letter. I do get all the correct voice acting bits, up until the part where Flip says he's doing a 360, so at least I know I'm hitting the triggers. He stubbornly insists on flying BRC on full burner and high AOA. I'll give it one more try tonight, with autostart and initiating taxi to catapults as soon as possible, before the carrier changes course, and see if that works.

I suspect the latter is the problem, as I used Cat 2 in all my attempts (having already been forewarned not to use Cat 3 by several forum posts). I have shelved the campaign until the next patch since apparently M06 is also broken and those issues take me out of the experience. Never got around to finish the first Raven 1 campaign for the same reason, and so far never got around to see how the current state is. I wish ED would find a better solution to coordinate their patches with paid content creators, so that at least they get some form of heads-up regarding gameplay-breaking bugs. And maybe give them the opportunity to release hotfixes outside of ED's official patch cycles.

I've never expected Blade to join up immediately and always went to WP1 as briefed (climb to 2500 then turn 240 IIRC), and I do, and once I'm at WP and checked in hear Flip say that he'll do a quick 360 to have Blade hook up. Then nothing. On the SA page you can clearly see Blade going in the opposite direction (40+ miles away from WP1), and the F2 view reveals Blade "hanging in the air" in full AB and high AOA. I suspect that it somehow depends on how fast the player starts up and takes off, maybe related to the carrier changing course?

I tried all the suggested "fixes" for mission 5 (use F10 instead of spacebar, go to Cat 2, wait for Blade to hook up/ launch first, no SA page until WP1) but Blade still goes off and "hangs in the air" at full burner. During my last attempt, while waiting for Blade to hook up, I noticed the carrier changing course significantly. Maybe that's what's breaking the trigger? What time window does the player have to start up and taxi? I think I've performed the start-up procedure reasonably fast, but maybe autostart would be the answer here?