after applying a boolean mod, faces are initialized with a facemap index of 0 instead of -1 #65357

New Issue

MACHIN3 · 2019-05-31T17:32:50+02:00

MACHIN3 commented

2019-05-31 17:32:50 +02:00

System Information
Operating system: Linux-4.13.10-041310-generic-x86_64-with-debian-stretch-sid 64 Bits
Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.67

Blender Version
Broken: version: 2.80 (sub 73), branch: blender2.7, commit date: 2019-05-30 22:28, hash: fc336f973d

Short description of error
I have an object, that has a facemap (and faces assgined to it). Alternatively I have on object and have run bm.faces.layers.face_map.verify() on its mesh (even without the object having any face map).
If I then add a boolean mod to either of them, and use a second, new object, where face maps were never touched, and if I then apply the boolean mod, the faces of the new object will have a face map index of 0 on the new, booleaned mesh.
This then leads to the new faces being associated with a facemap they haven't been a part of before. The face map indices of the new faces should stay at -1, as they were before the boolean.

video demo

faces_after_boolean_are_initialized_with_index_0_instead_of_-1.blend

Exact steps for others to reproduce the error

open the blend file above
apply the boolean mod on the cube to the right
- go into edit mode and select the face map
- the new faces are part of the pre-existing face map, despite thefact that this face map did not exist on the (second) object and the faces haven't ben assigned to any face map
apply the boolean mod on the cube to the left
- go into edti mode, create a new face map and select its faces
- the new faces are part of the new face map, without having been assigned to it

**System Information** Operating system: Linux-4.13.10-041310-generic-x86_64-with-debian-stretch-sid 64 Bits Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.67 **Blender Version** Broken: version: 2.80 (sub 73), branch: blender2.7, commit date: 2019-05-30 22:28, hash: `fc336f973d` **Short description of error** I have an object, that has a facemap (and faces assgined to it). Alternatively I have on object and have run `bm.faces.layers.face_map.verify()` on its mesh (even without the object having any face map). If I then add a boolean mod to either of them, and use a second, new object, where face maps were never touched, and if I then apply the boolean mod, the faces of the new object will have a face map index of 0 on the new, booleaned mesh. This then leads to the new faces being associated with a facemap they haven't been a part of before. The face map indices of the new faces should stay at -1, as they were before the boolean. [video demo ](https://www.youtube.com/watch?v=0mk5lwoEMMk) [faces_after_boolean_are_initialized_with_index_0_instead_of_-1.blend](https://archive.blender.org/developer/F7081376/faces_after_boolean_are_initialized_with_index_0_instead_of_-1.blend) **Exact steps for others to reproduce the error** * open the blend file above * apply the boolean mod on the cube to the right * go into edit mode and select the face map * the new faces are part of the pre-existing face map, despite thefact that this face map did not exist on the (second) object and the faces haven't ben assigned to any face map * apply the boolean mod on the cube to the left * go into edti mode, create a new face map and select its faces * the new faces are part of the new face map, without having been assigned to it

MACHIN3 commented

2019-05-31 17:32:50 +02:00

Added subscriber: @MACHIN3

Ted Milker commented

2019-06-02 15:46:23 +02:00

Added subscriber: @Teds

Ted Milker commented

2019-06-02 15:46:23 +02:00

Confirmed, I get the same weird behaviour on Windows 10 64bit, Nvidia GeForce GTX 1080Ti, Blender 2.80 Beta Windows 64 bit Date: 2019-06-01 22:51 Hash: 079c7f918c

Confirmed, I get the same weird behaviour on Windows 10 64bit, Nvidia GeForce GTX 1080Ti, Blender 2.80 Beta Windows 64 bit Date: 2019-06-01 22:51 Hash: 079c7f918c81

Bohdan Lvov commented

2019-06-02 15:47:57 +02:00

Added subscriber: @ostapblender

Bohdan Lvov commented

2019-06-02 15:47:57 +02:00

Yup, exactly the same behavior in 079c7f918c on Windows

Yup, exactly the same behavior in 079c7f918c81 on Windows

Piotr commented

2019-06-02 16:13:31 +02:00

Added subscriber: @Pinnhead

Piotr commented

2019-06-02 16:13:31 +02:00

Confirmed. blender-2.80-079c7f918c81-win64. Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86

Andrei Nadin commented

2019-06-03 02:23:29 +02:00

Added subscriber: @AnadinX

Andrei Nadin commented

2019-06-03 02:23:29 +02:00

Confirmed on macOS, built with latest from lastnight
version: 2.80 (sub 74), branch: master, commit date: 2019-06-02 11:23, hash: 8d1666fc6d, type: Release

AMD Radeon Pro 560

Confirmed on macOS, built with latest from lastnight version: 2.80 (sub 74), branch: master, commit date: 2019-06-02 11:23, hash: 8d1666fc6de1, type: Release AMD Radeon Pro 560

Philipp Oeser commented

2019-06-03 14:02:07 +02:00

Added subscriber: @lichtwerk