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

Material is not applied on MeshInstance when opening scene #42675

Closed
volzhs opened this issue Oct 9, 2020 · 7 comments
Closed

Material is not applied on MeshInstance when opening scene #42675

volzhs opened this issue Oct 9, 2020 · 7 comments

Comments

@volzhs
Copy link
Contributor

volzhs commented Oct 9, 2020

Godot version:

3.2.4 beta 0cea273

OS/device including version:

Radeon RX570, both GLES2 and GLES3

Issue description:

Assigned material is not applied on MeshInstance after reopening scene.
(Assigning material to material_override works as expected)

Steps to reproduce:

  1. assign a material on MeshInstance
  2. save it
  3. close the scene
  4. reopen the scene

material

Minimal reproduction project:

material bug.zip

@volzhs
Copy link
Contributor Author

volzhs commented Oct 9, 2020

probably @pouleyKetchoupp has a clue...

@akien-mga akien-mga added the bug label Oct 9, 2020
@akien-mga akien-mga added this to the 3.2 milestone Oct 9, 2020
@pouleyKetchoupp
Copy link
Contributor

Ah yes, probably a regression from the software skinning change.

@akien-mga
Copy link
Member

No issue for me in 4040cd3, so it's likely a regression from #40313 indeed.

@pouleyKetchoupp pouleyKetchoupp self-assigned this Oct 9, 2020
@dsnopek
Copy link
Contributor

dsnopek commented Oct 13, 2020

I'm seeing this problem as well, but it's not just affecting the scene in the editor after reload: the material also fails to load when running the game from the editor, or when exported. If I move my material from "Material" to "Material Override", then it appears in game again.

@akien-mga
Copy link
Member

Fixed by #42846.

@Casqade
Copy link

Casqade commented Aug 28, 2023

It seems the issue is back in 4.1.1 stable (Compatibility renderer, both Windows and Linux). Although, it's only reproducible with certain Material values.
In my case, a new StandardMaterial3D with following changes is not applied properly upon reopening scene:

  • unshaded shading mode
  • nearest texture filter
  • disabled texture repeat
material_test.webm

@AThousandShips
Copy link
Member

Please open a new issue with an MRP

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

7 participants