Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.0f1
Issue ID
1057943
Regression
No
Performance: ScriptedImporters are very slow
I have two means of importing a Quake BSP asset:
1) Loading it via a button press in the Inspector (EditorBspTest.OnInspectorGUI)
2) Loading it through a ScriptedImporter (QBspImporter)
Both code paths are essentially identical. In fact, loading it through the Inspector actually creates a new ScriptedImporter object and calls the same Load() routine.
Comparing both approaches, the latter is significantly slower.
To reproduce:
1) Load the project
2) Click on "worldspawn" in the hierarchy
3) Click Load in the Inspector. Note how little time it takes.
4) Click Unload in the Inspector to remove everything.
5) Go to the Project view > Assets > Id1 > maps
6) Right click on e1m2.bsp (the same map)
7) Hit Reimport.
Actual: Load time is significantly increased.
Expected: Load time should be identical.
Reproduced: 2018.2.1f1, 2018.3.0b6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
- [macOS] Display flickers with bright colors when built Player uses 2 or more Displays
Add comment