Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2.0.0a10
Issue ID
UVSB-692
Regression
No
Type inference is too strict on generic Bolt type arguments
[Original Issue Link|https://support.ludiq.io/communities/5/topics/4989-type-inference-is-too-strict-on-generic-bolt-type-arguments] - Pending review
----
!screenshot-1.png|thumbnail!
Works if I check the index against the list:
!screenshot-2.png|thumbnail!
@Reality.Stop() mentioned on the discord:
yes, if the output of the foreach loop is connected to something that has to do type inference, it currently breaks[3:50 PM]which also can't means you can't plug a gameobject into a transform operation without a Get Transform in between, etc. If the type of the Item doesn't match the expected type you feed it into, it gives a very confusing error message. It's like instead of trying to determine what type to transform to going forward, it's trying to transform in reverse (in your example, it's like it thinks the entire For Each should be a list of whatever class "Has Weapon" is on
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
- Greyed out Icon for Tool Context is misaligned in the Tools Overlay in the URP 3D Sample Template
- HDR colors are recorded in gamma compressed values instead of linear values when using the Animation window
- Scroll bar fails to resize when content is dynamically removed in Player or Play Mode
- Error "Shader error in 'Shader Graphs/ScrollingHologram_Graph" when switching HDR Debug Mode to Gamut View
- "Unable to add Renderer to the Scene after Culling.“ and “NullReferenceException: Object reference not set to an instance of an object“ errors spawned when changing the light shadow settings in the Player
Resolution Note:
Bolt 2 will not be released as its own product. See https://forum.unity.com/threads/visual-scripting-roadmap-update-august-2020.951675/ for details.