-
-
Notifications
You must be signed in to change notification settings - Fork 20.1k
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
Exported Web Project does not work on Linux with Mesa 22.2+ #68180
Comments
I've tested the project on the same system and browser versions listed and I can't reproduce this. |
When I am working with godot I am actually always building from source, using the master branch. Here I used the official beta, to make sure my build process is not broken in any way. So, does anyone know about any build cache/temporary files/config file which could cause this? The thing is, that it also worked for me, up until ~2 weeks ago. And since then, I am stuck with the shown errors. |
I think those are the only folders that could be the culprit. You can try cleaning Just to confirm, this is on the non-mono version, and the web export prints If that doesn't resolve it, can you please upload a build showcasing these errors to itch.io? Could this be a gpu driver issue? |
Unfortunately this didn't helped either.
non-mono version and yes, it prints https://nico-g.itch.io/godot-bug-testing?secret=QyWWf5yhEeVCqjMq1imFUYBmuA But I did enable This is the exported project:
.... I am open for ideas on how to test it. Additionally Ive updated my system information in the OP |
itch's SharedArrayBuffer support only works in Chrome I think, so if the above test was in Firefox it may be why. |
Thanks! I got it running with Chromium. But unfortunately the issue is still there for me. (Btw, the uploaded project was created with the self-contained feature and a fresh project) EDIT: As I said earlier, It feels like the web export stopped working roughly 2 weeks ago. I have taken a look at the mesa drivers in the arch linux repository. The package says, it was last updated on "2022-10-14". That would also match your suspicion about a faulty GPU driver ... Maybe there is a problem with the mesa drivers. |
What is the first broken mesa version? There's a few versions in between 22.1.7 and 22.2.1: https://archive.archlinux.org/packages/m/mesa/ |
I've now tested
Iv'e also tested the
The error also occurs with version EDIT 1: Correction of version numbers EDIT 2: Upgraded to EDIT 3: Upgraded to |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
I have a similar problem with Godot 4 Beta 7. The only difference for me is that I do not get spammed with messages after the initial error. EDIT: removed link to project website, since I need to revert to a previous godot version. |
I've just compiled the newest version from master v4.0.beta.custom_build [a7937fe]. And it seems to get better ... I do see the capsule now, but there are still errors in the console output Current system information:
|
I can confirm that Godot 4 beta 8 solved the gray screen issue I was experiencing with Godot 4 beta 7. |
Can not confirm. |
My project is 2D only, since the screenshot from your comment shows a 3D object, maybe this is a hint to the discrepancies? |
The issue also appears to me with an empty 2DNode as the main scene. |
Are you using the gl_compatibility renderer in both cases? The fragment shader error is very interesting I can see the shader printout from your original post says that
In either case it is getting set to a value that it should never be set to and we will need to figure out why. Would you be okay compiling and running a custom build that prints a bunch more debug info? Also would be useful to test from a more up-to-date build as a7937fe does not include #69901 which is the PR I think may help |
The post of #68180 (comment) was done using the newest available version from master at this time. And I tested it again with the now newest version v4.0.beta.custom_build [2e657e5] and the issue is still there.
Where can I check that?
Good point, I didn't
Sure, but someone has to tell me what I should do and where I should do it. |
Is this still reproducible in 4.0 RC 3 or later? |
I'm getting console errors and extremely long load times (if it ever starts) right out of the box on RC4. This is with a project that is just one scene with the godot icon in it. This is on the Arc browser on MacOS (although I also tried other browsers with similar results). I haven't tested on Windows or Linux versions of Godot, when I get back where I can get to my VM I can try it on other builds to see if it's better. |
You seem to be experiencing #70691. Which is a macOS specific issue. This issue is Linux/mesa specific. |
I'm having the same issue, on archlinux, with a 6700XT and up-to-date drivers, when using spotlights and omnilights. |
Godot version
v4.0.beta4.official [e675154]
System information
Chromium Version 107.0.5304.87 (Official Build) Arch Linux (64-bit)
Firefox 107.0b8
OS: Arch Linux
KERNEL: 6.0.6-arch1-1KERNEL: 6.0.7-arch1-1KERNEL: 6.0.8-arch1-1KERNEL: 6.0.9-arch1-1
CPU: AMD Ryzen 7 3700X 8-Core
GPU: AMD Radeon RX 6900 XT (navi21, LLVM 14.0.6, DRM 3.48, 6.0.6-arch1-1)
GPU DRIVER: 4.6 Mesa 22.2.1
Issue description
When I try to start the provided minimal project as a web project, the mesh in the scene is not visible and the browser console is showing this error right after the site loaded:
![Screenshot from 2022-11-02 20-01-35](https://user-images.githubusercontent.com/18660100/199584004-2ab31cd9-374c-46c3-b3d3-2688cce7d7c8.png)
After that, the console is flooded with these error messages:
![Screenshot from 2022-11-02 19-49-14](https://user-images.githubusercontent.com/18660100/199581514-45acf4c0-b883-4e7a-9dbe-136e08f34df7.png)
Steps to reproduce
Use the official beta4 with the provided templates and try to start the provided project as a web application
Minimal reproduction project
beta4_webtest.zip
The text was updated successfully, but these errors were encountered: