Search Issue Tracker
In Progress
Fixed in 7.0.7, 10.0.0-pre.1
Fix In Review for 9.0.2
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)
-
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
- The terrain appears darker when "Per-pixel Normal" is enabled
- [Linux] Editor assertion causes Test Runner to fail when executing it in Batch Mode
- Color selection by the mouse cursor is still enabled when the "Esc" button is pressed
- Game view becomes black and the Scene window becomes grey, “ArgumentOutOfRangeException” errors and “Render Pipeline error” warnings appear after changing the name or deleting URP/HDRP global settings file
- Transform Component is not accessible inside the Player when RuntimeInitializeOnLoadMethod is used
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