PD919

I just replayed the mission twice. All but one flight started the ascent in both. Track corrupted though.

I heard about a new cooling system last year. Was this implemented yet? What is going to be changed?

Is this normal behavior. The Ai went to the first waypoint at the same altitude they circle the runway. They climbed only after the bombers spawn. This caused my whole flight to be way behind when the enemy fighters showed up.

It makes the cursor disappear. it's mainly used to control camera with mouse.

Experiencing this as well. If you hit Alt+C it still doesn't disappear.

At the start of the mission there is a significant amount of fuel in the fuselage tank. Is this correct because it make the P-51D handle terribly during the scramble. You can close the topic if that was your intention but I think It make the mission more difficult thank it should be.

On a separate note about Multicore. Asobo modiefied their DirectX 11 version of FS2020 and if you had a great Multicore processor your fps and framepacing improved dramatically in 2D and VR. Is DCS moving entirely to Vulkan or will they update the DirectX 11 engine as well. I think updating both will be a net benefit because Vulkan will likely be glitchy at launch compared to adding onto DirectX 11.

I really hope it does. A lot of script and object heavy campaigns cause a lot of stutter because too much is trying to happen on one thread. It because more noticeable in VR because your motion smooth will go wacky or you have intense stutter with no smoothing. DCS is GPU limited in VR but the framepacing issues that stop a constant 45 fps is the real challenge.

I will say that since I play in VR the microstutter is more noticeable then 2d because framepacing is more noticeable. Most of the stutter I see in DCS comes from framepacing not a poor FPS. I have a 5800x and 32 Gbs of RAM. GPU is 3080 Ti for reference.

I just ran a quick test with this from private multiplayer missions I've been hosting from my own PC without a dedicated server to single player missions. The stutter from AI communications and AI spawn was almost completely gone. I feel this would "fix" several campaigns in DCS that are script heavy. It seemed that it was taking all of the script work off of the main DCS core. It's a shame I can't load the DLC campaign missions into my "server." ED. Please implement a background "private server" option for people who play single player. It would be a huge boon for your great campaign creators as well, unless the multicore rendering is being designed to fix this issue.

They crash while turning toward the hostile aircraft. Sorry the .trk was corrupted.

I did it twice and the F-16 hit at the exact same angle.

F-15E should be capable of carrying 8 AMRAAMs though.

One of the F-16s turn into the C-17

I think even if ED doesn't want to make the F-15C full fidelity some little things that would extend the life of this plane immeasurably would be things like a programmable TACAN and radio. I can understand not wanting to go in and model every subsystem but this would solve annoying communication and navigation quirks for all FC3 planes, not just the F-15C.

South Atlantic might be interesting but it doesn't have the same pull as Persian Gulf or Syria for the average person. Sorry if you're personally a huge fan, but there is a reason most of the maps are basically in the Middle East including Caucasus. You could almost sew those maps together with a little development. Normany and Channel are WW2. The best way for RAZBAM to maximize sales of South Atlantic is to bundle it with the Mudhen. The F-15E is arguably the most popular American plane so it will sell as long as it's finished enough in early access. I would get SA as part of a bundle. Otherwise I'd wait on SA.

It seems like RAZBAM's goal is to release these at the same time. It looked like all of the F-15E shots were on South Atlantic. Has anything been announced as of yet. Seems like a good idea because I always get reluctant to buy maps compared to modules.

From what I heard, they rebuilt the plane from the ground up because ED updated the graphics engine. This is probably better because some of the older DCS assets look awful like the S-3. According to the new update this week, the flight model is done. They are just making the damage model now. It's wouldn't be fun to fly around in an invincible plane right? They have already said things like the bat bomb won't be ready for early access. Also, after thinking about it, it seems as though Leatherneck has their work cut out for them because they seem to have to put together a significant asset pack just to make the plane have real appeal. There is probably pressure for them to make at least one AI Zero. They are making a carrier. Heatblur was able to take their time on the Forrestal because the Supercarrier and Stennis exists. It would be awkward taking of from a Supercarrier in a Corsair. It would take you right out of WW2. If the Corsair came out without a carrier, I would just keep flying my P-51 because I enjoy it more. The Corsair is my 2nd favorite WW2 plane but carrier ops have a lot to do with it. This is arguably the most ambitious WW2 third party project because the Pacific theater assets just aren't there.

When I went into the NVIDIA settings it did not work in DCS. It was still 90 fps. Are you referring to Rivatuner or something like that?

I want to cap the software at 60 FPS while running the Reverb in 90 hz. Is this possible?

Update on the microstutter. I noticed subtle microstutter when not turning off the power Plon described during gameplay. Disabling this in windows did create a more stable framerate. The AI dialogue is still in issue.

This did not work for me.

Whenever I do things like communicate with AWACS in mission there is a little microstutter when it responds to commands like bogey dope.

You must map your RAM air control levers to an axis. The clickable levers in the cockpit DO NOT WORK. This will solve your max continuous problem. However, there is still a slight issue with the auto oil. It doesn't seem to start cooling until you hit the red line rather than leave the green zone.

If I want to stall in the Mustang I cut the throttle once I go under 150 mph. My engine is usually fine. You just have to cut it earlier than you think.