Issues with Snapshots resuming on Android

Solar2D Advanced Graphics
#1

Things are going well with our current project using Graphics 2.0, but we are looking to ship on Android and at the moment, it seems like there is an issue with resuming an application and having snapshots corrupted in the display.

Is this something that Corona is actively looking at? More than happy to work through more detailed examples, but for the moment, any snapshot displayed will be corrupted upon resuming.

#2

Can you try adding a system event listener, and on the “applicationResume”, call “snapshot:invalidate()”? 

#3

Also, if you are using the “discard” mode, you will not be able to recover your texture b/c the GPU is allowed to lose that data between a suspend/resume cycle.

#4

Hi Walter,

Was planning on getting a simple example together, but you beat me to it. Using the discard mode is exactly what we are doing (painting masks onto multiple layers (snapshots) ).

Can you think of any way around this? This would be a big problem if this is lost during resume.

Thanks

David

#5

Do you really need discard mode?

You can still use the canvas group either way. And the advantage of not using discard mode is that your previous edits are “saved” to the master snapshot.group, so when you call invalidate(), you can regenerate the texture upon a resume via snapshot:invalidate().

#6

I’ll try your suggestion later today and let you know how it goes! Btw, does iOS work differently for this, because we have no issues on that platform?

#7

Can you try adding a system event listener, and on the “applicationResume”, call “snapshot:invalidate()”? 

#8

Also, if you are using the “discard” mode, you will not be able to recover your texture b/c the GPU is allowed to lose that data between a suspend/resume cycle.

#9

Hi Walter,

Was planning on getting a simple example together, but you beat me to it. Using the discard mode is exactly what we are doing (painting masks onto multiple layers (snapshots) ).

Can you think of any way around this? This would be a big problem if this is lost during resume.

Thanks

David

#10

Do you really need discard mode?

You can still use the canvas group either way. And the advantage of not using discard mode is that your previous edits are “saved” to the master snapshot.group, so when you call invalidate(), you can regenerate the texture upon a resume via snapshot:invalidate().

#11

I’ll try your suggestion later today and let you know how it goes! Btw, does iOS work differently for this, because we have no issues on that platform?