It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
rampancy: ...
I know there is a patch for Wine, but as I said above, it tanks performance. There is no fix for the issue unless someone can get Apple fix their OpenGL implementation. The only ones that could convince Apple to look into it are either Crossover or GOG (nudge Judas) since they have a financial interest in Wine working properly. The issue is explained here:
I had a sneaking suspicion that that's what it would be.

Short version: as discussed in bug 29261, this is a bug in Apple's OpenGL. WineD3D could work around it, but Henri is disinclined to do that.

Long version:

Here's the thing, for some games, WineD3D does something a bit unusual: in circumstances where it's only really interested in using one buffer, it nevertheless creates a double-buffered context. It then only draws to the front buffer and ignores the back buffer.

This interacts poorly with the assumptions made in Apple's OpenGL optimizations. Those optimizations assume that, for a double-buffered context, the app will be drawing to the back buffer and swapping it to display it.

The result is that, for each frame, Apple's OpenGL is replacing the good drawing done by WineD3D with the garbage in the uninitialized back buffer. This is the cause of the horrible flickering.

What WineD3D is doing is unusual but legal. Apple's OpenGL optimization is therefore buggy.

The Mac driver, prior to commit d30705bd, was unintentionally doing something that was defeating optimizations in Apple's OpenGL. The one good effect of that was that it prevented the bad optimization from kicking in and causing the flickering. The obvious bad effect is that it negatively impacted performance of OpenGL graphics.

Commit d30705bd fixed this problem in the Mac driver, allowing Apple's OpenGL optimizations to take effect. In most cases, this is good. For those particular games which use this one-buffer-of-a-double-buffered-context technique, it also re-enables the optimization that causes the flickering. That's unfortunate, but not really the fault of the Mac driver.

WineD3D could change the way it operates to work around this bug in Apple's OpenGL. That's out of my area.
https://bugs.winehq.org/show_bug.cgi?id=34166#c4
avatar
HiPhish: I know there is a patch for Wine, but as I said above, it tanks performance.
...
https://bugs.winehq.org/show_bug.cgi?id=34166#c4
there is a second patch in that bug report that should fix the problem without affecting the performance.
at least according to this comment
Here are a couple games for your list:
https://wiki.dotslashplay.it/start?do=search&id=gog+wine

All have been tested with WINE 1.6 on Debian.
Post edited December 29, 2015 by vv221
avatar
immi101: ...
WTF, I was sure I had tried the Verbeet patch before, but I guess I had not. I have tried a pre-patched Wine 1.7.11 engine with Stronghold and it's smooth as silk at full HD now.
I have to ask: why is the (tm) after my nick and not elsewhere? :P
avatar
pablodusk: Good idea! I'm curious about Pax Imperia - Eminent Domain, if Judas™ reads this.
I haven't had the chance to delve too deep into this game but I know it seemed to work in WINE 1.7. I know that you should emulate a virtual desktop to your chosen resolution before playing the game or otherwise you'll end up playing it in a sort of windowed mode due to the way the game is initially rendered under WINE.
Post edited January 01, 2016 by JudasIscariot
avatar
JudasIscariot: I have to ask: why is the (tm) after my nick and not elsewhere? :P
avatar
pablodusk: Good idea! I'm curious about Pax Imperia - Eminent Domain, if Judas™ reads this.
avatar
JudasIscariot: I haven't had the chance to delve too deep into this game but I know it seemed to work in WINE 1.7. I know that you should emulate a virtual desktop to your chosen resolution before playing the game or otherwise you'll end up playing it in a sort of windowed mode due to the way the game is initially rendered under WINE.
Don't you have a New Year to celebrate or something? :P
avatar
JudasIscariot: I have to ask: why is the (tm) after my nick and not elsewhere? :P

I haven't had the chance to delve too deep into this game but I know it seemed to work in WINE 1.7. I know that you should emulate a virtual desktop to your chosen resolution before playing the game or otherwise you'll end up playing it in a sort of windowed mode due to the way the game is initially rendered under WINE.
avatar
InkPanther: Don't you have a New Year to celebrate or something? :P
Woo...

There, I celebrated :P
avatar
InkPanther: Don't you have a New Year to celebrate or something? :P
avatar
JudasIscariot: Woo...

There, I celebrated :P
I approve of keeping it civilized and not too noisy. ;)
I'm kind of a fan of making WINE reports in the actual forum for the game in question. It does take some dedication from users. I've made a few, but I guess it's fair to say I've been slacking. I'm not sure about having one epic thread in the gen forum trying to sort it out. Probably doesn't hurt to try.
avatar
HiPhish: Is there something I'm missing or can't you just look up the game in the AppDB?
https://appdb.winehq.org

Anyway here is a list of some of my games. All games that have the Mac flickering bug will flicker wildly on OS X, at least with my graphics card (Nvidia 9400m), they need either a patched version of Wine or Winetricks ddr=gdi. Both options lower performance quite noticeably.

Age of Wonders Wine 1.8
- Mac flickering

Aquanox Wine 1.8
- Works fine

Hitman 2 Wine 1.8
- Winetricks dsound

Heroes of Might & Magic 2 Wine 1.8
- Mac flickering
I've had beef with the App DB for a while now. It just doesn't tend to stay very current. After a few entries nobody adds to it. If we get a GoG version after that initial report set, it may not be all that relevant, and may not fully apply to the GoG version.

I kind of wish they would just nuke the whole thing and make people start over.

***edit: oops
Post edited January 01, 2016 by gooberking
avatar
Matruchus: Curious about getting Heroes of Annihilated Empires running under Wine?
The game does run in WINE 1.8 and in 1.7.51, but the menu graphics get really glitchy for some reason...so much so that they're rendered unusable when you get past the start screen. Under older versions of WINE in the 1.6.x and 1.5.x builds, the graphics run fine but the game crashes during the opening cutscene. The usual suspects (installing d3dx_36, directx9, ddr=gdi, glsl=disable) don't seem to have an effect.



avatar
gooberking: I've had beef with the App DB for a while now. It just doesn't tend to say very current. After a few entries nobody adds to it. If we get a GoG version after that initial report set, it may not be all that relevant, and may not fully apply to the GoG version.

I kind of wish they would just nuke the whole thing and make people start over.
What really annoys me is that often times, people will post reports with little to no information about what they had to do (e.g. dependencies in winetricks, registry edits, etc.) to get the game to run. In the worst cases, someone will have rated a game as "Gold" but say things like "oh yeah the game works but like the textures don't work and the menus and guis are messed up oh well roflmao". There's also, on top of that, people posting dupes with incorrectly named game entries.
Post edited January 01, 2016 by rampancy
Might have noticed, but I wound up not having time to work on this. It will have to wait until next year.

avatar
JudasIscariot: I have to ask: why is the (tm) after my nick and not elsewhere? :P
He's using it wrong. All of us are Judas™. You are just you.
avatar
gooberking: I've had beef with the App DB for a while now. It just doesn't tend to stay very current. After a few entries nobody adds to it. If we get a GoG version after that initial report set, it may not be all that relevant, and may not fully apply to the GoG version.
True, but that's the case with everything community-maintained. As long as there is no one paid or with a vested interest to sit down and maintain it you will always lag behind. To be honest, I don't know how this could be solved except by hiring someone whose job is to test a set of applications after every Wine release.

Even I myself, once I get a game working I don't tinker with it anymore.
low rated
avatar
rampancy: What really annoys me is that often times, people will post reports with little to no information about what they had to do (e.g. dependencies in winetricks, registry edits, etc.) to get the game to run. In the worst cases, someone will have rated a game as "Gold" but say things like "oh yeah the game works but like the textures don't work and the menus and guis are messed up oh well roflmao". There's also, on top of that, people posting dupes with incorrectly named game entries.
You can get a list of all the installed winetricks by doing
winetricks list-installed

This might be useful information to include in any appdb reports you submit. (In fact, maybe it should be required that those using winetricks do so.)
avatar
gooberking: I've had beef with the App DB for a while now. It just doesn't tend to stay very current. After a few entries nobody adds to it. If we get a GoG version after that initial report set, it may not be all that relevant, and may not fully apply to the GoG version.
avatar
HiPhish: True, but that's the case with everything community-maintained. As long as there is no one paid or with a vested interest to sit down and maintain it you will always lag behind. To be honest, I don't know how this could be solved except by hiring someone whose job is to test a set of applications after every Wine release.

Even I myself, once I get a game working I don't tinker with it anymore.
Which is why it's a good idea to not just lean on the AppDB when GoG gets something ( which is often later than the rest of the world) which was what I was originally responding to; the idea of why can't we just search the AppDB instead? And with the AppDB there just seems to be something special about the way stuff rots there. I get people get board of double checking, but the idea is that there hopefully are enough people in the community to keep stuff up to date, but it doesn't always look like there is. I had some rather negative reactions to entries I tried to make once upon a time, so maybe that is part of it. Things like this thread seem to indicate there is some shortcoming with it.

I personally like finding actual discussions on a game when you run internet searches on them so there are other places to find information in differing formats. If you search google for say "wine Blazblue" or "wine Two Worlds" the search results will return AppDB links but you also get links to threads I created here at GoG. Yes they are old, but it's different information, and often times we have had discussions on various experiences. I did update my experience with Alan Wake a couple of times, and some people came in in BlazBlue to report it's working now.
How well does the GOG version of Grandia II run in Wine?