Thu, Dec 7
There is no plan that goes into details for refactoring of smokes or a developer currently working on it for first 2.8. A refactoring of modifiers is expected for the end of 2.8 series but to convert modifiers's stack into modifiers nodes. Addition of an OpenVDB primitive can be done next year or more years later.
@ronan ducluzeau (zeauro)
Thanks for the workaround but the thing is that I need to render like 20 slices along Z and 10 on X and Y each, so 40 slices in total. And then I need to do the same thing with another smoke sim, maybe bigger, so even more slices.
Wed, Dec 6
This is a bug tracker system where we fix bugs which we can reproduce. We do not provide support here. For support you can use other placers like Blender Artists forum.
I think it is a known limitation that Camera Clipping is not working with smokes at rendering.
Thanks again Carlo, finally is going out now, allready 2/3 almost done.
Tue, Dec 5
sorry... no sobol... hilbert spiral
will try left-right, thanks a lot for helping!
I was going to say:
Whats your tile order? Try making it top-bottom or bottom top... You may be running out of ram with the denoising.
I´m seeing that pcie4 shares IRQs with sata and usb in this mobo, though i don´t know how interrupt requests works and if it could have something to do with this.
At i.e. 128 samples 1920x1080 it renders ok.
Have you tried rendering at 40 samples instead of 4000? does that finish sucessfully?
I had another stuck.
After some more crashes, driver update and bios tweaks all seems to be working fine.
I have deactivated the cpu power save features and now it seems that data is flowing to the capillarities.
This has become a little weird.
Wed, Nov 29
Thu, Nov 23
B-Maxwell might have a different interpretation of that setting than how it originally worked in Blender, so this is not strictly a bug.
Thanks. It works fine in a daily build
This issue should be fixed in latest builds already. So test blender from builder.blender.org and see if the issue happens there.
Sun, Nov 19
Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
Nov 14 2017
Blender-fix solved the issue
Nov 13 2017
I can confirm this fix works!
Thanks a lot for solving this problem.
Setting priority to incomplete since we are awaiting more feedback now.
Managed to redo system becoming frozen at some point during synchronization after BIOS update.
All our standard benchmark files survive. Performance is good. We don't have time now to restore or test production files.
It would go much faster if you would share a case, or tell us how to produce a case that's slow? Use one of the benchmark files, duplicate stuff or so?
So nice!, now burn the CPU with some crazy scenes to find out if there is something wrong with scene buffering.
We've just received a beefy system with Threadripper! Testing started :)
Nov 11 2017
Additional information was provided.
Setting to Needs Triage.
Nov 3 2017
dual E5 2660 v3's (2.6 ghz) (40 Threads) Z10PE D8 WS, 96 gigs of ram win 7 x64 GTX 970 Windows 7,
Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
Oct 31 2017
Oct 29 2017
I've several systems at home, and noticed that Cycles crashed when I had the Denoise feature enabled on my Intel Atom laptop.
Oct 24 2017
Right, I'd be happy to debug it at bconf. Remote desktop access would work as well at some other time.
AMD was meant to send us (Blender Institute) a threadripper in July already. I reminded them again what happens with it.
Oct 21 2017
Oct 20 2017
Right, the fixed 0.25 roughness is definitely a hack, hopefully we can get rid of that too.