Page MenuHome
Create Task
Maniphest T44173

Remove Doubles damages meshes with custom split normal data
Closed, ArchivedPublic
Actions

Description

System Information
Win 7 x64, GTX 560

Blender Version
Broken: 2.74 RC4

Short description of error
Running Remove Doubles on a mesh with custom split normals leads to bad normals, even if the doubled-up normals are exact matches.

Exact steps for others to reproduce the error
Open

custom_normals_remove_doubles.blend522 KBDownload
and run Remove Doubles on the mesh.

Expected: no visible change
Actual:

Event Timeline

Tom Edwards (artfunkel) created this task.Mar 29 2015, 1:40 PM
Tom Edwards (artfunkel) raised the priority of this task from to 90.
Tom Edwards (artfunkel) updated the task description. (Show Details)
Tom Edwards (artfunkel) added a project: BF Blender.
Tom Edwards (artfunkel) edited a custom field.
Tom Edwards (artfunkel) added a subscriber: Tom Edwards (artfunkel).
Bastien Montagne (mont29) changed the task status from Unknown Status to Archived.Mar 29 2015, 2:36 PM
Bastien Montagne (mont29) claimed this task.

Thanks for the report, but this is a known limitation - any change affecting topology will break custom normals. we may work on it in future, but this is not considered a bug currently.

Julian Eisel (Severin) added subscribers: Bastien Montagne (mont29), Julian Eisel (Severin).EditedMar 29 2015, 2:36 PM

@Bastien Montagne (mont29), hmm, I'm a bit afraid we have to recalculate the custom normals after that? Not a big fan of this, cause I heard this can be quite slow in heavy scenes :| If so we should probably just add a silly popup asking if the user wants to recalculate or not? (but maybe we should consider this as a todo)
Anyway, you might know this a bit better, just thinking out loud ;)

Edit: Okay, nevermind, Bastien was faster :P