CPU bound with only 20-30 FPS (even with lowest settings)

[diamond22]

I',m experiencing very low FPS with the Phantom, while I haven't particular issues with the other modules, although my PC need of some upgrade.

My specs:

• CPU Intel i5-6600K (Skylake) Quad-Core, 3.5 GHz
• motherboard MSI Z170A
• RAM 32 Gb DDR4
• GPU MSI GeForce RTX 3060 12GB

I read here that the module is very CPU demanding, but didn't think so much. I hope there it will be some kind of optimization in the future, because the Phantom is absolutely one of the best modules made for DCS (well done Heatblur). I'm also looking forward to upgrade soon my motherboard and CPU.

Happy landings 

[Czar66]

On 5/26/2024 at 2:15 PM, emc said:

Yeah, maybe... need check what which one will fit into motherboard's socket and will be supported by....

Upgrade to LGA 1700. Save the RAM and just get a new mobo + CPU. Any i5 would outperform your i7 there.

[Loukuins]

On 5/26/2024 at 4:06 PM, DrGarantia said:

Same issue here with an 5800X3D, massive frametime variations (constantly hitting 50ms or more) and a terrible average of 33 FPS in any somewhat complex missions (Grayflag MP server). That same CPU is capable of ~180-230 FPS for every other module. Even their own cold start mission FPS is limited to about 90 before start-up, that is less than half the average of other modules.
HB is probably looking at it for now, wait and see what happens.

You have an issue on your pc , got the 5800X3D and I have a steady 140fps with a WSO on a 60 player server

[Kev2go]

On 5/26/2024 at 7:57 PM, PhantomHans said:

I thought I noticed better performance in narrow scan than wide.  I was gonna say something but...I wasn't sure.

Makes me want to ask a few things...

 

First, can we get an even lower tickrate or can we get a "Low CPU" model that's DRASTICALLY simpler and lower demand.

 

Second, as another separate option can we get a configuration file to limit the jet to narrow scan or make it default to narrow scan and prevent Jester from going wide unless told?

Perhaps it is a cpu dependant issue after all, becuase after testing F15E, i noticed in comparison the F15E was more GPU dependent ( using like 90% gpu with low level flying but still had more framerates)  then the F4E, but less CPU dependant. Id generally hover aroun 30-40% CPU usage in the F15E, but in the F4E i was only using 40% CPU when i had TGP and/or Radar off.  When using those i noticed my CPU usage bump up 60-70% ranges. Still not overburned but i guess enough to lose FPS i guess.

 

The smoothest experience with the F4E has been flying with no human wso and with Radar and TGP in Standby. (not used)

On 5/27/2024 at 4:51 AM, Cobra847 said:

First, we'll ship our hotfix which should improve radar CPU performance impact - then we will circle back and try to find these hotspots for everyone.

Yeah i just read the Changelogs on your site. Its good to hear there are performance optimizations already inbound with the next upcoming patch! 

Edited June 4, 2024 by Kev2go