Search Issue Tracker
Fixed
Fixed in 6000.3.11f1, 6000.4.1f1, 6000.5.0a9, 6000.6.0a1
Votes
0
Found in
6000.3.0f1
6000.4.0a5
6000.5.0a2
6000.6.0a1
Issue ID
UUM-128715
Regression
No
Certain Painter2D properties are missing the get accessors
How to reproduce:
- Create and open a new project
- Import the “Test.cs“ script
- Observe the Console
Actual result: 4 errors for the “painter.fillGradient“, “painter.dashPattern“, “painter.fillTexture“, and “painter.strokeFillGradient“ properties are thrown
Expected result: No errors are thrown
Reproducible in: 6000.3.0f1, 6000.4.0a5, 6000.5.0a2
Could not test in: 6000.0.63f1, 6000.2.14f1 (The four properties have not been introduced yet)
Reproduced on: Windows 11 Pro (25H2)
Not reproduced on: No other environment tested
Note: All errors read: “The property or indexer ‘[property]’ cannot be used in this context because it lacks the get accessor“
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
- Active quality level set on a new Universal 2D project is not the default quality level when creating a new project
- Inspector Open button does nothing when navigating to a different folder with a locked asset
- Pre-generated XML serializers fail to deserialize types that use polymorphism when the Player is built with the IL2CPP scripting backend
- Editor crashes with error "Failed to present D3D11 swapchain due to device reset/removed" and Player freezes when rendering a particle system while using modified URP package on DX11
- Crash on Scripting::LogException when async HTTP callback executes after scripting domain teardown
Resolution Note:
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.5.0a9):
Fixed in 6000.5.0a9
Resolution Note (fix version 6000.4.1f1):
Fixed in 6000.4.1f1
Resolution Note (fix version 6000.3.11f1):
Fixed in 6000.3.11f1