Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related issue: #31177, #31168
Description
The PR introduces a user-customizable sub-build system, which allows for automatic control flows based on the build steps of the input materials. This is already advanced programming in TSL, but it is crucial for the variable intents to remain the same regardless of the input material being used.
The PR also replaces the
namespace()approach that did not allow for layering and deep detection of sub-builds if any dependent node usesFn.once( subBuilds )allowing to generate different flows automatically if necessary.Example in POSITION
A: This creates a simple
positionWorldin vertex-stage which is sent to colorNodeB: Now if I need to modify the object's position using
positionWorld, the system will have to identify the flow change and recreate thepositionWordbased on the updates, based on the user's intention.The system can also have different sub-build layers so that the node can have different codes if this is used in
colorNodeor innormalNodeorpositionNode, thus unifying the variables across user intent.Sub-Build System Test Code
The code below is for testing purposes only.
Code Generated