Currently, the Rhino Inside AutoCAD project does not have an auto-update mechanism built into it. So, we are creating this thread to publicise the project’s release cycle and inform users of the latest versions when they become available.
To install a new version, simply download the latest from:
Then, run the installer; it should update the previous version if it detects one installed.
If you have any issues, please reach out.
Tom
Version V1.0.11 - Release Notes
don’t understand Fixes bug in the Get objects by Filter Limit property.
There was a bug in the “Get Objects By Filter” Component, in which the limit values were not always respected, so you could set the limit to 10 but get 11 objects, for example. This is now fixed in V1.0.11.
Version V1.0.12 - Release Notes
V1.0.13 - Release Notes
V1.0.14 - Release Notes
New Find by Handle Icon Added
Fix conversion bug with Hatches
V1.0.15 - Release Notes
Any news or a roadmap to share about upcoming updates and features?
@tuomas.lehtonen We have a release candidate which we are hoping to get out either the end of this week or the beginning of next, it contains a number of new components predominantly around block editing and filtering. But this is very much a community driven project so if there are thing you would like to see do let us know and we can add it to the roadmap!
Hi Tom, any updates on this? The download link seems not working right now.
Hi @weekenlwk, the link on the website is still not working, but the latest version can be obtained directly from the McNeel GitHub, whilst the page is being updated.
Thanks for the information. 
Can the functions of such a LISP plug-in be implemented with Rhino.Inside.AutoCAD?
Select the drawing border.
Window-select all drawings that need to be split.
Select the attribute block to list all attributes. Pick one or more attribute values (the attribute values may be fields) as the drawing names after splitting.
Set the save folder for split drawings.
Start drawing splitting. The splitting process: According to the quantity n of the window-selected drawings, copy the general drawing n times, and name each copied drawing based on the drawing name in the selected drawing border.
Open the renamed drawings, delete drawings with other drawing numbers, and retain only the drawing whose number matches the file name.
Move the bottom-left corner of the drawing to the coordinate origin (0,0,0).
(1) Create viewport: Create a viewport in paper space. Rotate vertical viewports to horizontal orientation if needed. Move the bottom-left corner of the viewport to the coordinate origin (0,0,0); set the global scale LTSCALE to a custom value, and check Use Paper Space Units for Scaling (PSLTSCALE).
(2) Do not create viewport: Set the global scale LTSCALE to the product of the drawing border scale factor and a custom value (e.g., if the drawing border is scaled 4 times and the custom value is 10, the LTSCALE factor = 4×10=40), and uncheck Use Paper Space Units for Scaling (PSLTSCALE).
When a viewport is created, there are two methods to process the drawing border:
(1) Transfer the drawing border to paper space and set it to 1:1 scale;
(2) Keep the drawing border unchanged in model space.
When a viewport is created, rename the layout to the drawing number.
Set the current layer to Layer 0 and switch to model space.
Zoom both model space and paper space to full-screen display.
Purge redundant data and close the program.
The entire drawing splitting process shall display a progress bar window. If the program is interrupted halfway, a pop-up window shall prompt Drawing Splitting Failed; upon completion of splitting, a pop-up window shall prompt Drawing Splitting Completed.
Hi Alan,
Rhino.Inside.Autocad is primary a grasshopper node library and so there is not a 1 to 1 conversion from LISP to grasshopper components.
Some of the items in the list are possible currently, however, many are not currently supported in these early versions. For example we have no Viewport or Drawing border Components yet.
However, these are something we can look to add. In terms of the larger vision, this would all be possible - it is just not implemented.
The UI/ popup window aspect of your post does not lend itself to be natively supported in the grasshopper eco system, but there is nothing stopping you from taking the open source project and building off the code to include your own UI and dialogs. Alternatively, you could create a grasshopper definition to do this and execute it via the grasshopper player.
Can you send a screenshot of the Guid clash dialog so i can see what it is clashing with? Or if you know off the top of your head?
Yeah it was just some Grasshopper component of my own, which happened to have that same default GUID in the style of 123…ABC… and so on. So the GUID’s are clashing
So a fault from my side as well but should be handled more gracefully.
