Search Issue Tracker
Fixed
Fixed in 2021.3.7f1, 2022.1.8f1
Votes
0
Found in
2021.3.0f1
2022.1.1f1
Issue ID
UUM-1822
Regression
Yes
[Backport] Failed to load a custom asset when using Naninovel package
Reproduction steps:
1. Open the user's project "Test.zip"
2. Select `Assets/Scripts/TestScript.nani` asset
3. In the Inspector window edit the first line (change "1" to anything else)
4. Press "Apply" button
Expected result: Asset is saved without warnings.
Actual result: A "'' does not exist" warning is logged.
Reproducible with: 2021.2.0b8, 2021.2.4f1, 2022.1.0a3, 2022.1.0a17
Not reproducible with: 2019.4.3f1, 2019.4.33f1, 2020.3.23f1, 2021.1.0a5, 2021.1.28f1, 2021.2.0b1, 2021.2.0b7, 2022.1.0a2
Couldn't test with: 2019.4.2f1, 2021.1.0a4, 2021.2.0a15 (losing the package when converting the project to these versions)
Notes:
- Couldn't test on some versions and reproductible on all the other versions with macOS (no not reproductible with versions)
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 in Shader Graph Assets/Samples/Shader Graph/17.1.0/Production Ready Shaders/Lit/URPLit.shadergraph: Graph is generating too many variants…” error is thrown after importing Shader Graph Samples
- ComputeShader cannot access the depth element of RenderTexture targeted by an HDR camera
- Search in the Console window highlights wrong text when text contains HTML attributes
- Particle System doesn't always play when ParticleSystem.Play() is called
- Build Profiles: The vertical and horizontal window lines are different colors and this is not consistent with the other engine windows
Resolution Note (fix version 2022.1.8f1):
Fixed in 2022.1.8f1
Resolution Note (fix version 2021.3.7f1):
Fixed in: 2021.3.7f1