search

TASEmulators / vba-rerecording

Automatically exported from code.google.com/p/vba-rerecording
GNU General Public License v2.0
54 stars 11 forks source link

Can't take incremental screenshots while paused. #62

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Pause the game using the emulator's pause key.
2. Take a screenshot (by pressing the assigned button on Options --> Input --> 
Configure Controllers --> Controller 1).

What is the expected output? What do you see instead?
The screenshot should be taken, instead, nothing happens. 

What version of the product are you using? On what operating system?
VBA RR v22. Win XP SP3.

Please provide any additional information below.
I know you could take a screenshot using the "Tools --> Screenshot Capture" 
option, but that is no good if you want to take lots of sequential screenshots.

Original issue reported on code.google.com by reyvgm on 29 Oct 2010 at 11:30

GoogleCodeExporter commented 9 years ago 
Just like with the other inputs under the controller input, you have to frame 
advance with the screen capture button.  What certainly is a defect is that the 
key has to be let go for a frame until you can take the next screenshot.  I 
don't think the screenshot key should even be under that configuration anyways

Original comment by gcupcakekid on 30 Oct 2010 at 12:33

GoogleCodeExporter commented 9 years ago 
Oh, I see. It worked by pressing them both a the same time. I didn't know that. 
But still, isn't there some possible fix to let one take incremental 
screenshots without having to advance a frame first?

Original comment by reyvgm on 30 Oct 2010 at 12:44

GoogleCodeExporter commented 9 years ago 
The easiest way I've found from experience (not just on VBA) is to record a 
lossless video, open it in virtual dub, and save the video as a collection of 
images for each frame (or as an animated GIF)

Original comment by gcupcakekid on 30 Oct 2010 at 10:35

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I see, thanks. 

But do you think it's possible to fix the issue in a future VBA?

Wait, what am I saying? If you accepted the issue then of course it can be 
fixed :P

Original comment by reyvgm on 31 Oct 2010 at 9:11

GoogleCodeExporter commented 9 years ago 
I think this issue is covered by Issue 65.

Original comment by aquan...@gmail.com on 3 Nov 2010 at 12:07