This time around, I saved the sequence renders as a video file as opposed to a series of .jpg files. Whilst this had the drawback of creating a ridiculously huge video file numbering in the 30 gigabyte range, the end results seem to be a lot cleaner. There is no strange texture popping occurring and no cross hair in the center of the frame. When time allows I am going to return to the hangar scene and re-render the sequence using this method. At least now I can be confident that I can use the sequencer without any strange errors for my major project.
Tuesday, 27 March 2018
My Second Attempt with Unreal Engine Sequencer
Returning to my previous project the "Red Chases Blue" space base, I went about setting up a new camera sequence to see if I could get a better result. You can see the completed video here:
This time around, I saved the sequence renders as a video file as opposed to a series of .jpg files. Whilst this had the drawback of creating a ridiculously huge video file numbering in the 30 gigabyte range, the end results seem to be a lot cleaner. There is no strange texture popping occurring and no cross hair in the center of the frame. When time allows I am going to return to the hangar scene and re-render the sequence using this method. At least now I can be confident that I can use the sequencer without any strange errors for my major project.
This time around, I saved the sequence renders as a video file as opposed to a series of .jpg files. Whilst this had the drawback of creating a ridiculously huge video file numbering in the 30 gigabyte range, the end results seem to be a lot cleaner. There is no strange texture popping occurring and no cross hair in the center of the frame. When time allows I am going to return to the hangar scene and re-render the sequence using this method. At least now I can be confident that I can use the sequencer without any strange errors for my major project.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment