Search Issue Tracker
Fixed in 10.2.0
Votes
0
Found in [Package]
Master (481375fefe)
Issue ID
1284033
Regression
Yes
[Shadergraph] Second Input port of Divide node after being disconnected has value of 0 but shows 2
Reproduces on Master (481375fefe)
reproduces on 9.x.x/release (2ddf9def91)
doesn't reproduce in 8.x.x/release (4b3e9d383d)
Repro steps:
1. Create a "Float" (or "Vector 1") node, leave it as 0
2. Drag out the output of the float node, when the searcher opens choose "Divide" with slot B
3. Plug the float node's output into the Divide node's A input
4. Delete the float node's connection to the Divide node's B input
Expected result: the preview of the Divide node should be black, because it's 0 being divided by 2
Actual result: the preview of the Divide node is NAN indicating that B is still being treated as 0 even though it displays 2
Note: changing the slot value for B to some number and then back to 2 will make it behave properly
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment