Gary wrote:Hello Joe,
Didn't you use to use FormZ? If so, can you compare and contrast what it is like modeling architecture & interiors with the 2 of them? Model looks good! Thanks, Gary
Yes, I used FZ for architecture and interiors for quite a number of years. Everything I've done in FZ I can do in Rhino, and vice versa. Both have great user forums. More high end render options with Rhino not available with FZ....Brazil, VRay. Of course the Maxwell plugin is available for both...I love both the Rhino and Cinema4D Maxwell plugins (I also have used Cinema4d

). Texture mapping is probably about the same for both Rhino and FZ. Much better communication with McNeel (Rhino) than ADS. Upcoming version beta testing for Rhino is open to all licensed users...in effect you get to use the next version for free for quite some time. Rhino much more stable than our experience with FZ5.0. Both have excellent import/export functions, although since Rhino was part of Acad early on, it's excellent for exchanging data with Acad2D. Rhino has great viewing options that are very easy to access...like if you need a ghosted view to see your geometry, very easy to do. Don't remember what we did w/fz along this line. I think fz was better at booleans...I've had some difficulty at times w/Rhino...had to do a time consuming workaround, but my lack of experience could be a factor. Rhino was much easier for me to learn than fz, but I've used acad for quite a number of years....lot of similar commands. Both programs use layers well, both can group objects. Rhino's object snapping tools are great. I find that the structure of Rhino is easier to grasp, basically you work with curves (lines/arcs), surfaces (planes) and solids which are really closed/joined poly(multi)surfaces. FZ's wall creations are more obvious than Rhino, but once you figure out Rhino's commands (there are a LOT of commands!), it's very easy to run walls of any spec'd width quickly. I made my own door and window blocks and are very easy to insert in Rhino....probably about the same as in FZ. For me Rhino is faster to work with than fz. Maybe it's because of my prior acad experience, but Rhino just seems easier to grasp and become productive on. On the development side, I feel comfortable that Rhino keeps going in a direction that will benefit my workflow...they seem to be very responsive to user requests. I did not feel that way with fz/ads...felt like us architects/designers were being put on the back shelf with the implementation of animation in fz (just my impression, although I know I am not alone in feeling that way). On the other side, I did have some communications with the fz developer who indicated that major architecture-specific improvements were in the plan....I just don't think I'll live that long (I'm in my 60's already....wow, sure went fast

) These are of course all my opinions....there would be many

. In conclusion, I'm happy with Rhino and intend to stay with that, but if for some reason I had to use fz I would be ok with that. I would not be ok with going back to archicad or autodesk architectural desktop which I also used for a few years (acad2d no problem...just no acad3d for me, thank you.