Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2020.2.0b5
Issue ID
1281291
Regression
No
Invisible asset is created in Project Browser when create a material with 260+ symbols name
How can we reproduce it (please see attached gif)
1 Create new Project
2 Go to Project Browser and do RightMouseClick->Create->Material and set 260+symbols name (e.g. 1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890a1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890a12345678123456789012345678901234567890123456789011111111111111111111)
3 Click somewhere on the screen or press Enter
4 Pop up will appear - press Cancel
5 Click on empty space near the last asset in Project Browser
Actual result: an invisible object is created
Expected result: there should not be any invisible objects
Note: after Editor restart - the invisible object disappears
Checked only on Windows 10:
- Reproduces on 2020.2.0b5 and 2021.1.0a1
- On 2019.4.2f1 the behavior is slightly different - the same pop up (on step 4) appears two times in a row and after pressing Cancel on both of them the Invisible object doesn't appear - so, I am not sure if we should call this a regression or not (2 popups are the problem, but Invisible object doesn't appear) - feel free to change that field
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- Scene dependency changes do not trigger a scene re-hash during Content Archives build
Add comment