Search Issue Tracker
Fixed
Votes
1
Found in [Package]
Issue ID
GTFB-1372
Regression
No
Blocknodes available to ContextNode are not properly displayed when UseWithContext is set to a parent ContextNode
Steps to reproduce:
1. Open "Assets/MyGraph/IssueGraph"
2. Create ChildContext Node "Create Node -> ChildContext"
3. Press "Add a Block" and observe the available options
Reproduction steps:
1. Open the attached “IN-112334_Repro.zip“ project
2. Open the “Assets/IssueGraph.graph“ Graph
3. Create “ChildContext” Node (Create Node -> ChildContext)
4. Press "Add a Block" inside the “ChildContext” Node
5. Observe the available options
Expected result: “BlockOne“ and “BlockTwo“ Nodes are available for selection
Actual Result: None or only one of the Block Nodes is available
Reproducible with: 0.1.0-exp.1, 0.3.0-exp.1 (6000.2.3f1, 6000.3.0b1)
Reproducible on: M1 Max MacOS 15.5 (Tested by CQA), Windows 10 (Reported by the user)
Not reproducible on: No other environment tested
Notes:
- In version 0.3.0-exp.1, neither BlockOne nor BlockTwo nodes are present.
- In version 0.2.0-exp.1 and earlier, only the BlockTwo node is available; BlockOne is not present.
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
inayat441
Sep 05, 2025 21:23
Yeah, this is a known quirk with the Graph Toolkit. When you set a BlockNode to use a parent ContextNode with UseWithContext, the “Add Block” menu often won’t show it under the child contexts. A workaround is to tag the block with the exact ContextNode type you’re actually using instead of just the base. If you’ve got multiple child contexts, sometimes people create small wrapper blocks or helpers to make them appear. Unity’s filtering with UseWithContext isn’t perfect right now, so it’s more of a limitation than something you’re doing wrong.