Please include "Retopology Layers"

[Taros]

I think it is time to include a new layer-window for seperate retopology objects.

Example:

You have a finished voxel-head and a voxel-helmet on different voxel-layers.

In the retopology-mode it is no problem to hide one of the voxel-layers previously and retopologize the head-object. But you can't hide the retopologised head, when it is finished, to begin with the helmet object. The created head-retopology reacts with the new head-topology (snapping).

The result is a need for the following functions in the Retopo-Area:

- Access to the vox-layer window to show/hide voxel layers

- A new retopo-layer window to create seperate retopo-layers

- Possibility to lock/unlock individual retopology-layers to avoid snapping while retopolizing on a new retopo-layer

- Possibility to export one individual or all retopo-layers for further use

I hope, I didn't forgot something. If so, feel free to extend this thread with you ideas to this topic.

Thanks to Tinker for the idea.

Regards

Chris

[Tinker]

Or even make retopo objects in the same tree with voxel objects (with deferent icon or something).

Idea is: you have for example 6 leg spider model. You could retopo one leg, make polys voxel's child and clone/move it with voxel object together.

[cuffins]

I think it's also necessary to get the Hide functions to work in Retopo. Hide Menue has no function in Retopo. Selecting faces and the ability to hide and unhide them will improve workflow a lot...

Rene

[Tinker]

Definitely!

Im beging Andrew of this in beta topic at the moment

[Andrew Shpagin]

At least hide in retopo tool will be done soon.

[philnolan3d]

Andrew says hide in Retopo is done.

[JamesE]

The Layers option would be nice as you could UV each layer as well, yet still have it all conform to one mesh, which is great for doing characters in games, as they are often built from several pieces and merged together for final texturing, animation and export. Also, you could easily manage visibility of layers just like with the other Layer solutions already in 3dc.

[Javis]

This is an excellent idea. I'd rather it not be tied to vox tree, as Tinker suggested. That would limit it to voxel retopo only, and not import poly meshes (sorry Tinker!). Also it would be great to have it support LWO layers in reverse. 3DC already does, but, imagine that you're retopologizing, save all of your retopologized meshes into ONE file (LWO) and bam, you have instant access to each one in the same file.

[philnolan3d]

I agree. I'm working on retopoing a rather complex LWO file right now. I'm actully almost done but what I had to do was break up the model into many layers in LW then retopo one layer at a time and export each one as an LWO, then later I'll put them back together in LW.