Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
5.2.4
6.0.5
Issue ID
PBLD-230
Regression
No
ProBuilder shaders are included in build when no ProBuilder materials are used
How to reproduce:
1. Create a new empty project
2. Open the Package Manager
3. Navigate to the “Unity Registry” tab, and install the ProBuilder package
4. Select File → Build Profiles → Build
5. Close the Editor once the build finishes
6. Open the “Editor.log” file
7. Press CTRL+F and search for “Compiling shader "ProBuilder6/Standard Vertex Color"“ (6.0.5) or “Compiling shader "ProBuilder/Standard Vertex Color"“ (5.2.4)
8. Observe the result
Expected result: No shaders are compiled (After scriptable stripping: 0 in each section)
Actual result: Several variants are compiled (After scriptable stripping is nonzero)
Reproducible with: 5.2.4 (2022.3.61f1), 6.0.5 (6000.0.47f1, 6000.1.0f1, 6000.2.0a9)
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested
Notes:
- If the project is rebuilt several times, make sure to select “Clean Build” so the shaders are recompiled
- Where to find the “Editor.log” file: [https://docs.unity3d.com/6000.0/Documentation/Manual/log-files.html|https://docs.unity3d.com/6000.0/Documentation/Manual/log-files.html|smart-link]
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
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Resolution Note:
Thank you for reporting this issue and helping us identify potential areas for improvement. After careful evaluation, we have determined that this bug has a low impact on functionality or user experience and does not currently align with our immediate priorities.
While we greatly value your feedback and insights, we are unable to address this issue at this time as we are focusing our efforts on higher-priority bugs and improvements that affect a larger proportion of users or core functionality. Rest assured, we’ve documented this bug in our backlog for future reference, and it may be revisited as priorities evolve.
We understand that this might not be the outcome you hoped for, and we sincerely appreciate your patience and understanding. Your feedback is always valuable, and we encourage you to continue sharing any other concerns or ideas you may have.