Studio Performance Issues with Version 4.2 #2168
-
Hello everyone, I recently started using the Stride game engine, having installed version 4.2. After creating a project using the default template, I encountered a recurring issue where the software intermittently causes significant system lag. This lag is frequent enough to render the entire computer unresponsive, including other applications, and even the mouse interaction with the desktop becomes impossible. Notably, the lag occurs even when I am not interacting with Stride (i.e., when the window is not in focus and I am using other applications). During these lag episodes, I observed a sudden spike in Stride's CPU usage, approximately 20%, in the Task Manager. Following the lag, the CPU usage returns to normal levels. I did some search but find nothing about "lag" on the Internet, and I'm not sure what is causing the problem, so I came for help. Here are the specifications of my Windows environment:
Hardware Specifications:
If anyone has experienced similar problems or has insights into potential solutions, it would be greatly appreciated. Thank you for your time and assistance. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Upgraded to Win11 and the issue seems to be irreproducible. While it's a kind of solution I suppose. |
Beta Was this translation helpful? Give feedback.
-
By lag, you mean random freezes for a few seconds? If so, I've been experiencing the same issue for a while but really didn't had this happen in my previous PC with a Ryzen5 CPU until I upgraded to a 12th gen i9, same Win10 installation. It only seems to happen when rendering anything on my end. If it helps any, I normally bandaid-fix it by changing the CPU affinity of the Stride processes in Task Manager under Details to only use the last few cores. Somewhat tedious to do it everytime I restart the app or the editor but gets the job done. |
Beta Was this translation helpful? Give feedback.
By lag, you mean random freezes for a few seconds? If so, I've been experiencing the same issue for a while but really didn't had this happen in my previous PC with a Ryzen5 CPU until I upgraded to a 12th gen i9, same Win10 installation. It only seems to happen when rendering anything on my end.
If it helps any, I normally bandaid-fix it by changing the CPU affinity of the Stride processes in Task Manager under Details to only use the last few cores. Somewhat tedious to do it everytime I restart the app or the editor but gets the job done.