Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.67f1
6000.3.10f1
6000.4.0b9
6000.5.0a7
Issue ID
UUM-134937
Regression
No
[Linux] No “File already exists” pop-up thrown when saving Shader Variants with an already existing name from Build Profiles or Project Settings window
Steps to reproduce:
1. Create new Unity project
2. Open Build Profiles window
3. Add Build Profile
4. Press “Add Settings” button and add Graphics Settings
5. Scroll down to find “Shader Settings”
6. Press “Save to asset...” button
7. Save New Shader Variants
8. Press “Save to asset...” button again
Actual results: user is allowed to save identical Shader Variants without changing the name, no pop-up is thrown, informing about already existing file
Expected results: Pop-up stating “NewShaderVariants.shadervariants” already exists. Do you want to replace it?” is thrown to the user
Reproducible with versions: 6000.0.67f1, 6000.3.10f1, 6000.4.0b9, 6000.5.0a7
Tested on (OS): Ubuntu 24.04
Notes:
- on 6000.0.67f1, 6000.3.10f1 Shader Settings are in Project Settings > Graphics.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- Long Sprite names are not truncated in the Inspector window name label and the preview labels when a Sprite with a long name is selected
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Add comment