The notes for builds 2016.2928 and 2016.2931 state the following about display.save. I have not tried with these new builds (yet) but prior to these builds I had been experiencing intermittent issues with display.save saving blank images instead of the display object to the file system. The issue only occurs on the device and is not easy to reproduce (both iOS and Android). But it has happened often enough that I cannot rely on display.save so I have removed it from my code. Can I please get more details about what was actually fixed in regards to display.save in these recent builds? I could certainly do my own testing to see if my issue has gone away, but if the past is any indication, the issue could appear to have been resolved and then after several days just "randomly" happen again. Needless to say, I'd like more clarity on these fixes before spending more time on this. Thank you!
- Core: fixing new display objects not triggering scene update after display.save()
- Core: fixing culling offscreen objects with display.save. Casenum 43011