Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.5.2
1.6.1
1.7.3
Issue ID
UVSB-1398
Regression
No
Performance: Frame drop when a large embedded graph is visible in the inspector window.
See here for more details (or see attached video): [https://discord.com/channels/372898201088426004/372899380367458329/826160411232698428]
Unity 2021.1f0, Windows 10.
Repro steps:
# Open a project
# Set up a gameobject with an embedded script or state graph
# Edit the graph and make it as large as possible (to make the effect as noticeable as possible)
# Have the inspector for the gameobject visible
# Have the graph window visible
# Drag around on the graph window, notice how slow / fast it is
# Hide the inspector or the machine component on the inspector
# Drag around again to notice how much faster it is
Reported by Discord user @PurerLogic
!image-2021-05-05-16-34-06-296.png|width=881,height=224!
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
- Animator Controller throws MissingReferenceException after undoing Layer Creation
- Full stack trace is always printed when an exception occurs in an IL2CPP build
- Licensing Client fails to launch when opening Unity Hub (licensing client path is not found)
- Licensing Client fails to launch when opening Unity Hub
- Different custom Shader behavior when GPU Resident Drawer is enabled
Resolution Note:
This will be fixed with the integration of GTF in 2023.1. Right now, fixing this is really risky.