Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.4.7
Issue ID
UVSB-807
Regression
No
Bolt and Ludiq both take a lot of time when Editor changes state
<p>I made deep profiling and found when I play the game or chane something is scripts Unity Editor reloads its app domain code base and Bolt's static initializers take very long time in such moments. Sometimes I forget what I wanted to check while waiting for Unity Editor moves to play state or while compilation is done. It would be great to optimize Editor part of Bolt. What if you make some tweak to disable Bolt's editor part leaving runtime part? It would help to speedup Unity Editor.</p>
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
- UI Builder Data Path Source List starts flickering and scrolling when trying to select the last item in the list
- Crash on ProcessSceneBeforeExport when analyzing selected Addressables rules in a specific project
- HDR images are compressed incorrectly with default settings on Android Platform
- Crash with multiple stack traces when painting detail on Terrain with a highly detailed Prefab
- Crash on mono_object_handle_isinst_mbyref_raw when SerializedReference points to a struct implementing ISerializationCallbackReceiver whose first field is a UnityEngine.Object
Resolution Note:
Original Issue|https://support.ludiq.io/communities/5/topics/2287-delay-in-entering-play-mode] - Fixed as part of Work in Bolt 2.
Lazlo Bonin (Lead Developer) 1 year ago
This is largely fixed in Bolt 2 Alpha 4 thanks for the new Odin serialization and a ton of optimizations to the plugin container.