Log In
New Account
Home My Page Projects Blender 2.x BF release
Summary Activity Tracker SCM Files

Blender 2.6 Bug Tracker: Browse

[#32357] Subdivide fails on newly created edge

Date:
2012-08-18 17:46
Priority:
3
State:
Closed
Submitted by:
Tobias Oelgarte (niabot)
Assigned to:
Campbell Barton (campbellbarton)
Category:
Mesh Modeling
Status:
Fixed / Closed
Relates to:
Duplicates:
Patches:
 
Summary:
Subdivide fails on newly created edge
Detailed description
I appended an example file. If i open the file, select the two "free vertices", create an edge (F) and immediately call subdivide on it, then the subdivde operator does nothing. If i now deselect the vertices, select them again and use subdivide it works like it should.

Ubuntu 10.10 r49694

Followup

Message
  • Date: 2012-08-18 17:47
  • Sender: Tobias Oelgarte
  • PS: It only occurs in the case if the vertices already exist and are only connected to other edges (not part of a face).
  • Date: 2012-08-18 20:22
  • Sender: Nicholas Bishop
  • Couldn't confirm this (tried in 2.63a and latest SVN). What version of Blender are you testing?
  • Date: 2012-08-19 01:50
  • Sender: Campbell Barton
  • managed to redo this, but only sometimes (maybe one in 5 times or so), ran in valgrind and its not reporting un-initialized memory.

    need to look into this further.
  • Date: 2012-08-21 13:23
  • Sender: Tobias Oelgarte
  • Notice: This does happen to other operators as well. Just created a circle, selected every nth-vertex and then tried to invert the selection (Strg+I). It did nothing. As soon i left edit mode and entered it again it was working as usual.
  • Date: 2012-08-21 23:09
  • Sender: Alexander Pinzon
  • Hi, I can\'t reproduce this here, can you please try again on an
    up-to-date SVN revision?
  • Date: 2012-08-21 23:09
  • Sender: Alexander Pinzon
  • Couldn't confirm this (tried in blender rev 50102 32 bit, Windows 7).
  • Date: 2012-08-22 10:53
  • Sender: Tobias Oelgarte
  • I can still reproduce it on Ubuntu 10.10 32 bit with r50079 and r50104.

    In r49694 i had it every time and with r50079 and r50104 it happens more or less randomly. I just need to extrude two lines (edge->vert->edge->vert->...) and make a connection (edge) in between them. In roughly 50% of the times i have this behavior. The error must be somewhere in the selection code (if the selection is changed by an opertor), because other operators fail as well.

    My guess is the following: I can reproduce this bug in multiple ways, but it always involves a first call to operator that updates or changes the selection. Another condition is that none of the selected edges is connected to a face. So i would say that the edge selection status is not rightfully updated after the call to the first operator that changes the selection. The second operator must then see a wrong selection.
  • Date: 2012-08-22 13:01
  • Sender: Tobias Oelgarte
  • PS: Invert selection seams also to miss some vertices on more complex meshes after i used "Select inner region". The obviously something strange happening inside the selection code.
  • Date: 2012-08-22 21:14
  • Sender: Tobias Oelgarte
  • I think it gets a really serious issue. Even x-mirror is affected in such cases, not being able to find the mirrored vertex which is exactly at the right place. :(
  • Date: 2012-08-24 16:54
  • Sender: Campbell Barton
  • the newly created edge wasn't selected (only its verts were). fixed r50190.
 

Attached Files:

Name Date Download
subdiv-bug.blend 2012-08-18 17:46 Download

Changes:

Field Old Value Date By
status_idOpen2012-08-24 16:54campbellbarton
close_dateNone2012-08-24 16:54campbellbarton
StatusConfirmed2012-08-24 16:54campbellbarton
assigned_tonone2012-08-19 01:50campbellbarton
StatusNew2012-08-19 01:50campbellbarton
File Added21767: subdiv-bug.blend2012-08-18 17:46niabot