Generated Texture Coordinate works not as expected when used with curve and boolean modifier #53622

Closed
opened 2017-12-23 19:58:04 +01:00 by Marc Zbinden · 4 comments

System Information
Windows 10
Geforce GTX980

Blender Version
stable release: 2.79 5bd8ac9
experimental: 2.79 5e28b71

Short description of error
Generated texture coordinate changes when using boolean modifier

Exact steps for others to reproduce the error
I used the Curve modifier on meshes for building Brickwalls.
I added Textures with the Bricktexture with the generated texture coordinate in Cycles.
This worked until I used the boolean modifier to cut holes for windows and doors.
In the File you can see that the texturecoordinate changes when the boolean mesh touches the wall.
Even if it's only partly.
I'm not sure if this is an error, but I don't know how I could do this otherwise.
I tried to apply the modifiers but then the texturecoordinate also looses the shape of the curve.
It's otherwise possible to use uv coordinates instead but then the texturespace is limited by the size of the mesh.
Curve boolean generated Texture.blend

**System Information** Windows 10 Geforce GTX980 **Blender Version** stable release: 2.79 5bd8ac9 experimental: 2.79 5e28b71 **Short description of error** Generated texture coordinate changes when using boolean modifier **Exact steps for others to reproduce the error** I used the Curve modifier on meshes for building Brickwalls. I added Textures with the Bricktexture with the generated texture coordinate in Cycles. This worked until I used the boolean modifier to cut holes for windows and doors. In the File you can see that the texturecoordinate changes when the boolean mesh touches the wall. Even if it's only partly. I'm not sure if this is an error, but I don't know how I could do this otherwise. I tried to apply the modifiers but then the texturecoordinate also looses the shape of the curve. It's otherwise possible to use uv coordinates instead but then the texturespace is limited by the size of the mesh. [Curve boolean generated Texture.blend](https://archive.blender.org/developer/F1505771/Curve_boolean_generated_Texture.blend)
Author

Added subscriber: @MarcZbinden

Added subscriber: @MarcZbinden
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Philipp Oeser self-assigned this 2018-01-04 20:08:31 +01:00
Member

This is not only a problem of the curve or boolean modifiers specifically.
(It could also be a bend with a decimate afterwards e.g)
So afaik this is due to a constructive/generating modifier after a deforming modifier

when you only have a deform modifier it will still use to coordinates from the original space (thats why the bricks 'stick' nicely)
once a constructive modifier comes into play afterwards we have a new boundingbox/space and thats the basis now.
(Having a hard time finding the right words atm. but to sum it up: I think this is expected behaviour and I wouldnt consider this a bug)

However you can still kind of make your case possible [a lot less convenient though] by moving the boolean above the curve modifier [its less intuitive to place the boolean object right then...]
This way all geometry modification (array/boolean) takes place in a lined up space, and the deforming comes last
T53622_workaround.blend

This is not only a problem of the curve or boolean modifiers specifically. (It could also be a bend with a decimate afterwards e.g) So afaik this is due to a constructive/generating modifier after a deforming modifier when you only have a deform modifier it will still use to coordinates from the original space (thats why the bricks 'stick' nicely) once a constructive modifier comes into play afterwards we have a new boundingbox/space and thats the basis now. (Having a hard time finding the right words atm. but to sum it up: I think this is expected behaviour and I wouldnt consider this a bug) However you can still kind of make your case possible [a lot less convenient though] by moving the boolean above the curve modifier [its less intuitive to place the boolean object right then...] This way all geometry modification (array/boolean) takes place in a lined up space, and the deforming comes last [T53622_workaround.blend](https://archive.blender.org/developer/F1700301/T53622_workaround.blend)
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#53622
No description provided.