Open wagfeliz opened 1 year ago
wagfeliz
commented
1 year ago Update: I just restart the system, and it didnt fix it. So it turns out it have nothing to do with sunshine or remote, my suspect is now the use of gridmap in godot 4.1 because I was able to open another project that dont use it and it works fine, is this a know issue ?
wagfeliz
commented
1 year ago Update: Ok, I was able to make it works, first I had to manually rename the scene that have a gridmap, ( but now I dont think it have a relation with the gridmap at all ). Then I open in godot, it works because it cant instance the scene, I notice the light component have a warning saying it dont work on compatibility mode, then I change the project to foward++, and now it works... It seems if you create a scene with light in a project that is in compatibility mode you break godot ? I will try to create a empty project with this and post here ok.
Calinou
commented
1 year ago In my experience, remote desktop applications often make it difficult to use applications that require 3D acceleration. I'm not sure if this is a Godot issue – it sounds like a configuration issue with Sunshine or your X11 server.
PS: Code blocks should use triple backticks like this (with an optional language name for syntax highlighting):
```gdscript code here ```
I edited your post accordingly, but remember to do this in the future :slightly_smiling_face:
dvarrui
commented
1 year ago I recently updated my OpenSUSE OS and godot started giving this error when starting it.
❯ ./bin/Godot_v4.1.2-stable_linux.x86_64
Godot Engine v4.1.2.stable.official.399c9dc39 - https://godotengine.org
OpenGL API 4.6 (Core Profile) Mesa 23.2.1 - Compatibility - Using Device: Intel - Mesa Intel(R) Iris(R) Plus Graphics (ICL GT2)
================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.1.2.stable.official (399c9dc393f6f84c0b4e4d4117906c70c048ecf2)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] /lib64/libc.so.6(+0x3f190) [0x7f1e3e43f190] (??:0)
-- END OF BACKTRACE --
================================================================
[1] 7276 IOT instruction (core dumped) ./bin/Godot_v4.1.2-stable_linux.x86_64Reading the messages associated with this issue I have tried starting godot as follows:
❯ ./bin/Godot_v4.1.2-stable_linux.x86_64 --rendering-driver vulkan
Godot Engine v4.1.2.stable.official.399c9dc39 - https://godotengine.org
Vulkan API 1.3.255 - Forward+ - Using Vulkan Device #0: Intel - Intel(R) Iris(R) Plus Graphics (ICL GT2)It works fine! Thanks!
akien-mga
commented
1 year ago @dvarrui That seems to be an unrelated issue, the OP is having a crash in a specific project with a scene using GridMap.
Yours is the Mesa OpenGL driver seemingly being broken so it can't even show the project manager, IIUC. This should be reported to upstream Mesa, especially if it used to work fine but it broke after an update: https://gitlab.freedesktop.org/mesa/mesa
I have Mesa 23.1.7 locally and can't reproduce the issue.
akien-mga
commented
1 year ago It seems if you create a scene with light in a project that is in compatibility mode you break godot ? I will try to create a empty project with this and post here ok.
@wagfeliz Were you able to isolate a project that triggers the issue? It's very difficult to debug further with it as we can't reproduce the issue and there isn't useful debug information in the stacktraces.
Godot version
4.1.1
System information
Linux
Issue description
Godot is crashing for me today, I tried both 4.1 and 4.1.1, it opens the project selection screen, and if I select a project that have a 3d scene showing it crashes, if I select a project with pure code it works. The log above, shows it cant open a new opengl client, I am not sure why. I think if I restart the system it will start to work again, so I wander if its a bug of not releasing something or checking for something it should not be checking.
A note, I use godot for a while and its the first time it happens, something I think could be causing it its the use of remote development ( with sunshine in my case ), maybe its not releasing the opengl instance somehow ? Is it possible to have a parameter to ignore this error ?
Steps to reproduce
Not sure, I suspect that if you use sunshine+monligth to dev remotly it will get into it eventually, but I am not sure this is the case.
Minimal reproduction project
I tried several projects, the ones that got problem was anything that shows a rendering screen in startup, when opening a project that opens the screen in the code mode, it works until I open a screen.