Continuing the discussion from Named CPlanes disfunctional?:
I can confirm that a block instance is inserted aligned to the current CPlane. However, if you type co-ordinates into the insertion dialog instead of using the prompt, the instance will be placed at those co-ordinates in WCS, not the CPlane coordinates. This mix seems unintuitive.
In the following illustration you see the original object that was used to create the block definition whilst the CPlane was set to World Top. You see the CPlane now set to the red plane. And you see the position set to (10,10,0) ready to insert a new instance.
And here is the inserted block instance at W(10,10,0) but orientation according to the CPlane.
And furthermore, if you attempt a non-uniform scale for a new insertion with a CPlane that is not one of the World ones, then that is messed up. Below you see another insertion being configured, with the X-scale factor set to 2, the other directions left at 1.
Which results in an instance scaled incorrectly: diminished, not enlarged, and in both CPlane X and Y.
If you set the CPlane to World Top before inserting, then the scaling works correctly.
Wishes:
Add a choice of CPlane or WCS for unprompted insertion point.
Add a choice of CPlane or WCS for orientation of insertion.
Improve the documentation by covering the interaction of CPlanes with Block Instance insertion.
Bugfix:
Correct the scaling error.
Rhino 8.16.25034.21001, 2025-02-03
BlockInsertionCPlaneTesbed2.3dm (138.2 KB)
Regards
Jeremy