Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2017.3.0f3
Issue ID
983805
Regression
No
Sprite.Create() is Creating a sprite with incorrect bounds
How to reproduce:
1. Open QA provided stripped project "SpriteCreateBounds.zip"
2. Enter play mode
-- Notice one sprite is at the centre of camera viewport, and another one is perfectly following the mouse
3. Exit play mode and open "ColourPlacementCircle.cs"
4. Comment out line 41 (Sprite.Instantiate) and uncomment line 42 (Sprite.Create)
5. Enter play mode again
-- Notice that both sprites are offset to bottom left and not visible on the screen
Sprite.Instantiate() Bounds: Center
Sprite.Create() Bounds: -496, -496
Reproduced on: 2017.1.3f1, 2017.2.1p2, 2017.3.0p2, 2018.1.0b3, 2018.2.0a1
By design - Updated docs to reflect actual behaviour.
The correct pivot value that is passed into Sprite.Create should be normalized to (0,0) -> (1,1) where (0,0) is bottom left, (1,1) is top right (center will be (0.5, 0.5))
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- GfxDevice::UpdateBufferRanges when running UIBuilder tests
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
Add comment