This is not precisely a WIP question, but as nothing will be done in V6 or likely in V7 about this, I am putting it in this category as “Future”.
HatchTest.3dm (1.2 MB)
So, above I have a façade. It has been imported into V6 (or WIP, doesn’t matter) via .dxf. Rhino guessed the file was in mm on Open, but in fact it was originally drawn in cm. So, the measurements are all 10 times too small.
Now, I need to have the file at 1:1 scale in cm, plus the façade rotated so it’s horizontal so I can continue to work on it. (Note this is just a simplified sample, the actual file is much bigger and more complex.)
- Convert the file from mm to cm and accept the scale.
The hatches are now 10 times too large in scale. IMO they should have scaled correctly with the units change. Run _HatchScale – set to Enabled and the value to 0.1 – OK, things go back to normal. But, again IMO, this is not a good solution, as it only works while HatchScale is enabled. If it is disabled, or the file is transferred to another computer where it HatchScale is disabled, the hatches blow up again. The hatches need to be scaled “natively” when changing the model scale.
In the end, I will need to have the file back in mm and at a certain scale for production of a physical model, so the craziness starts all over again.
- OK, let’s deal with the rotation now.
Select all and rotate the façade so it’s horizontal (the angle is ~50.98°). The hatch rotation angles do not rotate with the rest. So, one needs to figure out what angle to input in Properties to get them back to their original orientation. There is no “rotate incrementally” (relative to current).
This one is relatively easy because bricks should be horizontal, if the pattern was correctly made originally, one can simply select them all and enter 0. Ooops, nope, the bottom row is actually a vertical tile pattern and it has already been rotated 90°, so you already need to do those separately from the rest.
And suppose if there were more hatches with many different rotations? Then we have a nightmare. For each different hatch rotation, you need to figure out the difference between that and the rotation you applied to the façade and then enter that in Properties. Luckily in this file the windows have a sort of random ‘sand’ hatch that doesn’t really matter if it’s rotated – because there are like 7 different hatch patterns in there and they have some different scales and rotations as well.
This stuff basically just sucks… I agree that the original file is a mess – but it’s the type of mess modelmakers most often get from architects/planners. We need to be able to fix this stuff easily.
I have scripts that help in some aspects of this, but it’s not the type of stuff you hand out to first week Rhino apprentices in class. Those scripts really shouldn’t be necessary if Rhino handled this type of operation correctly.