Search Issue Tracker
Fixed in 5.1.0
Votes
2
Found in
4.6.3p3
Issue ID
684401
Regression
Yes
Infinity fields cannot be set to Infinity after setting them to something else
To reproduce:
To reproduce:
1. Add a Hinge Joint to any game object
2. Set Break Force to any non-Infinity value (41, for example)
3. Set Break Force to Infinity
Expected result: It is set to Infinity
Actual result: it's set to 3.402823e+38
Note: This is probably only reporting difference, as it's likely that the values are the same internally.
Comments (3)
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
- 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
ChBasitGill
Aug 26, 2016 12:01
Same issue.
Pequisto
Apr 22, 2015 13:33
Same issue -- is there a workaround?
Drake088
Apr 21, 2015 03:43
I get the same 3.402823e+38 error when attempting to set Drag to infinity in a Rigidbody component.