[SOLVED] GTA V crashes with ReShade 17.1 + SweetFx

Running Reshade 17.1 fine on my GTA 5 (Rockstar none-Steam edition).

Only problem I have with it enabled is about a 4-8fps drop and in some parts of the game the game slows down further
[in these same places soon as you disabled Reshade the game is at perfect speed]

I was able to reproduce a crash with the "DXGI_ERROR_INVALID_CALL" error on NVIDIA with latest drivers. This particular issue I ran into seems to be due to a driver optimization (part of the "Game Ready" drivers from NVIDIA).
It only occurs when changing the "IDXGISwapChain::ResizeBuffers" member of the VTable, keeping that the original and hooking any other member is no problem. Sadly this one is an absolute requirement, so removing it is no solution.
Doesn't look like there is much I can do about it. Maybe I'm drawing the wrong conclusion, but this would also explain why the crash does not appear on another computer, which is still on one year old NVIDIA drivers.

Now one workaround is to avoid the game calling "ResizeBuffers". The following works for me: After launching the game, do not click on another window or move focus otherwise (through the entire social club starting sequence), just wait for the game to show up and only after start move your mouse/keyboard again. Also, make sure to run the game in fullscreen mode.

Same thing with v18 too.
I tried not moving the mouse but it still crashes. Tried also disabling my second display, setting the game to lowest settings, switching to dx10v of the game, windowed....still the same crash.
Should we roll back the driver?

V17 didn't work in GTAV for me, but v18 does. I have the newest NVIDIA driver to.

Same here, also can confirm that reshade 0.18 doesn't fix the problem. Everything is still the same. I still see the error 'IDXGIFactory::CreateSwapChain' failed with 'DXGI_ERROR_INVALID_CALL' as the last line in my log file.

So the only way to get this to work is wait for NVIDIA to update their drivers or roll back to the previous one?

Only success I had is with Radeon pro, by ignoring all APIs except dxgi in compatibility list (thx to a post on guru3d) then it doesn't crash, sweetfx works. But it is not viable, for some reason the screen is flashing when moving.
This may be a part of the answer.

I can confirm too what 0.18 still crashes with GTA V. I have 4GB Sapphire R9 290 Tri-X and still get that error with dxgi, so i think this is not only Nvidia related error with their "Game Ready". Its a global error. So sad what i still cant play with injectors (( I tried everything - SweetFX 2.0, Reshade from 0.14 to 0.18, tried to disable steam overlay - nothing helps.

You have to Rename dxgi to d3d11

The Logo menu at start might Lag a bit! But press the preset OFF key until you get ingame the press it On again

axelrol wrote: I can confirm too what 0.18 still crashes with GTA V. I have 4GB Sapphire R9 290 Tri-X and still get that error with dxgi, so i think this is not only Nvidia related error with their "Game Ready". Its a global error. So sad what i still cant play with injectors (( I tried everything - SweetFX 2.0, Reshade from 0.14 to 0.18, tried to disable steam overlay - nothing helps.

You have to Rename dxgi to d3d11

The Logo menu at start might Lag a bit! But press the preset OFF key until you get ingame the press it On again

Quentin-Tarantino wrote:

axelrol wrote: I can confirm too what 0.18 still crashes with GTA V. I have 4GB Sapphire R9 290 Tri-X and still get that error with dxgi, so i think this is not only Nvidia related error with their "Game Ready". Its a global error. So sad what i still cant play with injectors (( I tried everything - SweetFX 2.0, Reshade from 0.14 to 0.18, tried to disable steam overlay - nothing helps.

You have to Rename dxgi to d3d11

The Logo menu at start might Lag a bit! But press the preset OFF key until you get ingame the press it On again

You think i am not doing that? I tried everything - i told you. Always crash at startup.

Quentin-Tarantino wrote: You have to Rename dxgi to d3d11

No you don't, that particular bug was fixed with 0.18.0 . But as stated in the release thread, the other crash issue is still remaining.

guys, make sure you are also using the 64bit reshade with GTAV. Like I said, I am not getting these crashes anymore with 0.18. Everything works great.

Since I cannot reproduce the crash with the "CreateSwapChain" error on any of the computers I have access to, but it obviously is there, it would be really great if somebody with the problem could get in contact with me (Steam for example), to try some things.

I would love to help you out so that we can resolve this issue. What do you need?

One thing I noticed with GTA V and ReShade yesterday was that Windows was throwing a couple of Kernel exceptions (Nothing crashed though.) but I have not managed to pin down the exact cause of these, could be some deeper driver conflict which would explain the framerate problem I'm getting so when I next try and if this problem repeats if I can find a way to recreate it I'll see about getting one of those crash dumps or error logs uploaded here, could be of use although I'm unsure if it can fix the crash on load issue that many others are experiencing.

EDIT: That Windows error report doesn't seem to occur with 0.18.0 so that's good, nothing to worry about then.

But here's the dxgi.tracelog file from entering and exiting the game.

dxgi.rar
www58.zippyshare.com/v/xTcRZS5q/file.html

(Starting with the effects disabled or enabled doesn't seem to do much in 0.18.0 as either of them will cause a severe framerate drop though the game works although it would be unplayable of course but I'm really glad that whatever that exception error was it's gone now so hopefully it was entirely unrelated - so I still have to find what actually caused it in the first place. - or 0.18.0 fixed it somehow.)

JBeckman wrote: (Starting with the effects disabled or enabled doesn't seem to do much in 0.18.0 as either of them will cause a severe framerate drop though the game works although it would be unplayable of course but I'm really glad that whatever that exception error was it's gone now so hopefully it was entirely unrelated - so I still have to find what actually caused it in the first place. - or 0.18.0 fixed it somehow.)

It still fixes it, under 0.18.0 too. But the framework shader pack doesn't actually disable everything when you configure it to start disabled. It still runs some basic utility shaders, which cause the stuttering at startup.

Ah so that could be why then.

The thing about the framerate was because under ReShade 0.17.0 and it's version of the Framework disabling the effects would boost the framerate to around 15 instead of 5 which it would be at with the effects on whereas now with 0.18.0 it stays at around 5 regardless of the effects being on or off.

That thing about the Windows Error Reporter collecting some Kernel fault mini dump was the main problem however (I should have saved one of them but I noticed them first when I ran CCleaner to trim out a few files so it was too late.) but since that seems fixed now and I can't seem to re-create the problem this little issue with the framerate drop isn't much of a issue really especially compared to this larger crash problem, however this framerate drop is unfortunately constant instead of just being during the intro logos and main menu screen but I'm guess it's likely a problem on my end than something with the injector so I need to do more testing and find out the real issue behind this or how to say.
(And if I remember correctly from other discussions on these boards the actual shaders don't really have the ability to cause such errors so it can't be that.)

By the way, I was able to narrow the intro sequence stuttering down to a totally valid API call (ID3D11DeviceContext::CopyResource takes ages to return), so I can only suspect a driver optimization going bad and can't think of anything to fix it from my end unfortunately. These kind of problems are quite common with GTA 5 apparently, no idea how they could mess up this much.

Nvidia should have had plenty of time with the game and getting a "GameReady" driver out but AMD's 15.4 seems a bit more rushed, actually uses the same D3D version as 15.3 which in turn uses the same D3D version as 14.12 "Omega" with the only real display driver difference between 15.3 and 15.4 being tweaks to the GTA V profile.
(The main activity seems to be with the driver branch they're using with Windows 10 which is updated very frequently so I assume that's what they are focusing on now with W10's release getting closer.)

I check the latest patch notes, which included a little line that had my hopes up that they were trying to allow ReShade to work with the game:
"Fixed a rare issue where the Steam version of the game would crash right after launching."
Reinstalled ReShade, both 17.1 and 18, and neither one works. My hopes and dreams have been crushed.