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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment