Page MenuHome

Inset going nuts
Closed, ResolvedPublic


System Information

Blender Version
Broken: 2.70 stable release
Worked: 2.69

Short description of error
On that simple mesh the insetting is getting out of hand

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps

  • load Blender 2.70 stable
  • File -> Load Factory Settings
  • File Open -> Load UI disabled and then load the attached blend.
  • Go into front Right View (Numpad 3) in Edit Mode
  • Select all if it's not already selected
  • Press I to inset and move the mouse , the mesh go nuts

If i load that blend in 2.69 stable , while it's not going to get a satisfying{F81952} result, at least the mesh does not explode.

Note : Inset individual (pressing 2 times I ) works without a problem in every versions.

Event Timeline

Sanc Tuary (sanctuary) set Type to Bug.
Sanc Tuary (sanctuary) created this task.
Sanc Tuary (sanctuary) raised the priority of this task from to Needs Triage by Developer.

looks like i can't edit what i wrote, so
Go into front Right View (Numpad 3) in Edit Mode

was meant to be
Go into Right View (Numpad 3) in Edit Mode

and the attached file ( F81952 ) for some reason has placed itself just after the word "satisfying" despite i didn't dragged it there, i guess my browser settings are not friendly to those new scripts on that page

Some important additional note i found today while testing more :

I noticed after pressing I, having then the inset "exploding" and pressing enter/right click to apply it that if i press F6 (or look into the operator) and disable "Edge Rail" that is an option by default, the inset does not explode anymore.

In Blender 2.69 in which the inset does not explode (but is not making a good result on the provided mesh) that the Edge Rail option does not exist in the Inset operator

And probably important, in 2.70 that make the inset explode, if i disable that new "Edge Rail" setting, the inset is really good on that mesh, nothing in common with the bad result of 2.69

Campbell Barton (campbellbarton) raised the priority of this task from Confirmed, Medium to Unbreak Now!.Mar 28 2014, 2:35 AM

This is really bad. somehow it didnt show up in my tests, will look into a fix today for 2.70a