Image as Plane cloth error #61640

Closed
opened 2019-02-17 19:03:49 +01:00 by Sergey · 19 comments

System Information
Operating system: Windows 10 64
Graphics card: Nvidia GTX1060Q

Blender Version
blender-2.80.0-git.0f135f80f271-windows64
Worked: (optional)

Short description of error
Image as Plane in cloth simulation generates distorted mesh while Self Collision is enabled

Exact steps for others to reproduce the error

  1. Import Image as Plane
  2. Subdivide
  3. Assign pinning vertexes group.
  4. Enable Cloth simulation for the Plane.
  5. Select pinning vertexes group for cloth
    ( simulation will run correctly)
  6. Enable Self Collision.
  7. Start simulation.
 It will generate heavily distorted mesh or crash.
 A plane created from Add Mesh works correctly. 
**System Information** Operating system: Windows 10 64 Graphics card: Nvidia GTX1060Q **Blender Version** blender-2.80.0-git.0f135f80f271-windows64 Worked: (optional) **Short description of error** Image as Plane in cloth simulation generates distorted mesh while Self Collision is enabled **Exact steps for others to reproduce the error** 1. Import Image as Plane 2. Subdivide 3. Assign pinning vertexes group. 4. Enable Cloth simulation for the Plane. 5. Select pinning vertexes group for cloth ( simulation will run correctly) 5. Enable Self Collision. 6. Start simulation. ``` It will generate heavily distorted mesh or crash. ``` ``` A plane created from Add Mesh works correctly.
Author

Added subscriber: @iKeyborg

Added subscriber: @iKeyborg

Added subscriber: @StephenSwaney

Added subscriber: @StephenSwaney

Got a .blend for us?

Got a .blend for us?
Author

IMAGE_PLANE_CLOTH.blend

Please open and run simulation

[IMAGE_PLANE_CLOTH.blend](https://archive.blender.org/developer/F6643825/IMAGE_PLANE_CLOTH.blend) Please open and run simulation
Author

Please disable Self Collision, It will work.

Please disable Self Collision, It will work.
Member

Added subscriber: @nacioss

Added subscriber: @nacioss
Member

Yeah, it does get weird results in your blend.
However, i tried with the latest build of today's 2019-02-18 and it seems to work properly now:
Screenshot.jpg

Yeah, it does get weird results in your blend. However, i tried with the latest build of today's 2019-02-18 and it seems to work properly now: ![Screenshot.jpg](https://archive.blender.org/developer/F6648808/Screenshot.jpg)
Author

I have downloaded blender-2.80.0-git.7d792976e100-windows64 (2019-02-18)

It still doesn't work.

image.png
Please don't disable Self Collision and click play.

I have downloaded blender-2.80.0-git.7d792976e100-windows64 (2019-02-18) It still doesn't work. ![image.png](https://archive.blender.org/developer/F6649297/image.png) Please don't disable Self Collision and click play.

Added subscriber: @ZedDB

Added subscriber: @ZedDB

If I open that fine and play the animation, I can see the same problem.

However, if I disable self collision AND then re-enable it works.

Does this happen for you too?
If it solves it for you, can you still make this happen when recreating the scene?
I suspect this is something that has been fixed but blend files that were saved when this bug was in is still broken until you toggle the settings.

If I open that fine and play the animation, I can see the same problem. However, if I disable self collision AND then re-enable it works. Does this happen for you too? If it solves it for you, can you still make this happen when recreating the scene? I suspect this is something that has been fixed but blend files that were saved when this bug was in is still broken until you toggle the settings.
Author

Unfortunately, It doesn't work even after toggling self collision.
I created a cloth model from scratch in 2.18.2019 Blender. I see the same problem. Can it be Preference or Registry corruption?

Unfortunately, It doesn't work even after toggling self collision. I created a cloth model from scratch in 2.18.2019 Blender. I see the same problem. Can it be Preference or Registry corruption?

If Load Factory Settings and save then Save Startup file and save user preferences. Can you still reproduce this?

If `Load Factory Settings` and save then `Save Startup file` and save user preferences. Can you still reproduce this?
Author

I did everything you suggested with today's build (02.19.2019).
I got a new piece of information. If I create a plane from image and subdivide it to 20x20 mesh, it works. If I divide the image as plane in to 50x50 mesh it doesn't work. If I subdivide 20x20 mesh once it doesn't work as well.

I did everything you suggested with today's build (02.19.2019). I got a new piece of information. If I create a plane from image and subdivide it to 20x20 mesh, it works. If I divide the image as plane in to 50x50 mesh it doesn't work. If I subdivide 20x20 mesh once it doesn't work as well.

Does it help if you increase the number of quality steps of the simulation to 20 or so?

Does it help if you increase the number of quality steps of the simulation to 20 or so?
Author

Quality steps don't help. Max working subdivision factor is 25x25.
26x26 doesn't nork
I installed 2/20/2019 version on a different old laptop never used for blender.
I does same thing. Do you import image as plane? What is difference between plane from Add Mesh and imported image?

Quality steps don't help. Max working subdivision factor is 25x25. 26x26 doesn't nork I installed 2/20/2019 version on a different old laptop never used for blender. I does same thing. Do you import image as plane? What is difference between plane from Add Mesh and imported image?

I don't think this is an add plane issue. It is just a general stability issue with simulations.

If you add a normal plane it is 2x2meters. The import as plane defaults to 1m
The add image as plane makes the imported plane rectangular (unless the image size is square).

What happens here is that the solver for the cloth sim has a hard time to find a solution to the simulation.
This case it hard because of the smaller size and that you have pinned all edge verts on one side.
Additionally the plane is collapsing in on itself.

In the example you attached, the distance between the verts on the flag horizonatally is ~0.02m. In the self collision settings, you can see that the amount of distance you want to keep between the self colliding verts are 0.015m. As you can guess this leaves very little space for the flag to have the verts move. So you can set it to 0.001m instead and it should be better.

Can you confirm that changing the value to 0.001m works for you?

I don't think this is an add plane issue. It is just a general stability issue with simulations. If you add a normal plane it is 2x2meters. The import as plane defaults to 1m The add image as plane makes the imported plane rectangular (unless the image size is square). What happens here is that the solver for the cloth sim has a hard time to find a solution to the simulation. This case it hard because of the smaller size and that you have pinned all edge verts on one side. Additionally the plane is collapsing in on itself. In the example you attached, the distance between the verts on the flag horizonatally is ~0.02m. In the self collision settings, you can see that the amount of distance you want to keep between the self colliding verts are 0.015m. As you can guess this leaves very little space for the flag to have the verts move. So you can set it to 0.001m instead and it should be better. Can you confirm that changing the value to 0.001m works for you?
Author

Sebastian,

    Thank you.

Now it works like a charm.

    Sorry, I wasted your time. I did not find a good explanation for all cloth parameters and they are little bit different from 2.79.

I think little diagnostic or error message if self-collision distance is bigger than minimum mesh cell would be helpful to avoid some simulation errors.
Looks like only self-collision distance can prevent from self-penetration: not too big to keep simulation successful and not too small to prevent self- penetration. Is there another way to prevent self-penetration?

Sergey

Sebastian, ``` Thank you. ``` Now it works like a charm. ``` Sorry, I wasted your time. I did not find a good explanation for all cloth parameters and they are little bit different from 2.79. ``` I think little diagnostic or error message if self-collision distance is bigger than minimum mesh cell would be helpful to avoid some simulation errors. Looks like only self-collision distance can prevent from self-penetration: not too big to keep simulation successful and not too small to prevent self- penetration. Is there another way to prevent self-penetration? Sergey

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sebastian Parborg self-assigned this 2019-02-22 10:56:51 +01:00

Self-collision is the only way to prevent it falling through itself in this case.

There could perhaps be some kind of self diagnostics as you said, however that is move of a feature request (so not something for this bug tracker).

There have been talks about replacing the cloth and particle system in the future. So these areas are currently not worked on that much (as they will probably be replaced).

Self-collision is the only way to prevent it falling through itself in this case. There could perhaps be some kind of self diagnostics as you said, however that is move of a feature request (so not something for this bug tracker). There have been talks about replacing the cloth and particle system in the future. So these areas are currently not worked on that much (as they will probably be replaced).
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
4 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#61640
No description provided.