Search Issue Tracker
Fixed in 2017.1.0f3
Fixed in 5.6.X, 2017.2.X
Votes
0
Found in
5.6.2p1
Issue ID
925765
Regression
Yes
Moving multiple objects makes only one of them to move according to handles
Steps to reproduce:
1. Open attached TransformIssue.zip project
2. Open scene "repro"
3. In hierarchy's search bar search for "a"
4. Select all objects named "a"
5. In scene view, try to move selected objects using transform handles
6. Notice that only one follows transform handles
Reproduced with: 5.6.2p1, 2017.1.0f1, 2017.1.0f2, 2017.2.0b1
Not reproducible: 5.6.2f1, 2017.1.0b10
Regressed in, 5.6.2p1, 2017.1.0f1
Fixed in 2017.2.0p1
Comments (12)
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Vilmantasj
Oct 23, 2017 20:50
Very annoying bug. When can we expect a fix for this in 2017.2.x?
kemalakay
Oct 17, 2017 13:24
Fixed in 2017.3, needs to be backported to 2017.2.x, 2017.1.x and 5.6.x