Collision between convex hull and triangle mesh causing slow fps in bge #46752

Closed
opened 2015-11-12 21:09:13 +01:00 by Ian · 11 comments

2.6b Build. Collisions between and triangle mesh physics objects are not respecting the collision radius values. This is leading to unpredictable physics simulations compared to 2.74 and severely decreased frame rates. Example file (attached) runs at 32 fps regardless of the a) emitter running b) the number of colliding objects added using spacebar. In 2.74 the added objects (via spacebar) make their way cleanly from top to bottom whilst bouncing off the included obstacles freely.

Tested on 2.74 release version and 2.75 official daily build from 10/11/2015 19:35 Hash 8c84a18
Machine: PC Windows 10 Pro. I7 with geforce GT 540M.tedhbug276.blend

2.6b Build. Collisions between and triangle mesh physics objects are not respecting the collision radius values. This is leading to unpredictable physics simulations compared to 2.74 and severely decreased frame rates. Example file (attached) runs at 32 fps regardless of the a) emitter running b) the number of colliding objects added using spacebar. In 2.74 the added objects (via spacebar) make their way cleanly from top to bottom whilst bouncing off the included obstacles freely. Tested on 2.74 release version and 2.75 official daily build from 10/11/2015 19:35 Hash 8c84a18 Machine: PC Windows 10 Pro. I7 with geforce GT 540M.[tedhbug276.blend](https://archive.blender.org/developer/F254198/tedhbug276.blend)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @iansmith

Added subscriber: @iansmith
Author

Edit to the above description. It was tested today on the latest 2.76 daily build and the problem still exists.

Edit to the above description. It was tested today on the latest 2.76 daily build and the problem still exists.

Added subscriber: @panzergame

Added subscriber: @panzergame

Confirm the bug

Confirm the bug

Added subscriber: @you.le

Added subscriber: @you.le

Hi, we can notice a performance/behavior change issue since this commit: https://developer.blender.org/rB909d3228b1d0254888d0c97d269e9ab2e315dba9

Hi, we can notice a performance/behavior change issue since this commit: https://developer.blender.org/rB909d3228b1d0254888d0c97d269e9ab2e315dba9

@iansmith: You can set margin to 0 to solve all of your issues.

Why ?
The commit 909d3228b1 introduced the support of margin for physique shapes based on triangles.

What's wrong ?

  1. Apparently Bullet create a big slow down when it must compute with a shape's margin.
  2. It's my fault, i forgot to set margin to 0 in the compatibility file when i commited this support, now is to late (commited in 2.75)...

Sorry for the disturbance.
If it works for you close the bug them.

@iansmith: You can set margin to 0 to solve all of your issues. `Why ?` The commit 909d3228b1 introduced the support of margin for physique shapes based on triangles. `What's wrong ?` 1) Apparently Bullet create a big slow down when it must compute with a shape's margin. 2) It's my fault, i forgot to set margin to 0 in the compatibility file when i commited this support, now is to late (commited in 2.75)... Sorry for the disturbance. If it works for you close the bug them.
Author

Hi, if I change the collision bounds of my static triangle mesh from '0.4' to '0.1' and reduce the dynamic objects convex hull 'Radius' from '1.0' to '0.1' (along with a collision bounds margin to '0.0') the original behaviour and performance is restored.
I'm happy to close it if this is an acceptable/intended change between versions rather than a bug. Is this the case?

Hi, if I change the collision bounds of my static triangle mesh from '0.4' to '0.1' and reduce the dynamic objects convex hull 'Radius' from '1.0' to '0.1' (along with a collision bounds margin to '0.0') the original behaviour and performance is restored. I'm happy to close it if this is an acceptable/intended change between versions rather than a bug. Is this the case?
Author

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Ian closed this issue 2015-11-15 22:26:36 +01:00
Ian self-assigned this 2015-11-15 22:26:36 +01:00
Author

Hi, as this can be worked around it will be closed.

Hi, as this can be worked around it will be closed.
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#46752
No description provided.