Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2021.2.0a5
2021.2.0b11
2022.1
Issue ID
1364651
Regression
Yes
Scene can't be enabled because it doesn't exist after deleting a folder with "_" character at the beginning of the name
How to reproduce:
1. Open the attached "136451.zip" project
2. Open the "NewScene" Scene in the "_Folder" folder
3. Enter and exist the Play mode
4. Delete the "Folder" folder
5. Open the "SampleScene" Scene
6. Open the Package Manager or Project Settings
7. Observe the console window
Expected result: There are no error messages
Actual result: "[Scene path] can't be enabled because it doesn't exist" error message appears
Reproducible with: 2021.2.0a5, 2021.2.0b13, 2022.1.0b11
Not reproducible with: 2019.4.30f1, 2020.3.19f1, 2021.1.22f1, 2021.2.0a4
Notes:
1. It reproduces only when a character "" is at the beginning of the name (Examples: "Folder", "").
2. Got compilation errors on 2019.4.30f1 and 2021.2.0a5 when downgrading. Tested by creating a new project -> creating a new folder -> naming it "_" -> creating a scene in the folder -> following reproduction steps.
Comments (2)
-
spider853
Apr 10, 2023 14:01
2021.3.16f same issue, can't get rid of it after deleting a scene
-
ratking
Feb 20, 2023 11:03
Will this get fixed in 2021.3 too? If not, why not?!
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a14