1.Duplicating or pasting game objects changes rectTransform x and y positions to weird decimal places
WHY?!
2. Pasting a selection of game objects rearranges their order
WTF?!
3. Adding new files to the project changes the folder I was in in the Project tab STAHP! Example: I have 2 Project Tabs in my Editor layout, one for sprites and one for scenes. Sometimes when adding new files to my project, all Project Tabs would change to a random folder in my project.
4. Pasting prefabs into a canvas up-scales the prefab, even though both the prefab and canvas scale are set to 1 (this does not happen on run time) NO REASON TO SCALE UP!
These bugs drive me absolutely insane! I am using 5.4.1f1, so can anybody using the latest version confirm if these issues still occur? I cannot fathom how they still exist, surely this is affecting everyone? Where can I report these bugs or see if they are already reported?
Umm well, the “weird decimal places” part is just a floating point precision thing, the numbers have been converted to scientific notation, they still are really close to the actual value they were set at. That isn’t really a glitch at all, but just how things are done in almost every engine or software that has to calculate huge decimal numbers.
I agree that the way duplicated objects are not pasted in the same order might be frustrating, but I never have really been bugged by it, just because I usually dupe one thing at a time.
The other two things you mention I am not familiar with or have never experienced, and I work with the UI a lot. Maybe you are using some UI scaling type components that are changing it for some reason?
I can’t say I’ve ever noticed unity changing things I’ve typed directly into the inspector when duplicating…
For me it always seem to stay where I had it put, and the only time I get the numbers becoming any different, is after doing some kind of transform using the handles (dragging the arrows in the scene view) or perhaps when sliding the values in the inspector (dragging left and right on x or y transform) but not when duplicating. Here I duplicate and the numbers stay the same:
This is what happens to me. Not to every single game object, but usually to more complex prefabs and its children. As you can see the scale is also affected if not set to 1.
Ahh so you have your prefab deeply nested under other gameobjects? That might be the problem. I’m not sure why, but for some reason, the more parents each transform gets, the worse its precision gets, and although your entering 0, the engine has to remember 0 + 0.000 + 0.000 + … for a lot of transforms… and the deeper it is, the worse the precision becomes. At least that is my understanding. Or best guess
Maybe try just having it a more shallow nesting, remove a few things if you can somehow, and get it closer to the root object.
I am on 5.5.1p3 right now.
EDIT: Actually I can’t prove that theory, because I made a really deeply nested object and it still keeps the numbers I had when I duplicate. Maybe try duplicating root objects and see if the same thing happens to you though?
Ok well scratch that idea. I have no idea off the top of my head why that happens to you all the time. Maybe somebody else will come along and have better answers
EDIT: Oh ya know what, @enchiridion - might be a bug, check this out:
Hello guys, well the development team decided it was a “floating point precision issue” when they responded the bug report when this issue was reported quite a while ago and instead of using an epsilon to determine if there is an actual and meaningful change to the transform they just update it.
You might also find interesting this report as well:
I gotta say, there likely is more to “fix” here than just “copy x and y and z, duplicate, paste xyz…” and it’s gotta be some kind of deeply rooted problem if they are ignoring it. Has to be right?
I wonder why it doesn’t seem to ever cause me problems? Do you think the latest versions might have addressed this without any indication on those bug reports?
The actual question is “Why is not set up to just copy xyz when duplicating in the first place”. Literally no calculation needs to happen, especially when it is only affecting the parent!
Except that is not a correct statement. There’s a layout engine behind the UI that has to run every UI component through a set of calculations based on screen size, anchors, parent anchors, layout components, and on and on. When you do single precision floating point math you get around 7 significant digits. When running numbers through all of those calculations you’re going to get precision issues. For your issue, 0.00000000007 is not materially different from 0. Unity says it’s a floating point precision issue because that is in fact the case. If you really don’t like seeing the scientific notation then manually change it back to 0. Is it annoying? Sure. But calling it a bug is incorrect.
Again, it shouldn’t even be doing calculations, just duplicating what’s already there, you know, mirror image, replica, exact double.
When duplicating, the UI should not be going “ok copy object → parent the object in the canvas → check canvas settings/scales etc → position newly pasted object with corresponding values”, and instead be going “ok copy object → paste object with exact values of original object”.
That’s not how UI layout systems work. Unity has no idea what particular combination of custom UI components live on the objects you just copied. What if these objects live in a vertical layout container? They all have to be laid out again after you paste them. It would not be practical to examine the objects you’re pasting to determine which ones may or may not need to be laid out, especially when you can create your own custom layout components. The only practical way of dealing with this is to run everything through the layout engine every time there’s a change.
