Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.7.8
1.8.0
Issue ID
UVSB-2466
Regression
Yes
Custom inspectors are not generated automatically when using Visual Scripting
Reproduction steps
1. Open the “BugDemo” project
2. Open the "Assets/Scenes/SampleScene.unity" Scene
3. In the Hierarchy Window select the “GameObject” Game Object.
4. In the Inspector Window observe the “Variables” Component and it’s “Type” Property which has the “Tag” set to it
5. Open the “Tag.cs” script
6. Remove lines 137-143 and save the changes
Expected results: The removed lines of codes were generated in Custom Inspectors and “Tag” was removed
Actual results: The lines of code were not generated in Custom Inspectors and “Tag” is still set to “Type” Property
Reproducible with: 1.7.7, 1.7.8 (2021.3.16f1, 2022.1.24f1), 1.8.0 (2022.2.2f1, 2023.1.0a25)
Could not test with: 2020.3.44f1 (Visual Scripting is not available for this version)
Not Reproducible with VS 1.7.6
Reproduced on: Intel MacOS 13.1
Notes: The manual creation of the “SerializedPropertyProviderAttribute” for the data type functions as a workaround
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
Fixed in 1.9