Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Internal package modules that are not used in a project do not get stripped from player builds.
1) Create a simple project in URP, HDRP or built-in render pipeline, whichever render pipeline is desired.
2) Go to the package manager, filter BuiltIn packages, and notice that the NVIDIA package is disabled by default. This is done on purpose, we disable this package by default.
3) Build a player for 64-bit windows standalone with mono scripting backend.
4) When building is done, go to the folder of the project.
Notice that NVIDIAModule.dll/pdb, and other libraries such as NVUnityPlugin.dll and nvngx_dlss.dll are now present in the built player, despite the fact that the builtin package was not included.
The expectation is to not have libraries (nvngx_dlss.dll and NVUnityPlugin.dll) as well as the module dlls not present in the player built.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Lighting Data asset is not created when baking multiple Scenes at the same time
- Performance issues when instantiating a recognizer under UnityEngine.Windows.Speech
- Build fails with "Exception: Unity.IL2CPP.Building.BuilderFailedException: Build failed with 0 successful nodes and 0 failed ones" when building the project for iOS
- [Android] .aab Build fails when using Asset Bundles
- Builds fail without a useful error message when building a project with invalid product name