I had that exact same problem. I think it has something to do with file size. My test walkthroughs worked and I was able to playback using WMP. Then I went to do the actual walkthrough using the same settings, and like you, I let it run for days... The file was HUGE! 1.8GB and would not play in any sort of player. I downloaded and installed Windows XP codec package + various other codec package, nothing worked. Ultimately, I had to do redo the walkthrough. The 2nd time around, I heeded some of the others' advise and selected JPG output. Then used VirtualDub to compile the frames. As long as you have the JPGs, you're safe. No more fear of having a corrupt AVI output. There are some big advantages to this. 1. You have rendered JPGs to use for other purposes. 2. Render time seemed faster. I think because Revit doesn't have to encode on the fly. 3. I was running Revit on a dual quad-core Xeon workstation and was able to run two sessions of Revit. I made a copy of the model and set one session to render frames 1-300, and the other to render frames 301-end. Why I ran two sessions? Because a session of Revit only used half the CPU processing available. Two sessions allowed me to fully utilitize the hardware resources. That is, of course, if you have enough RAM. You could also render the 2nd session or additional sessions if you have other computers and licenses available. NOTE: VirtualDub is sweet. You pick the first frame and it auto-detects the rest. But, from my limited experience with VirtualDub, I had to compile two AVIs and use VirtualDub to append one to the other. Works fine. I didn't find a way to have VirtualDub append two sets of JPG. You can also look at your render settings and reduce them to get faster rendering. Once compiled into AVI, most of the images will become a "blur" anyway. So experiment with the settings.
|
Search
