"inset polygon" goes crazy after "limited dissolve" #45805

New Issue

mathieu menuet · 2015-08-15T12:56:59+02:00

mathieu menuet commented

2015-08-15 12:56:59 +02:00

System Information
Operating system and graphics card

Blender Version
Broken: 2.75a

Short description of error
If "inset polygon" is called just after "limited dissolve", created faces are broken.

Exact steps for others to reproduce the error
Open attached blend, call "limited dissolve" on it and then "inset polygon". You get wrong results. Switching between edit and object mode between the 2 function calls prevent the problem to appear.
bug inset polygon.blend

**System Information** Operating system and graphics card **Blender Version** Broken: 2.75a **Short description of error** If "inset polygon" is called just after "limited dissolve", created faces are broken. **Exact steps for others to reproduce the error** Open attached blend, call "limited dissolve" on it and then "inset polygon". You get wrong results. Switching between edit and object mode between the 2 function calls prevent the problem to appear. [bug inset polygon.blend](https://archive.blender.org/developer/F224522/bug_inset_polygon.blend)

mathieu menuet commented

2015-08-15 12:56:59 +02:00

Changed status to: 'Open'

mathieu menuet commented

2015-08-15 12:56:59 +02:00

Added subscriber: @bliblubli

Aaron Carlisle self-assigned this 2015-08-17 02:08:12 +02:00

Aaron Carlisle removed their assignment 2015-08-17 02:09:04 +02:00

Aaron Carlisle commented

2015-08-17 02:09:04 +02:00

Added subscriber: @Blendify

Campbell Barton commented

2015-08-17 07:58:37 +02:00

Added subscriber: @ideasman42

Campbell Barton commented

2015-08-17 07:58:37 +02:00

Changed status from 'Open' to: 'Archived'

Campbell Barton closed this issue

2015-08-17 07:58:37 +02:00

Campbell Barton self-assigned this 2015-08-17 07:58:37 +02:00

Campbell Barton commented

2015-08-17 07:58:37 +02:00

Is this using the "inset polygon" addon? or Blender's built-in inset?
What values produce incorrect results?

Please show an image of the failing case.

- Is this using the "inset polygon" addon? or Blender's built-in inset? - What values produce incorrect results? Please show an image of the failing case.

mathieu menuet commented

2015-08-17 11:47:43 +02:00

it's using the addon "inset polygon" from Howardt. All values and produce incorrect results in my case (also default ones) as long as the 2 tools are used direct after eachother (first limited dissolve then inset polygon).
Correct version with an edit mode - object mode -edit mode switch between "limited dissolve" and "inset polygon"

Wrong version when inset polygon is called just after limited dissolve

it's using the addon "inset polygon" from Howardt. All values and produce incorrect results in my case (also default ones) as long as the 2 tools are used direct after eachother (first limited dissolve then inset polygon). Correct version with an edit mode - object mode -edit mode switch between "limited dissolve" and "inset polygon" ![no bug inset after dissolve with edit mode switch.PNG](https://archive.blender.org/developer/F224818/no_bug_inset_after_dissolve_with_edit_mode_switch.PNG) Wrong version when inset polygon is called just after limited dissolve ![bug inset after dissolve.PNG](https://archive.blender.org/developer/F224819/bug_inset_after_dissolve.PNG)

mathieu menuet commented

2015-08-17 12:46:59 +02:00

why is it closed as invalid ?

Adam Friesen commented

2015-08-17 20:50:24 +02:00

Added subscriber: @Ace_Dragon

Adam Friesen commented

2015-08-17 20:50:24 +02:00

Why not just use the official tool hardcoded in C (I-key). I used it on a similar curvy shape after invoking the limited dissolve operator and it did so with no problems.

Any new enhancements are going into the official tool and the addon is more or less dead development wise.

Why not just use the official tool hardcoded in C (I-key). I used it on a similar curvy shape after invoking the *limited dissolve* operator and it did so with no problems. Any new enhancements are going into the official tool and the addon is more or less dead development wise.

mathieu menuet commented

2015-08-17 20:58:22 +02:00

well, try to make an inset of 20meters with the hard coded one, it sucks. Even with 1 m, there are already overlapping faces. The addon is much more advanced. I already asked for the self intersection detection to be included in the C code, but it is "awaited behavior" to have possibly unusable geometry.

Campbell Barton removed their assignment 2015-08-18 00:09:55 +02:00

Howard Trickey was assigned by Campbell Barton

2015-08-18 00:09:55 +02:00

Howard Trickey commented

2015-08-18 12:53:07 +02:00

I think this may be the kick I need to look at putting my self-intersection-handling code into the hardcoded C inset, and retiring my add-on. I will start to work on this task (but it won't be a quick fix).