Thanks a bunch! :) On November 25, 2017 1:55:43 PM GMT-03:00, Ton Roosendaal <[email protected]> wrote: >Hi, > >Just for history - within a day the issue was fixed and closed. :) >https://developer.blender.org/rB5e13097dc3a3463d6b8643a5ace673d7a462c934 > >-Ton- > >-------------------------------------------------------- >Ton Roosendaal - [email protected] - 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 <[email protected]> >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 >> -BFCT- >> >> >> _______________________________________________ >> Bf-committers mailing list >> [email protected] >> https://lists.blender.org/mailman/listinfo/bf-committers > >_______________________________________________ >Bf-committers mailing list >[email protected] >https://lists.blender.org/mailman/listinfo/bf-committers
-- Sent from my Android device with K-9 Mail. Please excuse my brevity. _______________________________________________ Bf-committers mailing list [email protected] https://lists.blender.org/mailman/listinfo/bf-committers
