Search Issue Tracker
Won't Fix
Votes
0
Found in
5.3.0b5
Issue ID
741723
Regression
No
[Editor] Using Alt+LMB Drag reverts texture parameters only
Steps to repro
Notes: Behavior varies in 5.1x to 5.3, however I decided it was not regressive, but by design.
~ There is no definition of what ALT + LMB + Drag/Drop does in the documentation. I personally used it to duplicate to new folder.
Open Unity 5.3bx and open uploaded project.
1. Select 'Texture A' and observe inspector, the texture is set to Normal Map.
2. Do: ALT + Left Mouse Button + Drag/Drop (To another space in project window)
3. Click new copied texture 'Texture A 1'
4. Observe inspector to see Normal map is now "Texture" or "Sprite" in 5.1x
Part 2 : Comparing to materials
1. Create a new Material, we'll call it MatA
2. Drag and drop any texture to Albedo slot.
3. ALT + LMB + Drag/Drop (like before)
4. Observe new material now reverts back to 'white' (empty fields).
5. Duplicate MatA material with Ctrl+D
6. Then ALT + LMB + Drag/Drop MatA
7. Observe New material doesn't reset anymore.
8. Make changes to MatA (Change to a new albedo or set another parameter)
9. ALT + LMB + Drag/Drop MatA
10. Observe new material will revert to previously duplicated material.
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note (2019.1.X):
Hi there,
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.
Unity QA Team