direct translation between c4d and vw, both ways

[grant_PD]

The time spent fixing c4d files that have to be exported as .dwg or .3ds and brought in to VW probably meets or exceeds the time one would spend to create a comparable rendering in renderworks, which doesn't support such things as UV mapping, ambient occlusion, etc.

Until renderworks meets or exceeds the quality of a c4d render, as a viable option for presentation it is a dead end.

We need to have direct translation between the two file formats so that firms can harness the power of each products' strengths: rendering and modeling in c4d, organization and plate notation in VW. Doing this is a win win for both products as it instantly creates a pipeline that everyone can benefit from and draws would be users to a very efficient and powerful workflow.

[PVA - Admin]

Adding this to a few existing requests. This is definitely the direction we want to go in.

[M5d]

We need to have direct translation between the two file formats so that firms can harness the power of each products' strengths: rendering and modeling in c4d, organization and plate notation in VW.

This is definitely the direction we want to go in.

Are you referring to integrated exchange, i.e. exchange that reads, edits and preserves native information as it's circulated back and forth between applications?

[grant_PD]

Yes. The geometry needs to remain the same and usable (not groups of meshes or 3d polygons) between each program. They need to recognize each others file formats.

[zoomer]

This would be fine but maybe not that easy as both work quite

different.

Also beside Solids, VW's mesh editing options aren't that bad for

a CAD solution (volume modeler).

I would be happy with only a C4D importer for VW though.

Same quality as the exporter has.

Meshes itself would be fine,

as they have more editing options than VW Solids like editing

multiple edges of multiple elements at one time and they export

better to DXF,

if they had the same value as Solids for things like Clip Cube

Cut Faces.

[grant_PD]

Yes, it's all about the mesh editing. In c4d one can weld the points, dissolve the segments, grab and move multiple points/faces/segments. All of that functionality goes away in VW. So lets say you had an extrusion that needed to be .05" longer along one edge, and you needed it AFTER you had imported back to VW. And the extrusion came through with 100 points. That's a lot of work in VW.

Designers need a pipeline that allows presentation style renders (c4d) and production quality drafting (vw). The key to having that workflow is to make the transition between the two programs as seamless as possible. I'm not for having an "all in one solution," I just don't think that companies have the resources to devote to that sort of thing. Maxon shouldn't waste their time building modules for c4d that allow for line drawing presentation and note management and database functionality and all that. Nor should VW waste their time with texture tagging, uv painting, motion rigging, etc. Just create the pipeline and people will naturally migrate towards it.

[zoomer]

And there needs to be a direct conversion between Solids and

(valid) Meshes for plain VW work too.

[grant_PD]

Yes.