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
The second screenshot is never generated. Interestingly, I have around hundred tests and only 4-6 have this problem. It's not game related, maybe more save state related.
Looking at the code where the console ask for the screen shot:
As I understand the code, the core ask for a screenshot "next time" the video plugin reach video_plugin_render_callback. But the console ask for M64CMD_STOP as soon the last frame+1 is reached. This mean, the frame callback M64CMD_SET_FRAME_CALLBACK is executed before the video plugin reach video_plugin_render_callback and take its screenshot.
I will do some test to know if wait few frames after the latest screenshot before close the emulator could help...
The text was updated successfully, but these errors were encountered:
I realize, in some situation, every requested screenshots (argument
--testshots
) are not all generated.I have a test suite that open a rom with a save state and save some screenshots. Generated command line looks like this:
The second screenshot is never generated. Interestingly, I have around hundred tests and only 4-6 have this problem. It's not game related, maybe more save state related.
Looking at the code where the console ask for the screen shot:
https://github.com/mupen64plus/mupen64plus-ui-console/blob/master/src/main.c#L141
And how the core handle it:
https://github.com/mupen64plus/mupen64plus-core/blob/b9765eca453ed46773655c44bc86fbcdeb33ab7c/src/main/main.c#L725
As I understand the code, the core ask for a screenshot "next time" the video plugin reach
video_plugin_render_callback
. But the console ask forM64CMD_STOP
as soon the last frame+1 is reached. This mean, the frame callbackM64CMD_SET_FRAME_CALLBACK
is executed before the video plugin reachvideo_plugin_render_callback
and take its screenshot.I will do some test to know if wait few frames after the latest screenshot before close the emulator could help...
The text was updated successfully, but these errors were encountered: