@macuso, Can you provide more details?
Yes. The newest DWG version supported by Rhino is 2007. I think a newer version will be great.
When exporting black lines into the DWG drawings and opening afterwards the DWG file with AutoCAD, having a black background in AutoCAD, I can’t see the lines. They remain Black on black background. AutoCAD has a special kind of case for the black lines created in AUtoCAD, if the background is black, the black lines will be displayed white, and reverse, but for the drawings exported from the Rhino, will remain black lines on black background which is unreadable.
Also the exported drawings are not centred in AutoCAD viewport. For every single drawing I need to right-click/Zoom/ZoomExtents and save again the file, this time from AutoCAD. It will be great to be able to open into AutoCAD DWG files created in Rhino and to maintain the actual viewport location, I mean to have the same view in AutoCAD like I do have in Rhino when exporting.
Now, if I open a DWG file (created in AutoCAD) in Rhino, usually the layouts are offset-ed up or down but not on the centre of the page.
1 Like
Thank you for the tip. Now I can see white lines on black background in AutoCAD.
Is there “preserve dimension format” checkbox somewhere, so Rhino dims keep the same size and units in DWGs opened in AutoCAD perchance?
Hi - there is no such checkbox, no.
What happens to the size? Can you post an example that changes the size?
As for the units, is the case that you have set the Length units > Units - formats option to something else than Model units?
-wim
Hi Marcuso,
Does this happen in Rhino 6 for Windows? Mac? Rhino 7WIP?
Please attach a file(s) that will show us this issue. If you do not want to post it here, email it to mary@mcneel.com.
I have not been able to duplicate it here with my files.
It works with my files. I am using AutoCAD 2019 and writing out the 2018 file format.
I was using a imperial units with inch for both the model and layout unit. Your file will help me out.
See the video here:
When I import an AutoCAD DWG, I do need to turn off the Rhino “Enable Layout Scaling” on Annotations. This typically works best for most AutoCAD dwgs. Here the text that is size in Model space will just be viewed on the Layout and “not scale”.
Again, send get us a DWG that will show us this issue. Erase anything in it that is not for disclosure.
Thanks,
Mary Ann Fugier
McNeel Technical Support and Training
Seattle, WA
Details Sheet in AutoCAD 2019
2018 DWG imported to Rhino 6 for Windows sr19
1 Like
See if this can be reproduced on your end. Fractions from R6 turn to decimals in DWG and dimension size gets scaled down into unreadable size. R5 wasn’t perfect, but was tolerable and workable. And yeah, you have to open DWG export in AutoCAD.
Not necessarily - round-tripping to Rhino does that too. Continuing this one in your original post.
-wim
Block attributes is the one of the few things I miss from Autocad.
There 's a promising attempt in WIP7 that allows user text to depend on parent block’s.
Linking this to DWG import and export could make Rhino support DWG block attributes.
Yes. There is some work in W7 that should help. Stay tuned.
1 Like
1 Like
As an architect, two missing features that force me to keep AutoCAD around:
-
XClip or equivalent - some sort of block masking is integral for 2D drafting workflows imho. Also, if I open a .dwg file that was created with xclips in Rhino, I can’t tell what on earth is going on.
-
Dynamic blocks - also something that breaks if I open a .dwg file in Rhino. This is probably a bit trickier because their constraints system is so convoluted. It’s a nice feature for common office workflows though, as it allows me to “transfer” some of my computational knowledge to people who know nothing about it or feel intimidated. I understand VisualARQ has a similar feature, with a dynamic-block equivalent being controlled by Grasshopper files - I think this belongs in vanilla Rhino and I assure you architects will love you forever if you add that feature.
2 Likes
Hi @bobmcneel and @John_Brock I’m a happy boy anyway but since Christmas is coming for “atmospheric assimilation” then easter, if Santaclaus and its awesome developer team can bring me this list, I will be a happy boy.
-
Bug fixing instead of wont-fix = new feature. Since a feature that does not work is not a feature at all and a bug fixing means an old feature that actually works is in practice a real new feature.
-
More QC software testing instead/before user quality improvement as for example:
Rhino Surface To Mesh For Product Visualisation, Presentations, Game Dev, Cinema, VR
- Rhino to Painter and back to Rhino workflow that works for simple and complex objects: RH-54784
- This means that UV mapping is applied to complex objects by using different polysurface in more simple UI RH-53857 RH-54103 RH-54119 RH-53888 RH-54765 (fixed RH-54101).
- Tha the UVEditor shows up the correct UV mapping Major Bug RH-54126.
- That polysurface merge conserve/preserve the UV mapping RH-53858.
- That converting to mesh preserves the UV mapping RH-54126
- That reducing the mesh preserve the UV mapping RH-54062
- Backface occlusion polygon edge selection for meshes to prevent wrong backside edge selection RH-54653.
- Faster mesh seams mesh selection (same RH-54653)
- Include correct UV mapping when exporting OBJ FBX (IGES?) file RH-55120.
- Importing FBX back to Rhino (RH-54785)
2 Likes
How do those architects handle RCPs?
Rhino resources are very limited. More features we ask more issues we will have. So isolate very well your problem, look for a workaround and push for bug fixing making a compact define and specific bug report.
There is no unique workflow for Rhino.
Input
Sketch volume in Blender o Zbrush mesh > Rhino retopology to surface and grasshopper
output
→ R123 IGES CATIA Solidworks, to make the master, class A,etc.
→ R456 STL 3d printer for millennials
→ R789 (SubD and fixing workflow) FBX OBJ Adobe Substance Painter → Octane Render Houdini VR Unity Unreal etc more in union with SubD.
Rhino7 is for Designers. There is no competitor to Rhino
Because of its relation prize and unique capacity to modelate complex nice shapes. Sometimes that is not possible inside solidworks or catia (cost 10000 + 2000 yr). Its only direct competitor is Alias is 15000usd (now VR and powerful).
Because angry people has migrated to Rhino PC in the 90s (Alias Indigo 70.000usd vs Rhino PC 300usd) and the other portion migrated when Alias split into Maya for animation rendering, instead of making a unique product. Users know how Autodesk works: Split and charge.
I don’t think so There is VR and SubD but that can explain why stupid boolean bugs are still there in alias and Maya.
Because it’s cost. But only for making meshes. You can make a rig or Lotus Elise and rendered but you can’t make a Wally yacht or Ferrari.
Rhino vertex normals red correct one. Blue is other software vertex normals.
SubD: since G1 is missing and you can’t make perfect radius, is more for making soft toys shapes and I hope that exporting process relative to UV mapping will be fix before RH7 ships.
I don’t know what your post has to do with what you expect to see in V7, but since you tagged me I feel that I need to point out that you missed Fusion 360 as something which probably will soon approach a similar market share as Rhino, and if you click on this link you can see some pretty interesting workflows that is has (also, don’t forget, it has T-splines, since Autodesk bought it).
EDIT: To make this about V7, I’d love to see setback fillet support in Rhino, similar to what Fusion 360 (and Solidworks 2018) has… but I guess I don’t expect it. 
In addition to SubD I’d like to see in Rhino 7 improvements to important commands (srf editing), the most used ones, for example: blend srf, extend srf, match srf, offset srf, etc.
Solve all limit cases and upgrade their options.
2 Likes
I believe many would agree it is time to lock this thread.
This single thread is taking over the purpose of the whole “Serengeti” category.
1 Like
SubD definition sounds just fine. Definitely not one of the actual problems affecting Rhino.