Edge Split Modifier don't work anymore when a Array Modifier is after the Edge Split Modifier added #41630

New Issue

David Schrott · 2014-08-29T12:44:46+02:00

David Schrott commented

2014-08-29 12:44:46 +02:00

System Information
Operating system and graphics card
Windows 7 64bit
AMD Phentom X6 1100T
AMD Radeon HD 6950 2gb

Blender Version
Broken: (example: 2.69.7 4b206af, see splash screen)
2.71.6 6891f1c
Worked: (optional)
2.71 release

Short description of error
When you smooth a Mesh and then add a Edge Split Modifier and then afterwards a Array Modifier. Then the Mesh looks like if there were no Edge Split Modifier added.
Exact steps for others to reproduce the error
Open the file

Based on a (as simple as possible) attached .blend file with minimum amount of steps

**System Information** Operating system and graphics card Windows 7 64bit AMD Phentom X6 1100T AMD Radeon HD 6950 2gb **Blender Version** Broken: (example: 2.69.7 4b206af, see splash screen) 2.71.6 6891f1c Worked: (optional) 2.71 release **Short description of error** When you smooth a Mesh and then add a Edge Split Modifier and then afterwards a Array Modifier. Then the Mesh looks like if there were no Edge Split Modifier added. **Exact steps for others to reproduce the error** Open the file Based on a (as simple as possible) attached .blend file with minimum amount of steps

David Schrott commented

2014-08-29 12:44:46 +02:00

Changed status to: 'Open'

David Schrott commented

2014-08-29 12:44:46 +02:00

Added subscriber: @thelasthope

David Schrott commented

2014-08-29 12:46:01 +02:00

![Bug.jpg](https://archive.blender.org/developer/F107274/Bug.jpg)

David Schrott commented

2014-08-29 12:47:11 +02:00

bug.blend

[bug.blend](https://archive.blender.org/developer/F107276/bug.blend)

Bastien Montagne self-assigned this 2014-08-29 12:51:51 +02:00

Bastien Montagne commented

2014-08-29 12:51:51 +02:00

Strange… Things are OK is Split Edge is applied…

Note you can use new 'Auto Smooth' feature instead of Split Edge modifier, things a re OK in this case.

Strange… Things are OK is Split Edge is applied… Note you can use new 'Auto Smooth' feature instead of Split Edge modifier, things a re OK in this case.

blender-admin commented

2014-08-29 18:07:54 +02:00

This issue was referenced by cba2e0afa7

This issue was referenced by cba2e0afa7525f93d1834cc5de6ca659547fdc5a

Bastien Montagne commented

2014-08-29 18:08:40 +02:00

Changed status from 'Open' to: 'Resolved'

Bastien Montagne closed this issue

2014-08-29 18:08:40 +02:00

Bastien Montagne commented

2014-08-29 18:08:40 +02:00

Closed by commit cba2e0afa7.

Closed by commit cba2e0afa7.

David Schrott commented

2014-09-01 01:14:10 +02:00

Changed status from 'Resolved' to: 'Open'

David Schrott reopened this issue

2014-09-01 01:14:10 +02:00

David Schrott commented

2014-09-01 01:14:10 +02:00

Sorry that I reopen this report, but i found another bug in the Edge Split or Array Modifier and its releated to this bug report. So the problematic is not fully fixed.

But please tell me when you want that i make a seperated report.

Problem:
When you smooth a Mesh and then add a Edge Split Modifier and then afterwards a Array Modifier. Then the Mesh looks like if there were no Edge Split Modifier added. (Like before, but now the problematic appears when have Merge in the Array Modifier activated.

Sorry that I reopen this report, but i found another bug in the Edge Split or Array Modifier and its releated to this bug report. So the problematic is not fully fixed. But please tell me when you want that i make a seperated report. Problem: When you smooth a Mesh and then add a Edge Split Modifier and then afterwards a Array Modifier. Then the Mesh looks like if there were no Edge Split Modifier added. (Like before, but now the problematic appears when have Merge in the Array Modifier activated.

David Schrott commented

2014-09-01 01:15:22 +02:00

![bug.jpg](https://archive.blender.org/developer/F107756/bug.jpg)

David Schrott commented

2014-09-01 01:17:11 +02:00

new_bug.blend

[new_bug.blend](https://archive.blender.org/developer/F107758/new_bug.blend)

Bastien Montagne commented

2014-09-01 10:46:18 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2014-09-01 10:46:18 +02:00

Bastien Montagne commented

2014-09-01 10:46:18 +02:00

No bug here, quite obviously if you enable merge the edge that were split by the previous modifier are merged again…

Bastien Montagne commented

2014-09-01 10:46:54 +02:00

And please always rather open new report, reopening should remain the exception and be done by dev team.

David Schrott commented

2014-09-01 11:49:45 +02:00

That isn't a bug?
I thought it was a bug because it had worked in the release of 2.71 (and i think in also in previous versions also) and now it don't work in the newest build.

When this isn't a bug, you should tell in the Release Notes that in 2.72 there is compatibility break for older files with this special case.

That isn't a bug? I thought it was a bug because it had worked in the release of 2.71 (and i think in also in previous versions also) and now it don't work in the newest build. When this isn't a bug, you should tell in the Release Notes that in 2.72 there is compatibility break for older files with this special case.

Bastien Montagne commented

2014-09-01 11:59:27 +02:00

More precisely, in 2.71 and before, there was only a partial merge, because only vertices at the 'boundaries' between duplicates were checked. Imho, this gave even worse (less predictable) results, see e.g. mod_edgesplit_array_merge.blend.

So yes, think doing a full merge is better than partial one, makes things much more reliable and predictable.

In any case, modifiers like edgesplit (but also subsurf, etc.) should always be put late in the stack, makes more sense.

More precisely, in 2.71 and before, there was only a partial merge, because only vertices at the 'boundaries' between duplicates were checked. Imho, this gave even worse (less predictable) results, see e.g. [mod_edgesplit_array_merge.blend](https://archive.blender.org/developer/F107847/mod_edgesplit_array_merge.blend). So yes, think doing a full merge is better than partial one, makes things much more reliable and predictable. In any case, modifiers like edgesplit (but also subsurf, etc.) should always be put late in the stack, makes more sense.

David Schrott commented

2014-09-01 12:51:12 +02:00

okay thanks for this detailed answer

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Edge Split Modifier don't work anymore when a Array Modifier is after the Edge Split Modifier added #41630