Visual Link Tree
21-May-93 12:57:34
Sb: #44363-Visual Link Tree
Fm: Joe Miller 70544,2436
To: Craig Sharp [Mem TM] 73417,2320
Craig,
Being one of the most adaptable people on earth (at least in my opinion), I
already _have_ adapted my use of ACAD to 3D Studio <g>. At least it works
well for me.
To give you an example, in constructing the model for a building in ACAD, I
have grouped repetitive window elements into blocks. Within the blocks, on
separate layers, are the window mullions, the window sills, and the glazing
itself. The window sills are on the same layer as the rest of the exterior
building finish.
When I transfer the DXF into 3D Studio creating 3DS objects by ACAD layer,
the window sills and the exterior finish are part of the same 3DS object, as
I want them to be, because they were on the same ACAD layer. All the window
mullions are part of the same 3DS object, also as I want them to be. 3DS
ignores the internal block structure of the ACAD DXF file, as I want it to.
Visual Link does not improve on this process in any way and in fact
tremendously complicates the process. In light of what I've described
above, I think you'll agree that your idea of exploding the ACAD blocks when
using VL will not work in my case.
VL in my opinion is supposed to simplify the task of importing ACAD geometry
into 3D Studio, not complicate it. I have no problem adapting my usage of
ACAD to 3D Studio realities, but I have a _major_ problem adapting my usage
of ACAD to Visual Link when I see no payback whatsoever in doing so.
I'd be more than interested in a class on the wedding of ACAD and 3DS. I
don't claim to have all the answers, but I do know when something works and
when it doesn't. What is Autodesk U? I can't recall hearing about it on
this forum, but then again, after that lobotomy, I can't recall much of
anything <g>.
Joe