AJaromir

I agree. I think this scheme just causes problems in general. Apache is not the only machine where it doesn't work. Another is the Hornet, for example, which has a recurring problem with low engine thrust in this mode. I think the cancellation will benefit everyone. For one thing, the developers will have less work to do and for another, the game will be more accessible. Because in my opinion the main problem is not realism. I think the best way to make the game more accessible is to completely rebuild the basic training missions for the SU-25T. Furthermore, these missions should not only include how to operate the machine, but should teach the basics of flying. This is particularly lacking in DCS:W. Probably not a problem for many veterans since we already played IL2, Rise of Flight, FSX, LoMAC twenty years ago. But newcomers to the genre have a hard time in my opinion.

Yes, because peeple see it works in many other games. But DCS:W is not like other games. It is huge game in huge playground and graphics is relatively small part of it. If some game is already well optimised, change of API would not provide miracles.

They talk about Vulkan as the new graphic platform.

Matt Wagner is the Icon of the DCS:World. Also there would be interesting to cooperate with Andrei Celeste.

I like the Vulkan is developed. Vulkan is multi-platform compatibile which could make the game in future natively compatibile with other operating systems.

As far as I remember, ED works on system of time based "deferred" calculation for low-priority units - in distance - invisible.

For that reason the special flight model, called "GFM" or General Flight Model is now made for AI aircrafts.

It sounds a bit like pilot error. You talk about take off or about landing? Generally you only need to set axis curves. Make sure you have turned off the game mode. Make sure you have turned off force feedback in misc. options menu. Is this your issue?

As far as I know, in Mig-15 is simulated that you have your oxygen mask always on. So no matter your canopy is open or not, you will not get hypoxia because you wear oxygen mask. But once you turn off the main valve, you will starve oxygen, even on ground because your mask is always on.

Yes, in my opinion this is not simulated the best way in P-47. It is made well in Mig-15

Why the flaps must be up? I did not find anything about that in manual

Please make the BLC (SPS) detent on throttle like the real 21 have. Make it possible to toggle on/off like in other aircrafts is possible for afterburner. Thank You.

Forcing the disabling of core parking via MSconfig is also an option to solve the problem. But raising the FPS limit seems like a better solution to me.

LOL It would be irony that this issue is caused by better performance. I noticed that my 99% percentil FPS is much higher than ever before.

I have no idea then. My current fix is to set FPS limit to 90. Maybe because at higher FPS the CPU must work "more". It is not parking cores. I don't know.

Is possible that is caused by core parking? Like PG is more resouces demanding than NTTR. When the FPS limit is set to 60, there is message CPU bound (main thread and rendering thread - switching rapidly). When I increase the FPS limit to 90, there is message CPU bound (fps limit) or CPU bound (rendering thread). When I unlock the FPS, there is "GPU bound" only. The higher FPS limit I set, the more stutters occur. When I set it to 30, it is ridiculous.

O.k. I take it back. The second test was not the same mission. The first one was the UH-H free flight in Persian Gulf in Instant action. The second one was in NTTR. I tried the PG again and the issue is still there. In NTTR it is not.

Literally I have no idea. Maybe there is some hidden cause which I am not able to find out yet.

Game restart fixed the issue partially. Once I deleted the "fxo" and "metashaders2" the issue have been fixed completely. But this happened like 2nd time after the latest update. And always fixed by deleting those folders.

Hereoptions.lua

Note: When I set FPS limit to 90 it more like holds the 60fps Still without stutters. I have 144hz display with FreeSync (Gsync Compatibile) I use no external graphics settings. No mods, no custom shaders e.t.c... Vsync off.

I use FreeSync. Thus I am not using Vsync.

GPU driver version 551.61

Hello. When I set some FPS limit bellow the maximum, it causes stuttering. See the video. Game version 2.9.3.51704 My system: MB: Asus ROG STRIX Z790-H GAMING WIFI CPU: Core I9-13900KF GPU: MSI Ventus RTX2080 TI 11G OC RAM: 64GB G.Skill DDR5 Ripjaws S5 5600MHz CL28 Dual Channel Kit 2x 32GB Black OS: WIndows 11 home SSD: HD SAMSUNG SSD 980 PRO 1TB, PCIe 4.0 NVMe