Replay Mod Forums

Saving Keyframe Edited Video and Stone Error?
    • User
    • 13 forum posts
    User493
    #1

    Aug 13 15, 05:41 PM

    First, when you edit a recording with custom keyframes and time frames can you save your camera path? Also, there are random times during the recording that the screen is filled with a dark stone texture and nothing else is visible!


    • User
    • 13 forum posts
    User493
    #2

    Aug 13 15, 05:42 PM

    So I can close the edits and then reopen and edit them later?


    • Moderator
    • Beta Tester
    • 249 forum posts
    User20
    #3

    Aug 13 15, 05:42 PM

    You can use the X key to save Time -and Keyframes in your Replay. Further information here


    • Beta Tester
    • 250 forum posts
    User34
    #4

    Aug 13 15, 05:45 PM

    Is that bug during recording or viewing an already recorded replay?


    • User
    • 13 forum posts
    User493
    #5

    Aug 13 15, 05:53 PM

    Exporting the replay as a video, then playing it back using Windows Media Player. It does not occur during any preview of the camera path



    • Beta Tester
    • 250 forum posts
    User34
    #6

    Aug 13 15, 05:53 PM

    What render settings did you use?


    • User
    • 13 forum posts
    User493
    #7

    Aug 13 15, 05:54 PM

    manuelgo you are a lifesaver


    • User
    • 13 forum posts
    User493
    #8

    Aug 13 15, 05:54 PM

    MP4 Defaul Quality, Default Rendering, 1920X1018 resolution, framerate 30, had to give new path for ffmpeg.exe


    • User
    • 13 forum posts
    User493
    #9

    Aug 13 15, 05:55 PM

    Do I need to get another version of ffmpeg?


    • Beta Tester
    • 250 forum posts
    User34
    #10

    Aug 13 15, 05:56 PM | Last edited: Aug 13 15, 05:56 PM

    Which operating system are you using?



    • User
    • 13 forum posts
    User493
    #11

    Aug 13 15, 05:56 PM

    Windows 7


    • Beta Tester
    • 250 forum posts
    User34
    #12

    Aug 13 15, 05:59 PM

    Can you upload the replay file so I can test it myself?


    • User
    • 13 forum posts
    User493
    #13

    Aug 13 15, 06:06 PM

    I am guessing I need a different version of ffmpeg
    http://www.mediafire.com/download/5m2nt07sj3jbhaa/2015_08_12_22_49_02.mcpr


    • User
    • 13 forum posts
    User493
    #14

    Aug 13 15, 06:08 PM

    What is the recommended ffmpeg version for a Windows 7 64 bit system?


    • Beta Tester
    • 250 forum posts
    User34
    #15

    Aug 13 15, 06:13 PM

    I'm not sure about the recommended version.
    But how long was the camera path you rendered?



    • User
    • 13 forum posts
    User493
    #16

    Aug 13 15, 06:18 PM

    using those specs 10 1/2 mins
    The camera path goes all around the world


    • Beta Tester
    • 250 forum posts
    User34
    #17

    Aug 13 15, 06:20 PM

    So the path is the entire video long?


    • User
    • 13 forum posts
    User493
    #18

    Aug 13 15, 06:24 PM

    no it starts around 1 minute in, and the camera path stops around 30 secs from the end


    • Beta Tester
    • 250 forum posts
    User34
    #19

    Aug 13 15, 06:27 PM

    I'm going to render it like you said and test if I also get this 'Stone texture' this might take a while.


    • Moderator
    • Beta Tester
    • 249 forum posts
    User20
    #20

    Aug 13 15, 06:29 PM

    Could you provide screenshots for the "stone textures"?



    • User
    • 13 forum posts
    User493
    #21

    Aug 13 15, 06:37 PM

    http://www.mediafire.com/view/2xu5o4w3p2jb1vm/Untitled.png


    • Beta Tester
    • 250 forum posts
    User34
    #22

    Aug 13 15, 06:58 PM

    I have rendered the video and can confirm that this bug does exist. Although I don't know what it is caused by. I will contact a developer as soon as possible and add this to the bug list! #
    I hope this gets resolved soon


    • User
    • 13 forum posts
    User493
    #23

    Aug 13 15, 07:02 PM

    Thanks, please let me know when this gets fixed! :)


    • Developer
    • 1883 forum posts
    User10
    #24

    Aug 14 15, 04:53 PM

    This should be fixed as of 1.0.2
    Could you test again and confirm that it was fixed?