Change Details

{F13156164} Reasons for why we might not want to have this: * We are thinking about removing the idea of "original data" in favor of having "edit mode nodes". This is a node that outputs e.g. a mesh that can be edited manually/destructively, without needing a separate object. So a single object could have multiple edit modes, each of which corresponds to a node. * Technically it is not necessary to have this functionality, because one can always use two separate objects. The second object just uses an Object Info node to get the data from the first one and then applies more operations.

{F13156164} (mockup by aryeramaty) Reasons for why we might not want to have this: * We are thinking about removing the idea of "original data" in favor of having "edit mode nodes". This is a node that outputs e.g. a mesh that can be edited manually/destructively, without needing a separate object. So a single object could have multiple edit modes, each of which corresponds to a node. * Technically it is not necessary to have this functionality, because one can always use two separate objects. The second object just uses an Object Info node to get the data from the first one and then applies more operations.

{F13156164} (mockup by aryeramaty) Reasons for why we might not want to have this: * We are thinking about removing the idea of "original data" in favor of having "edit mode nodes". This is a node that outputs e.g. a mesh that can be edited manually/destructively, without needing a separate object. So a single object could have multiple edit modes, each of which corresponds to a node. * Technically it is not necessary to have this functionality, because one can always use two separate objects. The second object just uses an Object Info node to get the data from the first one and then applies more operations.