[Bf-committers] priority for bevel fix???

Nahuel Belich casillapforos at yahoo.com.ar
Mon Nov 27 03:58:37 CET 2017

Tested the Fix! now can spread the voice, """LETS GO BACK TO HARD SURFACE MODELING""!!!     

This was a pain for a lot of enthusiast modelers :)  


    El Sábado, 25 de noviembre, 2017 14:04:32, Eugenio Pignataro <info at oscurart.com.ar> escribió:

 Thanks a bunch! :)

On November 25, 2017 1:55:43 PM GMT-03:00, Ton Roosendaal <ton at blender.org> wrote:

Just for history - within a day the issue was fixed and closed. :)


Ton Roosendaal - ton at blender.org - www.blender.org
Chairman Blender Foundation, Director Blender Institute
Entrepotdok 57A, 1018 AD, Amsterdam, the Netherlands

 On 22 Nov 2017, at 21:46, Nahuel Belich <casillapforos at yahoo.com.ar> wrote:
 This is not a feature request or something like that, im here to ask for some priority in this bug report developer.blender.org/T53145 if its possible. 
 More or less a month ago appear this bug that makes bevel really annoying to use, even if it is possible managing to deal with it using operator properties after the bevel gone to 1000000, its being mentioned all around, facebook, blenderhoy, even Pablo (venom) was asked several times about it in his live streams so it became a problem because its not a corner or obscure case, probably every modeler using trunk may have to deal with it, even more these was mentioned in several duplicated reports its really common to find, just bevel two times in the same object and the bevel value jumps to 1000000. 
 Thanks in advance.
 Nahuel Belich 

 Bf-committers mailing list
 Bf-committers at blender.org

Bf-committers mailing list
Bf-committers at blender.org

Sent from my Android device with K-9 Mail. Please excuse my brevity.


More information about the Bf-committers mailing list