https://bugs.winehq.org/show_bug.cgi?id=42141
Bug ID: 42141 Summary: Star Ruler 2 black screen on macOS and FreeBSD Product: Wine Version: 2.0-rc3 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: acescopezz@gmail.com
Created attachment 56706 --> https://bugs.winehq.org/attachment.cgi?id=56706 error log
The GOG version of Star Ruler 2 doesn't work on FreeBSD and macOS. It works on Ubuntu.
https://bugs.winehq.org/show_bug.cgi?id=42141
acescopezz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Hardware|x86 |x86-64
https://bugs.winehq.org/show_bug.cgi?id=42141
--- Comment #1 from acescopezz@gmail.com --- Created attachment 56707 --> https://bugs.winehq.org/attachment.cgi?id=56707 log with Mac Driver enabled
https://bugs.winehq.org/show_bug.cgi?id=42141
--- Comment #2 from acescopezz@gmail.com --- Created attachment 56708 --> https://bugs.winehq.org/attachment.cgi?id=56708 log with Staging rc3
https://bugs.winehq.org/show_bug.cgi?id=42141
Ken Thomases ken@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ken@codeweavers.com
--- Comment #3 from Ken Thomases ken@codeweavers.com --- My guess is that this is an OpenGL-based (rather than Direct3D-based) game and that it's calling a function from an extension before checking if that extension is available. Since the extension isn't available, the function pointer is NULL, which would explain the crash. Just a guess, though.
That said, though, a +tid,+d3d,+wgl log would help confirm. See https://wiki.winehq.org/FAQ#get_log for instructions on collecting a log.
https://bugs.winehq.org/show_bug.cgi?id=42141
--- Comment #4 from acescopezz@gmail.com --- Created attachment 56710 --> https://bugs.winehq.org/attachment.cgi?id=56710 +tid,+d3d,+wgl log
(In reply to Ken Thomases from comment #3)
My guess is that this is an OpenGL-based (rather than Direct3D-based) game and that it's calling a function from an extension before checking if that extension is available. Since the extension isn't available, the function pointer is NULL, which would explain the crash. Just a guess, though.
That said, though, a +tid,+d3d,+wgl log would help confirm. See https://wiki.winehq.org/FAQ#get_log for instructions on collecting a log.
I added the log you asked for.
https://bugs.winehq.org/show_bug.cgi?id=42141
--- Comment #5 from acescopezz@gmail.com --- Created attachment 56711 --> https://bugs.winehq.org/attachment.cgi?id=56711 +tid,+d3d,+wgl,+seh log with macdrv instead of x11
https://bugs.winehq.org/show_bug.cgi?id=42141
--- Comment #6 from Ken Thomases ken@codeweavers.com --- Thanks for the logs. They confirm that the game is using OpenGL directly and not Direct3D. I'm not seeing anything which indicates exactly which GL function it's trying to call, which is not surprising.
Unfortunately, this means that the game is just not compatible with macOS, at least not 10.7.x with that GPU. Since we rely on the system OpenGL — Wine doesn't reimplement OpenGL in the same way that it reimplements Direct3D — there's no way for us to bridge the gap.
If I'm right about what's going on, the crash is actually a game bug. It's possible (though unlikely) it may get fixed on their side.
https://bugs.winehq.org/show_bug.cgi?id=42141
--- Comment #7 from acescopezz@gmail.com --- (In reply to Ken Thomases from comment #6)
Thanks for the logs. They confirm that the game is using OpenGL directly and not Direct3D. I'm not seeing anything which indicates exactly which GL function it's trying to call, which is not surprising.
Unfortunately, this means that the game is just not compatible with macOS, at least not 10.7.x with that GPU. Since we rely on the system OpenGL — Wine doesn't reimplement OpenGL in the same way that it reimplements Direct3D — there's no way for us to bridge the gap.
If I'm right about what's going on, the crash is actually a game bug. It's possible (though unlikely) it may get fixed on their side.
Thank you for your effort to help me. Would it be better if I would get you some logs off a Mac running Mavericks, with an Nvidea GPU?
https://bugs.winehq.org/show_bug.cgi?id=42141
acescopezz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #56706|0 |1 is obsolete| | Attachment #56707|0 |1 is obsolete| | Attachment #56708|0 |1 is obsolete| | Attachment #56710|0 |1 is obsolete| | Attachment #56711|0 |1 is obsolete| |
--- Comment #8 from acescopezz@gmail.com --- Created attachment 56715 --> https://bugs.winehq.org/attachment.cgi?id=56715 +seh,+tid,+d3d,+wgl,warn+heap log with X11 recent iMac
(In reply to Ken Thomases from comment #6)
Thanks for the logs. They confirm that the game is using OpenGL directly and not Direct3D. I'm not seeing anything which indicates exactly which GL function it's trying to call, which is not surprising.
Unfortunately, this means that the game is just not compatible with macOS, at least not 10.7.x with that GPU. Since we rely on the system OpenGL — Wine doesn't reimplement OpenGL in the same way that it reimplements Direct3D — there's no way for us to bridge the gap.
If I'm right about what's going on, the crash is actually a game bug. It's possible (though unlikely) it may get fixed on their side.
Here's a log from a 2011 iMac with an AMD Radeon HD 6970M 1024 MB. This is without macdrv enabled. I'll post one with macdrv as well.
https://bugs.winehq.org/show_bug.cgi?id=42141
--- Comment #9 from acescopezz@gmail.com --- Created attachment 56716 --> https://bugs.winehq.org/attachment.cgi?id=56716 (compressed) +seh,+tid,+d3d,+wgl,warn+heap log with macdrv Mavericks iMac
had to compress as it was bigger than 5MB
https://bugs.winehq.org/show_bug.cgi?id=42141
--- Comment #10 from acescopezz@gmail.com --- What I don't understand is why it says my OpenGL version is 2.1, because I looked around on Google, and my iMac with that GPU should have OpenGL 4.1, but it could be that I'm not understanding something here.
https://bugs.winehq.org/show_bug.cgi?id=42141
--- Comment #11 from Ken Thomases ken@codeweavers.com --- (In reply to acescopezz from comment #10)
What I don't understand is why it says my OpenGL version is 2.1, because I looked around on Google, and my iMac with that GPU should have OpenGL 4.1, but it could be that I'm not understanding something here.
Thanks for those other logs. Unfortunately, they don't really tell us more. They confirm that the problem wasn't confined to that older version of macOS nor the GPU.
It's reporting OpenGL 2.1 because things got complicated with OpenGL 3.0 and later. It's no longer the case that there's just a version number, there are now different flavors (known as "profiles") of OpenGL. There's the core profile vs. the compatibility profile. Within the core profile, there's the full profile vs. the forward-compatible profile. If a platform offers a high version (e.g. 4.x) of the compatibility profile, an app will get that with no special steps on its part. However, because the core profile has had functionality removed, the app won't get a core profile unless it specifically tells the system it can handled it.
MacOS only offers versions of OpenGL higher than 2.1 in the forward-compatible core profile. Apps won't be able to get OpenGL 4.1 support unless they specifically say they can accept the forward-compatible core profile. The Mac driver supports an app requesting that, but Star Ruler 2 does not do so. So, it's limited to OpenGL 2.1 on the Mac. According to the minimum requirements for the game on its Steam page, that should be enough, but it apparently requires/assumes specific extensions.
https://bugs.winehq.org/show_bug.cgi?id=42141
--- Comment #12 from acescopezz@gmail.com --- (In reply to Ken Thomases from comment #11)
(In reply to acescopezz from comment #10)
What I don't understand is why it says my OpenGL version is 2.1, because I looked around on Google, and my iMac with that GPU should have OpenGL 4.1, but it could be that I'm not understanding something here.
Thanks for those other logs. Unfortunately, they don't really tell us more. They confirm that the problem wasn't confined to that older version of macOS nor the GPU.
It's reporting OpenGL 2.1 because things got complicated with OpenGL 3.0 and later. It's no longer the case that there's just a version number, there are now different flavors (known as "profiles") of OpenGL. There's the core profile vs. the compatibility profile. Within the core profile, there's the full profile vs. the forward-compatible profile. If a platform offers a high version (e.g. 4.x) of the compatibility profile, an app will get that with no special steps on its part. However, because the core profile has had functionality removed, the app won't get a core profile unless it specifically tells the system it can handled it.
MacOS only offers versions of OpenGL higher than 2.1 in the forward-compatible core profile. Apps won't be able to get OpenGL 4.1 support unless they specifically say they can accept the forward-compatible core profile. The Mac driver supports an app requesting that, but Star Ruler 2 does not do so. So, it's limited to OpenGL 2.1 on the Mac. According to the minimum requirements for the game on its Steam page, that should be enough, but it apparently requires/assumes specific extensions.
Thank you very much for taking the time to explain all that. Should I change the status to 'INVALID', since it seems to be a game bug?
https://bugs.winehq.org/show_bug.cgi?id=42141
--- Comment #13 from Ken Thomases ken@codeweavers.com --- (In reply to acescopezz from comment #12)
(In reply to Ken Thomases from comment #11)
Thank you very much for taking the time to explain all that.
You're welcome.
Should I change the status to 'INVALID', since it seems to be a game bug?
You can. I suspect there won't be any more work on this. However, I wasn't really able to determine what was happening _conclusively_. I (or somebody) would probably have to debug interactively (not via logs) to be absolutely sure what's happening. So, you could leave this open in the hopes that somebody will do so, if you want.
https://bugs.winehq.org/show_bug.cgi?id=42141
--- Comment #14 from acescopezz@gmail.com --- (In reply to Ken Thomases from comment #13)
(In reply to acescopezz from comment #12)
(In reply to Ken Thomases from comment #11)
Thank you very much for taking the time to explain all that.
You're welcome.
Should I change the status to 'INVALID', since it seems to be a game bug?
You can. I suspect there won't be any more work on this. However, I wasn't really able to determine what was happening _conclusively_. I (or somebody) would probably have to debug interactively (not via logs) to be absolutely sure what's happening. So, you could leave this open in the hopes that somebody will do so, if you want.
I'll just leave it open and see what happens. I can always hope someone can take the time to look into this.
Thank you again for everything.
https://bugs.winehq.org/show_bug.cgi?id=42141
--- Comment #15 from acescopezz@gmail.com --- Created attachment 57051 --> https://bugs.winehq.org/attachment.cgi?id=57051 Game error log
(In reply to Ken Thomases from comment #13)
(In reply to acescopezz from comment #12)
(In reply to Ken Thomases from comment #11)
Thank you very much for taking the time to explain all that.
You're welcome.
Should I change the status to 'INVALID', since it seems to be a game bug?
You can. I suspect there won't be any more work on this. However, I wasn't really able to determine what was happening _conclusively_. I (or somebody) would probably have to debug interactively (not via logs) to be absolutely sure what's happening. So, you could leave this open in the hopes that somebody will do so, if you want.
Sorry to bother you again, but I found this file on my Mac and though it might shed more light on this issue. Hopefully it is useful.
https://bugs.winehq.org/show_bug.cgi?id=42141
acescopezz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #16 from acescopezz@gmail.com --- Actually scratch that. The game works perfectly all of a sudden. I have no idea what fixed it. I managed to get it to work with Wine Staging 2.0 (not sure if plain works or not). I had to make sure to start the game with Star Ruler 2.exe from the top installation folder. Not with Star Ruler 2.exe from the win32 folder.
https://bugs.winehq.org/show_bug.cgi?id=42141
fjfrackiewicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fjfrackiewicz@gmail.com
--- Comment #17 from fjfrackiewicz@gmail.com --- (In reply to acescopezz from comment #16)
Actually scratch that. The game works perfectly all of a sudden. I have no idea what fixed it. I managed to get it to work with Wine Staging 2.0 (not sure if plain works or not). I had to make sure to start the game with Star Ruler 2.exe from the top installation folder. Not with Star Ruler 2.exe from the win32 folder.
Was there an update to the game itself? The game does have an autopdater within the game...
https://bugs.winehq.org/show_bug.cgi?id=42141
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #18 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 2.1.
-
wine-bugs＠winehq.org