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
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
- "GetPreferedValue" returns max value when using auto-sizing
Resolution Note:
Fixed in 1.9