Skip to content
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

AY-3956_Fusion: Ayon menu init #22

Open
ynbot opened this issue Oct 7, 2024 · 2 comments
Open

AY-3956_Fusion: Ayon menu init #22

ynbot opened this issue Oct 7, 2024 · 2 comments
Assignees
Labels
sponsored This is directly sponsored by a client or community member type: enhancement Improvement of existing functionality or minor addition

Comments

@ynbot
Copy link
Contributor

ynbot commented Oct 7, 2024

Please describe the enhancement you have in mind and explain what the current shortcomings are?

ilithian : helloo, the Ayon menu still takes ages to open in Fusion, i understood it was because it was loading in all these addons still, but eventually the idea is that it wouldn't need to be doing this right? so it should get faster then?
m_u_r_p_h_y: <@709309437004873768> can help here?

How would you imagine the implementation of the enhancemenent?

No response

Describe alternatives you've considered:

No response

Additional context:

link to discussion on Discord
(might be a private channel)

This issue was automatically created from Clickup ticket AY-3956

@ynbot ynbot added sponsored This is directly sponsored by a client or community member type: enhancement Improvement of existing functionality or minor addition labels Oct 7, 2024
@BigRoy
Copy link
Collaborator

BigRoy commented Oct 7, 2024

Hard to debug without background information on their specific setup.

The menu entry basically starts its own fuscript Python process when you click it - where - I've found in the past - the majority of the time is spent on loading the Qt libraries depending on your studio configuration. If the Qt libraries are loaded from a network share - you may check out what the speed difference would be if you were deploying these locally (and run the Python executable Fusion uses locally as well.)

@BigRoy
Copy link
Collaborator

BigRoy commented Oct 19, 2024

@m-u-r-p-h-y I understood from client the recent releases have been much better than before and not problematic. Of course we should always keep optimizations in mind, but I believe the issue here isn't necessary to keep open until it actually becomes a problem again.

Can you confirm, and if so, close the issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sponsored This is directly sponsored by a client or community member type: enhancement Improvement of existing functionality or minor addition
Projects
None yet
Development

No branches or pull requests

2 participants