Particles -> Physics none -> Hit render -> Particles flying around. #54445

Closed
opened 2018-03-28 10:02:49 +02:00 by Minne Danhieux · 15 comments

System Information
WIN7 64b GTX 970

Blender Version
2.79b and a

Short description of error
I use a grid type geotry for making grass. There is a particle system om the this geometry with physics set to none. Everything is ok and fine until i hit render.
For some reason the particles move a little bit visualy in the viewport when blender prepares for rendering. This results in exploding particles. I can not really reproduce the error for the moment in a test scene. But this is really frustrating.

Exact steps for others to reproduce the error
Unfortunatly not yet found reproduction. I keep testing in a meanwhile.29665055_961987153977532_1458597520929934552_o.jpg

**System Information** WIN7 64b GTX 970 **Blender Version** 2.79b and a **Short description of error** I use a grid type geotry for making grass. There is a particle system om the this geometry with physics set to none. Everything is ok and fine until i hit render. For some reason the particles move a little bit visualy in the viewport when blender prepares for rendering. This results in exploding particles. I can not really reproduce the error for the moment in a test scene. But this is really frustrating. **Exact steps for others to reproduce the error** Unfortunatly not yet found reproduction. I keep testing in a meanwhile.![29665055_961987153977532_1458597520929934552_o.jpg](https://archive.blender.org/developer/F2522489/29665055_961987153977532_1458597520929934552_o.jpg)
Author

Added subscriber: @MinneDanhieux

Added subscriber: @MinneDanhieux
Author

I downloaded 2.79 zip and that seems to work fine for now. So the problem started in the 2.79a release.

I downloaded 2.79 zip and that seems to work fine for now. So the problem started in the 2.79a release.
Author

To fast conclusion. It still is exploding.

To fast conclusion. It still is exploding.
Author

I found some reproduction posibilities.. i will make a video and a scene with the bug later on.

I found some reproduction posibilities.. i will make a video and a scene with the bug later on.
Author

This is a file that screws up "physics > none" in the particle settings. In the 2 images you can see what is the problem.
Sometimes the grass is good, but sometimes the grass explodes when i hit F12. Random stuff going on. It shouldn't move at all nice and smooth flat.

setup_V007.blend
image.png

image.png

This is a file that screws up "physics > none" in the particle settings. In the 2 images you can see what is the problem. Sometimes the grass is good, but sometimes the grass explodes when i hit F12. Random stuff going on. It shouldn't move at all nice and smooth flat. [setup_V007.blend](https://archive.blender.org/developer/F2584308/setup_V007.blend) ![image.png](https://archive.blender.org/developer/F2584330/image.png) ![image.png](https://archive.blender.org/developer/F2584335/image.png)
Author

Anybody? :)

Anybody? :)
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Please dont change priority yourself.
Having a look now...

Please dont change priority yourself. Having a look now...
Member

Unfortunately I havent been able to reproduce this here.
You were talking about some reproduction posibilities, have you found something that makes a difference between "good" and "exploding"?

Unfortunately I havent been able to reproduce this here. You were talking about some *reproduction posibilities*, have you found something that makes a difference between "good" and "exploding"?
Author

Hi Philipp,

the problem with this bug is that it is random. Did you hit F12 a couple of times?
Sometimes it happens, sometimes it doesn't. It should never happen when physics is off.
I'm spending 1 hour a day testing stuff out. But the problem seems to be there hidden to strike most of the time when i think i fixt or found the problem.

So Everybody testing this scene. Hit F12 on frame 2. wait and see if the grass that is rendered is nice and clean. The moment you start to see holes in de ground stuff wil also be flying around.
The next time you hit it, it could very well be normal again.

I hope this can be solved sooner or later. I was hoping that some kind of setting would fix it, but the random nature of the problem makes it unlikely.

Thx for anybody testing and getting the same shit. I had 1 person on the blender group on facebook that also has this problem.

Gr,

Minne

Hi Philipp, the problem with this bug is that it is random. Did you hit F12 a couple of times? Sometimes it happens, sometimes it doesn't. It should never happen when physics is off. I'm spending 1 hour a day testing stuff out. But the problem seems to be there hidden to strike most of the time when i think i fixt or found the problem. So Everybody testing this scene. Hit F12 on frame 2. wait and see if the grass that is rendered is nice and clean. The moment you start to see holes in de ground stuff wil also be flying around. The next time you hit it, it could very well be normal again. I hope this can be solved sooner or later. I was hoping that some kind of setting would fix it, but the random nature of the problem makes it unlikely. Thx for anybody testing and getting the same shit. I had 1 person on the blender group on facebook that also has this problem. Gr, Minne
Author

I downloaded the file again just to be sure. This is what happend the first time i hit F12. Explosion, but look, the physics is set to none! :)

image.png

I downloaded the file again just to be sure. This is what happend the first time i hit F12. Explosion, but look, the physics is set to none! :) ![image.png](https://archive.blender.org/developer/F2604724/image.png)
Author

Ok, news here.
I deleted blender and every trace. I made a imaculate new installation of blender and its gone!
So the problem isn't there in default installation.

I wil try to figure out wich addon or change causes the bug to ocure.

Hopfully an update soon... i keep testing. :)

Ok, news here. I deleted blender and every trace. I made a imaculate new installation of blender and its gone! So the problem isn't there in default installation. I wil try to figure out wich addon or change causes the bug to ocure. Hopfully an update soon... i keep testing. :)
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Philipp Oeser self-assigned this 2018-04-09 12:29:04 +02:00
Member

Glad to hear this, and thx for your testing!
I will close this then. You can still keep us posted with updates or reopen if you found a bug (e.g. with bundled addons) causing this. [I'm also interested in what might have caused this]

Glad to hear this, and thx for your testing! I will close this then. You can still keep us posted with updates or reopen if you found a bug (e.g. with bundled addons) causing this. [I'm also interested in what might have caused this]
Author

Ok, I think I found the croocked handle.

default 'Window Draw Method' is 'Automic'.
For some reason i remember testing this leaving this on 'Full'.

When setting on 'Full' in default config the scene goes bananas.
When switching 'Full' to 'Automatic' in my old config the scene goes to normal.

So 99% sure this is causing it. But i need confirmation:

Reproduce instructions: Download the scene previously found in this threat. Open up preferences set the window draw method to full. Test F12 couple of times switch to frame 1-2. If it is croocked it will show after some tries.
Good Luck!

I will never leave this on Full again because it is not recommended either to do so. :)

image.png

Ok, I think I found the croocked handle. default 'Window Draw Method' is 'Automic'. For some reason i remember testing this leaving this on 'Full'. When setting on 'Full' in default config the scene goes bananas. When switching 'Full' to 'Automatic' in my old config the scene goes to normal. So 99% sure this is causing it. But i need confirmation: Reproduce instructions: Download the scene previously found in this threat. Open up preferences set the window draw method to full. Test F12 couple of times switch to frame 1-2. If it is croocked it will show after some tries. Good Luck! I will never leave this on Full again because it is not recommended either to do so. :) ![image.png](https://archive.blender.org/developer/F2642705/image.png)
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#54445
No description provided.