[Bug 57801] New: Marble Marcher Community Edition: Startup error "Compute shader compilation error."

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57801

Bug ID: 57801
           Summary: Marble Marcher Community Edition: Startup error
                    "Compute shader compilation error."
           Product: Wine
           Version: 10.0
          Hardware: x86-64
               URL: https://github.com/WAUthethird/Marble-Marcher-Communit
                    y-Edition/releases/download/1.4.6/MMCEwin64.zip
                OS: MacOS
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]

% wine --version
wine-10.0

% openssl sha256 MMCEwin64.zip
SHA2-256(MMCEwin64.zip)=
a4bad1ac87cce73cb71ca718dabb72683af8976bf1ee943ee6e5574325bfb990

Whenever I try to start Marble Marcher Community Edition, I keep getting
multiple error messages that say "Compute shader compilation error."

Steps to reproduce:
1. Download and extract the linked ZIP file.
2. Start `wine MarbleMarcher.exe`

Actual results:
Error message on startup: "Compute shader compilation error."

Expected results:
Startup works properly.

[Bug 57801] Marble Marcher Community Edition: Startup error "Compute shader compilation error."

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57801

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |download

[Bug 57801] Marble Marcher Community Edition: Startup error "Compute shader compilation error."

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57801

Maotong Zhang  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from Maotong Zhang  ---
Created attachment 78021
  --> https://bugs.winehq.org/attachment.cgi?id=78021
test-app

wine-10.0
Use the command wine MarbleMarcher.exe inside the /drive_c/MMCEwin64/ folder of
the container
There will be no problems or errors in the test, and it can be run.
Can provide logs to view issues

[Bug 57801] Marble Marcher Community Edition: Startup error "Compute shader compilation error."

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57801

--- Comment #2 from Tobias (:Tobbi) Markus  ---
(In reply to Maotong Zhang from comment #1)
> Created attachment 78021 [details]
> test-app
>
> wine-10.0
> Use the command wine MarbleMarcher.exe inside the /drive_c/MMCEwin64/ folder
> of the container
> There will be no problems or errors in the test, and it can be run.

I copied the MMCEwin64 directory into my /drive_c/ directory and was facing the
same issue.
> Can provide logs to view issues

Do you mean that I should provide logs or that you will provide logs for
whatever reason?

In any case: The issue remains. I'm assuming it's dependent on the host OS and
the shader compiles fine on your system.

[Bug 57801] Marble Marcher Community Edition: Startup error "Compute shader compilation error."

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57801

--- Comment #3 from Maotong Zhang  ---
Can you provide the running log

[Bug 57801] Marble Marcher Community Edition: Startup error "Compute shader compilation error."

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57801

Zeb Figura  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #4 from Zeb Figura  ---
I don't get that error on Linux (although it also doesn't seem to render
properly? I just get a white screen...)

It's a GL game, and it's being run on Mac, so I suspect it's just the Mac GL
driver being broken again. Chances are they'll never fix it, so it'll need some
community-driven emulation layer, whichever one that ends up being. Probably
out of the scope of Wine either way. Not sure if we should resolve this as
NOTOURBUG or WONTFIX...

(It could always be something else, but I think it's a pretty sure thing...)