Search Issue Tracker
Won't Fix
Won't Fix in 1.15.X
Votes
0
Found in [Package]
1.14.2
1.15.0
Issue ID
ISXB-1731
Regression
No
Input Actions Asset Icon is obscured in the Inspector when the Asset is assigned as a Project-wide Input Actions Asset
Steps to reproduce:
- Open any Project with the New Input System Installed
- In the Project Browser create and select an Input Actions Asset
- In the Inspector observe the Asset Icon
- Click the button "Assign as the Project-wide Input Actions"
- Observe the Asset Icon again
Actual results: When the Asset is assigned as a Project-wide Asset and the Inspector Layout changes, the Asset Icon is obscured a bit from below
Expected results: Icon isn't obscured
Reproducible with versions: 1.14.2, 1.15.0 (6000.4.0a2)
Tested on (OS): Windows 11
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
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (1.15.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.