Search Issue Tracker
Active
Under Consideration for 0.3.X
Votes
0
Found in [Package]
0.3.0-exp.1
Issue ID
GTFB-1368
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment