@nathanletwory not sure if you saw this, but Plasticity made a livebridge and any such addon on Blender’s side should be GPL compliant, which means you may be able to adapt it to Rhino:
The issue is not the technology, but availability of resources (time).
I noticed it’s at release 0.0.16… so very early days. But how are you feeling about your Rhino to Blender reader? Do you have a roadmap? I’m interested in comparing CPU-only Cycles in Rhino to the GPU-enabled Cycles in Blender…
Why would you want to do CPU only rendering in Rhino using Cycles if you have a GPU?
Anyway, I am currently busy with finishing up the Cycles upgrade for Rhino 9, so I have been neglecting the add-on a bit. I know there are some things to tidy up for instance to support Blender 5.0, and I will do so when I am done with the upgrade. Other than that there isn’t a hard roadmap for the add-on. Pretty much depends on what users need and what rhino3dm provides in functionality, but at least you should be able to get much of the geometry imported.
Because Cycles in Rhino on wine appears to be CPU only. Whereas Cycles in Blender native to Linux is GPU enabled.
As for the roadmap, I totally understand!
Edited to add: and good luck on the Cycles for Rhino 9 work you’re doing!
Hello Nathan,
Thank you so much for your add-on! I finally managed to get it working with Rhino 7 by downloading the file import_3dm-0.0.16_extension.zip. It’s working great, but the geometry I obtained has a little too few polygons ://
Do you know if there is any way to generate more polygons during the import?
I was usually importing a .DAE file which had enough polygones for my renders (1rst image) and on the second image is what I got with the rhino importer Addon …
Thanks you so much in advance !!
To me this looks like the vertices are merged during import. Currently the importer merges vertices with a fixed distance. There is an open pull request to provide options during import.
Option to merge vertices on import by rockjail · Pull Request #150 · jesterKing/import_3dm · GitHub
Until that is merged, you can try scaling up the model first before save/export.
Thanks a lot !
I’m back working on import_3dm, currently tackling the crash issue on Linux, then going over all the other issues and PRs.
I’m running into some trouble with rhino3dm at least on my amd64 Linux box. It looks like layers aren’t being parsed properly. It works on my aarch64 Linux box.
I’m in the process of debugging this now. I had to build rhino3dm manually anyway on Linux to work around a crash problem when rhino3dm is running in Blender ( PR to OpenNURBS Rename z_inflate to jk_z_inflate. by jesterKing · Pull Request #115 · mcneel/opennurbs · GitHub ). The modified rhino3dm branch I’ll be using is at GitHub - jesterKing/rhino3dm at fix_linux_zinflate_crash .
At least on my aarch64 Linux box I am able to import 3dm files in Blender 5.2 (Alpha).
It looks like on x86_64 Linux the release build of rhino3dm has issues. The debug build works. That makes debugging a bit of a tricky issue. I may just in the interim make a new import_3dm release with the debug builds on x86_64 linux while I have a go at figuring that out.
I still have to see if the official rhino3dm module on the same platform has the same issue or not.
nvm. I just remembered that the official build is actually also a debug build, just with the debug info stripped.
I made a v0.0.17 release:
I will probably upload this also to the extension platform at some point. edit: probably not. The add-on is currently under MIT license, and extensions.blender.org requires add-ons to be GPL 3.0 or later.
See for already newer release:
Hello everyone! I’m a new Blender user of a few months now, and I’ve struggled quite a bit with transfers between Rhino and Blender. Having previously used Twinmotion and its DataSmith plugin on Rhino, I realized that nothing like it existed for Blender, or at least I couldn’t find a real equivalent. A little over a month ago, I finally decided to create this alternative, and I’ve released this on Superhive. So, if this might interest anyone in the Rhino/Blender community, feel free to tell me what you think!
looks amazing, I will give it a try!
Curious to see how it works with a lot of objects (10 000+ block instances)
Looks like a very nice addition for those that work between these two worlds. Putting in my vote a Mac version in the future.
Hi! Thanks for your interest! Feel free to let me know if you try it out and if everything works well. Normally, version 1.1 handles up to 15,000 objects (I have a lot of RAM, so we’ll see how it behaves on other configurations). I’ve just released the Mac version! I haven’t updated the docs yet, but please give me feedback if you encounter any bugs or things to improve.
Hi @martin37
Does this work with Rhino V7? I’m not running V8 but would purchase if it works with Rhino V7. I think there are a lot of V7 users not using V8.
This plugin seems important enough to deserve its own thread.
Thanks,
RM
Hello,
At the moment, Rhino version 7 is not supported. However, I started looking into the issues related to version 7 and the changes it implies for the code yesterday. Version 7 should be available within the next few days—I will let you know once it is ready.