Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.50f1
2022.3.61f1
6000.0.46f1
6000.1.0b14
6000.2.0a8
6000.3.0a1
6000.4.0a1
Issue ID
UUM-102588
Regression
No
Create Node window appears on the top left corner of the Editor when opening window with space keyboard shortcut after selecting a Context
Steps to reproduce:
1. Create a project
2. Create > Visual Effects > Visual Effect Graph
3. Open newly created VFX Asset
4. Select any of the default templates
5. Select a Context
6. Press space keyboard shortcut on the VFX Graph window
7. Observe the opened create Node window
Actual results: Create Node window appears in the top left corner of the Editor
Expected results: Create Node window appears in the VFX Graph window
Reproducible with versions: 2021.3.50f1, 2022.3.61f1, 6000.0.46f1, 6000.1.0b14, 6000.2.0a8
Tested on (OS): macOS Sequoia 15.3.1 (Intel)
Note:
- Created Node is difficult or impossible to find in graph view
- Does not seem to reproduce with SG
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note:
Forward-ports for this version need to be handled at a later time.