This is not a bug, but macOS limitation on voronoi texture.

Well, I got a clue : in my scene, I use Principled BSDF with Subsurface at 1.000. By turning down the Subsurface at 0, it works.

numpy has official releases on github nowdays, so no more sf weirdness current link at

For me, it still even worse with 385.69 NVidia drivers. Blender crashes instead of giving the error and a file that worked with previous version of drivers crashes now :(.

In T52572#461882, @Kayran Schmidt (Winnetou) wrote:

UPDATE:
Yesterday I installed the newest Nvidia Driver: 385.69
this seemed to fix the crash.
agent 327 renders fine on gpu even with larger tile sizes (though 256x256 lead to blender crashing completely -> other topic)

Was hopeful at reading this, but unfortunately it has made absolutely no difference for me. I even used DDU to reinstall from scratch to be safe, but I'm still having the exact same problem, so I guess you're lucky if you're not having the problem anymore!

New drivers has resolved my issue, using Intel HD Graphics 520.

UPDATE:
Yesterday I installed the newest Nvidia Driver: 385.69
this seemed to fix the crash.
agent 327 renders fine on gpu even with larger tile sizes (though 256x256 lead to blender crashing completely -> other topic)

ok thank you for the answer.In 3ds max edited objects can still be hided,but never mind,Blender does in different way.

By default, timeline playback range is synchronized with animation rendering range.
So minimal start can not be less than 1. You have to use an alternative range by clicking on Clock icon to be able to have a negative Start.
https://docs.blender.org/manual/en/dev/editors/timeline.html#header-controls

Well it seems Vertex Weight Proximity is not the problem, another modifiers like Subsurf or Triangulation placed before second Displace also break simulation

hi, it's quite surreal that this is already 1 year old.
currently i've rewritten the original patch for 2.79 after.
also written new edit modes 'w' key, v/e/f menus,
new space info header,
new file menu,
compact the node editor,
various ui tweaks
new patches to follow soon.
thanks.

This option only changes whether you can click and place the current frame indicator before frame 0.

I confirm that the toggling of the option duplicate all particle systems . User can cancel action and redo the operator to avoid that.
But it is clearly not the best way to have a choice between duplicate active and duplicate all.

No problem at all, I'd already converted the image sequence into a ProRes clip to finish off the shot, just wanted to report the bug 👍

More than a week passed without a reply.

My excitement got the best of me. Thankyou!

More than a week passed without a reply.

More than a week passed without a reply.

More than a week passed without a reply.

Ok, now i'm sad :(
Thanks for the info @colin (col-one) ! :)

It is OIIO thing. For now, you need now to use other format for the images, sorry for inconvenience caused.

I would love... but i think not ={

Hi all !

Yeah, now confirmed.
Textures are found, you can see them in textured/material viewport, but moment you hit cycles on, you can see nothing but pink panther's back.

Apologies, I was trying lots of different things (packing/unpacking) to figure out what specifically was causing the problem, so the .001 may be a bit of a red herring...

This is a known limitation of Motion Blur that modifiers altering geometry may have an undesired impact.
https://docs.blender.org/manual/en/dev/render/cycles/settings/scene/render/motion_blur.html#options