v2.79 - Particle System "Current Cache to Bake" Not Work #53440

Open
opened 2017-12-01 07:45:58 +01:00 by SeawiseGiant · 6 comments

System Information
Windows 10 Enterprise 64-bit
Nvidia GeForce GTX1080Ti

Blender Version
Broken: v2.79(5bd8ac9)
Worked: (optional)

Short description of error
After previewed and cached the simulation, I cannot read back the cached files after hitting "Current Cache to Bake", instead I have to hit the "Bake" button to bake it all again(spend the same amount of time as the first time caching it). This way I can read back the baked files and use on any new objects. However It would be nice if "Current Cache to Bake" works so I can save some time on every simulation I have already cached.

Exact steps for others to reproduce the error

  1. Create a simple mesh(e.g. a plane).
  2. Add a new particle system.
  3. Set up a simple simulation(e.g. set normal velocity to 40 to simulate a fountain).
  4. Go to Cache tab, check Disk Cache, double click the cache and give a simple name(e.g. 001).
  5. Put timeline indicator to frame 0 and hit play, and then it will cache the simulation on a new folder next to your .blend file.
  6. After it is cached, hit "Current Cache to Bake".
  7. In the same Cache tab, check "external", locate the file path, and leave the cache file name as "001"(as you named it). Leave the Index Number to 0.
  8. It shall now indicate that "2 Points are Found!"(where you shall have 1000 points by default). If you hit play it will only play 2 out of the 1000 particles you have cached.
  9. Now return to Step 6, hit the "Bake" button instead of "Current Cache to Bake", the progress bar will show and it will take the same amount of time as your first time played(cached) the simulation.
  10. After baked, repeat Step 7, you should get "1000 Points Found!" now.
**System Information** Windows 10 Enterprise 64-bit Nvidia GeForce GTX1080Ti **Blender Version** Broken: v2.79(5bd8ac9) Worked: (optional) **Short description of error** After previewed and cached the simulation, I cannot read back the cached files after hitting "Current Cache to Bake", instead I have to hit the "Bake" button to bake it all again(spend the same amount of time as the first time caching it). This way I can read back the baked files and use on any new objects. However It would be nice if "Current Cache to Bake" works so I can save some time on every simulation I have already cached. **Exact steps for others to reproduce the error** 1. Create a simple mesh(e.g. a plane). 2. Add a new particle system. 3. Set up a simple simulation(e.g. set normal velocity to 40 to simulate a fountain). 4. Go to Cache tab, check Disk Cache, double click the cache and give a simple name(e.g. 001). 5. Put timeline indicator to frame 0 and hit play, and then it will cache the simulation on a new folder next to your .blend file. 6. After it is cached, hit "Current Cache to Bake". 7. In the same Cache tab, check "external", locate the file path, and leave the cache file name as "001"(as you named it). Leave the Index Number to 0. 8. It shall now indicate that "2 Points are Found!"(where you shall have 1000 points by default). If you hit play it will only play 2 out of the 1000 particles you have cached. 9. Now return to Step 6, hit the "Bake" button instead of "Current Cache to Bake", the progress bar will show and it will take the same amount of time as your first time played(cached) the simulation. 10. After baked, repeat Step 7, you should get "1000 Points Found!" now.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @zijianzhou

Added subscriber: @zijianzhou

Added subscriber: @zeauro

Added subscriber: @zeauro

Same on ubuntu 16.04 with 2.79 and master 1d33843

Same on ubuntu 16.04 with 2.79 and master 1d33843
Member

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Member

I can reproduce the issue, but it is unlikely that someone is going to work on this anytime soon. Therefore I'll reclassify this as a known issue.

I can reproduce the issue, but it is unlikely that someone is going to work on this anytime soon. Therefore I'll reclassify this as a known issue.
Philipp Oeser removed the
Interest
Nodes & Physics
label 2023-02-10 08:48:01 +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
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#53440
No description provided.