Bevel in Maya 2017

[pascal]

There is a bug in the bevel tool.

The result is not accurate.

 in Absolute offset - world mode : type 1 and you get 1.414...

Please developers, update your pythagore formula...

An please Autodesk, reconsider your work about the UI...

Nothing is working well, reading this forum should makes you react.

For now, I repeat than I can't use maya 2017 as is. I still use 2014.

And I'm really not alone..

[Nadja.Bueckmann]

Hi @pascal,

can you show me what exactly you are doing and how what the result of the bevel is?

Thanks,

Nadja

[_sebastian_f]

@Nadja.Bueckmann i think his screenshot says all.

take i.e. a 2*2*2 cm cube, select an edge, bevel with absolute and world space set to 1. you will expect the new edges are inset 1 unit from the original position but they are not.

[Nadja.Bueckmann]

Hi @pascal and @_sebastian_f,

I can reproduce it on my side.

I will forward it to our development department so that they can have a look into the issue.

Best, 

Nadja

[pshwayka]

It seems to work correctly if you enable "Offset As Fraction" in the bevel options. You can access these by clicking on the little "hamburger" menu in the upper right hand corner of the bevel pop-up.

[smbell1979]

unfortunately offset by fraction doesn't let your get consistent bevel sizes across multiple objects, that's the purpose of the world space distance. 🙂

[pshwayka]

Sorry...I didn't word that well. What I meant was the offset by fraction option seems to work correctly (as a workaround for a single object.) 

[pshwayka]

Another (and probably better) workaround that will produce consistent results across multiple objects is to create a toolbar icon out of the following script. Once you have done that, you can right-click on the icon, click "edit" and adjust the number after the word "offset" for the desired world space offset amount.

______________________________________________________________________ 

polyBevel -offset 1 -offsetAsFraction 0 -autoFit 1 -segments 1 -worldSpace 1 -uvAssignment 0 -fillNgons 1 -mergeVertices 1 -mergeVertexTolerance 0.0001 -smoothingAngle 30 -miteringAngle 180 -angleTolerance 180 -ch 1 ;

[_sebastian_f]

thanks but sorry but the offset as fraction can not even be considered a solid workaround for this issue. it works on simple edge attachments but there a cases were even this fails or at least produces unpredictable results. also if i get asked to create a specific radius on a corner i don´t want to measure the adjacent edges and take out my calculator to find out what fractional offset i need to get my desired bevel amount.

haha, while writing this i receive your next post.

yes you´re right using the old bevel still works but unfortunately you loose all the new features which finally made bevel much more useful like the option not to chamfer.

it just needs to get fixed.

[pshwayka]

---

@_sebastian_f wrote:

it just needs to get fixed.

---

Of course it does, silly! 

Keep in mind that if workarounds were solutions, then they would be called "solutions." 

[_sebastian_f]

hahaha indee:)

[pascal]

Hi,

There is no workaround. 

And even if there is, I don't think I have to loose my time to fix the mistakes of Autodesk.

I mean I'm Maya user since the V1, I paid a lot of money, and I just have to get a solid software to make my job.

So, sorry to repeat, but please just fix it.

And read the forum... Maybe you will realize that you have a lot of work to do.

-Pascal

[pascal]

Hi,

I just installed the update 3 and...

Nothing fixed about this bevel bug.

And of course still remain this erratic and unusable UI.

Well, I just have my eyes for cry

Thanks

[trevor.adams]

Hey folks,

The problem reported in this thread is indeed reproducible in the latest release of Maya 2017, Update 3.  I had looked into this issue not too long ago thanks to a similar report on our Small Annoying Things forum, here:

http://mayafeedback.autodesk.com/forums/160518-small-annoying-things-to-fix-in-maya-forum/suggestion...

The good news is that we've identified the source of the problem on our end. Long story, short: It's a regression caused by a separate bug fix we did in our bevel code.  We currently have this defect fixed internally and we're planning on including the fix in an upcoming Maya release.

Thanks for bringing this up here.  I'll post an update here once this is fixed in a publicly-available release.

[trevor.adams]

Update: Maya 2017 Update 4 has been released today and includes a fix for the bevel issue reported in this thread.  Please let me know if this is indeed solved on your end after checking it out, by clicking on the "Accept as Solution" button.  Thanks again for all the feedback on this one!