Roosterfeet

Could some kind soul look at this and tell my why my engine failed at 19:05:55? I have no idea what I did wrong here. As far as I can tell, all the gauges looked great until the the engine suddenly lost RPM. This was in Reflected's BNBOB mission 5. Sorry the track is so long but I can't replicate this with short track. nullnull P51engine fail.trk

Just picked up the P-51 would you recommend flying this or Blue Nose Bastards first?

Seems much better. Hovering with att and alt hold feels much more stable and I can even yaw the aircraft while hovering. Before I felt like the aircraft was fighting me with or without hold modes enabled. Tonight I was able trim to a hands free hover without hold modes. Never been able to do that before.

I'm 2 missions in and the campaign is great so far but I'm pretty sure I'm gooning up the landing pattern at H4 real bad. It's hard to descend in the pattern described in SPINS with enough speed for an overhead break without straying over town below the altitude restriction. Can anyone share a detailed description or video of it being done properly?

With my RTX 4070, 2D at 2560x1440, sharpening 0.5, I've found that TAA produces less ghosting than DLAA and less shimmering than MSAA 4x and with better performance than both. For me TAA at 1440 seems like the sweet spot image quality wise for now. Just thought I would contribute a data point. Update: My initial impression in the cockpit was that TAA produces noticeably less ghosting than DLAA on MFDs in particular. After putting some hours in, I've found lots of places where TAA produces massively more ghosting than DLAA, particularly in external views. I'm going to try DLAA for a while; I suspect that the overall result will be superior despite a little MFD weirdness.

This was a truley excellent mission. I particularly liked the graphic novel approach. I sincerely hope you make more.

Speaking of double-ugly loadouts. How do you trim for that so you're not fighting a hard bank off the cat? I set my trim for that with a best guess which is usually wrong.

Good point about the actual difference in clock speeds. I am running a stock cooler on a 65W processor at the moment. Any recommendations on what kind of cooler I would need for a 5800X3D? I do no significant overclocking. I run everything at default bios setting except for loading the xmp profile that came with my ram.

I recently upgraded my GPU and I've been noticing stutters in CPU intensive missions like those generated by Liberation. I will briefly become main thread limited and there will be a short dip in frame rate. The x3D processors have overall better gaming performance vs their non 3D vcache counterparts but I'm wondering if I wouldn't be better off with a higher clock speed instead for the DCS main thread bottleneck that I'm seeing.

Infantry no longer smoke when injured or killed I wish they had taken their time with that one. I'm going to miss my favorite bug.

I feel much better about this plan.

I recently replayed this in MT and was able to work around most of the DCS AI problems. Don't let your wingmen do anything unless you absolutely have to. In mission 3, hit all of the targets yourself. In mission 11, rearm yourself with 4 JSOWS at mission start and hit the coordinates that you have tell smoke to hit yourself. In mission 14a. launch from Cat 1; if the mission does not complete after the "Bug southwest" message, skip the mission and play 14b. which resumes at that point. If something is clearly broken and not progressing I suggest you RTB just for fun and skip to the next mission.

I think the mission is supposed to end after the "Bug Southwest" message. Just skip it and play part 2 which starts at "Bug Southwest."

Couldn't get the MK20's to hit close enough from above 10k so I change my loadout in the mission planner to ugly with 2xGBU-12. That did the trick but if anyone can consistently hit targets from above 10k with MK20's I'm all ears.

Some indication of G's aside from blackout would be really helpful for ACM. In particular it's important to be able to tell if G is increasing or decreasing while tracking a bandit. Something like an optional color change or bass tone with a variable pitch might work. Personally, I would be happy with nice big numbers in the corners of the screen. Here's an example of a renowned F-14 pilot really struggling to control the aircraft during ACM in DCS because he doesn't have a lot of time in DCS and since he can't feel the G load like he would in real life while tracking a bandit, he has a strong tendency to pull too hard and stall. It's a great instructional video, btw.

Wild guess: you have a two stage trigger and both stages (button 1 and button 2) are both bound to "Trigger."

In my experience spotting is easier at 1080 but cockpit instruments are easier to read at 1440. If your playing on a competitive multiplayer server with no labels or only dot labels then 1080 might be preferable. Single player, if you don't mind turning on labels once in a while (I have a key bound), you may prefer 1440. Also, you still get the large pixel spotting benefits if you play at 1080 on a 1440 monitor, it just doesn't look as nice as as it would if it were native resolution.

I find that DCS looks noticeably better at my monitor's native resolution. When I got my 1440 30" monitor, I discovered that I preferred to turn some graphics options down rather than play at 1080. 1080 content on a 1440 monitor looks blurry in a way that 1080 content on a 1080 monitor does not.

I ran into this and never got the mission complete message after the "Bug southwest" message, probably because I didn't launch from CAT 1. Also my dash3 and dash4 launched around push time and never caught up. Playing the second half (mission 15), I strongly suspect that the SU-33 is way more dangerous than it was when the campaign was first released. After repeated failures to get to the merge, I finally shot him down when I turned labels on and saved my AMRAAM to give him a pitbull in the face while I defended his AA-10. Overall this is still a really good campaign. I managed to complete all the missions without skipping, except for 14 which wasn't really a big deal. (I took 4 JSOWS and did all the work myself in 11). It just needs a little love to safeguard against ED's wonky AI finding new and creative ways to break triggers.

The RTX 4060 is rumored to be coming in April and I'm curious to see what it looks like. The answer might be buy a RX6800 but it's hard to say before they release the specs. As of right now I would say that AMD cards are a far better value but DCS prefers Nvidia. I bought a RX 5600XT a few years ago and I've been disappointed in the graphics problems (looking at you partial black screen flashes) that keep popping up in DCS.

Just took control of your track and confirmed that "\" does not work. I was able to proceed though. Try this. Bind keys or a HOTAS button to "COMM Switch - COMM 1 (call radio menu)" and "COMM Switch - COMM 2 (call radio menu)." Use one of those keys to open the comms menu. Now that I think about it, I may have used a COMM Switch Key yesterday as well.

A few seconds after the start of the mnullission you should be able to bring up the coms menu select "F10. Other" then "F1. Skip first part." That should start you with full fuel behind the tanker. Hopefully the track file will be short enough to post. I really think that would help. Other than that. Make sure you have "easy communications" and "Presets: no force from mission, use mine" disabled. Uninstall all mods including Viacom or Voice Attack. Run a full repair after uninstalling mods. Also don't touch the backspace key, that apparently can mess with scripting for some reason.

By "hangs," you mean you can't advance the mission or DCS freezes and won't respond? I just flew this using single thread in the current OB without skipping the first part of the mission and it worked fine for me. Pretty sure I used the \ key to bring up the coms menu to select F10. You might check your key bindings to make sure nothing is conflicting with the coms menu or F10. Assuming DCS isn't crashing, If you start the mission from the tanker, and quit after encountering the problem, your track file might be small enough to post here which could be helpful. Also, if you find your way past that issue, It's probably best to do everything yourself so Smoke doesn't wander off to Iran.

It would be great to have more moving map resolutions supported by DCS aircraft. For instance, the F-18 can only display the map when the HSI or SA page is set to 10 miles. The map is blank at 20 and 40 nm.

This is a constant headache for third party campaign creators and I suspect that the only real solution is for ED to get serious about the Stable version being an actual stable version where the AI has been thoroughly tested and works as intended so that the missions they sell don't break. Right now stable is in no way more reliable than the the open beta; it has fewer features and the bugs are older. It's no wonder that everyone ignores "stable" in favor of beta.