Search Issue Tracker
Fixed
Fixed in 1.9.6
Votes
1
Found in [Package]
1.9.4
Issue ID
UVSB-2550
Regression
Yes
Property Provider is generated in the wrong location when the PropertyDrawer is from a custom Assembly
Reproduction steps:
1. Open the attached “BugRepro” project
2. In the Project Settings window (Edit > Project Settings…), Generate Custom Inspector Properties (Visual Scripting > Generate)
3. In the Project window, enter “PropertyProvider_MyEditorClass” in the Search bar
4. Select the Script from the search results and observe its path
Expected result: The Script’s path should be “…/Property Providers/Editor/PropertyProvider_MyEditorClass”
Actual result: The “MyEditorAssembly” Assembly Definition Platform is ignored, resulting in the Script’s path being “…/Property Providers/PropertyProvider_MyEditorClass”
Reproducible with: 1.9.0 (2021.3.29f1, 2022.3.7f1), 1.9.4 (2021.3.38f1, 2022.3.29f1, 6000.0.2f1)
Not reproducible with: 1.8.0 (2021.3.29f1, 2022.3.7f1)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment