Created attachment 57527 [details]
gta5 screenshot

The game creates render target view for the backbuffer, but never uses it for some reason. It renders everything to a texture, but doesn't draw it onto the backbuffer.

No idea why, but here's a workaround;
- Open winecfg and setup virtual desktop
- Start the game in fullscreen mode (<Windowed value="0" /> in My Documents/Rockstar Games/GTA V/settings.xml)
- When you hear the sounds there, press alt+enter (the game switches between fullscreen/windowed mode)
- Now everything is rendered ok

The screenshot is taken with wine-2.3. (with <DX_Version value="0" /> in settings.xml, dx11 works also)

Some additions to previous;
- It is probably best to switch between fullscreen/windowed mode after the intro video is finished, or not. Switching the mode while the video is playing takes couple of seconds, and it tends to break the game in various ways. (your mileage may vary)
- Although everything is rendered quite ok, the game is still unplayable, eg. moving is impossible. Pressing any key like 'w' freezes the game completely for 2 seconds, nothing else happens. You can only look around with mouse and shoot. I'll open a separate bug for that later, if needed.

I'm able to reproduce all of Kimmo's results on Wine 2.3-staging; doing alt+enter worked every time I tried it. Neato.

Also experienced mouse controls working and keyboard inputs freezing the game for a bit but not doing anything. I have a USB game controller that I plugged in, on the off chance that the game would be able to get inputs from that. Alas, the game doesn't even acknowledge the existence of a controller.

I've also been able to replicate all of Kimmo's results, using the registry hacks to trick the game into seeing my GTX 970 as a RX 480 and using the alt + enter trick to clear the black screen.

The issue now seems to be with in-game keyboard input. Keyboard input works fine in the menus and I'm able to remap keys and they're identified correctly, however, whenever I press a key in-game, the graphics seems to freeze temporarily while the key is held and shortly after.

I was actually able to walk around in game by assigning the alternate buttons of "Walk Forward" and "Walk Backward" to Mouse buttons 4 and 5 respectively. Unfortunately the game doesn't scroll wheel tilt or mouse buttons 6 and 7 (which isn't uncommon and probably not a bug), so my testing ends when another button is required.

Tested with wine staging 2.4 on Ubuntu 16.04, same problem.  I wonder if installing some input libraries through PoL would fix the issue

I have the same issue, but alt-tabbing does not make the screen render. It just switch the black screen from windowed to fullscreen and back.

In fact it worked once after multiple attempts with different settings, but I cannot replicate it anymore.

I use the following:
- Regedit hack for AMD RX480 (I have a Nvidia GTX970).
- MaxVersionGL set to 0x30002.
- tried different switch combinations of -width, -height, -windowed,
  -fullscreen, -DX10.

Tried deleting "My documents/Rockstar Games".

Forgot to say I tried with virtual desktop of different sizes.

I tried myself again the other day trying to replicate the results from comment #3 but had the same results as the comment above. Blank screen regardless of alt tab and windowed or full screen.

Also running on a GTX 970

I meant alt+enter in my comment above.

(In reply to Olivier F. R. Dierick from comment #9)
> I meant alt+enter in my comment above.
I have a GTX 960, and did not need to the registry hack or the max GL version hack to get it working, I just have a virtual desktop and alt+enter fixes the problem.  I am running a pirated copy (no tux no bux) but im not sure if that has anything to do w/ it

(In reply to Olivier F. R. Dierick from comment #9)
> I meant alt+enter in my comment above.
I have a GTX 960, and did not need to the registry hack or the max GL version hack to get it working, I just have a virtual desktop and alt+enter fixes the problem.  I am running a pirated copy (no tux no bux) but im not sure if that has anything to do w/ it

Got a wine-staging debian package update today:
2.4.0~jessie -> 2.4.0-3~jessie.

Still black screen with audio and no alt+enter workaround.

I have the retail DVD version.

This game also requires support for at least this unimplemented instructions:
dcl_input_ps
dcl_input_ps_sgv
dcl_input_ps_siv
sample_d

(In reply to o13g86 from comment #13)
> This game also requires support for at least this unimplemented instructions:
> dcl_input_ps
> dcl_input_ps_sgv
> dcl_input_ps_siv
> sample_d

Just curious, how did you find out that these functions are needed to fix the keyboard issue

Tested on Ubuntu 16.04 wine staging 2.7, same keyboard error persists

I have confirmed that the ActivateKeyboardLayout function is not the cause, I have modified the source and disabling that function does not affect the issue in the slightest.  Do any of you guys know how I can retrieve a stacktrace of all running threads at any given time?  I can't use winedbg due to steamapi64.dll

Tested w/ 2.8, same problem

Tested with wine staging 2.6, 2.7, 2.8 and 2.9 same problem.

But there is a workaround.

Start the game, once you hear the police sound:
1. Alt + Tab to another window
2. Click directly onto the GTA V window
3. Alt + Tab to another window
4. Click directly onto the GTA V window

Short video: https://youtu.be/kEHES0Z8B8M

(In reply to Xavier Sellier from comment #18)
> Tested with wine staging 2.6, 2.7, 2.8 and 2.9 same problem.
> 
> But there is a workaround.
> 
> Start the game, once you hear the police sound:
> 1. Alt + Tab to another window
> 2. Click directly onto the GTA V window
> 3. Alt + Tab to another window
> 4. Click directly onto the GTA V window

This workaround does not work on my computer either.

The keyboard input issue has been reported there: bug 43102.
Affected people should add themselves to that bug.

(In reply to Xavier Sellier from comment #18)
> Tested with wine staging 2.6, 2.7, 2.8 and 2.9 same problem.
> 
> But there is a workaround.
> 
> Start the game, once you hear the police sound:
> 1. Alt + Tab to another window
> 2. Click directly onto the GTA V window
> 3. Alt + Tab to another window
> 4. Click directly onto the GTA V window
> 
> Short video: https://youtu.be/kEHES0Z8B8M

This workaround is not working on my computer either, I tried downloading xfce4 since my WM doesnt have any alt tabbing but it was to no avail.

A better (working) workaround is needed, anyone got some ideas?

(In reply to gotziem from comment #20)
> (In reply to Xavier Sellier from comment #18)
> > Tested with wine staging 2.6, 2.7, 2.8 and 2.9 same problem.
> > 
> > But there is a workaround.
> > 
> > Start the game, once you hear the police sound:
> > 1. Alt + Tab to another window
> > 2. Click directly onto the GTA V window
> > 3. Alt + Tab to another window
> > 4. Click directly onto the GTA V window
> > 
> > Short video: https://youtu.be/kEHES0Z8B8M
> 
> This workaround is not working on my computer either, I tried downloading
> xfce4 since my WM doesnt have any alt tabbing but it was to no avail.
> 
> A better (working) workaround is needed, anyone got some ideas?

Just run the game ins a virtual desktop, press alt enter 1 or 2 times when you hear the loading sound, and it should work

(In reply to dereklesho52 from comment #21)
> (In reply to gotziem from comment #20)
> > (In reply to Xavier Sellier from comment #18)
> > > Tested with wine staging 2.6, 2.7, 2.8 and 2.9 same problem.
> > > 
> > > But there is a workaround.
> > > 
> > > Start the game, once you hear the police sound:
> > > 1. Alt + Tab to another window
> > > 2. Click directly onto the GTA V window
> > > 3. Alt + Tab to another window
> > > 4. Click directly onto the GTA V window
> > > 
> > > Short video: https://youtu.be/kEHES0Z8B8M
> > 
> > This workaround is not working on my computer either, I tried downloading
> > xfce4 since my WM doesnt have any alt tabbing but it was to no avail.
> > 
> > A better (working) workaround is needed, anyone got some ideas?
> 
> Just run the game ins a virtual desktop, press alt enter 1 or 2 times when
> you hear the loading sound, and it should work

Ok, I managed to see something now (the loading the screen), I did what you said but I also had to change the backscreen rendering mode from FBO to Backbuffer, although now it crashes once I actually get into the game. I'm gonna keep trying until I get it working, I'll try to get an error log if I manage to dechipher the wine manual.
Although when not using backbuffer as the offscreen rendering mode then I was able to play the game, just that I couldnt see anything, and by playing I mean clicking left mouse button and hearing the gun shoot.

Does this work any better;
- default settings (no OffscreenRenderingMode changes etc)
- Use "Windowed Bordeless" mode
  * <Windowed value="2" /> in settings.xml
  * set ScreenWidth and ScreenHeight to match your screen
- Contrary to my old comment, don't use virtual desktop
- Press alt-enter when you hear the sounds

The above method works on my GTX680/i7-3770K machine, the one I posted earlier (with virtual desktop) works with GTX980/i7-5930K.
alt-tabbing does not work on either one (xfce, Ubuntu).
Just trying to narrow this down to something.

(In reply to Kimmo Myllyvirta from comment #23)
> Does this work any better;
> - default settings (no OffscreenRenderingMode changes etc)
> - Use "Windowed Bordeless" mode
>   * <Windowed value="2" /> in settings.xml
>   * set ScreenWidth and ScreenHeight to match your screen
> - Contrary to my old comment, don't use virtual desktop
> - Press alt-enter when you hear the sounds
> 
> The above method works on my GTX680/i7-3770K machine, the one I posted
> earlier (with virtual desktop) works with GTX980/i7-5930K.
> alt-tabbing does not work on either one (xfce, Ubuntu).
> Just trying to narrow this down to something.

At last!
That workaround does work on my computer.
I also have those tweaks in the registry:
- MaxVersionGL DWORD value 0x00030002.
- nvidia-to-radeon PCI Vendor and Product IDs substitution.

There's a bug in gnome-shell (current Debian Jessie version) that makes full-screen windows click-through (that is : not focused, keyboard and mouse input are sent to other windows or the desktop background). Usually, alt-tabbing to the Wine window does "activate" input to the full-screen application, but this negates the alt+enter workaround for this game. I have to switch to another DE (i.e. gnome-classic) to be able to use the workaround.

The performance is very low (2 to 6 FPS reported by the in-game tests) and bug 43102 is present.

Not to me :(

Ive tried a lot already and ofcause came over the DeviceID and VendorID problems.
Actually im using a 1060gtx with 6gb memory and im stuck with ERR_MEM_EMBEDDEDALLOC_ALLOC .

Im using the bleeding edge wine, currently 2.11-63.

The game launches, black screen, no solution yet.
The best progress was the rx480 registry hack, that made the memory error be gone but its still a black screen.

At least i have sound and know its loading, but its loading forever and does not switch into the gaming modus.
Ive also tried to set the values for my own gfx card, but that gave me the memory error back as soon as the screen opens.

/shrug

i5-2320, 16GB RAM, GTX 970. Using Linux 4.11.3, nvidia prop 381.22, and Wine 2.11-staging.

The Alt+Enter trick used to work for me (I'm comment #3 here), but I'm unable to get it to work now. I've tried many of the tricks mentioned here, including MaxVersionGL. The game will now launch with or without the RX 480 regedit hack, but I'm unable to get it away from the black screen.

Wine 2.11 staging made the game load but still black screen.
The game is loading, alt-enter or alt-tab wont pop the gfx.

Wonder whats the difference btw. the systems of ppl is, that see gfx and the ones that cant.

Im on Fedora 25 on AMD8150 on ga970-UD3 with 8gb 1866 DDR3 and my 6gb nv1060gtx.

Alt-Entering still works with newest GTA 5 and wine-2.11-staging, but it got harder to achieve the rendering. I usually need 3 tries to get it work and i do it by spamming alt-enter as soon as i hear the sound.
If it doesnt render after spamming for about 2 minutes, kill the gta process and retry (i have a terminal open with the "wine taskmgr" command and just open the wine taskmanager, scroll with the arrow keys to the process and press ALT+B(german keyboard) to end the process)

Yes its a bit painful and i hope this issue gets fixed soon, but you can still play the game, you just need to try harder

(In reply to BieHDC from comment #28)
> Alt-Entering still works with newest GTA 5 and wine-2.11-staging, but it got
> harder to achieve the rendering. I usually need 3 tries to get it work and i
> do it by spamming alt-enter as soon as i hear the sound.
> If it doesnt render after spamming for about 2 minutes, kill the gta process
> and retry (i have a terminal open with the "wine taskmgr" command and just
> open the wine taskmanager, scroll with the arrow keys to the process and
> press ALT+B(german keyboard) to end the process)
> 
> Yes its a bit painful and i hope this issue gets fixed soon, but you can
> still play the game, you just need to try harder

Is it possible to play the multiplayer too?

I made a video to show how the game runs with wine-2.11 on my computer:
https://www.youtube.com/watch?v=MNX89Dphrx0

I press Alt+Enter once when the sound starts playing, then I Alt+Tab out and in the game so that it get the focus back. The game switches back to borderless window by itself, no need to press Alt+Enter again. Sometimes, alt+tabbing is not sufficient to bring the focus back to the game and I have to switch desktop too.

Note that at least one other window has to be open in order to alt+tab out of the game.

That is plain wine 2.11 + single staged patch from bug 43102 + tweaks from comment #23 and comment #24.

Contrary to comment #24, I set the game to a size less than fullscreen so I do not have to switch DE to workaround the fullscreen bug in gnome-shell.

The black screen bug happens before the main menu.
It should not impact multiplayer mode.
Issues with multiplayer mode should be reported separately.

(In reply to winetest from comment #29)
> Is it possible to play the multiplayer too?
I haven't tried yet and i refuse to because my next ban will be a ban forever (thanks kiddie hackers)
It does not violate rockstar's terms of service etc, but you never know how the anti cheat will react.


I also made a quick video of getting the game to render using a different method than Olivier did: https://www.youtube.com/watch?v=h6BUEpcyf4A
I hope it helps

How did you guys get it working? I'm getting an error:

err:seh:setup_exception stack overflow 3024 bytes in thread 002c eip 00007fff8ea931db esp 0000000000130a40 stack 0x130000-0x131000-0x230000

I'm on macOS Sierra update 6, wine 2.10.

(In reply to John from comment #32)
> How did you guys get it working? I'm getting an error:
> 
> err:seh:setup_exception stack overflow 3024 bytes in thread 002c eip
> 00007fff8ea931db esp 0000000000130a40 stack 0x130000-0x131000-0x230000
> 
> I'm on macOS Sierra update 6, wine 2.10.

You need eiter wine-staging (any recent version) or plain wine 2.11.
NVidia users also need a registry tweak (use radeon PCI vendor/product IDs).

If you use that and still get a crash, file a bug report and attach a full terminal outpout.

(In reply to John from comment #32)
> How did you guys get it working? I'm getting an error:
> 
> err:seh:setup_exception stack overflow 3024 bytes in thread 002c eip
> 00007fff8ea931db esp 0000000000130a40 stack 0x130000-0x131000-0x230000
> 
> I'm on macOS Sierra update 6, wine 2.10.

You need either wine-staging (any recent version) or plain wine 2.11.
NVidia users also need a registry tweak (use radeon PCI vendor/product IDs).

If you use that and still get a crash, file a bug report and attach a full terminal outpout.

(In reply to Olivier F. R. Dierick from comment #34)
> (In reply to John from comment #32)
> > How did you guys get it working? I'm getting an error:
> > 
> > err:seh:setup_exception stack overflow 3024 bytes in thread 002c eip
> > 00007fff8ea931db esp 0000000000130a40 stack 0x130000-0x131000-0x230000
> > 
> > I'm on macOS Sierra update 6, wine 2.10.
> 
> You need either wine-staging (any recent version) or plain wine 2.11.
> NVidia users also need a registry tweak (use radeon PCI vendor/product IDs).
> 
> If you use that and still get a crash, file a bug report and attach a full
> terminal outpout.

It still failed with same error but with. different numbers, should i use winedbg or just that line because the logs from winedbg are about  1000 pages or so.

(In reply to Olivier F. R. Dierick from comment #34)
> (In reply to John from comment #32)
> > How did you guys get it working? I'm getting an error:
> > 
> > err:seh:setup_exception stack overflow 3024 bytes in thread 002c eip
> > 00007fff8ea931db esp 0000000000130a40 stack 0x130000-0x131000-0x230000
> > 
> > I'm on macOS Sierra update 6, wine 2.10.
> 
> You need either wine-staging (any recent version) or plain wine 2.11.
> NVidia users also need a registry tweak (use radeon PCI vendor/product IDs).
> 
> If you use that and still get a crash, file a bug report and attach a full
> terminal outpout.

It still failed with same error but with. different numbers, should i use winedbg or just that line because the logs from winedbg are about  1000 pages or so. 

I forgot to mention that I'm using a crack not an original, didn't have space to re download 60gb on my Mac.

(In reply to John from comment #36)
> I forgot to mention that I'm using a crack (...)

I have to bring this to your attention:

"The use of cracks is considered off topic on the forums, IRC channels, etc and will not be tolerated (summarily dismissed and deleted)."

https://wiki.winehq.org/Copy_Protection

(In reply to Olivier F. R. Dierick from comment #34)
> (In reply to John from comment #32)
> > How did you guys get it working? I'm getting an error:
> > 
> > err:seh:setup_exception stack overflow 3024 bytes in thread 002c eip
> > 00007fff8ea931db esp 0000000000130a40 stack 0x130000-0x131000-0x230000
> > 
> > I'm on macOS Sierra update 6, wine 2.10.
> 
> You need either wine-staging (any recent version) or plain wine 2.11.
> NVidia users also need a registry tweak (use radeon PCI vendor/product IDs).
> 
> If you use that and still get a crash, file a bug report and attach a full
> terminal outpout.

It could be that also intel owners need those registery keys. I remember being able to get into main menu and also into game, but i don't have ati card anymore so my last attempts have been with intel integrated card and I do get black screen. Latest  effort was with wine-staging 2.12. I didnt test the registery keys.

The nvidia to radeon registry tweak is to avoid the nvapi bug, not the blackscreen bug.

Anything new on this ?
Its still a gamable game to get it working.
I was not able to find a 100% procedure yet, to start the game.
Anyone else maybe ?

(In reply to rawfox from comment #40)
> Anything new on this ?
> Its still a gamable game to get it working.
> I was not able to find a 100% procedure yet, to start the game.
> Anyone else maybe ?

Gameplay: https://www.youtube.com/watch?v=g-pC6HVGDCA
Doing the Alt-Enter workaround: https://www.youtube.com/watch?v=h6BUEpcyf4A

I have the same issue on a computer with NVidia 9800 GT.
The alt+enter workaround did work twice and then I couldn't get it to work again. When the workaround did work the 3D rendering was completely broken.

On the GTX970 machine, the workaround works most of the time, and the rendering is correct.

On my 1060gtx its total random, mostly i need to try for 10+ times to get it working, sometimes its not working after 20 tries, sometimes its working on the second time.

(In reply to rawfox from comment #43)
> On my 1060gtx its total random, mostly i need to try for 10+ times to get it
> working, sometimes its not working after 20 tries, sometimes its working on
> the second time.

It does seem random.

I will say that I seem to have the best experience by:
1) Increase linux swappiness. GTAV loves using every bit of ram it can, and seems to expect the OS to swap out as it loads new environments. This will result in stuttering if your swappiness is too low. Either use a swap file or swap partition (preferably with zswap), then increase swappiness to about 90: # sysctl vm/swappiness=90 
Doing so drastically reduces major stuttering, and hdd thrashing.
2) Start in windowed mode (not borderless). When you hear the SECOND gun shot, alt enter. Wait until audio comes back. Hit alt+enter as soon as you hear it. Wait until audio comes back. Hit alt+enter again. If that doesn't work, you may as well alt-tab out and pkill GTA, try again. I've never seen it work after a third alt-tabbing, to be honest. Even this is a total crap shoot. Like you said, it's variable --- Sometimes I get it the second time around. Sometimes I get it to work after about 20x of doing the exact same thing. It'd be great if the wine devs could get gtav to start. Once it does, it actually runs fairly well [in full screen; miserably in windowed mode].

If the game swaps to a grind, then I often lose audio altogether. Also, sometimes the audio begins crackling, and I have no idea why. If it will crackle, it seems to do so by the main menu. If it isn't going to crackle, then the main menu even sounds normal. Seems to happen due to alt-enter timing. No silver bullet yet, but I'm impressed by its performance if you can get it to run.

GTAV bugs native on my windows10 sometimes, maybe once a week. My whole PC went into brrrrbrraaabrrroommm, everything is slowed down, sound total destroyed.
The same bug appeared in wine.

Another sound issue is the slowly dieng out of the sound. First a little crickeling then its just gone. Game works "normal" but its all silent.

Then there is some oddy with the screens.
Sometimes when the sound has issues or the game feels clumpy slow, i found a second steam-screen were i think it has build with the alt-enter/alt-tab thing anyhow. Its just a dead second black screen without purpose but the performance drops heavy.

On a note to GTA Online, my toon was seen as pretty laggy, loads of rubberbanding and thelike.

We are not there yet.

wine 2.13 just released, the game is fully loading but the black screen bug and fix are still in effect.
The performance is 2fps ^^
42528 Grand Theft Auto 5 crashes while loading seems really fixed now.
Let see what the wine-staging tweaks bring us in a couple days, looking forward :)

I cannot get the alt+enter fix to work on wine-staging 2.13. One thing I've noticed is that < 2.13, when I hit alt+enter, the sound will pause. I typically did the following for the game to launch:

Launch.
Wait until about second gunshot, hit alt+enter.
Wait for sound to return, hit alt+enter.
Wait for sound to return, hit alt+enter.

But now the sound doesn't stop, and I cannot figure out how to get past the black screen now. Has anyone had luck with wine-staging 2.13?

(In reply to hwkiller from comment #47)
> I cannot get the alt+enter fix to work on wine-staging 2.13. One thing I've
> noticed is that < 2.13, when I hit alt+enter, the sound will pause. I
> typically did the following for the game to launch:
> 
> Launch.
> Wait until about second gunshot, hit alt+enter.
> Wait for sound to return, hit alt+enter.
> Wait for sound to return, hit alt+enter.
> 
> But now the sound doesn't stop, and I cannot figure out how to get past the
> black screen now. Has anyone had luck with wine-staging 2.13?

yes it still works, see my video: https://www.youtube.com/watch?v=rc8H_Uh2zEo
i still tried to do it the old way, but when the sound just continued, i spammed alt+enter and it worked. when taking this video it worked on the 2nd try.

I've since gotten it to work, but it seems /much/ harder than before.

I seem to have better luck just hold down alt-enter and letting it keep cycling between windowed and not windowed. I have had MUCH better luck by forcing it to start full-screen, then holding down alt+enter (which, due to nvidia + using a non-native resolution, causes my monitor to basically stay black while it adjusts resolution over and over again), for a long while. Then letting go, and sometimes (probably 20% of the time) it will work.

I can very, very rarely get it working from windowed mode on startup though, and I'm not sure why.

But yes, it does perform much better! I still have the blindingly bright sun problem and glitchy shadows (which I now just disable). The audio is messed up pretty consistently, whereas before when I didn't have to just hold down alt+enter the entire time (and alt+entered based on some loose timings I've gotten used to), the audio could often be fairly perfect.

(In reply to hwkiller from comment #49)
> But yes, it does perform much better! I still have the blindingly bright sun
> problem and glitchy shadows (which I now just disable). The audio is messed
> up pretty consistently, whereas before when I didn't have to just hold down
> alt+enter the entire time (and alt+entered based on some loose timings I've
> gotten used to), the audio could often be fairly perfect.

For the audio mess up:
Set an attached microphone to enabled in SpeechChat. If you dont the following wont work:
every time audio messes up, go to the menu, settings and keep the down button pressed, so it switches through the menu entrys. after at least 2 cycles, it should be "fixed" for a random time. if you dont set a mic, it will hang for 2 sec and the audio is completely gone.


Whats the progress on the rendering issue anyway? Is it fixable? https://bugs.winehq.org/show_bug.cgi?id=42330#c1

There was a game update and now I cannot get the alt+enter workaround to work anymore.
wine 2.15, wine 2.16 and wine-staging 2.16.

There is another workaround (100% working this time):
Add the following to the steam launch option :-StraightIntoFreeMode -online
Meaning GTA V will launch into the Online mode directly.
You will have a black screen, but about 1 minute (while loading the online mod) you will be able to enter the game (Alt + Enter).

I hope it helps !

(In reply to Olivier F. R. Dierick from comment #51)
> There was a game update and now I cannot get the alt+enter workaround to
> work anymore.
> wine 2.15, wine 2.16 and wine-staging 2.16.

It still works. When you hear the intro:
~2 seconds before you hear the shots fired, do alt+enter
after the sound resumes, instantly alt+enter again

40/60 chance of working with experience

if it doesn't work, you can still spam alt+enter (i just put something on the keys) and if youre lucky, it works.
else retry, but it does work still.

Created attachment 60117 [details]
blackscreen workaround for staging-2.21

This patch works around the blackscreen problem and makes GTA5 start up every time. It is probably not the right way to do it (really the bind flags should come from DXGI_SWAP_CHAIN_DESC.BufferUsage) but it lets you at least play GTA: 5 without having to Alt+Enter a whole bunch of times.

(In reply to Piotr W from comment #54)
> Created attachment 60117 [details]
> blackscreen workaround for staging-2.21
> 
> This patch works around the blackscreen problem and makes GTA5 start up
> every time. It is probably not the right way to do it (really the bind flags
> should come from DXGI_SWAP_CHAIN_DESC.BufferUsage) but it lets you at least
> play GTA: 5 without having to Alt+Enter a whole bunch of times.

I can confirm it working as described. Also tested some other DX10/11 games and it doesn't seem to cause any regressions.

(In reply to Piotr W from comment #54)
> Created attachment 60117 [details]
> blackscreen workaround for staging-2.21
> 
> This patch works around the blackscreen problem and makes GTA5 start up
> every time. It is probably not the right way to do it (really the bind flags
> should come from DXGI_SWAP_CHAIN_DESC.BufferUsage) but it lets you at least
> play GTA: 5 without having to Alt+Enter a whole bunch of times.

Hack from comment #54 doesn't work with plain wine 3.0-rc4.

(In reply to Olivier F. R. Dierick from comment #51)
> There was a game update and now I cannot get the alt+enter workaround to
> work anymore.
> wine 2.15, wine 2.16 and wine-staging 2.16.

Since wine 3.0-rc2 the Alt+Enter workaround is working again (either plain wine or staging).