@rose123 said:
BTW, it doesn't seem like I have a file uploading option. Do you have to have a certain # of posts before you can do that?
New members have a bit of limitations (first couple of posts moderated) but nothing with attachments so you should be able to upload even with the very first post.
My thought would be to make the stair tread both transparent and an emitter and make the LEDs emitters as well. I haven't tried it but that would be my approach.
Look below the message window when you're typing. There's a tab labelled Upload attachment. Click on that, select the file and hit the "Add the file" button.
Thank you for the answer, about those circles, once you extrude them to become cylinders, will Rhino then make them into polygons as well? Because, in that case, I can easily use cylinder from Sketchup right?
And about 3D max, does that work in the same way as Rhino, or does it also use circles/cylinders, made of polygons?
Thank you
Please see attached files.
See the closest red handle. Notice the line extending back and the far red handle. The little yellow info box that says "Red scale about opposite point" did not show in the screen shot. This handle will mean the shape's edges will move on the near side line only, and only straight out along the red axis. The grid of hidden lines does become stretched uniformly
In the other direction scaling, the shape will not be exactly the same. Since it has a curve in it, it will stretch that curve some--straight out, but the high/low points and the relative shape should be the same. I assume this stretch is inconsequential for the purposes of showing your terrain.
[image: 3d4N_Screenshot2012-07-17at11.40.11AM.png]
[image: 2hDR_Screenshot2012-07-17at11.58.15AM.png]
If the transactions between the two scripts are in one session without any need to remember things for the next session then why not make the two scripts within the same module and pass @arrays between them ?
module Mojaki def self.script1() ... @faces<<face...etc ... end end#module
AND in another file
module Mojaki def self.script2() ... @faces.each{|f|...etc ... end end#module
You run the scripts as Mojaki.script1() etc as needed...
The @faces array is remembered/accessible between the two scripts because it's in the same Module...
So as script1 makes/changes it, script2 can read it...
If you had read the script's instructions carefully [first page in its thread] you might have seen that align_2d appears in the Tools menu not the Plugins menu as you 'assumed'... and it is in fact designed to be used with the right-click context-menu when you have suitable objects selected...
@unknownuser said:
Make a selection (other objects than groups or components are ignored)
Select " Align 2D" in the context menu or in the Tools menu
Click 2 points that define a line for the alignment.
A construction line is temporarily drawn and a dialog box is displayed
Choose your options:
horizontally align all groups/components along X axis at the intersection with the cline
vertically align all groups/components along Y axis at the intersection with the cline
perpendicularly align all groups/components along a perpendicular virtual line at the intersection with the cline.
Other options self-explanatory
I don't scale the copy back down, though. I just close it after editing it and delete it. The original at its original size remains with its faces intact.
@unknownuser said:
Where did you read that, Pilou? I don't see that anywhere in his original post.
You right for the text
I had interpreted the images! And was right!
And sure your method is more speedy than the FredoScale when you start from the beginning!
But when you have yet the object, that is an another story!