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.
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
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/