Search Issue Tracker
By Design
Votes
0
Found in
2.2.0
Issue ID
UUM-133899
Regression
No
Sentis shaders are present in Editor logs when building the Player without referencing Sentis in Project
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open Build Profiles (File > Build Profiles)
3. Click Build
4. After build finishes observe the Editor.log
Expected result: No Sentis shaders exist
Actual result: Sentis shaders are present
Reproducible with: 2.2.1 (6000.0.62f1), 2.5.0 (6000.0.67f1, 6000.4.0b6)
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
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
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow. The provided project does include the Sentis Inference Engine package in it's manifest . To avoid having the Sentis shaders copied to the runtime just remove Sentis from the project manifest using the package manager.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow. The provided project does include the Sentis Inference Engine package in it's manifest . To avoid having the Sentis shaders copied to the runtime just remove Sentis from the project manifest using the package manager.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.