wallworm Posted June 7, 2017 Report Share Posted June 7, 2017 I think it might be helpful to add an option for each path similar to the Enable/Disable and Show/Hide that lets you freeze/cache the current path so that it doesn't need to be calculated anymore (so in essence, a snapshot of its paths and mesh internally). Assume you have a fairly complex plant that utilizes object/path reaction that is slow to calculate and you want to tweak some settings of a sub-path. Each change can be slow if you want to see the plant in context of all paths. Since changes to parent paths might invalidate accuracy, this case should be considered by letting the user know there could be discrepancies if the parent path(s) change. If the parent paths are also frozen, then no notice is necessary. Quote Link to comment Share on other sites More sharing options...
Eduard Posted June 9, 2017 Report Share Posted June 9, 2017 Hi Shawn, If we talk about the Object reaction modifier, then in the settings there is a Bake Direction button. Maybe this is what you need? Thanks! Quote Link to comment Share on other sites More sharing options...
wallworm Posted June 9, 2017 Author Report Share Posted June 9, 2017 Similar. What I was thinking was more of a bake of the entire path, not just the Object Reaction modifier. For example, say you have a plant with several paths and the root paths are calculation intensive (maybe several Path Reactions between the paths and meta meshes). When done with those, "Bake/Freeze" them so that the calculations for the final paths preview faster (maybe just leaves at the end of the tree, for example, that you are still tweaking) . For each path, it would be a bake of the completed path (including mesh and after mesh modifiers). Mainly, I'm thinking of this in terms of helping change parameters and seeing results faster. Essentially, I'm thinking of getting the speed increase you get by turning the visibility off on a path but still seeing the path results for reference while working on sub-paths, especially when working with metamesh. Maybe it isn't practical based on how metameshes merge between paths? In any event, I'm mainly just thinking about making it easier to work with complex trees. Quote Link to comment Share on other sites More sharing options...
Eduard Posted June 9, 2017 Report Share Posted June 9, 2017 I don't even know... We can still implement the baking directions in the Modify direction, but it's impossible to bake metameshes, because the metamesh is created every time from scratch, and we can not delete something and leave something, and then create again that was deleted. To quickly configure other paths, you can temporarily turn on the Disable all metameshes in the Preference parameters rollout. Thanks! Quote Link to comment Share on other sites More sharing options...
wallworm Posted June 9, 2017 Author Report Share Posted June 9, 2017 Thanks for the info. I had a hunch it wouldn't work for metamesh, but it was worth a shot. In terms of the paths, I guess it would depend on how much time it could save to baking the directions. Quote Link to comment Share on other sites More sharing options...
Eduard Posted June 14, 2017 Report Share Posted June 14, 2017 In terms of the paths, I guess it would depend on how much time it could save to baking the directions. I'm not sure that this will save much time. In the Object reaction modifier, this was added for a different purpose, mainly to hold the directions during the movement of the reaction object, so that the paths don't changes their directions. Thanks! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.