Search Issue Tracker
Fixed
Fixed in 1.2.X, 1.3.X - Entities, 7000.0.0a1
Votes
2
Found in [Package]
1.2.1 - Entities
1.3.X - Entities
7000.0.0a1
Issue ID
ECSB-1105
Regression
Yes
Scripts have poor compilation times when using Entities versions 1.2.0 and higher
How to reproduce:
1. Open the attached “IN-75966” project
2. Open the “ApplicationTools“ script from the Project window (Assets/Game/Scripts/Tools/ApplicationTools.cs)
3. Add an empty line and save the script (CTRL + S)
4. Close the script editor and take note of the compilation time
5. Open the package manifest (IN-75966_MP-ECS/Packages/manifest.json)
6. Change “com.unity.entities.graphics” and “com.unity.physics“ to version “1.2.1” and save the file (CTRL + S)
7. Repeat steps 2 through 4
Expected result: The compilation time stays approximately the same before and after changing the package versions
Actual result: The compilation time increases significantly after upgrading the package versions (27 seconds to 210 seconds)
Reproducible in: 1.2.0 (2023.3.30f1, 6000.0.4f1), 1.2.1 (2022.3.30f1, 6000.0.4f1)
Not reproducible in: 1.2.0-pre.12 (2023.3.30f1)
Could not test with: 2021.3.39f1 (Entities not supported)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
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
- Rigidbody2D.Slide API does not have the needed configuration when creating a 2D Top-Down character controller
- Opening reference for "Playables"component redirects to a missing page
- Sprite Renderer image is changed when switching Mask Interaction and changing Sprite to a shared Sprite
- An unsigned integer is not compared with an integer correctly in player when using IL2CPP backend
- Graphical artifacts are being rendered in Scenes that are loaded during run-time when GPU Resident Drawer is turned on
Resolution Note (fix version 1.3.X - Entities):
This will be addressed in the next 1.3 release.
Resolution Note (fix version 1.2.X):
This will be fixed in an upcoming 1.2 release.