@bottobot/td-mcp
Version:
TouchDesigner Documentation MCP Server v2.3 - Pure MCP server for VS Code/Codium with comprehensive operator documentation for 629 operators + 7 tutorials across all categories (TOP, CHOP, SOP, DAT, MAT, COMP, POP). Features experimental POP operators wit
757 lines • 50.5 kB
JSON
{
"id": "capture",
"name": "Capture",
"displayName": "Capture",
"category": "SOP",
"subcategory": "Generators",
"version": "",
"lastUpdated": "2025-08-08T00:37:40.464Z",
"sourceFile": "C:\\Program Files\\Derivative\\TouchDesigner\\Samples\\Learn\\OfflineHelp\\https.docs.derivative.ca\\Capture_SOP.htm",
"url": "",
"description": "The Capture SOP is used to weight points in a geometry to capture regions. The weighting scheme is described in the next section, Capture Region SOP.",
"summary": "The Capture SOP is used to weight points in a geometry to capture regions. The weighting scheme is described in the next section, Capture Region SOP.",
"details": "",
"usage": "",
"tips": [],
"warnings": [],
"parameters": [
{
"id": null,
"name": "Group",
"label": "Group",
"group": "General",
"page": "",
"type": "float",
"dataType": "number",
"style": "",
"defaultValue": null,
"minValue": null,
"maxValue": null,
"step": null,
"menuItems": [],
"menuLabels": [],
"allowCustom": false,
"maxLength": null,
"pattern": null,
"isArray": false,
"arraySize": 1,
"dimensions": 1,
"description": "From Derivative\n\t\t\n\t\t\n\t\t\n\t\t\n\t\tJump to navigation\n\t\tJump to search\n\t\t\nThe Capture is used to weight points in a geometry to capture regions. The weighting scheme is described in the next section, Capture Region SOP.\t\t\nThe weights and the regions they correspond to are transferred down the chain as point and detail attributes.\t\t\t\nThe Capture can take an optional second input to specify extra capture regions to use in the capture process. Any capture regions that are in this second input are processed after the capture regions that are in the object hierarchy specified by the parameter. You can also specify a second input and not specify a Parent Object at all.\ncaptureSOP_Class\n\nContents\n \n \n \n \n \n \n \n\n\n\n\n\n group - Specify the point groups from the first input (input0) to operate on.\n\n\n\n rootbone - An object hierarchy is traversed to find the Capture Regions with which to do the weighting. This parameter specifies the top of the traversal hierarchy.\n\n\n\t\t\n weightfrom - - Use this menu to specify where to get the weight from.\n\n surface - (default) Uses the surface to compute the weight of a point (or CV in the case of NURBS). This is very helpful for NURBS surfaces when the CV's may be far off the surface. By using , each CV is weight based on the surface's location within a Capture Region. This is determined by calculating the CVs \"most influenced point\" on the NURBS surface and computing the weight of that position. cv - Using the choice, the location of the point within the region is used for the weighting.\n\t\t\n captframe - Specifies the frame number to do the capture computations. Every time TouchDesigner reaches this frame, the geometry will be re-captured. It is a common practice to set the to an frame outside of your animation range, -1 for example. Specifies the frame number to do the capture computations. Every time TouchDesigner reaches this frame, the geometry will be re-captured. It is a common practice to set the to an frame outside of your animation range, -1 for example.\t\nNote: When a file is loaded, all of the associated capture regions are evaluated at the . Keyframes must be set to position the capture regions properly at the , otherwise the geometry will be weighted incorrectly upon the subsequent file loads.\n\n\n\t\t\n color - - This option colors each point by capture region (using point attributes) according to its capture weight. The points inherit their colors from the Capture Region(s) in which they lie. For example, if a point falls within a blue capture region and also a yellow capture region, the point will be colored green (more blue near if the blue weighting dominates, and more yellow if the yellow weight dominates). In addition, the points become darker as the weighting gets lighter. For example, near the edge of a blue region, a caught point will appear dark blue. Near the centre, it will appear bright blue. If a point is not caught by any region, it is colored bright red.\n\n coldefault - colregion -\n\t\t\n captfile - The name of the capture override file (*.ocapt). This file is loaded after TouchDesigner completes its point weighting. Each line of the override file lists a point number, a region (path and primitive number) and a weight. The points on the geometry are modified to use these custom weights.\t\nOverride File Format - Each line in the override file must have the following format:\t\t\t\nFor example:\t\t\t\n\n0 /obj/chain_bone1/cregion 0 0.0 \t\t\t\n0 /obj/chain_bone2/cregion 0 3.757989 \t\t\t\n0 /obj/chain_bone3/cregion 0 1.757989\t\t\t\n\n\t\t\t\nThis weights point 0 to three regions (actually only two because the first entry has a weight of zero). Remember that the is read after TouchDesigner does it's own capture weight computation, so in this case, if point 0 was originally assigned to region /obj/chain_bone4/cregion 0, this part of its weighting would be unchanged.\t\t\t\nThere is no upper limit to the number of regions that can be weighted to a point. If a point/region combination is in the file twice, the second one is used.\t\t\t\nFor example:\t\t\t\n\n0 /obj/chain_bone1/cregion 0 1.0\t\t\t\n0 /obj/chain_bone1/cregion 0 2.0\t\t\t\n\nThis causes the first entry to be ignored (a weighting of 2.0 is used).\t\t\t\nThe weight field is used to prescribe the relative amount of influence a region has on a point. It can be any number. The range of the weights computed by TouchDesigner are specified by the parameter of each Capture Region (please see Capture Region SOP).\t\t\t\nThe easiest way to a capture is to use the button (see below) and start from the file produced by TouchDesigner.\n\n\n\n\n\n savefile - The file specified here can be used as a \"working file\" to save the point weighting of all the points or a selected subset of points. The file format for the capture override files is fairly straight-forward (see above), so this is a good place to start if you need to do custom overriding.\n\n\n\t\t\n autoincr - This increments the name before saving. Be careful about turning this option off because there is no warning or confirm dialog to prevent you from overwriting an .ocapt file.\n\n\n\t\t\n savecaptfile - This saves the point weighting of all points to the .\n\n\n\t\t\n savesel - This saves the point weighting only for the points that are selected in the viewport.\t\n you must be editing this particular in the Viewport for this selection to apply to this .\n\n\n\n\n\n -\n -\n\nExtra Information for the Capture can be accessed via an Info CHOP.\n\n\n\n - Number of points in this . - Number of primitives in this . - Number of particles in this . - Time spent in another thread updating geometry data on the from the 's CPU data. As it is part of another thread, this time is not part of the usual frame time. - Time spent in another thread updating meta surface geometry data (such as metaballs or nurbs) on the from the 's CPU data. As it is part of another thread, this time is not part of the usual frame time.\n - Number of times the operator has cooked since the process started. - Duration of the last cook in milliseconds. - Frame number when this operator was last cooked relative to the component timeline. - Frame number when this operator was last cooked relative to the absolute time. - Time in milliseconds at which the operator started cooking in the frame it was cooked. - Time in milliseconds at which the operator finished cooking in the frame it was cooked. - 1 if operator was cooked this frame. - Number of warnings in this operator if any. - Number of errors in this operator if any.\nTouchDesigner Build: Latest\\n2022.241402021.100002018.28070before 2018.28070\nSOPs\n• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • \n\nA Operator Family that reads, creates and modifies 3D points, polygons, lines, particles, surfaces, spheres and meatballs. Particles and point clouds are now done primarily on the GPU using TOPs.\n\n\n\nHierarchy relates components with other components. There are two groups of Hierarchy in TouchDesigner. 3D Object Components, and 2D Panel Components. Hierarchies let one component to be positioned relative to another. Each group can be connected via lines between the bottoms/tops of nodes in a network, or by placing one component inside the other.\n\n\n\nThe term \"Frame\" is a measurement of time used (1) in the Timeline, (2) as a time-unit in CHOPs, and (3) as a time unit in movie files that are read into TOPs and written out from TOPs. The frame rate is the frames per second (FPS).\n\n\n\nTOuch Environment file, the file type used by TouchDesigner to save your entire project.\n\n\n\nEach SOP has a list of Points. Each point has an XYZ 3D position value plus other optional attributes. Each polygon Primitive is defined by a vertex list, which is list of point numbers.\n\n\n\nAn Operator Family which operate on Channels (a sequence of numbers (Samples)) which are used for animation, audio, mathematics, simulation, logic, UI construction, and data streamed from/to devices and protocols.\n\n\n\nThe Graphics Processing Unit. This is the high-speed, many-core processor of the graphics card/chip that takes geometry, images and data from the CPU and creates images and processed data.\n\n\n\n\n\n\n\n\nRetrieved from \"https://docs.derivative.ca/index.php?title=Capture_SOP&oldid=24255\"\n\t\tCategory: SOPs",
"tooltip": "",
"help": "",
"units": "",
"examples": [],
"isReadOnly": false,
"isAdvanced": false,
"isHidden": false,
"isAnimatable": true,
"isExpression": false,
"isPython": false,
"dependsOn": [],
"affects": [],
"linkedTo": [],
"expressionLanguage": "",
"defaultExpression": "",
"commonExpressions": [],
"order": 0,
"isVisible": true,
"conditionalDisplay": null,
"isValid": true,
"validationErrors": [],
"lastUpdated": "2025-08-08T00:37:40.460Z",
"rawData": {},
"sourceElement": null
},
{
"id": null,
"name": "Group",
"label": "Group",
"group": "General",
"page": "",
"type": "float",
"dataType": "number",
"style": "",
"defaultValue": null,
"minValue": null,
"maxValue": null,
"step": null,
"menuItems": [],
"menuLabels": [],
"allowCustom": false,
"maxLength": null,
"pattern": null,
"isArray": false,
"arraySize": 1,
"dimensions": 1,
"description": "From Derivative\n\t\t\n\t\t\n\t\t\n\t\t\n\t\tJump to navigation\n\t\tJump to search\n\t\t\nThe Capture is used to weight points in a geometry to capture regions. The weighting scheme is described in the next section, Capture Region SOP.\t\t\nThe weights and the regions they correspond to are transferred down the chain as point and detail attributes.\t\t\t\nThe Capture can take an optional second input to specify extra capture regions to use in the capture process. Any capture regions that are in this second input are processed after the capture regions that are in the object hierarchy specified by the parameter. You can also specify a second input and not specify a Parent Object at all.\ncaptureSOP_Class\n\nContents\n \n \n \n \n \n \n \n\n\n\n\n\n group - Specify the point groups from the first input (input0) to operate on.\n\n\n\n rootbone - An object hierarchy is traversed to find the Capture Regions with which to do the weighting. This parameter specifies the top of the traversal hierarchy.\n\n\n\t\t\n weightfrom - - Use this menu to specify where to get the weight from.\n\n surface - (default) Uses the surface to compute the weight of a point (or CV in the case of NURBS). This is very helpful for NURBS surfaces when the CV's may be far off the surface. By using , each CV is weight based on the surface's location within a Capture Region. This is determined by calculating the CVs \"most influenced point\" on the NURBS surface and computing the weight of that position. cv - Using the choice, the location of the point within the region is used for the weighting.\n\t\t\n captframe - Specifies the frame number to do the capture computations. Every time TouchDesigner reaches this frame, the geometry will be re-captured. It is a common practice to set the to an frame outside of your animation range, -1 for example. Specifies the frame number to do the capture computations. Every time TouchDesigner reaches this frame, the geometry will be re-captured. It is a common practice to set the to an frame outside of your animation range, -1 for example.\t\nNote: When a file is loaded, all of the associated capture regions are evaluated at the . Keyframes must be set to position the capture regions properly at the , otherwise the geometry will be weighted incorrectly upon the subsequent file loads.\n\n\n\t\t\n color - - This option colors each point by capture region (using point attributes) according to its capture weight. The points inherit their colors from the Capture Region(s) in which they lie. For example, if a point falls within a blue capture region and also a yellow capture region, the point will be colored green (more blue near if the blue weighting dominates, and more yellow if the yellow weight dominates). In addition, the points become darker as the weighting gets lighter. For example, near the edge of a blue region, a caught point will appear dark blue. Near the centre, it will appear bright blue. If a point is not caught by any region, it is colored bright red.\n\n coldefault - colregion -\n\t\t\n captfile - The name of the capture override file (*.ocapt). This file is loaded after TouchDesigner completes its point weighting. Each line of the override file lists a point number, a region (path and primitive number) and a weight. The points on the geometry are modified to use these custom weights.\t\nOverride File Format - Each line in the override file must have the following format:\t\t\t\nFor example:\t\t\t\n\n0 /obj/chain_bone1/cregion 0 0.0 \t\t\t\n0 /obj/chain_bone2/cregion 0 3.757989 \t\t\t\n0 /obj/chain_bone3/cregion 0 1.757989\t\t\t\n\n\t\t\t\nThis weights point 0 to three regions (actually only two because the first entry has a weight of zero). Remember that the is read after TouchDesigner does it's own capture weight computation, so in this case, if point 0 was originally assigned to region /obj/chain_bone4/cregion 0, this part of its weighting would be unchanged.\t\t\t\nThere is no upper limit to the number of regions that can be weighted to a point. If a point/region combination is in the file twice, the second one is used.\t\t\t\nFor example:\t\t\t\n\n0 /obj/chain_bone1/cregion 0 1.0\t\t\t\n0 /obj/chain_bone1/cregion 0 2.0\t\t\t\n\nThis causes the first entry to be ignored (a weighting of 2.0 is used).\t\t\t\nThe weight field is used to prescribe the relative amount of influence a region has on a point. It can be any number. The range of the weights computed by TouchDesigner are specified by the parameter of each Capture Region (please see Capture Region SOP).\t\t\t\nThe easiest way to a capture is to use the button (see below) and start from the file produced by TouchDesigner.\n\n\n\n\n\n savefile - The file specified here can be used as a \"working file\" to save the point weighting of all the points or a selected subset of points. The file format for the capture override files is fairly straight-forward (see above), so this is a good place to start if you need to do custom overriding.\n\n\n\t\t\n autoincr - This increments the name before saving. Be careful about turning this option off because there is no warning or confirm dialog to prevent you from overwriting an .ocapt file.\n\n\n\t\t\n savecaptfile - This saves the point weighting of all points to the .\n\n\n\t\t\n savesel - This saves the point weighting only for the points that are selected in the viewport.\t\n you must be editing this particular in the Viewport for this selection to apply to this .\n\n\n\n\n\n -\n -\n\nExtra Information for the Capture can be accessed via an Info CHOP.\n\n\n\n - Number of points in this . - Number of primitives in this . - Number of particles in this . - Time spent in another thread updating geometry data on the from the 's CPU data. As it is part of another thread, this time is not part of the usual frame time. - Time spent in another thread updating meta surface geometry data (such as metaballs or nurbs) on the from the 's CPU data. As it is part of another thread, this time is not part of the usual frame time.\n - Number of times the operator has cooked since the process started. - Duration of the last cook in milliseconds. - Frame number when this operator was last cooked relative to the component timeline. - Frame number when this operator was last cooked relative to the absolute time. - Time in milliseconds at which the operator started cooking in the frame it was cooked. - Time in milliseconds at which the operator finished cooking in the frame it was cooked. - 1 if operator was cooked this frame. - Number of warnings in this operator if any. - Number of errors in this operator if any.\nTouchDesigner Build: Latest\\n2022.241402021.100002018.28070before 2018.28070\nSOPs\n• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • \n\nA Operator Family that reads, creates and modifies 3D points, polygons, lines, particles, surfaces, spheres and meatballs. Particles and point clouds are now done primarily on the GPU using TOPs.\n\n\n\nHierarchy relates components with other components. There are two groups of Hierarchy in TouchDesigner. 3D Object Components, and 2D Panel Components. Hierarchies let one component to be positioned relative to another. Each group can be connected via lines between the bottoms/tops of nodes in a network, or by placing one component inside the other.\n\n\n\nThe term \"Frame\" is a measurement of time used (1) in the Timeline, (2) as a time-unit in CHOPs, and (3) as a time unit in movie files that are read into TOPs and written out from TOPs. The frame rate is the frames per second (FPS).\n\n\n\nTOuch Environment file, the file type used by TouchDesigner to save your entire project.\n\n\n\nEach SOP has a list of Points. Each point has an XYZ 3D position value plus other optional attributes. Each polygon Primitive is defined by a vertex list, which is list of point numbers.\n\n\n\nAn Operator Family which operate on Channels (a sequence of numbers (Samples)) which are used for animation, audio, mathematics, simulation, logic, UI construction, and data streamed from/to devices and protocols.\n\n\n\nThe Graphics Processing Unit. This is the high-speed, many-core processor of the graphics card/chip that takes geometry, images and data from the CPU and creates images and processed data.\n\n\n\n\n\n\n\n\nRetrieved from \"https://docs.derivative.ca/index.php?title=Capture_SOP&oldid=24255\"\n\t\tCategory: SOPs",
"tooltip": "",
"help": "",
"units": "",
"examples": [],
"isReadOnly": false,
"isAdvanced": false,
"isHidden": false,
"isAnimatable": true,
"isExpression": false,
"isPython": false,
"dependsOn": [],
"affects": [],
"linkedTo": [],
"expressionLanguage": "",
"defaultExpression": "",
"commonExpressions": [],
"order": 0,
"isVisible": true,
"conditionalDisplay": null,
"isValid": true,
"validationErrors": [],
"lastUpdated": "2025-08-08T00:37:40.461Z",
"rawData": {},
"sourceElement": null
},
{
"id": null,
"name": "Group",
"label": "Group",
"group": "General",
"page": "",
"type": "float",
"dataType": "number",
"style": "",
"defaultValue": null,
"minValue": null,
"maxValue": null,
"step": null,
"menuItems": [],
"menuLabels": [],
"allowCustom": false,
"maxLength": null,
"pattern": null,
"isArray": false,
"arraySize": 1,
"dimensions": 1,
"description": "The Capture is used to weight points in a geometry to capture regions. The weighting scheme is described in the next section, Capture Region SOP.\t\t\nThe weights and the regions they correspond to are transferred down the chain as point and detail attributes.\t\t\t\nThe Capture can take an optional second input to specify extra capture regions to use in the capture process. Any capture regions that are in this second input are processed after the capture regions that are in the object hierarchy specified by the parameter. You can also specify a second input and not specify a Parent Object at all.\ncaptureSOP_Class\n\nContents\n \n \n \n \n \n \n \n\n\n\n\n\n group - Specify the point groups from the first input (input0) to operate on.\n\n\n\n rootbone - An object hierarchy is traversed to find the Capture Regions with which to do the weighting. This parameter specifies the top of the traversal hierarchy.\n\n\n\t\t\n weightfrom - - Use this menu to specify where to get the weight from.\n\n surface - (default) Uses the surface to compute the weight of a point (or CV in the case of NURBS). This is very helpful for NURBS surfaces when the CV's may be far off the surface. By using , each CV is weight based on the surface's location within a Capture Region. This is determined by calculating the CVs \"most influenced point\" on the NURBS surface and computing the weight of that position. cv - Using the choice, the location of the point within the region is used for the weighting.\n\t\t\n captframe - Specifies the frame number to do the capture computations. Every time TouchDesigner reaches this frame, the geometry will be re-captured. It is a common practice to set the to an frame outside of your animation range, -1 for example. Specifies the frame number to do the capture computations. Every time TouchDesigner reaches this frame, the geometry will be re-captured. It is a common practice to set the to an frame outside of your animation range, -1 for example.\t\nNote: When a file is loaded, all of the associated capture regions are evaluated at the . Keyframes must be set to position the capture regions properly at the , otherwise the geometry will be weighted incorrectly upon the subsequent file loads.\n\n\n\t\t\n color - - This option colors each point by capture region (using point attributes) according to its capture weight. The points inherit their colors from the Capture Region(s) in which they lie. For example, if a point falls within a blue capture region and also a yellow capture region, the point will be colored green (more blue near if the blue weighting dominates, and more yellow if the yellow weight dominates). In addition, the points become darker as the weighting gets lighter. For example, near the edge of a blue region, a caught point will appear dark blue. Near the centre, it will appear bright blue. If a point is not caught by any region, it is colored bright red.\n\n coldefault - colregion -\n\t\t\n captfile - The name of the capture override file (*.ocapt). This file is loaded after TouchDesigner completes its point weighting. Each line of the override file lists a point number, a region (path and primitive number) and a weight. The points on the geometry are modified to use these custom weights.\t\nOverride File Format - Each line in the override file must have the following format:\t\t\t\nFor example:\t\t\t\n\n0 /obj/chain_bone1/cregion 0 0.0 \t\t\t\n0 /obj/chain_bone2/cregion 0 3.757989 \t\t\t\n0 /obj/chain_bone3/cregion 0 1.757989\t\t\t\n\n\t\t\t\nThis weights point 0 to three regions (actually only two because the first entry has a weight of zero). Remember that the is read after TouchDesigner does it's own capture weight computation, so in this case, if point 0 was originally assigned to region /obj/chain_bone4/cregion 0, this part of its weighting would be unchanged.\t\t\t\nThere is no upper limit to the number of regions that can be weighted to a point. If a point/region combination is in the file twice, the second one is used.\t\t\t\nFor example:\t\t\t\n\n0 /obj/chain_bone1/cregion 0 1.0\t\t\t\n0 /obj/chain_bone1/cregion 0 2.0\t\t\t\n\nThis causes the first entry to be ignored (a weighting of 2.0 is used).\t\t\t\nThe weight field is used to prescribe the relative amount of influence a region has on a point. It can be any number. The range of the weights computed by TouchDesigner are specified by the parameter of each Capture Region (please see Capture Region SOP).\t\t\t\nThe easiest way to a capture is to use the button (see below) and start from the file produced by TouchDesigner.\n\n\n\n\n\n savefile - The file specified here can be used as a \"working file\" to save the point weighting of all the points or a selected subset of points. The file format for the capture override files is fairly straight-forward (see above), so this is a good place to start if you need to do custom overriding.\n\n\n\t\t\n autoincr - This increments the name before saving. Be careful about turning this option off because there is no warning or confirm dialog to prevent you from overwriting an .ocapt file.\n\n\n\t\t\n savecaptfile - This saves the point weighting of all points to the .\n\n\n\t\t\n savesel - This saves the point weighting only for the points that are selected in the viewport.\t\n you must be editing this particular in the Viewport for this selection to apply to this .\n\n\n\n\n\n -\n -\n\nExtra Information for the Capture can be accessed via an Info CHOP.\n\n\n\n - Number of points in this . - Number of primitives in this . - Number of particles in this . - Time spent in another thread updating geometry data on the from the 's CPU data. As it is part of another thread, this time is not part of the usual frame time. - Time spent in another thread updating meta surface geometry data (such as metaballs or nurbs) on the from the 's CPU data. As it is part of another thread, this time is not part of the usual frame time.\n - Number of times the operator has cooked since the process started. - Duration of the last cook in milliseconds. - Frame number when this operator was last cooked relative to the component timeline. - Frame number when this operator was last cooked relative to the absolute time. - Time in milliseconds at which the operator started cooking in the frame it was cooked. - Time in milliseconds at which the operator finished cooking in the frame it was cooked. - 1 if operator was cooked this frame. - Number of warnings in this operator if any. - Number of errors in this operator if any.\nTouchDesigner Build: Latest\\n2022.241402021.100002018.28070before 2018.28070\nSOPs\n• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • \n\nA Operator Family that reads, creates and modifies 3D points, polygons, lines, particles, surfaces, spheres and meatballs. Particles and point clouds are now done primarily on the GPU using TOPs.\n\n\n\nHierarchy relates components with other components. There are two groups of Hierarchy in TouchDesigner. 3D Object Components, and 2D Panel Components. Hierarchies let one component to be positioned relative to another. Each group can be connected via lines between the bottoms/tops of nodes in a network, or by placing one component inside the other.\n\n\n\nThe term \"Frame\" is a measurement of time used (1) in the Timeline, (2) as a time-unit in CHOPs, and (3) as a time unit in movie files that are read into TOPs and written out from TOPs. The frame rate is the frames per second (FPS).\n\n\n\nTOuch Environment file, the file type used by TouchDesigner to save your entire project.\n\n\n\nEach SOP has a list of Points. Each point has an XYZ 3D position value plus other optional attributes. Each polygon Primitive is defined by a vertex list, which is list of point numbers.\n\n\n\nAn Operator Family which operate on Channels (a sequence of numbers (Samples)) which are used for animation, audio, mathematics, simulation, logic, UI construction, and data streamed from/to devices and protocols.\n\n\n\nThe Graphics Processing Unit. This is the high-speed, many-core processor of the graphics card/chip that takes geometry, images and data from the CPU and creates images and processed data.\n\n\n\n\n\n\n\n\nRetrieved from \"https://docs.derivative.ca/index.php?title=Capture_SOP&oldid=24255\"",
"tooltip": "",
"help": "",
"units": "",
"examples": [],
"isReadOnly": false,
"isAdvanced": false,
"isHidden": false,
"isAnimatable": true,
"isExpression": false,
"isPython": false,
"dependsOn": [],
"affects": [],
"linkedTo": [],
"expressionLanguage": "",
"defaultExpression": "",
"commonExpressions": [],
"order": 0,
"isVisible": true,
"conditionalDisplay": null,
"isValid": true,
"validationErrors": [],
"lastUpdated": "2025-08-08T00:37:40.463Z",
"rawData": {},
"sourceElement": null
},
{
"id": null,
"name": "Group",
"label": "Group",
"group": "General",
"page": "",
"type": "float",
"dataType": "number",
"style": "",
"defaultValue": null,
"minValue": null,
"maxValue": null,
"step": null,
"menuItems": [],
"menuLabels": [],
"allowCustom": false,
"maxLength": null,
"pattern": null,
"isArray": false,
"arraySize": 1,
"dimensions": 1,
"description": "group - Specify the point groups from the first input (input0) to operate on.",
"tooltip": "",
"help": "",
"units": "",
"examples": [],
"isReadOnly": false,
"isAdvanced": false,
"isHidden": false,
"isAnimatable": true,
"isExpression": false,
"isPython": false,
"dependsOn": [],
"affects": [],
"linkedTo": [],
"expressionLanguage": "",
"defaultExpression": "",
"commonExpressions": [],
"order": 0,
"isVisible": true,
"conditionalDisplay": null,
"isValid": true,
"validationErrors": [],
"lastUpdated": "2025-08-08T00:37:40.463Z",
"rawData": {},
"sourceElement": null
},
{
"id": null,
"name": "Hierarchy",
"label": "Hierarchy",
"group": "General",
"page": "",
"type": "float",
"dataType": "number",
"style": "",
"defaultValue": null,
"minValue": null,
"maxValue": null,
"step": null,
"menuItems": [],
"menuLabels": [],
"allowCustom": false,
"maxLength": null,
"pattern": null,
"isArray": false,
"arraySize": 1,
"dimensions": 1,
"description": "rootbone - An object hierarchy is traversed to find the Capture Regions with which to do the weighting. This parameter specifies the top of the traversal hierarchy.",
"tooltip": "",
"help": "",
"units": "",
"examples": [],
"isReadOnly": false,
"isAdvanced": false,
"isHidden": false,
"isAnimatable": true,
"isExpression": false,
"isPython": false,
"dependsOn": [],
"affects": [],
"linkedTo": [],
"expressionLanguage": "",
"defaultExpression": "",
"commonExpressions": [],
"order": 0,
"isVisible": true,
"conditionalDisplay": null,
"isValid": true,
"validationErrors": [],
"lastUpdated": "2025-08-08T00:37:40.463Z",
"rawData": {},
"sourceElement": null
},
{
"id": null,
"name": "Weight from",
"label": "Weight from",
"group": "General",
"page": "",
"type": "float",
"dataType": "number",
"style": "",
"defaultValue": null,
"minValue": null,
"maxValue": null,
"step": null,
"menuItems": [],
"menuLabels": [],
"allowCustom": false,
"maxLength": null,
"pattern": null,
"isArray": false,
"arraySize": 1,
"dimensions": 1,
"description": "weightfrom - - Use this menu to specify where to get the weight from.\n\n surface - (default) Uses the surface to compute the weight of a point (or CV in the case of NURBS). This is very helpful for NURBS surfaces when the CV's may be far off the surface. By using , each CV is weight based on the surface's location within a Capture Region. This is determined by calculating the CVs \"most influenced point\" on the NURBS surface and computing the weight of that position. cv - Using the choice, the location of the point within the region is used for the weighting.",
"tooltip": "",
"help": "",
"units": "",
"examples": [],
"isReadOnly": false,
"isAdvanced": false,
"isHidden": false,
"isAnimatable": true,
"isExpression": false,
"isPython": false,
"dependsOn": [],
"affects": [],
"linkedTo": [],
"expressionLanguage": "",
"defaultExpression": "",
"commonExpressions": [],
"order": 0,
"isVisible": true,
"conditionalDisplay": null,
"isValid": true,
"validationErrors": [],
"lastUpdated": "2025-08-08T00:37:40.463Z",
"rawData": {},
"sourceElement": null
},
{
"id": null,
"name": "Surface",
"label": "Surface",
"group": "General",
"page": "",
"type": "float",
"dataType": "number",
"style": "",
"defaultValue": null,
"minValue": null,
"maxValue": null,
"step": null,
"menuItems": [],
"menuLabels": [],
"allowCustom": false,
"maxLength": null,
"pattern": null,
"isArray": false,
"arraySize": 1,
"dimensions": 1,
"description": "surface - (default) Uses the surface to compute the weight of a point (or CV in the case of NURBS). This is very helpful for NURBS surfaces when the CV's may be far off the surface. By using , each CV is weight based on the surface's location within a Capture Region. This is determined by calculating the CVs \"most influenced point\" on the NURBS surface and computing the weight of that position. cv - Using the choice, the location of the point within the region is used for the weighting.",
"tooltip": "",
"help": "",
"units": "",
"examples": [],
"isReadOnly": false,
"isAdvanced": false,
"isHidden": false,
"isAnimatable": true,
"isExpression": false,
"isPython": false,
"dependsOn": [],
"affects": [],
"linkedTo": [],
"expressionLanguage": "",
"defaultExpression": "",
"commonExpressions": [],
"order": 0,
"isVisible": true,
"conditionalDisplay": null,
"isValid": true,
"validationErrors": [],
"lastUpdated": "2025-08-08T00:37:40.463Z",
"rawData": {},
"sourceElement": null
},
{
"id": null,
"name": "Capture Frame",
"label": "Capture Frame",
"group": "General",
"page": "",
"type": "float",
"dataType": "number",
"style": "",
"defaultValue": null,
"minValue": null,
"maxValue": null,
"step": null,
"menuItems": [],
"menuLabels": [],
"allowCustom": false,
"maxLength": null,
"pattern": null,
"isArray": false,
"arraySize": 1,
"dimensions": 1,
"description": "captframe - Specifies the frame number to do the capture computations. Every time TouchDesigner reaches this frame, the geometry will be re-captured. It is a common practice to set the to an frame outside of your animation range, -1 for example. Specifies the frame number to do the capture computations. Every time TouchDesigner reaches this frame, the geometry will be re-captured. It is a common practice to set the to an frame outside of your animation range, -1 for example.\t\nNote: When a file is loaded, all of the associated capture regions are evaluated at the . Keyframes must be set to position the capture regions properly at the , otherwise the geometry will be weighted incorrectly upon the subsequent file loads.",
"tooltip": "",
"help": "",
"units": "",
"examples": [],
"isReadOnly": false,
"isAdvanced": false,
"isHidden": false,
"isAnimatable": true,
"isExpression": false,
"isPython": false,
"dependsOn": [],
"affects": [],
"linkedTo": [],
"expressionLanguage": "",
"defaultExpression": "",
"commonExpressions": [],
"order": 0,
"isVisible": true,
"conditionalDisplay": null,
"isValid": true,
"validationErrors": [],
"lastUpdated": "2025-08-08T00:37:40.463Z",
"rawData": {},
"sourceElement": null
},
{
"id": null,
"name": "Point Coloring",
"label": "Point Coloring",
"group": "General",
"page": "",
"type": "float",
"dataType": "number",
"style": "",
"defaultValue": null,
"minValue": null,
"maxValue": null,
"step": null,
"menuItems": [],
"menuLabels": [],
"allowCustom": false,
"maxLength": null,
"pattern": null,
"isArray": false,
"arraySize": 1,
"dimensions": 1,
"description": "color - - This option colors each point by capture region (using point attributes) according to its capture weight. The points inherit their colors from the Capture Region(s) in which they lie. For example, if a point falls within a blue capture region and also a yellow capture region, the point will be colored green (more blue near if the blue weighting dominates, and more yellow if the yellow weight dominates). In addition, the points become darker as the weighting gets lighter. For example, near the edge of a blue region, a caught point will appear dark blue. Near the centre, it will appear bright blue. If a point is not caught by any region, it is colored bright red.\n\n coldefault - colregion -",
"tooltip": "",
"help": "",
"units": "",
"examples": [],
"isReadOnly": false,
"isAdvanced": false,
"isHidden": false,
"isAnimatable": true,
"isExpression": false,
"isPython": false,
"dependsOn": [],
"affects": [],
"linkedTo": [],
"expressionLanguage": "",
"defaultExpression": "",
"commonExpressions": [],
"order": 0,
"isVisible": true,
"conditionalDisplay": null,
"isValid": true,
"validationErrors": [],
"lastUpdated": "2025-08-08T00:37:40.463Z",
"rawData": {},
"sourceElement": null
},
{
"id": null,
"name": "Default Source Color",
"label": "Default Source Color",
"group": "General",
"page": "",
"type": "float",
"dataType": "number",
"style": "",
"defaultValue": null,
"minValue": null,
"maxValue": null,
"step": null,
"menuItems": [],
"menuLabels": [],
"allowCustom": false,
"maxLength": null,
"pattern": null,
"isArray": false,
"arraySize": 1,
"dimensions": 1,
"description": "coldefault - colregion -",
"tooltip": "",
"help": "",
"units": "",
"examples": [],
"isReadOnly": false,
"isAdvanced": false,
"isHidden": false,
"isAnimatable": true,
"isExpression": false,
"isPython": false,
"dependsOn": [],
"affects": [],
"linkedTo": [],
"expressionLanguage": "",
"defaultExpression": "",
"commonExpressions": [],
"order": 0,
"isVisible": true,
"conditionalDisplay": null,
"isValid": true,
"validationErrors": [],
"lastUpdated": "2025-08-08T00:37:40.463Z",
"rawData": {},
"sourceElement": null
},
{
"id": null,
"name": "Override File",
"label": "Override File",
"group": "General",
"page": "",
"type": "float",
"dataType": "number",
"style": "",
"defaultValue": null,
"minValue": null,
"maxValue": null,
"step": null,
"menuItems": [],
"menuLabels": [],
"allowCustom": false,
"maxLength": null,
"pattern": null,
"isArray": false,
"arraySize": 1,
"dimensions": 1,
"description": "captfile - The name of the capture override file (*.ocapt). This file is loaded after TouchDesigner completes its point weighting. Each line of the override file lists a point number, a region (path and primitive number) and a weight. The points on the geometry are modified to use these custom weights.\t\nOverride File Format - Each line in the override file must have the following format:\t\t\t\nFor example:\t\t\t\n\n0 /obj/chain_bone1/cregion 0 0.0 \t\t\t\n0 /obj/chain_bone2/cregion 0 3.757989 \t\t\t\n0 /obj/chain_bone3/cregion 0 1.757989\t\t\t\n\n\t\t\t\nThis weights point 0 to three regions (actually only two because the first entry has a weight of zero). Remember that the is read after TouchDesigner does it's own capture weight computation, so in this case, if point 0 was originally assigned to region /obj/chain_bone4/cregion 0, this part of its weighting would be unchanged.\t\t\t\nThere is no upper limit to the number of regions that can be weighted to a point. If a point/region combination is in the file twice, the second one is used.\t\t\t\nFor example:\t\t\t\n\n0 /obj/chain_bone1/cregion 0 1.0\t\t\t\n0 /obj/chain_bone1/cregion 0 2.0\t\t\t\n\nThis causes the first entry to be ignored (a weighting of 2.0 is used).\t\t\t\nThe weight field is used to prescribe the relative amount of influence a region has on a point. It can be any number. The range of the weights computed by TouchDesigner are specified by the parameter of each Capture Region (please see Capture Region SOP).\t\t\t\nThe easiest way to a capture is to use the button (see below) and start from the file produced by TouchDesigner.",
"tooltip": "",
"help": "",
"units": "",
"examples": [],
"isReadOnly": false,
"isAdvanced": false,
"isHidden": false,
"isAnimatable": true,
"isExpression": false,
"isPython": false,
"dependsOn": [],
"affects": [],
"linkedTo": [],
"expressionLanguage": "",
"defaultExpression": "",
"commonExpressions": [],
"order": 0,
"isVisible": true,
"conditionalDisplay": null,
"isValid": true,
"validationErrors": [],
"lastUpdated": "2025-08-08T00:37:40.464Z",
"rawData": {},
"sourceElement": null
},
{
"id": null,
"name": "Save File",
"label": "Save File",
"group": "General",
"page": "",
"type": "float",
"dataType": "number",
"style": "",
"defaultValue": null,
"minValue": null,
"maxValue": null,
"step": null,
"menuItems": [],
"menuLabels": [],
"allowCustom": false,
"maxLength": null,
"pattern": null,
"isArray": false,
"arraySize": 1,
"dimensions": 1,
"description": "savefile - The file specified here can be used as a \"working file\" to save the point weighting of all the points or a selected subset of points. The file format for the capture override files is fairly straight-forward (see above), so this is a good place to start if you need to do custom overriding.",
"tooltip": "",
"help": "",
"units": "",
"examples": [],
"isReadOnly": false,
"isAdvanced": false,
"isHidden": false,
"isAnimatable": true,
"isExpression": false,
"isPython": false,
"dependsOn": [],
"affects": [],
"linkedTo": [],
"expressionLanguage": "",
"defaultExpression": "",
"commonExpressions": [],
"order": 0,
"isVisible": true,
"conditionalDisplay": null,
"isValid": true,
"validationErrors": [],
"lastUpdated": "2025-08-08T00:37:40.464Z",
"rawData": {},
"sourceElement": null
},
{
"id": null,
"name": "Increment Save File",
"label": "Increment Save File",
"group": "General",
"page": "",
"type": "float",
"dataType": "number",
"style": "",
"defaultValue": null,
"minValue": null,
"maxValue": null,
"step": null,
"menuItems": [],
"menuLabels": [],
"allowCustom": false,
"maxLength": null,
"pattern": null,
"isArray": false,
"arraySize": 1,
"dimensions": 1,
"description": "autoincr - This increments the name before saving. Be careful about turning this option off because there is no warning or confirm dialog to prevent you from overwriting an .ocapt file.",
"tooltip": "",
"help": "",
"units": "",
"examples": [],
"isReadOnly": false,
"isAdvanced": false,
"isHidden": false,
"isAnimatable": true,
"isExpression": false,
"isPython": false,
"dependsOn": [],
"affects": [],
"linkedTo": [],
"expressionLanguage": "",
"defaultExpression": "",
"commonExpressions": [],
"order": 0,
"isVisible": true,
"conditionalDisplay": null,
"isValid": true,
"validationErrors": [],
"lastUpdated": "2025-08-08T00:37:40.464Z",
"rawData": {},
"sourceElement": null
},
{
"id": null,
"name": "Save All Data to File",
"label": "Save All Data to File",
"group": "General",
"page": "",
"type": "float",
"dataType": "number",
"style": "",
"defaultValue": null,
"minValue": null,
"maxValue": null,
"step": null,
"menuItems": [],
"menuLabels": [],
"allowCustom": false,
"maxLength": null,
"pattern": null,
"isArray": false,
"arraySize": 1,
"dimensions": 1,
"description": "savecaptfile - This saves the point weighting of all points to the .",
"tooltip": "",
"help": "",
"units": "",
"examples": [],
"isReadOnly": false,
"isAdvanced": false,
"isHidden": false,
"isAnimatable": true,
"isExpression": false,
"isPython": false,
"dependsOn": [],
"affects": [],
"linkedTo": [],
"expressionLanguage": "",
"defaultExpression": "",
"commonExpressions": [],
"order": 0,
"isVisible": true,
"conditionalDisplay": null,
"isValid": true,
"validationErrors": [],
"lastUpdated": "2025-08-08T00:37:40.464Z",
"rawData": {},
"sourceElement": null
},
{
"id": null,
"name": "Save Selected Points to File",
"label": "Save Selected Points to File",
"group": "General",
"page": "",
"type": "float",
"dataType": "number",
"style": "",
"defaultValue": null,
"minValue": null,
"maxValue": null,
"step": null,
"menuItems": [],
"menuLabels": [],
"allowCustom": false,
"maxLength": null,
"pattern": null,
"isArray": false,
"arraySize": 1,
"dimensions": 1,
"description": "savesel - This saves the point weighting only for the points that are selected in the viewport.\t\n you must be editing this particular in the Viewport for this selection to apply to this .",
"tooltip": "",
"help": "",
"units": "",
"examples": [],
"isReadOnly": false,
"isAdvanced": false,
"isHidden": false,
"isAnimatable": true,
"isExpression": false,
"isPython": false,
"dependsOn": [],
"affects": [],
"linkedTo": [],
"expressionLanguage": "",
"defaultExpression": "",
"commonExpressions": [],
"order": 0,
"isVisible": true,
"conditionalDisplay": null,
"isValid": true,
"validationErrors": [],
"lastUpdated": "2025-08-08T00:37:40.464Z",
"rawData": {},
"sourceElement": null
}
],
"parameterGroups": {},
"codeExamples": [],
"pythonExamples": [],
"expressions": [],
"commonInputs": [],
"commonOutputs": [],
"relatedOperators": [],
"workflowPatterns": [],
"images": [],
"videos": [],
"assets": [],
"keywords": [
"capture",
"used",
"weight",
"points",
"geometry",
"regions.",
"weighting",
"scheme",
"described"
],
"tags": [
"SOP",
"TouchDesigner",
"Capture"
],
"searchWeight": 1,
"contentHash": "",
"processingDate": "2025-08-08T00:37:40.464Z",
"processingVersion": "1.0.0",
"isValid": true,
"validationErrors": []
}