Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2017.4.X, 2018.3.X
Votes
1
Found in
2017.2.1f1
Issue ID
1022819
Regression
No
Can't load a scene from asset bundle if scene has a period in the name
To reproduce:
1. Open users attached project "TestProject.zip"
2. Enable Development Build
3. Open the built project
4. Press Assets/Test.1.unity button
Expected result: scene is loaded
Actual result: getting
Scene 'Assets/Test.1.unity' couldn't be loaded because it has not been added to the build settings or the AssetBundle has not been loaded.
To add a scene to the build settings use the menu File->Build Settings... error
Reproduced on: 2017.1.3p3 2017.2.1f1 2017.2.2p3
Notes:
Scripting Runtime Version: Experimental (.NET 4.6 Equivalent)
Api Compatibility level: .Net 4.6
Was unable to test on iOS device, only getting a black scene.
Can not test on 5.6.x because of the C# 4.0 errors
From 2017.3.0a2 to 2018.2.0a9 crashes the build
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Font character thickness does not adjust properly in UI Toolkit text when changing Bold Weight in Font Asset
- Multiple "[...] is inaccessible due to its protection level" errors are thrown when opening project with Unity Version Control installed
- Font character thickness does not adjust properly in UI Toolkit text when changing Bold Weight in Font Asset
- Sorting icons are tiny and misaligned in Import Activity window
- The Undo system does not record HideFlags.HideInHierarchy changes
Add comment