collection instance rotates 90 degrees automatically when being instantiated by another object with mirror modifier #77575

Open
opened 2020-06-07 19:43:10 +02:00 by zyc17 · 20 comments

System Information
Operating system: mac os 10.14.6
Graphics card: Intel Iris Plus Graphics 655

Blender Version
Broken: version: 2.82a, 2.30.0 release, 2.90 (sub 3), branch: master, commit date: 2020-05-24 21:18, hash: 5db2d9c82b
Worked: Unsure.

Short description of error
as shown in the following screenshot, to use modifiers on a collection instance I parent the collection instance to a plane and change the instancing of the plane to faces, so that the collection instance will follow what modifiers will affect on the plane, but when using the mirror modifier with mirror object set to an empty at the center, the collection instance on the other side rotates 90 degrees on z axis automatically, which is not expected
屏幕快照 2020-06-08 上午1.30.46.png
Exact steps for others to reproduce the error
open the attached .blend file and you'll see the problem
collection instance problem.blend

Steps if you want to recreate from scratch:

  1. Create a new collection, I will call it Suzzane.
  2. In the collection Suzzane create a Suzzane (Monkey Head) then disable the collection in the outliner.
  3. In the new collection, create an instance of the collection Suzzane by pressing Shift+A -> Collection Instance -> Suzzane. From now onwards, we will be working in this new collection.
  4. Create a plane. Select the instanced Suzzane then the plane and parent the Suzzane to the plane with Ctrl+P -> Object
  5. In the outliner, select the instanced Suzzane and hid it with the little eye icon.
  6. Select the plane and in the properties editor in the Object tab select Instancing -> Faces.
  7. Give the plane a mirror modifier and notice how to newly instanced Suzzane is rotated 90 degrees rather than mirrored.
**System Information** Operating system: mac os 10.14.6 Graphics card: Intel Iris Plus Graphics 655 **Blender Version** Broken: version: 2.82a, 2.30.0 release, 2.90 (sub 3), branch: master, commit date: 2020-05-24 21:18, hash: `5db2d9c82b` Worked: Unsure. **Short description of error** as shown in the following screenshot, to use modifiers on a collection instance I parent the collection instance to a plane and change the instancing of the plane to faces, so that the collection instance will follow what modifiers will affect on the plane, but when using the mirror modifier with mirror object set to an empty at the center, the collection instance on the other side rotates 90 degrees on z axis automatically, which is not expected ![屏幕快照 2020-06-08 上午1.30.46.png](https://archive.blender.org/developer/F8589456/屏幕快照_2020-06-08_上午1.30.46.png) **Exact steps for others to reproduce the error** open the attached .blend file and you'll see the problem [collection instance problem.blend](https://archive.blender.org/developer/F8597871/collection_instance_problem.blend) Steps if you want to recreate from scratch: 1. Create a new collection, I will call it `Suzzane`. 2. In the collection `Suzzane` create a Suzzane (Monkey Head) then disable the collection in the outliner. 3. In the new collection, create an instance of the collection `Suzzane` by pressing `Shift+A -> Collection Instance -> Suzzane`. From now onwards, we will be working in this new collection. 4. Create a plane. Select the instanced `Suzzane` then the plane and parent the `Suzzane` to the plane with `Ctrl+P -> Object` 5. In the outliner, select the instanced `Suzzane` and hid it with the little eye icon. 6. Select the plane and in the properties editor in the `Object` tab select `Instancing -> Faces`. 7. Give the plane a mirror modifier and notice how to newly instanced `Suzzane` is rotated 90 degrees rather than mirrored.
Author

Added subscriber: @389150029

Added subscriber: @389150029

#88708 was marked as duplicate of this issue

#88708 was marked as duplicate of this issue
Member

Added subscriber: @Alaska

Added subscriber: @Alaska
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

open the attached .blend file and you'll see the problem

Are you able to upload the .blend file or provide the steps required to reproduce the issue?

I'm having difficultly trying to reproduce this issue in my own files.

> open the attached .blend file and you'll see the problem Are you able to upload the .blend file or provide the steps required to reproduce the issue? I'm having difficultly trying to reproduce this issue in my own files.
Author

In #77575#948123, @Alaska wrote:

open the attached .blend file and you'll see the problem

Are you able to upload the .blend file or provide the steps required to reproduce the issue?

I'm having difficultly trying to reproduce this issue in my own files.

sorry, I accidentally deleted the file when I edit the task and I didn't notice, the file is now uploaded

> In #77575#948123, @Alaska wrote: >> open the attached .blend file and you'll see the problem > Are you able to upload the .blend file or provide the steps required to reproduce the issue? > > I'm having difficultly trying to reproduce this issue in my own files. sorry, I accidentally deleted the file when I edit the task and I didn't notice, the file is now uploaded
Member

Changed status from 'Needs User Info' to: 'Confirmed'

Changed status from 'Needs User Info' to: 'Confirmed'
Member

Can confirm. Seems to also affect Blender 2.83 and 2.82.

Will add some steps to the original task just in case someone wants to recreate this from scratch.

Can confirm. Seems to also affect Blender 2.83 and 2.82. Will add some steps to the original task just in case someone wants to recreate this from scratch.

Added subscriber: @Jamumamu

Added subscriber: @Jamumamu

I encountered this same problem today and did a little investigation. It appears this is a side-effect of how face instancing works:

When calculating the basis for the instance it takes the Z axis to be the face normal and the X axis to point in the direction of the first edge of the polygon. Mirroring a polygon requires its vertex order to be reversed for the normal to be consistent, which means X will now point in the direction of the last edge. For a quad, this results in a 90 degree rotation.

Here's an illustration of the problem with a pentagon: only the two indicated vertices affect the orientation of the axis marker.

image.png

To solve this, Blender would need to either:

  • rotate the vertices by one spot any time it reverses the vertex order; i.e. [0,1,2,3] would become [1,0,3,2] (instead of [0,3,2,1]), or
  • change how the coordinate space is calculated (and probably offer options to select how to decide the X axis)

Hope this helps.

I encountered this same problem today and did a little investigation. It appears this is a side-effect of how face instancing works: When calculating the basis for the instance it takes the Z axis to be the face normal and the X axis to point in the direction of the first edge of the polygon. Mirroring a polygon requires its vertex order to be reversed for the normal to be consistent, which means X will now point in the direction of the last edge. For a quad, this results in a 90 degree rotation. Here's an illustration of the problem with a pentagon: only the two indicated vertices affect the orientation of the axis marker. ![image.png](https://archive.blender.org/developer/F8737095/image.png) To solve this, Blender would need to either: - rotate the vertices by one spot any time it reverses the vertex order; i.e. [0,1,2,3] would become [1,0,3,2] (instead of [0,3,2,1]), or - change how the coordinate space is calculated (and probably offer options to select how to decide the X axis) Hope this helps.

This comment was removed by @Jamumamu

*This comment was removed by @Jamumamu*

Added subscriber: @tonpix

Added subscriber: @tonpix

What's the status of this bug? Is there some ETA for fix? I had the same issue as well, parented Collection Instance to Plane that had Array + Curve + Mirror. Instances on mirrored side had incorrect rotations sadly. I've attached an simplified .blend if it helps anyone
arrayIssue.blend
image.png

What's the status of this bug? Is there some ETA for fix? I had the same issue as well, parented Collection Instance to Plane that had Array + Curve + Mirror. Instances on mirrored side had incorrect rotations sadly. I've attached an simplified .blend if it helps anyone [arrayIssue.blend](https://archive.blender.org/developer/F8958783/arrayIssue.blend) ![image.png](https://archive.blender.org/developer/F8958761/image.png)

Added subscriber: @SUNGHOON-JEONG

Added subscriber: @SUNGHOON-JEONG

img.png
In my case, I was modeling an audio mixing console and found this problem.

With Faces Instancing, you only need to bind one object that array multiple planes to an armature.
It's very efficient because you only need one source mesh and one instance object.
A more complete modeling workflow would be possible if the opposite side flipped by the mirror modifier didn't rotate 90 degrees.

![img.png](https://archive.blender.org/developer/F9371002/img.png) In my case, I was modeling an audio mixing console and found this problem. With Faces Instancing, you only need to bind one object that array multiple planes to an armature. It's very efficient because you only need one source mesh and one instance object. A more complete modeling workflow would be possible if the opposite side flipped by the mirror modifier didn't rotate 90 degrees.

I created a potential fix for this some time ago but it never felt like the "right" solution. As far as I know this is (one of?) the only features in Blender that cares about vertex order. There aren't tools for viewing or reordering face vertices and based on the little bit of research I've done it seems that going down that path is discouraged (which I think I agree with).

In my opinion the real fix is improving the instancing toolset to provide some options for the instancing itself. This could better leverage features Blender already provides. For example:

  • Texture coordinates:
    • Use the tangent space of the UV map to define the local x/y space
    • z is calculated to be perpendicular (same as current behaviour)
    • Mirroring geometry will produce predicable results
    • UV tools can be used to adjust instancing

I don't know whether this fits better with the roadmap for instancing in general, however.

I created a potential fix for this some time ago but it never felt like the "right" solution. As far as I know this is (one of?) the only features in Blender that cares about vertex order. There aren't tools for viewing or reordering face vertices and based on the little bit of research I've done it seems that going down that path is discouraged (which I think I agree with). In my opinion the real fix is improving the instancing toolset to provide some options for the instancing itself. This could better leverage features Blender already provides. For example: - Texture coordinates: - Use the tangent space of the UV map to define the local x/y space - z is calculated to be perpendicular (same as current behaviour) - Mirroring geometry will produce predicable results - UV tools can be used to adjust instancing I don't know whether this fits better with the roadmap for instancing in general, however.
Member

Added subscribers: @Olliver, @lichtwerk

Added subscribers: @Olliver, @lichtwerk

Added subscriber: @asdf-1

Added subscriber: @asdf-1

this seems to be still happening, does anybody know of a workaround?

this seems to be still happening, does anybody know of a workaround?

I would suggest just using geometry nodes at this point since they give you a lot more control, at the expense of a more complex workflow.

I would suggest just using geometry nodes at this point since they give you a lot more control, at the expense of a more complex workflow.
Philipp Oeser removed the
Interest
Modeling
label 2023-02-09 15:29:14 +01:00
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
8 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#77575
No description provided.