Array modifier does not respect duplivert setting in cycles #32154

Closed
opened 2012-07-20 22:32:45 +02:00 by Thomas Beck · 7 comments
Member

%%%Hi Brecht,

Dupliverts are essential for motion graphics! And as cycles is reaching more and more a professional level, it needs the ability to handle dupliverts right:

When I duplivert an object and clone it with an array modifier, I assume that the dupliverts are distributed along the given axis. But they remain on the original object. See the supplied blend for evidence.

Greetings Thomas

R49089, i7 8gb nvidia 560ti oc%%%

%%%Hi Brecht, Dupliverts are essential for motion graphics! And as cycles is reaching more and more a professional level, it needs the ability to handle dupliverts right: When I duplivert an object and clone it with an array modifier, I assume that the dupliverts are distributed along the given axis. But they remain on the original object. See the supplied blend for evidence. Greetings Thomas R49089, i7 8gb nvidia 560ti oc%%%
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

%%%As I further tested it, it seems that putting a modifier on the dupliverted object does the thing I want... it's not really intuitive but it works...could you clarify this behaviour or is this a bug?! Greetings..%%%

%%%As I further tested it, it seems that putting a modifier on the dupliverted object does the thing I want... it's not really intuitive but it works...could you clarify this behaviour or is this a bug?! Greetings..%%%
Member

%%%Indeed I would agree that this doesn't seem like the intended behavior, but I am pretty sure that it has nothing to do with cycles. It seems like for whatever reason, the array modifier just deals with the actual meshes instead of any child objects of the mesh, which I think the spheres you have might actually be considered to be part of, in a technical sense.

I suppose you could also just apply the modifier and let the dupliverts distribute across the new mesh the way you want too.%%%

%%%Indeed I would agree that this doesn't seem like the intended behavior, but I am pretty sure that it has nothing to do with cycles. It seems like for whatever reason, the array modifier just deals with the actual meshes instead of any child objects of the mesh, which I think the spheres you have might actually be considered to be part of, in a technical sense. I suppose you could also just apply the modifier and let the dupliverts distribute across the new mesh the way you want too.%%%
Member

%%%Also, you may also want to use the "Make dupliverts real" option and then join the meshes to the cube. (Sorry, almost forgot that trick existed!)%%%

%%%Also, you may also want to use the "Make dupliverts real" option and then join the meshes to the cube. (Sorry, almost forgot that trick existed!)%%%
Author
Member

%%%Hi Dan,

I know that option already...but it's no option in this case...you loose all your "dynamic" behaviour (having modifiers themself) when you're making the duplis real. You know, in motion graphics, all has to be dynamic and changable anytime :) So unfortunately I can't make the objects real :(%%%

%%%Hi Dan, I know that option already...but it's no option in this case...you loose all your "dynamic" behaviour (having modifiers themself) when you're making the duplis real. You know, in motion graphics, all has to be dynamic and changable anytime :) So unfortunately I can't make the objects real :(%%%
Member

%%%Combining dupliverts with modifiers is not a guaranteed feature in Blender. You are using two incompatible methods here.

I tried the test file, and the result in Cycles are similar as in Internal, and similar as it draws in the viewport. It's not clear what you consider a bug here. (Expecting the duplivert and array to work together is not a bug ;)%%%

%%%Combining dupliverts with modifiers is not a guaranteed feature in Blender. You are using two incompatible methods here. I tried the test file, and the result in Cycles are similar as in Internal, and similar as it draws in the viewport. It's not clear what you consider a bug here. (Expecting the duplivert and array to work together is not a bug ;)%%%
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
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
3 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#32154
No description provided.