-
-
Notifications
You must be signed in to change notification settings - Fork 21.5k
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
4.1 Mono Regression - Export via CLI is broken (not saving all required resources) #79159
Comments
Tested locally on Linux with the MRP, it seems to export fine for me:
The generated |
@DillonSteyl Can you try the same steps on 4.1 dev/beta/RCs? You can download them here. |
That's interesting. I managed to get it to work using "Export selected resources (and dependencies)" as the export mode, and selecting all of the resources explicitly. None of the other export modes I've tried will do it for me when I'm using the CLI, so maybe related to how resources are "discovered"? |
@akien-mga I can confirm this is only an issue for the MONO version of Godot 4.1. I will update to reflect this |
CC @godotengine/dotnet |
@Calinou The regression was introduced in |
|
Reverting that seems to fix the issue, not sure how it is related. |
That was going to be my guess. The MRP has the export filter But in the .NET module we are only calling Also, since the MRP doesn't contain a C# project or any C# scripts at all, what is even making those calls to |
it calls them probably for the editor tools scripts, notably for those scripts |
I see, we should probably avoid calling it for editor scripts since they are not part of the project. And also, maybe |
I don't think we can (easily) avoid that since this is also part of the initial load and these scripts still need to work like scripts, or the editor just breaks. |
I think what you've done in #79173 is good enough, since we only update EFS to update global classes and the only C# scripts that can be global classes must have a path. |
Godot version
v4.1.stable.mono
System information
Windows 11
Issue description
The automated build system I set up (via Gitlab CI/CD) for exporting my game is no longer working in 4.1.
The
.pck
file generated during export is orders of magnitude smaller than I'd expect, and the game doesn't get past the first frame of the splash screen due to the lack of resources. I've noticed thesavepack
part of the export process seems to skip some steps...Exporting through the UI works as expected, but exporting via CLI (e.g. via something like
godot4 --export-release windows-64bit export/test.exe
) results in the issue described above.Steps to reproduce
.pck
file is either not present or much smaller than expectedMinimal reproduction project
export-cli.zip
The text was updated successfully, but these errors were encountered: