What is the difference? SOLVIEW (solid view) vs. VIEWBASE (base view)

[Anonymous]

I am used to using baseviews for documentation. I'm familiar with how to create and then edit them as needed later. My main complaint would be that my dimensions don't always like to stay associated. Overall, I love how much simpler it is than viewports, and the lines print better. I just came across the Solid View, Solid Drawing, and Solid Profile commands that seem to largely provide similar 'looking' end products. My questions are: Can someone explain some clear distinctions between these two different processes? & Should I bother to learn the ins and outs of the SOLVIEW / SOLDRAW / SOLPROF commands?

[Anonymous · Accepted solution]

VIEWBASE creates views that maintain associativity between the solid model and the views that are generated. If you make a change to the model the views will be refreshed and reflect the change. SOLVIEW / SOLDRAW / SOLPROF create geometry and do not maintain that associativity.

There may be times when you find them useful.

I am for the most part old school and continue to use SOLVIEW / SOLDRAW / SOLPROF (in an automated fashion via AutoLISP) but there are times I've used VIEWBASE. - some things I like, some things I don't. There are two major factors that influence my use of VIEWBASE: it creates line work, colors, and layering that I'm not keen on. It strictly works with solids - I integrate some 2D elements into my solid models that are not included in the output of VIEWBASE. They are essential elements in my work flow.

I've overcome some issues with the use of EXPORTLAYOUT after using VIEWBASE.

Currently my workflow is a hybrid approach using SOLVIEW / SOLDRAW / SOLPROF  (automated) FLATSHOT, and some custom autolisp.