With gpu profiling turned on, the render thread usage and gpu usage is suddenly really high, which seems to be the correct data, compared to before. It happened as I was editing shadow settings for the scene's Directional Light although that likely has nothing to do with the actual problem. the main project (in 2019.1.0b7) started to lag. I'll let you know if I see the problem (either in the buggy test-project or in the main project) in 2019.1.0b7 (or later).Įdit: Just a few minutes after posting this. I have not attempted to use the buggy project in 2019.1.0b7 yet. The "wake up" when I shut it down last time was just a coincidence. Unless Windows Security refused to give up several minutes after I shut it off, it looks like it may not be the cause.
I started typing up this post without turning off either Unity instance any more times after a handful of minutes of writing this post, I noticed that the editor "fixed itself" and it was responding normally. I restarted the Unity instance that was laggy, and the lag persisted when it relaunched.
I turned off Windows Security (Real-time protection, Cloud-delivered protection, and Automatic sample submission) and the lag persisted. I took a screenshot of the "Profile Editor" on 2019.1.0b6. The 2019.1.0b7 project was responding normally during this time. I noticed that the 2019.1.0b6 (buggy) project had massive editor lag. (I was intending to copy some shadow settings over from the test scene.) I just had two instances of Unity open, one in 2019.1.0b7 on my main project and one in 2019.1.0b6 on the buggy project that I submitted with 1136028. So it turns out that Windows Security may not be the issue? This bug is not related to the buggy, March 1st Windows 10 update.) My most recent update is the February Patch Tuesday security update. (edit: I should note that I *do not* have the March 1st Windows Update installed, which is known to cause performance issues of some sort. (I mean, it gets 250+ FPS on a good day.) It's especially weird that it pretty much affects a single scene, and that scene isn't very complicated. It also kept that full performance when I turned those settings back on again, though. As soon as I disabled Real-time protection, Cloud-delivered protection, and Automatic sample submission from the Windows Security center, I turned on the build and got full performance again. until I noticed that Microsoft Anti-malware was using a significant amount of CPU. Interestingly, I was getting fairly consistently 2 FPS several times in a row. Sometimes I enter a specific level and get 250 FPS, and sometimes I enter that level and get 2 FPS.
even in builds, not just the editor although I've seen it in-editor, too. I seem to have been getting a similar issue.
0 kommentar(er)
