Applying a boolean modifier can delete UV maps or add empty ones #60076

Closed
opened 2019-01-02 16:40:56 +01:00 by Richard Kennaway · 2 comments

System Information
Operating system: OSX Mojave (10.14.2)
Graphics card: NVIDIA GeForce GTX 780M 4096 MB

Blender Version
Broken: 2.80 Beta, 4dd0a90f42, 2019-01-01
Broken (but differently) 2.79, 111179beb0, 2018-12-27, and the 2.79b release.

Short description of error

Applying a boolean modifier can cause a UV map to be deleted in 2.80, or an extra one to be added in 2.79, depending on whether one of the arguments has a UV map.

When I use a boolean difference operator to transform a shape A into A-B:

If A has a UV map and B does not, then in 2.80, A-B has no UV map. In 2.79 it works as expected: A-B has a single UV map that maps faces descending from A in the natural way and faces descending from B to (0,0).

If A and B both have UV maps then in 2.80 this works as expected: the new object has a single UV map computed in the natural way from those of A and B. In 2.79, the result also has the expected UV map, but it acquires a second UV map that maps every face to (0,0).

Exact steps for others to reproduce the error

The attached .blend files illustrate this, one for 2.79 and one for 2.80. Both files contain the same objects. The colours are for identification of parts.

Red: Cube has UV map, plane does not. The cube has a boolean difference modifier with the plane.
Green: As Red, after applying modifier. In 2.80, the cube has no UV map. In 2.79, it has the expected UV map.

Yellow: Both have UV maps. The cube has a boolean difference modifier with the plane.
Violet: As Yellow, after applying the modifier. In 2.80 and 2.79 it has the expected UV map, but in 2.79 it has an extra zero UV map.

boolUVbug279b.blend

boolUVbug280.blend

**System Information** Operating system: OSX Mojave (10.14.2) Graphics card: NVIDIA GeForce GTX 780M 4096 MB **Blender Version** Broken: 2.80 Beta, 4dd0a90f4213, 2019-01-01 Broken (but differently) 2.79, 111179beb0b1, 2018-12-27, and the 2.79b release. **Short description of error** Applying a boolean modifier can cause a UV map to be deleted in 2.80, or an extra one to be added in 2.79, depending on whether one of the arguments has a UV map. When I use a boolean difference operator to transform a shape A into A-B: If A has a UV map and B does not, then in 2.80, A-B has no UV map. In 2.79 it works as expected: A-B has a single UV map that maps faces descending from A in the natural way and faces descending from B to (0,0). If A and B both have UV maps then in 2.80 this works as expected: the new object has a single UV map computed in the natural way from those of A and B. In 2.79, the result also has the expected UV map, but it acquires a second UV map that maps every face to (0,0). **Exact steps for others to reproduce the error** The attached .blend files illustrate this, one for 2.79 and one for 2.80. Both files contain the same objects. The colours are for identification of parts. Red: Cube has UV map, plane does not. The cube has a boolean difference modifier with the plane. Green: As Red, after applying modifier. In 2.80, the cube has no UV map. In 2.79, it has the expected UV map. Yellow: Both have UV maps. The cube has a boolean difference modifier with the plane. Violet: As Yellow, after applying the modifier. In 2.80 and 2.79 it has the expected UV map, but in 2.79 it has an extra zero UV map. [boolUVbug279b.blend](https://archive.blender.org/developer/F6151603/boolUVbug279b.blend) [boolUVbug280.blend](https://archive.blender.org/developer/F6151605/boolUVbug280.blend)

Added subscriber: @RichardKennaway

Added subscriber: @RichardKennaway

Closed as duplicate of #59304

Closed as duplicate of #59304
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#60076
No description provided.