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 [Package]
1.4.11f2
Issue ID
UVSB-785
Regression
No
Prefab instances are corrupted (lost macro, missing references, empty variables) in 2018.3
Just posting this bug report in case other people look for it! It's a [known issue |https://ludiq.io/bolt/known-issues#prefab-reimport]with a simple fix:
When instantiating a prefab in Unity 2018.3, you might run into an issue where all its Bolt components are reset to their default state.
That means, for example:
* The source of machines is reset to Macro, and the macro reference is None
* The variables component is entirely blank
* A reference to this prefab elsewhere shows a null or missing
This happens for prefabs in projects that were created in the *old prefab workflow* (Unity 2018.2 and below) then opened in a newer version of Unity with the new prefab workflow (Unity 2018.3 and above).
The solution is simply to *Reimport* the affected prefabs. You can do so by selecting the prefabs, then choosing Assets > Reimport.
If you want to make sure you did not miss anything in your project, you can also use Assets > Reimport All. Note that a full reimport can be very long depending on the size of your project.
Bolt Version:
Unity Version:
2018.3
Platform(s):
Scripting Backend:
.NET Version (API Compatibility Level):
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
- [URP] Invalid update of shader stripping settings
- [HDRP] Errors on Shader stripper that do not stripp shaders.
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
- Prefab overrides don't recover missing managed references
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
Resolution Note:
Unity Bug