Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.1.0p2
Issue ID
939236
Regression
No
NPOT Textures cause Clean Builds to fail without warning
How to reproduce:
1. Open the attached project (notice the textures are rendered correctly)
2. Close the project and delete the Library folder from project's directory
3. Using batch mode build the project with this command (change the paths according to your machine):
"%ProgramFiles%\Unity\Editor\Unity.exe" -batchmode -quit -nographics -buildtarget win64 -projectPath "F:\Temp\TestNPOT" -buildWindows64Player "F:\Temp\NPOTTestBuild\TestBuild.exe" -logfile "F:\Temp\NPOTTestBuild\unitybuild.log"
4.Open the built project, the textures are not rendered
5.Open the project in the Editor, textures are not rendered and errors appear
Actual result: Textures are not rendered in the build and errors in editor appears.
Expected result: Textures should be rendered in the build and no errors should appear.
Reproducible with: 2017.1.0p2, 5.6.3f1.
Not Reproducible with 2017.3.0a3, 2017.2.0b6.
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
diekeure
Dec 05, 2017 15:32
It was reproducible in 2017.1.0p2, I can reproduce it in 2017.1.2p2
Can it be fixed in those versions? I cannot upgrade anymore to 2017.2