Search Issue Tracker
Fixed in 4.1.1
Votes
0
Found in [Package]
4.1.0
Issue ID
1167692
Regression
Yes
[ProBuilder] Experimental tools are exposed to users regardless of preferences
[ProBuilder] Experimental tools are exposed to users regardless of preferences
After installing ProBuilder, user preferences will be expanded with settings for ProBuilder, including the option to enable Experimental features, which is disabled by default. Currently this preference is ignored and experimental features (Boolean operations for example) are exposed to the user by default.
Steps to reproduce:
- Launch Unity with a new 2019.3 project, installing the ProBuilder package via Package Manager (on staging at this time, alternatively you can download the attached project)
- Menu: Edit > Preferences > ProBuilder > Observe the “Experimental Features Enabled” setting is disabled by default
- Menu: Tools > ProBuilder > Experimental > Boolean (CSG) Tool > Observe this experimental option is exposed to the user regardless of preference
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment