Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2018.2.X
Votes
10
Found in
2018.2.0a1
2018.2.0f2
Issue ID
1064071
Regression
Yes
Building Legacy Sprite Atlases in batchmode with -nographics results in Point sampled Atlases
Steps to reproduce:
1. Open QA attached project
2. Build the project using the "build/build.bat" (Adjust Unity.exe path to match setup).
3. Open the built game
4. Notice that the sprite using point filtering
5. Open the project in editor
6. Observe the sprite using bilinear filtering while the editor is on stop.
7. Press play and observe the sprite is using point filtering in play mode because unity switches using the previously packed sprite sheet instead
8. Change any of the sprite import settings causing the sheet to be repacked in editor
9. Press play and observe the sprite getting fixed
Expected result: Building Legacy Sprite Atlases in batchmode with -nographics should not result in Point sampled Atlases
Reproduced in: 2018.3.0a6, 2018.2.1f, 2018.2.0a1
Not reproduced in: 2018.1.9f1, 2017.4.7f1, 2017.3.2f1
Regression since: 2018.2.0a1
Fixed in: 2018.3.0a9
Reproduced on Windows player, Android and Editor
Comments (2)
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
- Getting a deprecated package for JetBrains Rider pop up when opening or creating a project
- [Android] Volume level of the same audio file is different on Samsung Galaxy Tab A8 between 2023.3.0b3 and 2023.3.0b4
- ‘Expected end of value’ warning occurs when a property declaration includes five or more variable references
- Crash on BurstCompilerService::CompileAsync when entering Play mode in a specific scene
- InvalidOperationException when using Game Camera Preview in Scene window with a custom RenderGraph pass
Cheerio
Jul 31, 2018 15:54
Thank you for fixing this!
unity_T2AJrYJSFRsrkA
Jul 26, 2018 23:43
This issue doesn't seem to be specific to the legacy sprite packer. We updated our sprites to use the more recent sprite packing and the issue still persists.