On Wed, Aug 3, 2016 at 6:27 PM, Christopher Sean Morrison <brl...@mac.com> wrote: > You shouldn’t make any assumptions about how objects are named. If you want > objects that are or are not regions, the “search” command will be more robust > (see the "-type region” option, run “brlman search” for docs).
Ah! Alright. This sure seems a better approach. I did the following command search -not -type region to get all the objects which aren't a region. > Why are you doing this? This presumably changes the model into a single > region (i.e., a single part) and also potentially changes the > definition/shape of the geometry (depending on how the regions were > arranged). I don’t see this being beneficial. I tried doing it with model axis.g and there was no change in shape. So thought maybe it would work with each model. What I wanted to do was to get a mged object which includes the entire model, and therefore after conversion we may get an obj file that renders the entire model. > To figure out what processing is needed, have to understand what you’re > trying to accomplish. This is not clear to me. Is the goal to have one .obj > file per part (regions), one .obj per assembly (combs above region), one per > .g file? Our goal is to reduce the number of .obj files per model. And if possible keep it to one per model for viewing purpose. For further tweaking and analyzing like giving a different color to each part of the model, we can render another version of the model that has different obj file for different part of the model. -- Fear is wisdom in the face of danger. It’s nothing to be ashamed of Gauravjeet Singh http://github.com/gauravjeetsingh ------------------------------------------------------------------------------ _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
