You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chance to get crash while transitioning between scenes, if scene transition type = Noble.Transition.Type.COVER.
Update error: libraries/noble/Noble.lua:269: attempt to index a nil value (upvalue 'currentScene')
stack traceback:
libraries/noble/Noble.lua:269: in field 'transitionMidpointHandler'
libraries/noble/modules/Noble.Transition.lua:115: in field 'fn'
libraries/noble/libraries/Sequence.lua:359: in local 'callTimeRange'
libraries/noble/libraries/Sequence.lua:368: in method 'updateCallbacks'
libraries/noble/libraries/Sequence.lua:81: in field 'update'
libraries/noble/Noble.lua:311: in function <libraries/noble/Noble.lua:308>
To increase chance of crash set duration of transition about 2 * frame duration. It can be 0.060 or 0.062 or 0.064 or 0.066 (if your FPS = 30).
I'm going to close this as it seems to be addressed with the updating and merging of #66.
I've also created checks for when either side of a transition duration is smaller than the duration of a single frame (and also not <= 0). It forces the transition to be at least one frame long, so that should clear up any other edge cases related to this as well.
Chance to get crash while transitioning between scenes, if scene transition type = Noble.Transition.Type.COVER.
To increase chance of crash set duration of transition about 2 * frame duration. It can be 0.060 or 0.062 or 0.064 or 0.066 (if your FPS = 30).
Noble.transition(ExampleScene2, 0.062, Noble.Transition.DipToBlack)
The reason for the crash is that sometimes you can get two midpoint callbacks in one Sequence. I described that here: NicMagnier/PlaydateSequence#10
Pull request with the fix: #66
The text was updated successfully, but these errors were encountered: