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

MeshInstances Randomly Disappearing/Reappearing In Scene #50630

Closed
WickedInsignia opened this issue Jul 20, 2021 · 3 comments
Closed

MeshInstances Randomly Disappearing/Reappearing In Scene #50630

WickedInsignia opened this issue Jul 20, 2021 · 3 comments

Comments

@WickedInsignia
Copy link

WickedInsignia commented Jul 20, 2021

Godot version

3.3.2 Stable

System information

Windows 10 v20H2, Intel i7 6700, Nvidia GTX1080, 16GB RAM

Issue description

I am experiencing completely random disappearances of MeshInstances. I primarily work with a "Main Scene", where the meshes are part of an inherited scene (the "Mesh Scene") that is then placed into this main scene.
I have encountered MeshInstances disappearing from both a Main Scene and Mesh Scene many times.

When it occurs the MeshInstance may still be selected, but the mesh is no longer visible and Godot does not recognize an assigned mesh in the Inspector. This happens most when both the Main Scene and Mesh Scene are open, and changes to the Mesh Scene have been saved. When going back to the Main Scene, a completely random meshinstance will no longer be visible. Sometimes it is also vice versa

Closing the scene usually rectifies the issue, but I have had meshes stay invisible upon reopening.
The "invisible" mesh is always different....if I have multiple MeshInstances in a scene, it is a completely random guess which one may disappear.

Steps to reproduce

This is a very difficult bug to reproduce since it seems to happen only when a scene reaches a certain amount of complexity or has been worked on for a period of time.

I've managed to capture it happening however. Here is the Mesh Scene in this circumstance:
DisappearingMeshes_Example_01

And here is the Main Scene. I had made some material roughness changes to the "room" mesh and upon going back I found one of the other meshes was randomly missing:
DisappearingMeshes_Example_02

Closing and reopening the project rectified the issue, but I know from experience that once it starts happening it will happen again shortly.

Minimal reproduction project

In an attempt to reproduce the bug I created a file that reflected the contents of the other projects that in appeared in:

  • A "Main Scene" with a "Mesh Scene" placed inside containing all of my MeshInstances for the scene.
  • A GIProbe encompassing the meshes.
  • A Reflection Probe doing the same.
  • A Directional Light.
  • Mutiple MeshInstances in the Mesh Scene with different materials.

I played around with the file for a bit until the bug occurred, and captured the screenshots above.
The file I created (packed into a zip as soon as the bug occurred) is available here:
Disappearing_Mesh_Bug.zip

This file most likely won't exhibit the bug immediately, but playing with the meshes and their materials in the Mesh Scene will coax it out.

@lawnjelly
Copy link
Member

When it occurs the MeshInstance may still be selected, but the mesh is no longer visible and Godot does not recognize an assigned mesh in the Inspector.

I did try the project just in case it was the culling code, but on reflection I think the problem is unlikely to be there - culling wouldn't cause changes within the inspector.

@TokisanGames
Copy link
Contributor

TokisanGames commented Nov 5, 2021

This issue is almost certainly the same as #53374. This report doesn't provide any console errors. Please compare your messages with the ones given in the other issue. You can also try the workaround in the issue, and watch the upcoming PR.

@akien-mga
Copy link
Member

Likely duplicate of #53374 indeed, fixed by #54650.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants