-
-
Notifications
You must be signed in to change notification settings - Fork 22k
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
Using the new --import
parameter in combination with --build-solutions
or --headless
shows still plugin loading errors
#92833
Comments
--import
parameter in combination with --build-solutions
shows still plugin loading errors--import
parameter in combination with --build-solutions
or --headless
shows still plugin loading errors
After some testing, I was able to reproduce this problem. MRP project: I'm pretty certain that the problem is caused by the fact that the I tried the same project and command line with the fix from #92303 it worked perfectly. |
@Hilderin thanks for the feedback 👍 |
I get the same behaviour with the plain gdscript version and the godot-jolt add on installed, it hangs forever the first time. It also doesn't matter if I use |
I tested on 4.3 master branch and I'm able to reproduce the problem with a bare project with only one scene and the godot-jolt addon. I also tested the same project with the PR #93972 and removing the .godot folder and the command line does not hang anymore. I tested MRP (I removed the android and ios library of jolt to fit in a zip less then 25mo): |
I'm also having this issue while running with --import-only --headless. |
Tested versions
v4.2.2.stable.mono.official [15073af]
System information
Windows
Issue description
I tested the new
--import
option to remove the Godot cache rebuild hack.But it shows still the same plugin loading errors when using in combination with
--build-solutions
$GODOT_BIN --path ./ --import --build-solutions --headless
Using the options in separate calls works without showing any errors.
And both option do loading the plugins, but it should only reimport resources or compile the c# classes.
More critical is the usage of
--build-solutions --headless
it runs editor forever and needs to be manually killed.From the documentation:
It is not a build only it runs the editor too.
Steps to reproduce
run this command
The editor finally hangs, I would expect the process to do only reimport and compile the c# classes.
Even if it is expected that with
--build-solutions
the editor started it produces the errors and makes--import
uselessat least using
--import --headless
shows also the errorsMinimal reproduction project (MRP)
n/a
The text was updated successfully, but these errors were encountered: