Textures on a dynamic component
-
Hi Brodie
@unknownuser said:
If your end goal is rendering
No, that's not my goal. The texture may help the students to understand, how wide, long and deep the box is. Each square is (should be) a square centimeter.
Regards
Kurt -
In that case you may be able to accomplish your goal with geometry rather than textures. Instead of a 1cm x 1cm texture maybe you could use 1cm x 1cm components. You could fix their scale in the DC options to 1cm x 1cm and then have add a COPY option to the component so that when you scale the overall object to, say, 50cm long, it creates 50 of those 1cm components. The only drawback would be that you'd have to limit the scaling options to 1cm increments. Does that make sense?
-Brodie
-
@unknownuser said:
Does that make sense?
Definitly! But as I am a bloody beginner with DC I have gone the way I could handle.
Changing this to geometry is perhaps a challenge when I have got more experience. By now I have no idea how to start.Kurt
-
I'd start by downloading something like a fence DC which copies the fence posts as you scale the fence up. That'll show you how to fix the size of the fence posts and how to determine how far apart the posts are from each other. You should be able to then translate that into what you're doing where the 'fence posts' are 1cmx1cm squares and the number of copies is the total length divided by 1cm minus 1.
So if the total length is 10 cm the equation would be calculated 10/1 - 1 = 9 giving you your 1 original square and 9 copies.
-Brodie
-
I will try and do my very best.
-
Perhaps something like that :
Box.skp
The 1cmร1cm square don't exit, it's only lines on the box faces, so you can't texture them like a checker. -
It looks good!
@unknownuser said:
texture them like a checker
It is not a must. I'am fine with your solution.
When I choose "LenZ = 1cm" the copies are not shown. I will figure it out when i going to spend more time to DC.
General question: Are DC often used or is that something for Geeks?
Regards
Kurt -
@meister-mischler said:
It looks good!
When I choose "LenZ = 1cm" the copies are not shown. I will figure it out when i going to spend more time to DC.Mmmm.....
I experienced the same error...
I think is because SU work in inch, and when I ask values in cm, the real value pass to sub object in inch and re-translate in cm. So, when you enter "1" is probably translate and re-translate to "0.99999999" and the integer is "0".
I only think of that error
I will look for a solution...@unknownuser said:
General question: Are DC often used or is that something for Geeks?
DCs are very often used by very few rare geeks
-
I've come across the same issue with the textures in DC's, and I think that's the primary reason I haven't bothered to learn them in depth, despite their usefulness. I'm just brainstorming here, but does anyone (especially the code gurus out there) think there would be any way to add a function/script that would reset or normalize the DC's UVQ coordinates when ever you hit "Apply" to make changes? I'm not experienced with Ruby yet to know if that's nonsense or not
-
Hi,
any news on the texture scaling problem? I'm trying to create a DC that is only scalable on the x-axis and that does not stretch the texture, rather repeats it like if I moved the end by hand in a normal operation inside the component...
Would the only alternative be to break the inside up into smaller pieces that repeat? (a la "DC fence")
Pointers appreciated, cheers LEGOsketcher
-
this is the idea of TIG
http://sketchucation.com/forums/viewtopic.php?t=49564#p525146
video how it works (sorry, in Russian)
http://www.youtube.com/watch?v=TWGGfoR5slI
Advertisement