Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.8.1
Issue ID
UVSB-2517
Regression
No
Visual Scripting Components become un-usable when a project is opened with a newer version of the Editor and the Package was updated
How to reproduce:
1. Create a new project with 2021.3.1f1
2. Install Visual Scripting
3. Add a “Visual Scripting Scene Variables” GameObject into the Hierarchy
4. Close the Project and open the project with a newer version of 2021.3
5. Update the Visual Scripting Package in the Package Manager
6. Select the “Visual Scripting Scene Variables” GameObject
7. Observe the Inspector
Expected result: Data/information is shown
Actual result: “Inspectors are disabled when plugin versions mismatch…” warning is shown and the related Components are un-usable
Reproducible with: 1.9.1 (2021.3.30f1)
Not reproducible with: 1.8.0 (2023.2.0b11), 1.9.0 (2022.3.10f1), 1.9.1 (2022.3.10f1, 2023.1.10f1, 2023.3.0a7)
Reproduced on: macOS Ventura 13.5 (Intel)
Not reproduced on: No other environment tested
Notes:
- Visual Scripting becomes completely unusable as newly created state/script machines are also affected
- Re-installing the package fixes the issue
- It would appear to only affect the 2021.3 Stream
- Cannot find the regression point as it would appear that it’s also reproducible on 2021.3.1f1
- Issue also reproducible when down-grading
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
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
- VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
- Operations on the Color32 array are not reflected in WebGL Player when HDR is off
- Rigidbody moves away from the original GameObject when Center of Mass is set in every frame
- WebGL Player does not proceed beyond logo screen when "Target WebAssembly 2023" is enabled
Resolution Note:
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration, we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues.
With the delivery of our latest release, we are now focusing on investigations and discovery to better determine how UVS needs to evolve to deliver on our broader goals, as well as being the right solution for future production needs. However, we know each case is different, so do please continue to log any issues you find, as well as provide general feedback on our roadmap page to help us prioritize.
Latest release: https://docs.unity3d.com/Manual/com.unity.visualscripting.html
Roadmap: https://unity.com/roadmap/unity-platform/gameplay
Reinstalling the Package fixes the issue.