The issue is most likely thermal throttling on your computer. Make sure it’s properly cooled. It could also just be an unoptimized scene. Have you activated DLSS through the level blueprint? 

Hi TwentyStudios,

i'm using liquid cpu cooler in my PC. And I activated DLSS using level blueprint. Even at maximum performance mode it is overloading starting from 40% and raising  more than 120% in few mins.

Still, check your CPU and GPU temps under heavy load. This is not a typical issue, so there’s clearly something going on with your setup or scene. DLSS also isn’t a magic bullet. There could be other bottlenecks in your scene besides resolution that could cause the issues.

There are also some issues when one of your video inputs comes with a higher framerate than the project.
See here: https://my.aximmetry.com/post/2354-feature-request-framerate-converter

Hi TwentyStudios,

I checked the GPU and CPU performance using Task Manager. If allow virtuals is off GPU utilization is in 97% and CPU utilization in 26%. If turned on GPU utilization is in 40% and CPU in 28%. Even when the Allow virtuals is on GPU and CPU overloading constantly keep on increasing from 40% TO 130%. The CPU and GPU temperature is normal. And i also changed the scalablity in UE5 using level blueprint. Don't know what is going on in Aximmetry Composer. Please help me to solve this issue.

Thanks.

I tried to cook a basic scene without any assets still i'm facing the same issue. Please help to fix that issue.
Thanks

Hi Samuel,

Did you test the basic scene without DLSS?

Also, you could test it on a different computer and see if the same happens. This way you can likely rule out the hardware issue.
And you can also test it with lower resolutions to see if the same thing happens. If at the low resolution the CPU and GPU don't increase over time, then it is likely thermal throttling or some similar hardware issue causing it.

If it turns out that something in your project causing it, or Aximmetry, or Unreal.
Then you can simplify your compound in the following way to see which component is causing the issue:
You connect only the Unreal compound as a video output. And you disconnect every input from the Unreal node:
If the issue is still present after this, then it is likely something in the Unreal engine causing it or it is a hardware issue.

If the issue was solved in the previous Flow Editor setup. Then you can try to see if the issue returns if you only connect your Camera compound's output pins to the Unreal node:

Warmest regards,