Search Issue Tracker
Fixed in 2017.1.X
Votes
32
Found in
5.6.0f1
Issue ID
893559
Regression
Yes
Rect Transform position values are set to NaN, when Rect Transform is created via script and canvas is scaled to 0.01
To Reproduce:
1. Open project
2. Play scene
3. In hierarchy choose 'Sizer' object in 'Canvas- Scale 0.01'-> 'Table Holder'-> 'TablePro'->'New Game Object'
4. Repeat 3rd step with 'Canvas- Scale 1' game object
Expected: no NaN values in Rect Transform position
Actual result: Sizer's object Rect Transform position has NaN values, also error is thrown: 'Assertion failed on expression: 'IsFinite(outDistanceForSort)''
Reproduced on: 2017.1.0a5, 5.6.0b3, f2
Not reproducible on: 5.5.2p3, 5.6.0a1, b1
Regression introduced in 5.6.0b3
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
- Red squares instead of ticks in Import Activity Window options dropdown
- Multiple simultaneous input with the touch screen sometimes leaves button in not default state
- Crash on ShowDelayedContextMenu(bool) when changing the Size options of a Visual Element in the UIToolkit Inspector
- Crash when total memory consumption is over 2GB
- Red dots are rendered when copying texture with ASTC format and CompressGpu
fredericoraiss
Apr 29, 2017 06:20
Not yet fixed? :(
I have the same problem!!! I need to update my game and it's giving this problem!
I use unity 5.6 f3
darkhog
Apr 20, 2017 15:05
Got info from QA person that it might be fixed for 5.6.0p3 but since it's not released yet and I cannot check it, take it with a grain of salt.
darkhog
Apr 20, 2017 14:03
Whhops, typo. I've meant "sent my entire project"
keni4
Apr 20, 2017 13:57
Unity 5.6.0 p1 broke my UI
darkhog
Apr 20, 2017 13:11
Sent my entire problem to Unity along with exact steps how to reproduce the bug on it. Hopefully it'll help fix it faster. Will try 5.6.0p1 to see if it was fixed there and will report the results.
Jromano0
Apr 20, 2017 03:37
I have upgraded the Editor today from 5.5 to 5.6 and I get this error. But, I don't believe about the solution showed in this case. Do I have to upgrade to a beta version to get the fix?
vzlomvl
Apr 18, 2017 09:22
This is problem. Now we can not use 5.6 =/
Menion-Leah
Apr 13, 2017 17:20
Great, after wasting a few hours trying to get rid of that issue, I eventually installed latest Unity beta (2017.1.0b1)... and issue is NOT fixed.
Guys, this is a serious game stopper, our UI is totally screwed up.
pixelsplit
Apr 11, 2017 14:40
So is there gonna be a fix for 5.6 too or will this be only fixed in 2017? o.O This is making 5.6 useless for us.
Gecube88
Apr 10, 2017 02:29
Eagerly awaiting a fix for this