Search Issue Tracker
Fixed
Fixed in 1.8.0
Votes
0
Found in [Package]
1.7.7
Issue ID
UVSB-2348
Regression
No
Serialization errors are thrown in the Player when Managed Stripping Level is set to High
Reproduction steps:
1. Open users attached project
2. Navigate to Edit > Project Settings > Player > Other Settings
3. Change Managed Stripping Level to Low
4. Go to File > Build Settings and press Build And Run
5. Open the Player.log file and observe the errors
6. Change Managed Stripping Level to High
7. Repeat 4-5 steps
Expected result: Visual Scripting is maintain similar levels of functionality with all Managed Stripping Level levels
Actual result: Visual Scripting components are stripped thus causing its functionality to fail
Reproducible with: 1.7.6 (2021.2.19f1), 1.7.7 (2021.3.1f1), 1.8.0-pre.1 (2022.1.0f1, 2022.2.0a11)
Couldn't test with: 2019.4.38f1, 2020.3.34f1 (Visual Scripting not supported)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment