Leaked footage of Green testing the brand new gameplay recorder
372 بار بازدید -
4 سال پیش
-
So we can finally play
So we can finally play and record at 1080p 60fps without slowdowns!
What we did before was sending each rendered frame directly to ffmpeg so that it encodes a video in realtime. We were able to capture at 60 fps gameplay, but we were playing in slow motion at half that speed or less, plus the video quality wasn't as high as we wanted sometimes. The true problem was playing in slow motion: the final video has superhuman reaction times and recording it becomes boring at such speeds.
So what we do now? We capture each rendered frame but instead of sending it to ffmpeg, we save each image to the hard drive in jpeg. Encoding the frame to jpeg takes about 20 milliseconds on a single thread on average on our computer. With 3 threads doing that work and saving the images to the hard drive, the time goes down to about 8, well under the 16 milliseconds budget. Because the game doesn't use that much cpu it wasn't a problem. As a bonus, each frame now has a lot of quality too.
The downsides are that the video in this format is not really a video, is a bunch of images, and each second takes about 20 MB, so it's easy to reach several GB of images after some minutes playing. Also, while not really a downside depending on how you look at it, the creation of an actual MP4 video is done later, meaning that the video isn't ready as soon as we finish playing. In fact, this video was encoded again because it had compression artifacts before.
Overall I'm sure this will let us capture more nice bugs like this one. I mean, more epic moments, yes!
What we did before was sending each rendered frame directly to ffmpeg so that it encodes a video in realtime. We were able to capture at 60 fps gameplay, but we were playing in slow motion at half that speed or less, plus the video quality wasn't as high as we wanted sometimes. The true problem was playing in slow motion: the final video has superhuman reaction times and recording it becomes boring at such speeds.
So what we do now? We capture each rendered frame but instead of sending it to ffmpeg, we save each image to the hard drive in jpeg. Encoding the frame to jpeg takes about 20 milliseconds on a single thread on average on our computer. With 3 threads doing that work and saving the images to the hard drive, the time goes down to about 8, well under the 16 milliseconds budget. Because the game doesn't use that much cpu it wasn't a problem. As a bonus, each frame now has a lot of quality too.
The downsides are that the video in this format is not really a video, is a bunch of images, and each second takes about 20 MB, so it's easy to reach several GB of images after some minutes playing. Also, while not really a downside depending on how you look at it, the creation of an actual MP4 video is done later, meaning that the video isn't ready as soon as we finish playing. In fact, this video was encoded again because it had compression artifacts before.
Overall I'm sure this will let us capture more nice bugs like this one. I mean, more epic moments, yes!
4 سال پیش
در تاریخ 1399/04/03 منتشر شده
است.
372
بـار بازدید شده