Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.0.0
Issue ID
UNDB-3
Regression
No
Merely adding com.unity.rendering.denoising package to an empty project doubles the build size
Repro steps:
1. Create an empty Unity project
2. Build it for Windows
3. Notice the output size is around 66 MB
4. Add com.unity.rendering.denoising package to the project manifest. Do not actually use any of its features or reference it in any other way from any scenes
5. Build the project for Windows again
6. Notice the output size is 137 MB.
Packages should not significantly affect build size just by the virtue of being in the project unless they are actively used by project settings or one or more scenes.
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
- Text overlap and is unreadable in Inspector > Terrain Paint Texture after creating new Terrain Layer
- Event "XRInputSubsystem.trackingOriginUpdated" triggers twice when recentering the view
- UITK TextField value is overwritten incorrectly by the converter result when Binding Mode is set to "To Source"
- Out of memory crash when selecting more than 80000 Assets simultaneously
- Test Runner fails to create a script in the active path when selecting a file as the active path
Resolution Note:
According to the package and il2cpp teams, there is no stripping mechanism for native plugins. The increase in player build size is expected and only affects projects that explicitly include the denoising package.
Games should not enable a package for offline neural-network based denoising. The applications that require this are usually in the "verticals" space and the extra size is expected (as the underlying neural networks require some space).