Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.7.8
1.8.0
Issue ID
UVSB-2480
Regression
No
PropertyDrawer not detected/used for VisualScripting when not in Editor folder
Reproduction steps:
1. Open project “VSPropDraw”
2. Open the “VS” script graph through the Project Window
3. Select the Node
4. Observe the Graph Inspector window (top left)
Expected result: No warnings are displayed for CounterB - PropertyDrawers are collected/used regardless of location
Actual result: A warning is displayed for CounterB - PropertyDrawers are only collected/used when in the Editor folder
Reproducible with: 1.7.8 (2021.3.0f1, 2022.2.0f1), 1.8.0 (2021.3.20f1, 2022.2.10f1, 2023.1.0b7, 2023.2.0a5)
Couldn’t test with: 1.8.0 (2020.3.46f1) (due to compiler errors)
Reproducible on: macOS Catalina 10.15.7 (Intel)
Notes:
- CounterA's PropertyDrawer is stored in the VS/Editor folder, CounterB's PropertyDrawer is stored in the CounterB.cs file
- Regenerating Nodes/Inspectors doesn't change the behavior
- If “Inspectors are disabled when plugin versions mismatch to prevent data corruption” is displayed after changing versions - go to Edit > Project Settings. In the Project Settings window, select Visual Scripting and click on the Generate button in the Custom Inspector Properties section
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UVSB-2466