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.

Sign up for GitHub

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

Jump to bottom

Linux Editor can't open scene #185

Open
ArtemkaKun opened this issue Oct 1, 2024 · 5 comments
Open

Linux Editor can't open scene #185

ArtemkaKun opened this issue Oct 1, 2024 · 5 comments

Comments

@ArtemkaKun
Copy link
Contributor

Describe the bug
I'm on dev branch. I'm on Arch Linux, using .NET 8. I can build Editor without an error. I can start the Editor and create and run a new project. The problem is when I try to open the newly created project - it loading stuff and then exists with error. The last things I see in the console are:

Attempting to Import Defaults/Grid.shader!

Process finished with exit code 139.

To Reproduce

  1. Switch to development branch.
  2. Build and start the Editor.
  3. Create a new project.
  4. Try to open the project.

Expected behavior
The Editor opens and shows me a scene and other normal stuff.
@michaelsakharov
Copy link
Contributor

@sinnwrig Can you reproduce this?
It seems to be fine for me on windows.

@sinnwrig
Copy link
Contributor

sinnwrig commented Oct 1, 2024 •
edited
Loading

This seems like it's a problem with some native compiler libraries. I'd need more info on the device specs to be sure, as ARM binaries are untested and might give you some trouble. Your glibc version might also be incompatible, but I can't verify what version I compiled the binaries with at the moment. If you'd like, you can try your hand at compiling our SPIRV-Cross binaries and DXC binaries on your system and replacing the corresponding libraries for your respective system under the runtimes folder in your build output.

@sinnwrig
Copy link
Contributor

sinnwrig commented Oct 15, 2024 •
edited
Loading

@ArtemkaKun This issue should be fixed in latest branch of development, but I will leave it open in case it isn't. There are still some known problems with Assimp which might cause the editor to repeatedly throw exceptions, but if you can confirm that the editor launches on Arch this issue should be fixed.

@ArtemkaKun
Copy link
Contributor Author

Thanks for your work, but I have no time right now to test the fix

@sinnwrig
Copy link
Contributor

No pressure! I'll leave this issue open for the meantime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@michaelsakharov @ArtemkaKun @sinnwrig