Search Issue Tracker
Fixed in 2017.1.X
Votes
2
Found in
2017.1.0b5
Issue ID
912745
Regression
No
[Windows] Calling Camera.Render() in headless mode (-batchmode) causes the scene/time to halt
Repro steps:
1. Open provided project
2. Click on "File" -> "Build Settings" -> "Build"
3. Create a shortcut of the just built .exe file
4. Right click on the shortcut and press "Properties"
5. In the "Target" field, after all the text, write "-batchmode"
6. Press "OK"
7. Start the build with the shortcut (A folder should appear called "UnityHeadlessRenderingScreenshots" where 20 screenshots should appear over 20 seconds, showing whats happening inside the game)
8. Enter that folder and see that all the screenshots are the same
Expected result: The screenshots should look different as time has passed in the build
Actual result: The screenshots all look the same even though time has passed in the build
Reproduced with: 5.6.0b3, 5.6.0b5, 5.6.0b11, 5.6.0f1, 5.6.0f3, 5.6.1p1, 2017.1.0b6, 2017.2.0a1
Regression first introduced in: Version 5.6.0b3 (358ff4ed3952)
Did not reproduce on(All screenshots are grey): 5.5.3p4, 5.6.0a1, 5.6.0b1, 5.6.0b2
Note:
There is a particle system in the project and because of it,you should clearly see that the screenshots have changed.
This affects only the particle systems and UI components
Normal mesh based GameObjects will rendered as expected
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
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
bhayward_incrowd
May 23, 2017 09:48
I am surprised that you were not able to reproduce this in 5.6.1. We have tried this in 5.4.2f2, 5.6.1f1, 5.6.1P1 and 2017.1.0b5. Are you able to send us some of the output screenshots to confirm that it works with 5.6.1p1? This GIF demonstrates the issue reproduced in 5.6.1p1: gfycat.com/WellwornSelfassuredIguana