Search Issue Tracker
Fixed
Fixed in 6000.4.1f1, 6000.5.0a7
Votes
0
Found in
6000.4.0b6
6000.5.0a7
Issue ID
UUM-133642
Regression
No
BlockNode.contextNode is not defined when initializing options and ports
How to reproduce:
1. Open the “ContextNodebugTest.zip” project
2. In the Project tab, open the “IssueGraph“
3. Delete all nodes inside the “MyContext” node and then clear the Console
4. Press “Add a Block“ and then add the “MyBlock“ block
5. Observe the Console
Expected result: “(Options) contextNode is defined“ and “(Ports) contextNode is defined“ are logged
Actual result: “(Options) contextNode is not defined“ and “(Ports) contextNode is not defined“ are logged
Reproducible in: 0.1.0-exp.1, 0.3.0-exp.1 (6000.2.0f1, 6000.3.0b1)
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Note:
- When changing the option values, the contextNode is defined
- When duplicating a block node, the contextNode is defined
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
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
- Advanced dropdown stops applying the Search Filter while the search text remains after clicking the header back Button during a Search
- SRP Batcher ignores ShadowCaster pass when Fallback shader has mismatched CBUFFER layout
- Crash on PolynomialCurve::BuildCurve when calling ParticleSystemRenderer.SetMeshes() with an AnimationCurve containing 9 or more keys
- NullReferenceException is thrown when a Graph Toolkit graph is "saved as"
Resolution Note:
Fixed in 6000.5.0a7
Resolution Note (fix version 6000.5.0a7):
Fixed in 6000.5.0a7
Resolution Note (fix version 6000.4.1f1):
Fixed in 6000.4.1f1