AJaromir

I am not sure yet.

Well. I've found the core parking have been somehow overriden. After reset power profiles it looks like the issue has gone. But I am not sure right now. I need to observe it for longer time to be sure.

No. Hybrid cores are only issue of Intel CPU's. Ryzen 9000 series may have exactly opposite problem with core parking than Intel has. AMD Ryzen 9000 series intentionally parks the cores so that the game runs on only single chiplet with 3D V-Cache, which is correct because it extremely reduces latency. The problem is that if you don't set up the system correctly, it doesn't work as it should. The cores don't park when they should. I recommend watching this video which explains the AMD problem in depth and gives solution how to fix that:

In W11 it is possible to manage that ony by editing windows registries. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\0cc5b647-c1df-4637-891a-dec35c318583\ There are two values. One is named "value max" and one is named "value min" This values in % determines the minimum and the maximum allowed ammount of parked cores. When the both values are set to 0, no core will be ever parked. After that the system restart is needed. Edit: Or I can change value "Attributes" to 0 and this will unlock the core parking setting in power settings, just like it is in W10

In Windows 10 power settings you can set core parking threshold. This setting is not available in W11

Core parking is issue only in W11

Should I add this into "autoexec.cfg" file?

Thank you. Will try. Just for your info. Now the issue is back (without turning off the hypervisor) and there is no "efficiency mode" mark in task manager. There is very often red CPU bound(main thread) message. Here is log: dcs.log

Murphy's Law of Order says that things always go wrong (get fixed) at the "right" time. So at this time, as if on purpose, I am unable to reproduce the problem. This screenshot is from my last attempt, when it was at least partially successful. In the normal case, when everything works as it should, the line on the graph is absolutely straight. Here it is slightly lame. Reproducing the problem is often helped by setting a low FPS limit like 30 or less. I normally use a limit of 60. In the attachments is the game log: dcs.log

Hi. Do you want to send my log when the process is in efficiency mode? It is quite difficult because I have to restart game few times until this stuttering randomly cames in. It often requires to restart whole PC, so give me like 10 minutes.

Yes, I have set ultimate power plan and DCS is in the high performance list. Also I have forced core parking off for my 13900kf, done by editing windows registries.

This is a problem I've been dealing with for a long time (since I have W11), but only now have I found out the cause. Sometimes I just have to restart the game to get it to recover and have a stable FPS. If I don't do that, the FPS looks like the picture here. You can see extreme stuttering in the graph on extremely hi-end PC. But always after game restart all have been fixed. Then it looked like this: In short: super smooth! And now I've probably found out why it's happening. For some reason unknown to me, the game is and is not running in efficiency mode. And my question is: How do I prevent the game from running in efficiency mode? Here is the picture in which you can see what is running in efficiency mode. It is not dcs.exe itself, but some subprocess for which I am not able to turn efficiency mode off:

Hello. I tested what's going on and found what's happening. Your throttle axis must be set to 0%. If the throttle axis is not set to 0%, you can not move throttle lever from cutoff to idle.

Full metal body of Flanker replica is not enough?

No. Thrustmaster is the only brand right now.

If the Fuel Tank Pressure valve should be off when using long range tank, is it safe to use long range tank at high altitudes?

This is my very first flight with Corsair in DCS:W. I did not read the entire flight manual. Only how to start engine. In the video you can see the aircraft is really very stable and flying like on rails. No curves set, no dead zones set.

According to manual and training mission I was never able to see this message? Where it should show itself? Am I doing something wrong?

From my point of view I have no issue with flight model. This video explains the most often issue of the rookie players. You might see it:

I can try that but this is not how the F-4U1D should be used. It is strike bomber, not interceptor/dogfighter.

Depends on variant. F4U-1A: 417 mph F4U-1D: 425 mph (with water injection) F4U-4: 446 mph or 453 mph (dispute between data sources) F4U-5: 470 mph (missed WWII)

First of all you have to use aircafts in a way of realism. 1) Corsair is made for carrier take-offs and landings. 2) The goal is to win war/battle. Not to kill or destroy something. Because of that the highest priority are the ground targets. And Corsair is meant to be used as the strike aircraft 3) The best defense in those days was to fly as high and as fast as possible. That's why I think the Mosquito and the P-47 were some of the best planes ever, even though the P-47 had major range issues. 4) It follows from the previous point that energy is more than maneuverability. Here's a nice video of the Germans convincing the Japanese that their most vaunted KI-27 is actually a mistake, and the reviled KI-44 is instead their best creation.

According to flight manual for carrier take off: Roll trim : 6° right Yaw trim: 6° right Pitch trim: 1° tail heavy From my experience if you want to trim the aircraft: 1) Stabilise pitch and roll first by stick and keep it stable. 2) After the pitch and roll is stabilised, stabilise yaw. 3) Set trim to yaw while keeping pitch and roll stable by stick. 4) Set trim to pitch and roll until you apply no pressure on stick.

According to DCS flight manual, page 24

My feelings about FM is: Quite common static stability for WWII warbird Extremely high dynamic stability for such heavy WWII warbird Gyroscopic precession is a thing (same like in P-47). Propeller with diameter around 5 meters results in big changes of yaw when trying to push or pull. Same for P-factor and SlipStream. Changing throttle results in need to change the rudder a lot. You don't need maneuverability when you can fly at speed of 600 km/h in altitude of 10 km. Noone can catch you.