godotengine / godotengine/godot
Dragging a texture to the inspector changes it to show the last object in the scene (viewport conflict)
- Dominant language
- C++
- Stars
- 117k
- Forks
- 26.8k
- PR merge metrics
- PR metrics pending
Description
### Tested versions
Reproducible between ~3.4 and 4.3
### System information
Fedora 40 (KDE Plasma, Wayland) - Godot v4.3.stable.mono
### Issue description
Dragging a newly-imported texture over the viewport and into the inspector causes the inspector to switch to an object of the scene _(the object gets selected as well)_
This only happens when getting the "Texture detected as used in 3D" notification
I have had this issue for years and I can reproduce it across operating systems and projects, but this issue is sometimes triggered and sometimes not for no apparent reason. I would recommend following the "steps to reproduce" in a scene that has tons of meshes/scenes filling the editor viewport.
Notably, this sometimes also happens after the drag is successful _(when the drag action is finished and the editor reimports the texture as part of enabling mipmap)_
[Screencast_20241028_004305 (trimmed).webm](https://github.com/user-attachments/assets/0e626a3b-4695-427b-940a-32c3a02b8f70)
_(apologies for the laggy recording, the screen recorder on KDE sucks)_
### Steps to reproduce
1. Create a 3D project
2. Make sure your filesystem is on the bottom left
3. Create a scene and add a few child nodes to it _(add in a model)_
4. Import in a texture _(make sure the editor doesn't know its going to be used for 3D)_
5. Create a new `StandardMaterial3D` and open it in the inspector
6. Drag the texture from the filesystem over the viewport and into the material inspector
If it doesn't happen right away, keep adding textures into the material _(only seems to happen when the material already has a texture assigned to it?)_
***The issue seems to occur more when accidentally dragging the texture over a model/scene.***
### Minimal reproduction project (MRP)
N/A
Contributor guide
Assessment
This issue has not been assessed yet.