reported Memory hitting 100% flicking through Encyclopaedia....

[RuskyV]

When starting DCS and going straight to the encyclopaedia, flicking left to right using the arrow keys while looking through the 3D models starts to eat up memory pretty quickly. 

-Most noticeable is the Tomcat by Heatblur, flicking left to right on both the A and B models while loading in their liveries, just eats the memory up to the point all of my 32gb of memory hits 100%. Its the same with the Viggen. Other 3D models especially the aircraft have the biggest impact.

The really odd thing is once its hit 100% memory DCS doesn't release the memory and it will sit at that percentage when exiting the encyclopaedia. This brings the simulation nearly to a crawl so loading the editor or trying to fly a mission gives horrendous performance. 

Its easy to repeat by opening the Task Manager and setting it to "always on top" then start flicking through the 3D models, once the memory tops out the only way to lower it is to quit DCS, which will then sit in the task manager until it finally quits about a minute later.
 

Could the similar issue be causing part of the stuttering people see in multiplayer when people are connecting and changing liveries? dose this force all clients to use up memory when ever a livery is selected and comes into the players view?

What could be happening here??

dcs.log

Edited August 24, 2022 by RuskyV

[silverdevil]

1 hour ago, RuskyV said:

When starting DCS and going straight to the encyclopaedia, flicking left to right using the arrow keys while looking through the 3D models starts to eat up memory pretty quickly. 

-Most noticeable is the Tomcat by Heatblur, flicking left to right on both the A and B models while loading in their liveries, just eats the memory up to the point all of my 32gb of memory hits 100%. Its the same with the Viggen. Other 3D models especially the aircraft have the biggest impact.

The really odd thing is once its hit 100% memory DCS doesn't release the memory and it will sit at that percentage when exiting the encyclopaedia. This brings the simulation nearly to a crawl so loading the editor or trying to fly a mission gives horrendous performance. 

Its easy to repeat by opening the Task Manager and setting it to "always on top" then start flicking through the 3D models, once the memory tops out the only way to lower it is to quit DCS, which will then sit in the task manager until it finally quits about a minute later.
 

Could the similar issue be causing part of the stuttering people see in multiplayer when people are connecting and changing liveries? dose this force all clients to use up memory when ever a livery is selected and comes into the players view?

What could be happening here??

dcs.log 58.91 kB · 3 downloads

 

i have not had this issue because of not having F14 in my missions. but an observation i have made, the F14 folder is 14.5 GB as opposed to FA18C that is 1.7 GB. thats a big difference. but probably not it. these issues havent been around forever. the F14 has always been the heaviest plane in dcs.

[RuskyV]

This a big part of the issue,

textures are taking up so much memory now even a high end system costing thousands is still no better off. No matter how much memory you have it gets eaten up. You can’t keep adding textures and triangles and not have a way to clear down memory, It’s a diminishing return on performance.

What’s the official line on this, Bug? Bad code? No standardised textures sizes for modules?

 

[jurinko]

Guys set textures to medium in graphic settings, good workaround until dcs core engine is updated. I personally cannot see any difference. 

[Lord Vader]

@RuskyV

Thank you for bringing this to our attention. This as been reported and we are investigating the possible causes.

[RuskyV]

My pleasure, glad it’s getting looked at 

[RuskyV]

2 hours ago, jurinko said:

Guys set textures to medium in graphic settings, good workaround until dcs core engine is updated. I personally cannot see any difference. 

Hi jurinko,

I think it’s more about working to a solution rather than a fix, looks like it’s a known issue now so hopefully we will see some improvements in coming updates.