-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Crashed on New Orchestration #335
Comments
What operating system are you using and is the Godot 4.2.2.stable version the official build @Deadhyena ? You also mention 2.0.1.stable, that isn't available on the Asset Library yet -- did you install 2.0.stable and then upgrade? |
@Naros Windows 11 23H2, Godot 4.2.2 via Steam |
I just installed Godot 4.2.2.stable via steam and downloaded the addon fro the asset library, worked fine. Did you make sure when you installed the plugin from the asset library that you unchecked the See https://docs.vahera.com/orchestrator/getting-started/introduction/installation-guide |
Did you make sure when you installed the plugin from the asset library that you unchecked the Ignore asset root checkbox? I just opened my projects (with installed Orchestrator) using the non-Steam version of Godot and everything works fine, however Steam version refuses to work with Orchestrator even after reinstallation. P.S. I think I'll just use the non-Steam version for now and call it a day |
When it crashes, is there anything logged in the Windows Event Viewer under the |
@Naros here are test results, I hope that helps. |
For anyone who has the same issue but wants to stay on the Steam platform (for example to keep time tracking), I found a weird workaround.
Orchestrator is working alright now. |
Describe the bug
Godot keeps crashing when creating a new orchestration, no matter if it's a new file or an existing one.
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
Godot full version
4.2.2 stable
Orchestrator version
2.0.1 Stable
Additional information
No response
The text was updated successfully, but these errors were encountered: