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
- 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.8f1):
Fixed in 2022.1.8f1
Resolution Note (fix version 2021.3.7f1):
Fixed in: 2021.3.7f1