Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
4
Found in
2021.2.0a17
Issue ID
1332465
Regression
Yes
Internal package modules that are not used in a project do not get stripped from player builds.
Repro steps:
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.
Comments (1)
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
- 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
Peter77
Jul 26, 2021 09:55
Related forum thread:
https://forum.unity.com/threads/dlss-binaries-now-ship-with-all-windows-builds-regardless-if-you-use-it.1145339/