You can use dynamic blocks created with AutoCAD as they are. They will keep their intelligence and parameters in ARES Commander. But now you may alternatively use the CBCONVERT command to convert them into custom blocks which definition can be further modified with ARES Commander.

Using Dynamic Blocks in ARES Commander

Dynamic blocks represent a more intelligent evolution of the block entities that we all use in CAD software. The difference is that a simple block has no intelligence, at best we can scale it, change its rotation, and little else. While a “Dynamic Block” (from AutoCAD) or a “Custom Block” from ARES Commander have additional grips and more intelligence.

At least the possibility of varying the geometry and its behavior depending on the parameters and grips that have been incorporated. Look at this “Custom Block” that was created with ARES Commander. It is a complex block, which you can learn to do step by step, through previous videos that we have created on this topic.

In ARES Commander we can use both the “Dynamics Blocks” created in other CAD such as AutoCAD and the “Custom Blocks” created with ARES commander technology. Here are some examples that illustrate different cases where it is interesting to have smart blocks.

The truth is that the “Custom Blocks” of ARESS Commander allow to achieve the same results as the “Dynamics Blocks” of AutoCAD.

Difference between Dynamic Blocks and Custom Blocks

The only difference is that “Dynamics Blocks” are created with AutoCAD, and can be used with ARES Commander, while “Custom Blocks” are created by ARES Commander only.

Now let’s select this “Dynamic Block” and press the right mouse button to choose the “EDIT BLOCK” option. ARES Commander shows us a new option to “Convert” this “Dynamic Block” into a “Custom Block”. Do we want that? If we choose “OK” instead of “Convert”, we will be able to edit the block. But as you can see it is now only a simple block, the parametric actions that were configured before would be lost. I could add new ones but I would start again from scratch… We go back.

Now we will perform the same steps to edit the block. But this time we are going to choose the new option to “CONVERT”. The block editor opens and now we see that the parameters it previously contained have been converted into the Custom block technology. As you can see, “VISIBILITY” states are kept as well as the action and grip to modify the radius.

Add or delete Visibility States

In the “Visibility States,” we can see that 3 options appear with their names but they are written in Spanish. We could now delete or add more states. Alternatively, I can take the opportunity to rename them to be in English.

Besides, I can use the new “TEST BLOCK” feature to test the modified block before returning to the drawing. As you can see, now the “Visibility States” are in English. We close the test mode. And we also close the block editor.

We save the changes. Now, the block will have the same capabilities as when it was a “Dynamic Block”, only now it is a “Custom Block” of ARES Commander. It should be noted that, unlike AutoCAD, ARES Commander allows working with both “Dynamics Blocks” and “Custom Blocks”.

AutoCAD only supports working with “Dynamics Blocks”. Thus, if an ARES Commander user creates a “Custom Block” and then that block is used in AutoCAD or other CAD software, the Custom Block will be treated as a simple block. It could still be viewed, printed, and even modified but without the intelligence of a smart block.

Therefore, if your goal is to create smart blocks, which can be used by both AutoCAD users and ARES Commander users, you can continue to use “Dynamics Blocks”. While if you want to create a new smart block library for ARES Commander, you can create them as “Custom Blocks” with ARES Commander.

The ability to convert dynamic blocks into custom blocks is just making it easy for you to convert and improve what you already have, without restarting from scratch. Learn more about the new features in ARES Commander.