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

Command line export doesn't work in Windows 10 for Godot 3.1.2 due to error code 12 #34148

Closed
2shady4u opened this issue Dec 6, 2019 · 5 comments
Assignees
Milestone

Comments

@2shady4u
Copy link
Contributor

2shady4u commented Dec 6, 2019

Godot version:

3.1.2 (the official one)

OS/device including version:

Windows 10

Issue description:

Exporting a Godot project (even a brand-new one) doesn't work in the command line as it returns an error:
failure_export_312

Steps to reproduce:

  • Make a new Godot Project in 3.1.2
  • Create some node (in my case I created a Node2D) and configure it to be the main scene.
  • Make an export preset for windows: "Windows Desktop"
  • Run following command in powershell (or any other cmd tool):
    godot -e -v --export-debug "Windows Desktop" build/test.exe
  • Exporting fails due to error code 12

Downgrade to Godot v3.1.1 and do the exact same steps. The export completes successfully without any issues... as seen here:

succes_export_311

@akien-mga akien-mga added this to the 3.2 milestone Dec 6, 2019
@akien-mga akien-mga self-assigned this Dec 6, 2019
@akien-mga akien-mga modified the milestones: 3.2, 3.1 Dec 6, 2019
@akien-mga
Copy link
Member

akien-mga commented Dec 6, 2019

Tested on Linux, it seems to work fine there:

~/tmp/godot/stable/3.1/Godot_v3.1.2-stable_x11.64 -e -v --export-debug "Linux/X11" build/test.x86_64

Note that I created the build folder beforehand. If I don't and the directory is missing, I get:

ERROR: _fs_changed: Project export failed with error code 9.
   At: editor/editor_node.cpp:495.

Maybe that's your issue?

It seems to fail the same in 3.1.1 so that wouldn't be a regression.
Edit: Well maybe not since you say it works for you with 3.1.1.

I'll try to boot up Windows 10 to check if I can reproduce it with PowerShell.

@2shady4u
Copy link
Contributor Author

2shady4u commented Dec 6, 2019

I also get error code 9 when I don't make the folder beforehand.
(in both 3.1.1 and 3.1.2)

However, the error code 12 only appears when I try to export with 3.1.2 in Windows 10.
I didnt try this yet with Linux or MacOsX so I have no idea if those OS' have the same issue...

@2shady4u
Copy link
Contributor Author

2shady4u commented Dec 6, 2019

So on Ubuntu LTS (18), I get following behaviour:

Godot v3.1.1, exporting to Windows:
linux-311

Godot v3.1.2, exporting to Windows:
linux-312

So it works on Linux (except for the memory leak, but whatever)

@2shady4u 2shady4u changed the title Command line export doesn't work in 3.1.2 Command line export doesn't work in Windows 10 for Godot 3.1.2 due to error code 12 Dec 11, 2019
@garyritchie
Copy link

Export path seems relative to project location.

Example: godot -v --export "Windows Desktop" ../BUILD/LTG.exe --path ENGINE/

This works for me where I have ENGINE/project.godot and BUILD/ within my repo. Tell all your friends and save 'em some frustration.

@2shady4u
Copy link
Contributor Author

@garyritchie
Thanks that did the trick!

Also shout-out to Calinou for adding this to the --help command (#34589) to spare future generations from running into this issue.

Closing this...

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