- 1,629
- Texas
- RC45
- RC45
I know the previous thread was closed and many others have been posted, but I figured a quick explanation might save others repeating the same request over when in reality we probably dont want it as it will need to be severly restricted in capability.
The problem with the rendering of the ingame replay to some kind of video file is the processing time.
rFactor (as an example) has built in ability to render the replay to a video file - but you must understand what that means to understand why it is actually a big deal.
In order to render the replay to a video file, the programmer needs to essentially set the 3D game engine up to behave like a 3D CAD program with a high end rendering engine hooked on. You have to export each frame of motion in the 3D world from that cameras view point and write that image to disc, compiling them together into a video file and add the audio track and sync it and write the file out.
And of course who knows what video/audio codec Kaz would choose that would bring with it all sorts of other issues.
Even a decent high end PC will take longer than real-time (in other words each second of video takes longer than 1 second to render and write to disc) - on a quad core 3.8GHZ 4GB ram 1GB video card, rfactor takes hours to render a 7 minute video in hires at 60fps. Thats a lot of time for a lot of computing. I am sure this is why even Forza3's video export is severly limited in scope and resolution to save from someone accidently trying to render a 30 minute race and locking up their console for a week
Even us PC rFactor racers would rather use a Windows screen cap utility like FRAPS to make our videos. We play the replay in the game and then jsut capture the video window to disc.
Now what we do use is the Director feature in rFactor to edit the videos - this lets you set start/end times of clips and change camera views and cars and then save that "edited replay" back to the game. It is still an ingame replay, but it uses the camera angles and car views we want for the cuts we like. A replay director in GT5 would be great and probably more useful than a video exporter.
These edited replay files can be viewed at any time in the future and the game will simply process the replay as ingame footage just like GT5 does now.
I would not really want my PS3 tied up for hours on end rendering a movie that in the end I might not like and needed to render again and edit on the PC with proper video editing tools anyway.
(Perhaps the mods might stick this in the Q&A section instead of it hanging out as its own thread)
Kaz please, add some SIMPLE features to the replays:
- The ability to export it to so kind of file that can be seen in a PC or Mac;
- Rewind to any point from begining to the end;
- And if not too hard: SLOWMOTIONS.
But the most important thing is the hability to send our replays to our friends around the world. Don´t need any YouTube feature. No. Just as simple as to export pictures, but with video files! We find our way to post it on internet.
It can´t be that hard!
Please!
If you guys agree and want that feature, please, let´s make some noise.
Thanks
The problem with the rendering of the ingame replay to some kind of video file is the processing time.
rFactor (as an example) has built in ability to render the replay to a video file - but you must understand what that means to understand why it is actually a big deal.
In order to render the replay to a video file, the programmer needs to essentially set the 3D game engine up to behave like a 3D CAD program with a high end rendering engine hooked on. You have to export each frame of motion in the 3D world from that cameras view point and write that image to disc, compiling them together into a video file and add the audio track and sync it and write the file out.
And of course who knows what video/audio codec Kaz would choose that would bring with it all sorts of other issues.
Even a decent high end PC will take longer than real-time (in other words each second of video takes longer than 1 second to render and write to disc) - on a quad core 3.8GHZ 4GB ram 1GB video card, rfactor takes hours to render a 7 minute video in hires at 60fps. Thats a lot of time for a lot of computing. I am sure this is why even Forza3's video export is severly limited in scope and resolution to save from someone accidently trying to render a 30 minute race and locking up their console for a week
Even us PC rFactor racers would rather use a Windows screen cap utility like FRAPS to make our videos. We play the replay in the game and then jsut capture the video window to disc.
Now what we do use is the Director feature in rFactor to edit the videos - this lets you set start/end times of clips and change camera views and cars and then save that "edited replay" back to the game. It is still an ingame replay, but it uses the camera angles and car views we want for the cuts we like. A replay director in GT5 would be great and probably more useful than a video exporter.
These edited replay files can be viewed at any time in the future and the game will simply process the replay as ingame footage just like GT5 does now.
I would not really want my PS3 tied up for hours on end rendering a movie that in the end I might not like and needed to render again and edit on the PC with proper video editing tools anyway.
(Perhaps the mods might stick this in the Q&A section instead of it hanging out as its own thread)
.
.
