Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
1.4.11
Issue ID
UVSB-7
Regression
No
Output of Cooldown completed is treated as unentered
Pending Review - 2 months ago. UX POV it's bad but does not impact graphs execution according to Lazlo.
[Original issue link|https://support.ludiq.io/communities/5/topics/4819-output-of-cooldown-completed-is-treated-as-unentered]
----
I don't know is it planned but two flows in cooldown are Dim even if it working flow like in 2 examples...
All working ok it just visual issue for me
[!https://support.ludiq.io/s/attachments/21929/5/273/7ccdc0da44a7c2e1dc218a6fff5780b9.png!|https://support.ludiq.io/s/attachments/21929/5/273/7ccdc0da44a7c2e1dc218a6fff5780b9.png]
Bolt Version:
1.4.11
Unity Version:
2018.4.14f LTS
Platform(s):
PC
Scripting Backend:
Mono
.NET Version (API Compatibility Level):
.NET 4.x
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment