Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.5.2
1.6.0
Issue ID
UVSB-1405
Regression
No
Comparing Not Equal on 2 exact int values return the wrong result.
Reproducible on:
- Visual Scripting version: 1.6, 1.5.2
- Unity version: 2021.1.0f1
Steps to Reproduce:
- Create a new game object
- Add to it a script machine with a script graph attached to it
- Create a simple graph using the Add Input and Not Equal node like the graph below
!NotEqual.JPG|thumbnail!
- Click to play
Outcome results:
- It seems that the Add Input node outputs a float, so when the user compares if Not Equal even if it's comparing exacts numbers will return true.
Expected Results:
- Add Input node should return the same type of the inputs being added, so when the user compares exact inputs the Not Equal node will return the proper results.
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
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
Resolution Note:
https://github.cds.internal.unity3d.com/unity/com.unity.visualscripting/pull/365