During 2017.2 beta, we found out that BuildPipelineInterfaces requires a good amount of time while entering play mode:
According to this post , it should be fixed in 2017.2.0f2. I tested this in 2017.3.0b6 and figured this issue isn’t fixed. Either it hasn’t been forward-ported (do you actually do this?) or the issue sneaked in again.
Here is a screenshot in 2017.3.0b6 using the project from Case 933679:
Screenshot
Hey Peter,
It’s in 2018.1a1 but hasn’t been backported yet. It’s staging for 2017.1 and 2017.2, so hopefully not much longer. Sorry for the inconvenience.
Forward porting does happen, but not automatically.
i have this problem also in Unity 2017.2.0f3 (64-bit) it happens on every scene change…
This problem was fixed in 2017.2.0p1 and 2017.1.2p2. The fix will appear later in 2017.3.
Are you sure about this?
I just downloaded 2017.2.0p1 and am still running into this issue:
Both of these spikes are scene changes.
Additionally, this case number isn’t listed in the 2017.2.0p1 patch notes:
https://unity3d.com/unity/qa/patch-releases/2017.2.0p1
And the case is still marked as active in the issue tracker:
https://issuetracker.unity3d.com/issues/buildpipelineinterfaces-causes-slow-enterplaymode-performance-when-there-are-many-cs-files-in-the-project
Am I missing something?
Hey @MorCompediaNet ,
I can again confirm that it was fixed there. The case is now closed and it will be updated on the issuetracker soon. About the patch notes, not all cases appear there due to various human errors.
Okay, now about the issue itself. The problem that we fixed was “Improve BuildPipelineInterfaces performance when there are many cs files”. In other words, it does not mean that we will not be doing that, but it will be much faster.
I have made some testing on my end and with 1000 scripts, performance improved from ~1.1s to ~20ms (similar to your results).
I hope this answers your question.
It does.
Thanks.
