This looks really great! I really hope it gets into Master.
Jan 30 2019
Nov 25 2018
Just a quick question: Is the plane to do this for all the editors too? Graph, dope, node, sequence, etc?
Jun 26 2018
I think I’m fine with center aligned. My issue is that I don’t think the center needs to be in the actual center. I think the actual value sliders and controls should be about half the size as they are. That way you’ll get a lot more room for the text to the left of them. I have a feeling that a lot of new users will try and pull out the panel while trying to read the properties names and wind up getting frustrated because the panel doubles up on its self.
Jun 8 2018
LOVE all of this soon much! Great work guys. Can't wait to see the implementation.
Jun 1 2018
I just wanted to say that I'm really loving everything that's happening here. I think one thing a lot of people are missing is the power of presets. Just imagine that you have a bunch of states that you normally use for each of the rollouts. Once you have these states (Presets) you'll basically never have a reason to open the rollout afterword. It has the potential to revolutionize how we work, Just imagine you're setting up a render and you switch to the render tab, pick the sample preset, pick the output size preset, turn on volumetrics and the best setting that you normally use all with a click of a preset and you're off. It's one thing to have a preset for the entire property page (which has the potential to confuse because you're not always sure about all the things that it changes) but an entirely different thing to be able to have such a high level of control with each of the rollouts having presets. Really amazing idea!
Nov 22 2017
If I may make a suggestion, in order to elievate confusion with distributed task network rendering, I would love for this to be renamed "Cooperative network rendering" or just "Cooperative rendering". Either that or we could make the distinction between, "Distributed frame" and "Distributed bucket" network rendering?
Aug 2 2017
Sep 14 2016
Sep 13 2016
May 30 2016
that is a nice proposal, but this is actually how alembic (or any pointcache for that matter) works. Only the current (or which ever you ask for) frame is loaded (otherwise you could run out of ram pretty quickly). Someone please correct me if I'm wrong.
May 26 2016
@Galen Beals (galenb), just in case for testing, do you have a simple example contianing fluid meshes?
May 5 2016
Mar 5 2016
Ton: thanks, I'll have a look at the finder option.
kévin: thanks, I apriciate you keeping a level head while I lost mine. ;-) I think I understand now. It's more about backward compatibility than anything else. By the way, I understood that the cache files were designed like this before you even worked on it. I was just surprised that there wasn't a solution at this point. Thanks again.
Hi Kévin, I have a lot of respect for you and your work and I don't want to get on your bad side but this really isn't an acceptable answer. What was the point of using OpenVDB if you can't exchange cache files between apps? It certainly isn't a "Better" replacement for the current cacheing system. It actually hinders playback speed. So, if you can't easily use these caches in other applications, what is the point of having it. I know I'm coming off as confrontational but I have waited sooo long to get this feature just to be told, that's the way it's supposed to work. There must be a better solution. I'm on OS X and there's no simple way to batch rename files. In windows it might be simple to "rename" with wild cards in the command line, but in Unix the standard way rename files is with 'mv' which does't handle batches of files. I could write a shell script but is every user going to need to do this if they want to use the files in other programs? Not to mention that renaming the files invalidates them for use in Blender.