Probuilder 4.2 enter in play mode load time very lon

Hey, I just updated my project to pb 4.2 in unity 2018.3.0f2 and 2018.3.2f1

I noticed a very long loading time when I enter play mode (even in an empty scene). Unistalling PB 4.2 solved the problem.
I made a debug project but I can't reproduce it with an empty project.
Maybe it's because my main project uses a lot of pb shapes ?

Anyway, as pb is now compatible in play mode, maybe there is someting going on here.

Thanks for any help,

Jonathan.

 

What means "very long loading time" expressed in seconds? Knowing this number with and without PB in the project would be interesting.

You could also use the Unity Profiler with "Profile Editor" and "Deep Profiling enabled to check where specifically the editor is spending that time.

 

Similar thing reported here: https://forum.unity.com/threads/probuilder-4-0-2-update-problems.616615/

 

ChaosResolution, indeed it seems like the same issue !

Peter77, something like 1 min. Usually it's 10 seconds on my project. I tried the profiling but not the deep one, so I'll try that

Thanks for the help !

I'll aslo try to make a fresh project and reimport every plugin one by one to see if there is any compatibilty problem with a third party.

 

I guess it's this ProBuilder issue.
https://forum.unity.com/threads/upd...5-sec-and-6-gb-of-memory.616468/#post-4131670

 

Yes I think it's that, I'm trying to do the deep profile but my computer just has 16 go of memory, that are getting saturated until Unity just crashes.

Edit : well on an empty scene I managed to deep profile without a crash.

So here is the memory profile :

Used Total: 42.27 GB Unity: 24.89 GB Mono: 0.91 GB GfxDriver: 16.46 GB FMOD: 1.2 MB Video: 0 B Profiler: 11.6 MB
Reserved Total: 50.55 GB Unity: 32.81 GB Mono: 1.27 GB GfxDriver: 16.46 GB FMOD: 1.2 MB Video: 0 B Profiler: 16.0 MB
Total System Memory Usage: 52.10 GB

Textures: 781 / 249.5 MB
Meshes: 18285 / 31.39 GB
Materials: 57 / 80.0 KB
AnimationClips: 58 / 11.5 MB
AudioClips: 0 / 0 B
Assets: 5007
GameObjects in Scene: 5
Total Objects in Scene: 18840
Total Object Count: 23847
GC Allocations per Frame: 1170 / 67.0 KB


Very weird knowing that it's an empty scene.

I was not able to do the Editor Profiling (crash every time) but I noticed 99 % cpu usage on "editor loop" exactly like the theard linked above by Peter77


Edit 2 :

So as it's apparently a known issue, I'll just go back to 3.9 and will wait for a fix.