Shrinkwrap not taking auxiliary target into account properly #48547

New Issue

Carlo Andreacchio · 2016-05-30T08:12:52+02:00

Carlo Andreacchio commented

2016-05-30 08:12:52 +02:00

System Information
Windows 7 x64 GTX580

Blender Version
Broken: 999d5a6 onwards (including 11b0874)
Worked: b0a7e77

Short description of error
Shrinkwrap does not take auxiliary target into account properly

Exact steps for others to reproduce the error

Open attached blend file in the git version provided
Notice it is going up into the air
revert git backwards
open attached blend file
notice how it sticks to the plane below
shrinkwrapbug.blend

**System Information** Windows 7 x64 GTX580 **Blender Version** Broken: 999d5a6 onwards (including 11b0874) Worked: b0a7e77 **Short description of error** Shrinkwrap does not take auxiliary target into account properly **Exact steps for others to reproduce the error** 1. Open attached blend file in the git version provided 2. Notice it is going up into the air 3. revert git backwards 4. open attached blend file 5. notice how it sticks to the plane below [shrinkwrapbug.blend](https://archive.blender.org/developer/F315283/shrinkwrapbug.blend)

Carlo Andreacchio commented

2016-05-30 08:12:52 +02:00

Changed status to: 'Open'

Carlo Andreacchio commented

2016-05-30 08:12:52 +02:00

Added subscriber: @candreacchio

Campbell Barton self-assigned this 2016-05-30 14:51:19 +02:00

Alex commented

2016-05-30 14:55:11 +02:00

Added subscriber: @SpectreFirst

Alex commented

2016-05-30 14:55:11 +02:00

System Information
Intel Core i7, 8 Gb RAM, AMD Radeon HD 7700
Windows 7 x64

Blender Version
Broken: 2.77 11b0874
Worked: 2.77a abf6f08

Short description of error
I can confirm there is a problem in latest builds and I have also found a couple of strange things:

If you enter Edit Mode on the bottom plane, shrinkwrap will start working.
It looks like that BOTTOM (Auxiliary) plane uses TOP (Target) plane’s dimensions as dimensions for shrinkwrapping! Changing the size of the top (Target) plane’s mesh seems to affect the bottom (Auxiliary) plane’s snapping for some reason.

You can take a look at my version of the test file, it's practically the same thing with planes, but some planes are changed to illustrate the issue I've found:

If you open my file in 2.77a, both small planes will shrinkwrap to both large planes.
If you open my file in latest build of 2.77, only closer one of the small planes will shrinkwrap to the bottom plane. Notice that closer plane does shrinkwrap because its top (Target) plane is bigger.
If you move the bottom (Auxiliary) plane left and right, you will also notice that far plane will eventually start shrinkwrapping too when bottom plane moves closer to its center.
shrinkwrap_bug_1.blend

**System Information** Intel Core i7, 8 Gb RAM, AMD Radeon HD 7700 Windows 7 x64 **Blender Version** Broken: 2.77 11b0874 Worked: 2.77a abf6f08 **Short description of error** I can confirm there is a problem in latest builds and I have also found a couple of strange things: - If you enter Edit Mode on the bottom plane, shrinkwrap will start working. - It looks like that BOTTOM (Auxiliary) plane uses TOP (Target) plane’s dimensions as dimensions for shrinkwrapping! Changing the size of the top (Target) plane’s mesh seems to affect the bottom (Auxiliary) plane’s snapping for some reason. You can take a look at my version of the test file, it's practically the same thing with planes, but some planes are changed to illustrate the issue I've found: - If you open my file in 2.77a, both small planes will shrinkwrap to both large planes. - If you open my file in latest build of 2.77, only closer one of the small planes will shrinkwrap to the bottom plane. Notice that closer plane does shrinkwrap because its top (Target) plane is bigger. - If you move the bottom (Auxiliary) plane left and right, you will also notice that far plane will eventually start shrinkwrapping too when bottom plane moves closer to its center. [shrinkwrap_bug_1.blend](https://archive.blender.org/developer/F315304/shrinkwrap_bug_1.blend)

Campbell Barton commented

2016-05-31 06:10:03 +02:00

Caused by 0b5a0d8412

Caused by 0b5a0d8412

blender-admin commented

2016-05-31 06:37:06 +02:00

This issue was referenced by 3ed5da0479

This issue was referenced by 3ed5da04791ec9568ae4d56ad8722f309431a1c5

Campbell Barton commented

2016-05-31 06:37:43 +02:00

Changed status from 'Open' to: 'Resolved'

Campbell Barton closed this issue