Aximmerty DE excessive System Processor Load

Studio Operators Bugs

 

Hi

I am testing Aximmerty DE for following PC configuration:

1.       Processor:  AMD Ryzen 7 3800X 8-Core Processor, 3893 Mhz, 8 Core(s), 16 Logical Processor(s)

2.       RAM: 32 GB

3.       GPU: RTX 2080

Aximmerty is showing 165% GPU use and 200% CPU use and frames are dropping.


However, Task manager is showing 26% CPU use and 35% GPU uses. I am going something wrong? This means Aximmerty is not using PC resources properly?



Please help me. Your software is very good and I want to use it.

   mauryafamily

 
Profile Image
ahmed ahmed
5/8/2020 7:16:25 PM
  -  

Maybe you need to optimize your project,For example reduce mirrors and reflection shaders.

Also maybe you need to use fewer media files played in same time.

You can review the following pdf file for Recommended Hardware to work with aximmetry DE

https://aximmetry.com/en/documentation/Manuals/Recommended%20hardware_de.pdf


 
Profile Image
mauryafamily
5/9/2020 2:32:28 AM
  -  

Well, two points. 

1. I was using a blank Unreal Project for this test.

2. Task manager is showing  ONLY 26% CPU use and 35% GPU uses. The system was running normal as well - fan running or heating.

To be it seem Aximmerty is not using all the PC resources.

 
Profile Image
TwentyStudios
5/10/2020 2:50:45 PM
  -  

Are using “Cooked” mode to open the UE4 scene?

 
Profile Image
mauryafamily
5/11/2020 3:41:40 AM
  -  

I am cooking the contents in Unreal and bringing in Aximmetry by dragging and dropping in new compound. Pulling Unreal project in Aximmetry in not affecting/increasing the CPU/GPU use. However,  as soon as I drop ‘VirtualCam_Unreal_A-B_Preview)3-Cam’ to new compound, the CPU use Jumps to 1% to 120%-140% range and frame rate drops to 12-13 FPS.

 
Profile Image
Aximmetry
5/11/2020 12:18:50 PM
  -  

Did you map any video capture cards in Device Mapper?  If yes, how many, what type, what resolution and at what framerate?

 
Profile Image
mauryafamily
5/12/2020 3:59:59 PM
  -  

Thanks Aximmetry, I had by mistake mapped three 4K inputs. Now the issue is resolved.