I have created a new Topic to help debug this issue!
@Tom_Norris The current block insertion functionality is still quite limited. My idea is: for newly created blocks, you should be able to edit their attributes and parameters before baking, with real-time preview. Once everything looks right, you then perform the final bake.
does autocad architecture work? or just the regular autocad?
Unfortunately the attributes and properties are not available in AutoCAD until after the block reference is create in the database.
To address the baking suggestion we need to delve into why some objects are bakeable and others are not. There are two kinds of objects in RiA : Database objects and Geometry objects. We treat them differently: the geometry we keep wherever possible tightly coupled to the Rhino Geometry counterparts. They use the grasshopper Geometry Goo as this has the benefit of allowing grasshopper transformations and morphs, even if they will eventually become AutoCAD database objects - It makes sense to keep these tightly coupled as we want to be able to switch between the Rhino and AutoCAD types on demand. These are the objects which can be baked and when they are backed they are added to the AutoCAD database.
Then there are the purely AutoCAD database objects like Layers, LineType and Block Definitions. These exist as objects isolated from their Rhino counterparts as a logical distinction, and they require an active database transaction to be created and are immediately added the database and so they do not any need for the baking functionality.
Block References then fall into a grey area, whilst they have a do have a geometry component it would not make sense to couple them to the Rhino block infrastructure as they need the AutoCAD Block definitions and database to be created, which is why they are currently in the second category and are created immediately. If we did consider making them bakeable so they are not added to the database until they are baked. This would not have the effect you are after as there attributes/ parameters would not be available until after they are created in the database. So all you would have is the default geometry from the block definition available to be previewed. It also would add a number of complications, as it would require making them Geometric Goo, which would allow some invalid operations.
We can have a think about ways to improve the infrastructure so it is less limited.
@Lawand_Noa_man we have not tested it on AutoCAD Architecture, but there should be no reason why it cannot, if you do have any issues, let us know and we can look to resolve them as we may need to update the package configuration to make sure AutoCAD loads it - but it also may just work out of the box.
Great I’ll give it a try and let yall know
where do I download/ install rhino-inside-autocad
see the first post in this thread for additional details.
I am very exited about Rhino.Inside.AutoCAD! as many of our work is done in AutoCAD. The highlight preview of selected elements would be a great feature!
When it comes to adding or changing a drawing, is it possible to get all object/blocks in a layer and then move these objects/blocks to a different already existing layer?
We mostly work by adding or removing existing parts of a drawing, and it is very rare to start with an empty sheet. What would then be useful blocks for selecting objects and removing or adding to an existing drawing? I have been playing around, but could not find how to do this.
Hello, there. Is there any way to retrive the element properties? like layer, lightweight, and etc? just like Rhino inside revit, you can access element parameter. I am trying to transfer the autocad" polyline to Rhino with its own layer.Thank you!
edit: I find a way to fliter by layer name and I am thinking maybe I can use Elefront to bake geometry with its layer.
Hi @LOKI1
Yeah that sounds like it would be a useful component to have, ive added it to the road map here:
Thanks for the feedback, it is really useful!
The highlight preview of selected elements would be a great feature!
We have now added this starting in version V1.0.19
is it possible to get all object/blocks in a layer
This is currently possible using the filter components:
and then move these objects/blocks to a different already existing layer?
This is also sort of currently possible but we are still working on the documentation side of the project so these slightly more convoluted ways of doing things are not so obvious. But for context:
The geometry objects in Autocad when in the grasshopper canvas are much more similar to Rhino geometry in Grasshopper than the Rhino Inside Revit approach. We can do this is because they have a direct geometry conversion type within Rhino (which the RiR types does not). This means they are on memory, geometry only (no properties) and do not exist in the Autocad Database until a Bake operation is performed. It is through the baking which you can set the layer of the geometry:
Blocks on the other hand are different. They always exist in the AutoCAD database they are not bakeable and currently there is no way to edit there properties - This is something we need to add - I am hoping to squeeze into V1.0.20
What would then be useful blocks for selecting objects and removing or adding to an existing drawing?
Adding geometry to layouts is defiantly something we want to expose in the future. You can follow the ticket here: Add support to bake objects into the Layouts · Issue #28 · mcneel/rhino.inside-autocad · GitHub
Yesterday Rhino.Inside.AutoCAD saved our lives..
We recieved a very big and messy autocad file, thousands of blocks and groups and object and for some reason we wanted every object to be on layer “00” even object inside of blocks and groups.
AutoLISP did nothing, importing it into rhino messed up the file and it was painfully slow. Rhino inside Autocad came in clutch.
C# SCRIPT.txt (4.4 KB)
Main.gh (6.8 KB)
@Tom_Norris
Operations performed using Rhino.Inside.AutoCAD generate a long sequence of operation history records in AutoCAD. Is it possible to package each operation as a single grouped unit, similar to Rhino.Inside.Revit?
@Tom_Norris
When I connect a CAD block to the AC-BlkRef component, if no color is input, the block’s color is forcibly changed to 0,0,0. This is unreasonable; in this case, the block’s original color should be preserved.
Hi Pan, Yeah someone else had also noted this, in the next release candidate the default has been updated to now ByLayer, would that work in your opinion? You can follow this issue: Block Reference Color · Issue #29 · mcneel/rhino.inside-autocad · GitHub
I will need to have a think about this, there are some key difference in the way RiR handles the revit transactions and we handle the RiA transactions. But potentially there are things we can do to group some of them together. What sort of operations were you doing?
For any operation, as long as multiple elements are involved in the same operation, each element leaves its own operation record. This is disastrous for undoability. I want each operation to be recorded only once, regardless of how many elements are bound.