Dis anyone reported CPU overload after running Aximmetry 2025 3.0 several hours?
Best regards
Eric Soulard EI
コメント
Eifert@Aximmetry
-
Hi Eric,
We have not experienced or received similar reports of CPU overload after running Aximmetry 2025.3.0 for several hours. However, it is always worth investigating further using the Task Manager. For example, you could check the load on individual CPU cores during usage or, with an even more precise program, check the CPU's temperature.
Are you using Unreal Engine with Aximmetry, or any other features alongside it? What is the performance load when you start Aximmetry with a fresh instance of the same project? Does the issue occur on other computers, or only on this particular system? Does it happen if you don't use any input device or output device other than the previews? Have you observed similar problems with other Aximmetry projects?
Hi Eric,
We have not experienced or received similar reports of CPU overload after running Aximmetry 2025.3.0 for several hours. However, it is always worth investigating further using the Task Manager. For example, you could check the load on individual CPU cores during usage or, with an even more precise program, check the CPU's temperature.
Are you using Unreal Engine with Aximmetry, or any other features alongside it? What is the performance load when you start Aximmetry with a fresh instance of the same project? Does the issue occur on other computers, or only on this particular system? Does it happen if you don't use any input device or output device other than the previews? Have you observed similar problems with other Aximmetry projects?
Additionally, does this problem occur only in Aximmetry 2025.3.0, or have you noticed it in previous versions as well? There was a forum post about a somewhat similar issue in version 2.0: https://my.aximmetry.com/post/4919-fillkey-lag-performance-degradation-afte
Warmest regards,