Emboss: Sketch profiles are not coplanar

Emboss: Sketch profiles are not coplanar

Anonymous
Not applicable
2,842 Views
23 Replies
Message 1 of 24

Emboss: Sketch profiles are not coplanar

Anonymous
Not applicable

Hi there,

 

I'm encountering a strange error I'm hoping someone can help whether is a strange bug or something I'm missing.

 

I have a curved surface that I want to emboss some text (imported as .SVG). At first this worked perfectly fine (see "Emboss working.f3d"). However, I wanted to scale down my text a bit. I used the scale command in the sketch workspace to scale it down. After doing so, when trying to emboss the "U" letter it gives me the error "Sketch profiles are not coplanar. Deselect sketch profiles that are not on the same plane." Even when selecting only the "U" letter (only one sketch profile selected, it still says that multiple are selected and that they are not coplanar. Model "Emboss failure.f3d" shows this error.

 

Has anyone experienced this before? I assume it must be something with the sketch profile of that specific letter that Fusion has issues with, but I can't figure out what's wrong with it.

 

Also if someone could confirm that the "U" letter cannot be embossed using the emboss command it would be very helpful.

 

Thanks

Alfred

EDIT: I tried deleting the old text sketch geometry and reinserting the .svg. Scaled it to correct size and now the "U" embosses fine. Still interested in seeing why it doesn't work in the attached files

0 Likes
Accepted solutions (1)
2,843 Views
23 Replies
Replies (23)
Message 21 of 24

bryn.parrott
Contributor
Contributor

Thanks, now I an adding to prior response.

Your findings are interesting, but from a user perspective it ought not be necessary for me to closely look at every letter and pick it apart from unknown requirements of the emboss function.

But may help the programmer discover a way to automatically & transparently handle the condition. 

If you were able to discover this cause in a short time, why not Autodesk paid software engineers?

0 Likes
Message 22 of 24

bryn.parrott
Contributor
Contributor
Thanks for responding on-topic.

What you say gives insight into the underlying technical issue. Essentially puts the ‘blame’ onto Apple, as this is one of the set of inbuilt fonts in MacOS.

But there’s an unexplained fact, only discovered today.
With Fusion unable to make the embossed text, I explored other options.
I exported the object (no text) as STL mesh, and opened it in Prusa Slicer, which has facility to emboss text, but not on a curved path. I created the same text using the same Brush Script font, and it prints pretty much ok (slight blurring) using raised lettering not sunken lettering.

So, Prusa Slicer can emboss text using Brush Script, but Fusion cannot do it using the Emboss command.
At the very least Fusion should detect the condition, and not present errant fonts that will not work.

Prusa Software is free. Fusion costs me a lot of money each year. Prusa Slicer is open source therefore its easy for a programmer to discover how it does what it does. This goes for handling of mesh files too by the way.

So, You will see why I have perspective that Autodesk ought to be able to fix this issue, certainly sometime since 2021 when it was first reported.

Cheers
0 Likes
Message 23 of 24

jeff_strater
Community Manager
Community Manager

you are not wrong.  Certainly this problem is fixable.  It is only a question of priority.  To be honest, this is probably not very high on the priority list right at the moment. 


Jeff Strater
Engineering Director
0 Likes
Message 24 of 24

bryn.parrott
Contributor
Contributor

One thing to add to the list of tasks: Fix that Arcane error message.  It means nothig to mere users (like me). It does not point to the problem. 
"Incompatible Font:" would tell the story more clearly.

Of course this issue of error messages that mean nothing to users is really a problem the size of Everest when referring to Fusion. I do not think I've seen even one error message that meant anything useful, and yet it has to thrust them at you to interrupt your workflow.

0 Likes