Search Issue Tracker




Found in [Package]



Issue ID




PropertyDrawer not detected/used for VisualScripting when not in Editor folder

Package: Visual Scripting


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)

- 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

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.