What export option to use to get Rhino into Affinity Designer?

Hmm… if the layers look correct when opened in Adobe Acrobat, there may not be much we can do. It may have to be something Affinity would need to look at.

We might have better luck with SVG if we figure out what Affinity use to define layers from svg tags

That’s how Illustator interprets this PDF:

Quite differently. Yet this clipping path stuff always was clumsy. I prefer Affinity Designer (and for 100 other reasons).

1 Like

Tried again with AD with different layer names:

Doesn’t make sense to me. Why is layer f omitted and e doubled?
Draw order, however, is correct.
What’ layer information is actually stored in a PDF? Does it support sublayers?

The issue is that the information stored in a PDF is not really “layers” in the sense how they are used in illustration applications. They are called optional content groups and are for allowing you to turn specific sets of items on and off. The items in each group do not necessarily correspond to a stacked order of how things are drawn. The program to test if what Rhino generates is correct is Acrobat as that is what the feature was initially designed for. We can keep trying different approaches to attempt to get a better layer set into Affinity, but we may never come to a solution by going the PDF route.

Try exporting a PDF from Affinity with layers and then reopen that PDF in Affinity. Does the layer information stay intact? Also, try the same thing with SVG in Affinity. If one of these formats keeps layer information, we might have a fighting chance to do the same from Rhino into Affinity.

Just wondering, would McNeel be able to help implementing a .3dm import to the Affinity suite, that is, if the drawings are 2D?

Hi -

That’s typically something that the Affinity people or a 3rd party developer would do and we would be happy to support them with any questions they would have with regards to the OpenNURBS library.