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

Shader materials are not imported by the headless build #39188

Closed
Dragoncraft89 opened this issue May 31, 2020 · 2 comments
Closed

Shader materials are not imported by the headless build #39188

Dragoncraft89 opened this issue May 31, 2020 · 2 comments

Comments

@Dragoncraft89
Copy link
Contributor

Dragoncraft89 commented May 31, 2020

Godot version:
3.2.1 headless build

OS/device including version:
Debian 10. Probably every Linux/BSD

Issue description:
Attempted to export the project in the CI/CD. We don't have the .import directory pushed to VC, as this is optional according to the docs.

Therefore before the game can be exported, some files need to be imported. This works fine for most files, but shader materials in escn files are ignored.

For comparison, I've included both files in a zip: (Opening in a normal text editor is enough to see that the headless import lacks the shader)
models.zip

It seems like shader materials are just stripped from the imported file in the headless build, as the same model works with a spatial material.

Steps to reproduce:
Extract the attached sample project. Export the project with godot --export "Test" test and run it with "./test". The material should be correctly loaded.

Now, rm -r .import/ to force a reimport. Export the project with godot_headless --export "Test" test_headless and run it. The material should be missing.

Minimal reproduction project:
headless_shader_import.zip

Edit: fixed project zip

@afk-mario
Copy link

This happened to me, it's weird because it worked on 3.4 and stopped working on 3.5

@Calinou
Copy link
Member

Calinou commented Jan 16, 2023

Duplicate of #55711.

@Calinou Calinou closed this as not planned Won't fix, can't repro, duplicate, stale Jan 16, 2023
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

3 participants