Search Issue Tracker
Fixed
Fixed in 7.0.7, 9.0.2, 10.0.0-pre.1
Votes
0
Found in [Package]
7.0.5
Issue ID
DANB-239
Regression
No
BezierUtility.BezierPoint function parameters are not in the right order
To reproduce:
1. Open the project “Test_sprite_shape”
2. Observe the Scene view
Expected result: The red line repeats the controller form
Actual result: The green line repeats the controller form
Reproducible with: 7.0.5 (2021.3.9f1)
Could not test with: 2020.3.40f1 (Package errors), 2022.1.16f1, 2022.2.0b8, 2023.1.0a10 (The shape is not visible)
Reproduced on: macOS Monterey 12.5.1 (Intel)
Comments (2)
-
pmurph03
Nov 02, 2022 17:51
Nevermind, that's incorrect as well.
-
pmurph03
Nov 02, 2022 17:34
For other people who are having this issue and discovered this issue tracker, in version 7.0.6, the method displays BezierPoint(startRightTangent, startPosition, endPosition, endLeftTangent), and will give an incorrect result.
To get the correct result instead use BezierPoint(startPosition, endPosition, startRightTangent, endLeftTangent)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 10.0.0-pre.1):
Fixed for this issue will be available on 2D SpriteShape package 10.0.0-pre.1 and above
Resolution Note (fix version 9.0.2):
Fix for this issue is available on 2D SpriteShape package 9.0.2 and above