Search Issue Tracker
Not Reproducible
Votes
0
Found in
2019.4
2019.4.3f1
2020.2
Issue ID
1273545
Regression
No
Objects are rendered in a different order when running the build in batchmode
How to reproduce
1. Download the attached project from the Google Drive link
2. Create a standalone (Windows) build in a selected folder and run it
3. Open the folder (which contains the build), then open and observe 'the test.png' file
4. Run the build in the Command line with '-batchmode' argument
5. Open and observe 'the test.png' file again
Expected result: The spheres are rendered in front of the text
Actual result: The spheres are rendered behind the text
Reproducible with: 2019.4.9f1, 2020.1.4f1
Not reproducible with: 2020.2.0b2
Cannot test with: 2018.4.27f1 (due to errors)
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:
In 2020.2.0b2 it became not reproducible