PD919

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.

I can attest to this issue. I've emptied half the belt into Bf-109 or FW and they will only have white smoke. The AI doesn't even adjust their flight path or slow down. When I dogfight the P51, 1 quick burst will take it out of the fight and another burst will down it. I know the German planes were tougher but I doubt it was that extreme.

Not sure if the effect is on the asset pack or in the main DCS assets. I discovered it while playing through the Charnwood campaign. When flying over Caen the FPS plummets. I noticed there are a lot of explosion effects on the ground. Once I leave the area I get 45-90 FPS again in VR. It drops to teens to 20 with lots of stutter whenever the explosion effects are present.

If coming off a cold start make sure you mapped your RAM air levers to an axis command or you will overheat real quick.

Sounds great. Most prolific campaign maker in DCS. Always quality stuff.

Having a blast with the campaign. I think using an F-14B would be a fun alternative if it's easily implemented.

When I click on the red cover it doesn't open. Is this a common bug? Doesn't really make a difference because supercharger should be left in auto, but it is annoying.

I've noticed joystick curves kill the plane in a turn. The sudden acceleration in stick movement breaks wings or makes you spin out of control. This plane needs to be flown with low or no curves and gently.

Whenever I use "options, take 1", etc. The menu always does the command on comm 1 even if I'm pressing comm 2. If I make the order verbally on comm 2, it will go through comm 2.

You have to map both RAM air axis to a joystick axis. Use control as a modifier to not effect everything else. This will fix the problem. You can keep up with AI flight etc.

Mission 12 has odd stutters which don't exist on the rest of the missions. Whenever an AI plane starts up there is a huge stutter. FPS goes single digits for 2 seconds.

It seems that when you push the lever up with the mouse it does nothing. When I mapped them to and axis it worked. This seems like a pretty plane breaking glitch. I noticed my plane was overheating in 1-2 minutes at high altitude until I discovered the work around. Is there another fix for this because I really don't want to use an axis for a lever you barely use?

Everything was working fine yesterday, but now Vaicom is not reading what plane I'm flying and voice commands are not working.

I have a Reverb G2. I would prefer Windows Mixed Reality to be the runtime, but DCS always crashes mid flight unless I set the runtime to SteamVR in SteamVR settings. Is there a workaround for this?

Same issue. Prince thinks he has a submarine.

Thanks. Great campaign, btw.

I have flown this mission multiple times. When I end the mission it brings me back to the same mission rather than moving onto next. Are their any special triggers to finish the mission? It's the mission where you fly over Bastogne, but it's on the Caucasus map.