-
-
Notifications
You must be signed in to change notification settings - Fork 21.8k
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
Plugin icon not displayed #102997
Comments
Regression from #101489 cc @RandomShaper |
This can't be from #101489 as it doesn't occur in |
Yeah I just realized that now by checking the merge date, but since doing a checkout one commit before it was working and on that commit not working, it made me say that. |
If you're able to bisect this it would be very helpful since you can confirm this |
So for me it does not work on beta3 (06acfcc), but it does work in beta2. I double checked and did a full bisection and it's indeed a regression from #101489 Can you retest @Saulo-de-Souza to see if it is indeed working for you in beta3 ? Maybe there was some cache keeping the icon or something like that ? |
I did a new test, but now creating a new project in beta 3 and as you said, it really should be cache or something like that, because now it didn't work in beta 3 either. What do I do? Do I need to change what I published here? Or are you already aware? |
You should update your issue report with the new information |
Done! Thank you! |
Tested versions
System information
Windows 11 - Vulkan 1.3.280 - Forward+ - Using Device #0: NVIDIA - NVIDIA GeForce RTX 3070
Issue description
The plugin icon is not displayed in Godot 4.4 beta 3 and beta 4 as shown in the images below:
Steps to reproduce
Create a new project. Create a main scene. Go to assetLib and download a plugin (I downloaded the Audio Manager 3D plugin). Activate the plugin and add it to the scene. You will see that the icon does not display both when choosing in the node tree and in the main scene.
Minimal reproduction project (MRP)
plugin_icon.zip
The text was updated successfully, but these errors were encountered: