-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Source assets tab is laggy #15
Comments
Same problem here, it is pretty much unusable as Unity becomes unresponsive. I can just take a screenshot of the top size assets and then that's about it. |
Same issue here. Makes it unusable |
卡蒙了, |
说实话不需要缩略图的。只需要显示名字分好类,然后再好一点就是点击可以看到索引 的内容,不需要把视图显示出来 |
Bring in fixes for the SourceAsset tab from an internal fork of the build report inspector. -Set a maximum number of assets, if surpased it won't display (rather than letting Unity freeze) -Collapse objects of the same type from the same asset together (tool tip shows the matching count) -show the build type (Player versus assetbundle) available on newer versions of Unity. -Show the build output path -use yellow for errors because red text is pretty unreadable on the dark theme. This should fix: #15 And improve situation for: #22 TestProject Add a second scene with an audio file so that is a bit more content to see in the report.
I agree this has been quite unusable for large numbers of objects, e.g. for large builds. #39 will fix the SourceAsset tab a lot by collapsing redundant entries together. And if the number of entries it is large it simply won't display so that other parts of the build report UI can be used. Beyond that the build report still gets quite large so there can be some performance problems but i will close this ticket when that PR lands and we can address further bottlenecks if new issues are opened. |
With this tab opening onto a page that is drawing thousands of included assets it's unusable in my project.
Editing the script to land on the collapsed importer type view makes it vaguely usable, but it seems this isn't very scalable.
This should use a list view functionality where it's only actually displaying the few visible elements.
The text was updated successfully, but these errors were encountered: