Update: check out this page for the 64-bit Xvid codec

I encountered a problem today related to walkthrough creation in Revit 2010 64 bit with Vista 64 bit. I was exporting a large walkthrough to uncompressed AVI format, and the file size would reach 4.00 GB (4,294,967,296 bytes), and then corruption of the AVI would result. It appears that a 4 GB limit was being imposed at some point in the walkthrough creation process.

Therefore, I tried to use an encoding format. When using Revit 32 bit, I recall that I had a number of options in the Video Compression ‘codec’ dialog when exporting a walkthrough. However, in Revit 64 bit, I only had a couple of basic options (Microsoft Video 1, Intel IYUV Codec, Full Frames (uncompressed)).

After some searching, and trialling a few different ideas, I found that I could access some decent codecs in this box after installing Shark007’s 64 bit components (link below).

64 bit Encoding Components

In addition to the above, it is recommended that you install Shark007’s 32 bit Codec Pack (link below):
Vista Codec Package 5.5.3 Final

After installing both of the above and restarting Revit (you may also need to restart Windows), I was intermittently able to access an additional filter in the dialog called ‘ffdshow’ – clicking ‘Configure’ opened up a whole range of encoding formats for use!However, there appear to be a few problems:

  1. The ‘ffdshow Video Codec’ encoder only appeared in the Video Compression dialog when a certain ‘Size Crop’ and resolution were selected. For me, the only settings that consistently seemed to work were: Size Crop width = 150 mm, and export resolution 886 x 500.
  2. The corruption still seemed to result if the uncompressed AVI format would have exceed 4 GB (even while using a compressed codec).
  3. Choosing H264 actually crashed Revit.
  4. WMV 8 using libavcodec simply did not proceed past the first frame.

Given the above limitations, my solution at this point is:

  1. Split the walkthrough into parts that have a size less than 4 GB (ie. part 1 = frames 1 to 100, part 2 = frames 101 to 200 etc) and use FULL FRAMES (UNCOMPRESSED) AVI format.
  2. Use VirtualDubMod to ‘append’ these segments together, and
  3. Use VirtualDubMod to ‘Save As…’ a different format. I was able to choose ‘Cinepak’ compression in VirtualDubMod, which turned my approx 5.4 GB uncompressed AVI into a 167 MB file in only about 5 mins of processing time.

After spending quite a few hours trying to make this work in a satisfactory and simple manner, I decided to contact our reseller and lodge a support call. I will let you know if I learn anything helpful.During this investigation, I tried a few things without success. They may be of interest to you (see links below).

Windows Media Encoder 64 bit

Xvid 64 bit

x264 64 bit

No doubt you would agree that our ‘attitude’ can have a big effect on our lives. If we look at things with the right outlook and viewpoint, we are more likely to feel successful and satisfied. So how does this relate to Revit?

There are a number of ways to approach Revit as a software platform. Consider some examples:

  1. “Revit is a modeling tool, and I want it to be able to easily model any form I can conceive.”
  2. “Revit is a drafting tool, and I want it to be able to draft quickly and easily, and I demand absolute graphic control over every single visible 2D element.”
  3. “I believe Revit should be intuitive and easy to use. It should be able to guess what I want and deliver the result that I seek.”
  4. “I have to use Revit because it is becoming the industry standard. I don’t have to like it or understand how it works.
  5. “I want to understand What Revit Wants, so that I can use it in a productive and appropriate manner.”

I would say that the first 3 are basically impossible, for any software tool. However, in some ways Revit can deliver the results that you seek when approaching it with the attitudes of 1, 2, or 3. It is capable of many things, but it does have limitations. Attitude Number 4 is a problem though. Why? Because you MUST understand, at least to some degree, how Revit works. Otherwise you will never succeed, and you will face a lot of frustration.

Yes, you must grasp What Revit Wants. You must try to think in the same way that Revit thinks.

  • Why is it trying to join the walls this way?
  • Why is object A masking object B?
  • What is causing Revit to show this line dashed instead of solid?

Instead of getting frustrated and angry, and instead of uttering unrepeatable phrases directed at ‘Autodesk’, just try and understand WHY. It is a little bit like meeting someone you don’t know for the first time. You may choose to judge them from first impressions. Or you may try to understand them, and why they act the way they do. If you come to understand them, you may be able to have a rewarding relationship with that person.In conclusion, give Revit a chance. Try to understand. Try not to judge or lose your patience. Don’t be afraid to find out What Revit Wants.