Maniphest T48887

in dayly nuild in ortho view snap not working
Closed, Resolved

Assigned To
Germano Cavalcante (mano-wii)
Authored By
B (bnzs)
Jul 18 2016, 9:09 PM
Tags
  • BF Blender
Subscribers
B (bnzs)
Brecht Van Lommel (brecht)
Sergey Sharybin (sergey)

Description

System Information
Win7x64 Geforce 430GT

Blender Version
Broken: (example: 2.77 a2c8f5)
Worked: 2.77a

Hi
In blender dayly build dont work snapping for components when try snap components of one object to another IN ORHTO view but in persp - work. In this video i show that in blender 2.76a all work but in dayli NO.
here video https://youtu.be/1EoQmqwClzM

Related Objects

Mentioned In
T48915: vertex snapping bug
rBf2fa73786b8f: possible fix for crash mentioned in T48887 - Adjust the depth min to the…
Mentioned Here
rBf2fa73786b8f: possible fix for crash mentioned in T48887 - Adjust the depth min to the…

Event Timeline

B (bnzs) created this task.Jul 18 2016, 9:09 PM
Sergey Sharybin (sergey) lowered the priority of this task from 90 to 30.Jul 19 2016, 11:11 AM
Sergey Sharybin (sergey) added a subscriber: Sergey Sharybin (sergey).

Please always attach .blend file which demonstrates the issue. Videos are rarely helpful for troubeshooting.

Campbell Barton (campbellbarton) assigned this task to Germano Cavalcante (mano-wii).Jul 19 2016, 3:57 PM
Germano Cavalcante (mano-wii) mentioned this in rBf2fa73786b8f: possible fix for crash mentioned in T48887 - Adjust the depth min to the….Jul 20 2016, 3:25 AM
Germano Cavalcante (mano-wii) added a comment.Jul 20 2016, 3:30 AM

By analyzing the code, I discovered an error in time to do_ray_start_correction.
I believe the problem was corrected in rBf2fa73786b8f30689c5810224204868775d9c4ec.
I will wait for confirmation.

Campbell Barton (campbellbarton) mentioned this in T48915: vertex snapping bug.Jul 21 2016, 6:45 PM
Brecht Van Lommel (brecht) changed the task status from Unknown Status to Resolved.Jul 30 2016, 4:01 PM
Brecht Van Lommel (brecht) added a subscriber: Brecht Van Lommel (brecht).

10 days without reply, let's assume this problem was fixed.