Component copies with different materials or mapping
-
If you don't apply any material inside the component and its nested components, you can assign a different material to the component globally. Then you have two copies of a component with two different materials assigned.
-
Thank you Casca, how about if I got one component representing 30 wooden colums and beams? what will be the best/easy way to texture without repeating pattern?
-
If each of this column inside the component a component or a group then the method is the same.
If not, then you could either turn them into components and apply the same method or texture them independently. Maybe some plugins would facilitate your work on this case.
NOTE: if you set your axis inside a component the textures will be relative to them. Origin of texture is axis origin. Define them well and the components will be easier to texture.
-
I'm affraid I don't get what you say.It looks like I'm try to bite my own tail! at the end of the day groups vs components doesnt make much different when it comes to file size?
-
Now you're talking about file size, texturing or multiple object texturing?
-
well the initial intention to use component was to keep file size small but yes I was talking about texturing component instances without obvious patterns, you menthion about axis but dont really understand your suggestion.
-
All instances of a component which have a material applied to its internal faces will look the same [plain or textured/mapped].
If the component instances can be 'rotated' that will disguise it somewhat - if its circular it offers many possibilities, but if it's square let's say four.
You can also 'scale' an instance -1 in x/y to flip its appearance.
Any faces within the component which are assigned with the default-material will display the material which has been applied directly to the instance - but if it's textured you cannot 'map' it as it belongs to the 'container'.You can select a few similar component instances and use context-menu 'make unique', you then have two definitions - the second's name has #1 appended etc.
Edit one of those instances and remap any textures as desired.
Combined with instance-rotation/scale-1, then that 'trick' might be enough to 'disguise' the commonality of the instances... -
Check this thread that paolo just opened:
http://sketchucation.com/forums/viewtopic.php?f=40%26amp;t=60533#p552647
I'm also going to explain about axis there.
-
Thank you both, good ideas. Tig first idea will work on my rectangular geometry but not on rafter or others, the second will also help but wanted to use as little components as possible or more than one texture
.
Sorry to open another thread I though... :% Casca thank you for that nice video can we move it here in order to delete the other thread?
Will be possible a plugin which mix groups and component behaviour with capacity to modify geometry in all instances but able to texture independently?
Maybe one day me too will stop trying to bite my own tail!
-
OK guys I have tried TIG idea for the pinecote pavilion which I think went ok, using a rectangular components for all columns and beams, trying to keep file size small. Please check the model in the 3d warehouse as pinecote pavilion ( about 6mb but went to 7mb after location) and let me know what you think.
Thanks for any comments or suggestions.
Advertisement