Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.55f1
6000.1.15f1
6000.2.0f1
6000.3.0a4
Issue ID
UUM-113218
Regression
No
Inconsistent spacing in Inspector Shader selector names list
Steps to reproduce:
1. Create new Unity project
2. In Project window create a new Material (Right-click > Create > Material)
3. Select the Material
4. In Inspector window open “Shader” dropdown window
5. Select “VR”
6. Observe “SpacialMapping” naming
Actual results: “SpacialMapping” has no space in its naming
Expected results: naming should have a space in “Spacial Mapping”
Reproducible with versions: 6000.0.55f1, 6000.1.15f1, 6000.2.0f1, 6000.3.0a4
Tested on (OS): macOS Silicon, Sequoia 15.5
Notes:
Identical issue also with:
Shader Graphs >
ArnoldStandartSurface
ArnoldStandardSurfaceTransparent
FullscreenInvertColors
PhysicalMaterial3DsMax
PhysicalMaterial3DsMaxTransparent
VFXSpriteLit
VFXSpriteUnlit
Autodesk Interactive>
AutodeskInteractive
AutodeskInteractiveMasked
AutodeskInteractiveTransparent
Nature>
SpeedTree7
SpeedTree8
Unlit>
SimpleDots
SimpleSpeedTreeDots
TestReportShader
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
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
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.