Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.3.3p1
Issue ID
774344
Regression
No
There's no way to determine the reason behind each of multiple calls of OnPostprocessAllAssets
Steps to reproduce:
First of all, multiple calls is by design so there's no bug in this aspect.
1. Open attached project
2. Open scene "test"
3. Clear the console
4. In scene "test" move some object so that it would become dirty
5. Save the scene
6. Notice that OnPostprocessAllAssets is called 3 times
7. Clear console
8. In Project tab, select material "efasdsad" and edit it
9. In top menu select "File > Save Project"
10. Notice that OnPostprocessAllAssets is called 2 times now
Problem with this behavior: Users can't determine which call of OnPostprocessAllAssets does what so there isn't much of the use case of having multiple calls. Also, since the number of calls can differentiate depending on the action performed in editor users can't "just skip some calls untill the final one and execute code then".
Reproduced with: 5.1.4f1, 5.2.4f1, 5.3.3p1, 5.4.0b8
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
- Crash on ModelImporter::ImportSkinnedMesh when disabling "Strip Bones" on a specific FBX model
- WebGL Development builds ignore the "Compression Format" setting when using "Gzip" compression
- [tvOS] Project crashes on startup on Apple TV simulator (both X86_64 and ARM64 architectures)
StaffanEk
May 11, 2017 13:32
This would be solved with the introduction of an "OnFinishedPostProcessing" callback, but I doubt anyone will read this comment since you can't even vote on this "non-issue".