Well…without trying to sound too overly biased… I would say that EIAS is a great solution for architectural visualization. But instead of just saying that…why don’t we take a little time to determine what features are good for doing architectural visualization.
If I were to make a list of requirements I would say:
- The ability to handle large numbers of polygons and hard surface rendering.
- A variety of shaders and material systems to recreate real world textures.
- A robust rendering engine capable of a variety of rendering solutions, particularly caustics, Global Illumination, raytracing, HDRI, and high resolution output.
- Compatibility and integration with other software for modeling.
- Environmental simulators for vegetation, water, and clouds.
- Placement tools for replicating objects simply and easily.
- Rotoscoping tools.
You should realize that although EIAS does not have its own modeling solution anymore, there are a number of solutions that are in place or being put in place to handle your modeling needs. EIAS comes with Silo, a sub-d modeler, that is good with organic shapes. FormZ, a package that has worked with EIAS since the beginning, is known for its architectural modeling tools. With FBX and Transporter, which are included in EIAS, practically any model can be brought into EIAS. So whatever package you decide upon for modeling… you’ll be fine. There are also internal modeling plugins that are available that can meet some of your basic needs.
How about you arch viz guys… (Ian) chime in anytime.
And oh… from the forum leader’s point of view, let’s remember to restrict making comparisons with other software packages and simply focus on what EIAS can provide for this person. (Not that I’ve had any problems with you guys on that) But CG Talk does not particularly appreciate threads that can potentially turn into flame wars. So if you must make a comparison, do it from a purely academic and informational point of view.

at