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.7
Issue ID
UVSB-787
Regression
No
Issues with example projects, specifically Space Shooter example in this case
[Original Issue|https://support.ludiq.io/communities/5/topics/2647-issues-with-example-projects-specifically-space-shooter-example-in-this-case] - Unity Bug
----
In short, the example is not working anymore with the latest version of Bolt and Unity. Some flow machines are not attached to their objects.
Some object variables are lost.
The macros also have default unity icons for some reason.
When I browse for macros it doesn't find any in explorer. Macros do attach if dragged on directly though.
I assume other example projects are in a similar state.
Bolt Version:
1.4.1b4
Unity Version:
2018.3.1f1
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
- UnityLinker causes crash when outputting snapshot data for very large projects
- Camera Preview does not detect multiple cameras with same GameObject name
- Crash on TypeTreeIterator::Children() when renaming a corrupted asset while Asset Serialization is set to Mixed
- Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
Resolution Note:
Unity Bug
Lazlo Bonin (Lead Developer) 2 years ago
I figured it out! That took quite a bit of testing.
Basically, if a Prefab was created in the old prefab workflow (2018.2 and below), like they were for example projects, it will fail to instantiate its Bolt components properly when opened in the new prefab workflow (2018.3 and above). Macro references will be null, variables will be missing, etc: as if the components were entirely reset.
The solution is simply to Reimport the prefab (right click menu). As a precaution, I would reimport the entire project (right click menu > Reimport All).
Then, the prefab instances all magically get fixed!
I will add this to the known issues page.
Here it is: https://ludiq.io/bolt/known-issues#prefab-reimport