I’m not sure what I’m looking at in those images… A Rhino 3dm file would be good to have. Can you just export a block that is causing issues to a new 3dm file and post that here?
-wim
Yes, I looked into that last week but didn’t get to ask the following-up question because I lost track of this thread and now I need to find those files again on a different machine…
Could you explain how you made, for example, the block instance that is colored pink in this picture? I tried 1D scaling the original block but that didn’t lead to the same situation…
everything is fine, I just wanted to ask, thanks for the answer.
The block is actually relatively simple.
It consists of:
• 1x rectangle
• 2x lines
• 3x points
• 1x hatch
The rectangle, lines and the hatch are on the same level (E_0), the points are on a different level (E_0_HILFSPUNKTE) and only serve as auxiliary objects.
The block itself is on another level (E_45_TRASSE_DECKE), this is only scaled to achieve the desired length.
Yes, I do.
I’m wondering how you created that specific block instance.
When I insert a new “E_KT_300_1m” block instance, it is, not surprisingly, 1 meter. When I then use Scale1D to make it 4.73 meter as the one that I marked in my image, I get the following in the properties tab:
@wim - I just had a report from a client that exporting .dxf to his CAM program stopped working with the update to 8.17… Says his CAM program can’t read them. Did someone modify the ACAD exporters between 8.16 and 8.17?
@wim I wanted to give you another update on my problem. Manually re-inserting and repositioning the blocks, even with Grasshopper, is an extra and time-consuming step that is inefficient in large projects. As an alternative, I’ve been exploding the blocks, which in turn leads to very large file sizes.
Additionally, in collaboration with a colleague, I’ve been trying to solve the problem with a Python script. We ran into errors that lead us to believe there may be a problem in the rhinoscriptsyntax library. The error messages, such as expected Plane, got Point3d and Could not convert ... to a Point3d, occur when the script attempts to create or apply a rotation or scale matrix. This suggests that the API for handling block transformations may be faulty, which could also be causing the export issue.
Since I have little expertise in this area and my colleague can no longer do much, I would prefer to find a different solution here.
@Helvetosaur I read about your client’s problem with the dxf export. How did he deal with the problem? Was the issue resolved for him after a later update?