Reshade and NUI In-process GPU Incompatibility

I’m all for the change of how mods work now, although the incompatibility with Reshade and NUI In-process GPU setting is very breaking for people who are utilising that setting.

The error which used to occur would generally solve itself after relaunching FiveM.

You now have to pick between barely being able to interact with NUI’s or not using Reshade.

I definitely can’t speak for everyone but I would definitely rather my game not opening here and there, then the new alternative.

Would have not been more beneficial to add a tip to the error screen stating a way to prevent the error, not making it a requirement?

13 Likes

This should be a request to the ReShade developers for them to fix the bug in their code, as such I moved it out of the feature requests section. Again however they don’t seem to have any contact details listed anywhere so this is the easiest way to fix the issue on our end and maybe make one of their team notice.

Alternately you can update to the Windows ‘Canary channel’ which has a fix for the Windows bug that makes it needed to use the in-process GPU option, or contact Microsoft to find out when they will backport that fix to Windows 10 or 11 (we haven’t had any luck by the way, the email address they set up for this just outright replies with ‘you’re not an allowed sender’).

The problem of ‘users being unable to read the text even though it says right in their face how to fix it’ still would remain.

3 Likes

Since I don’t have access to these shaders/resources, it has been impossible to verify.

But many of the recent steamoverlay reports on the forum also seem to track with race conditions elsewhere (users with a non-zero modpackages count).

Did you find a way to make ReShade work? I have been trying for ages now and nothing. What did you do?

1 Like

I understand that this change is intended to make things more stable, but I never had any real issues with NUI In-process GPU + ReShade and really need to use the NUI In-process GPU setting because otherwise NUI is almost unusable for me.

Wouldn’t it be possible to have another override inside the CitizenFX.ini file for people like me who would still wanna use both NUI In-process GPU with ReShade and know that things might not be stable?

3 Likes

This 100% I can’t believe how absolute blind sided this decision was made. We get that people can’t read at the best of times. However, I’ve never personally had an issue and now due to this blanket change, the game stutters so bad on the slow API call for windows.

5 Likes

Absolutely. We needed that fix option, and now it’s either reshade OR lag. Just a warning that it may cause issues or startup crashes will do. Hope it will be reverted to allow us to use reshade.

2 Likes

Why not instead try to get the authors of ReShade to fix the underlying bug?

This will impact A LOT of users, especially users that needed to use crosshair in-game. Very disappointed move by CFX.

2 Likes

put all the files from reshade into plugins fivem

It will just crash the game if you put Reshade file in the plugin folder

At least the way I suggest has the error and solution in their face, giving them no excuse to miss it.

Rather than expecting every user to have some type of minimal debugging experience to press F8 and reading the error, and if you are on the non release update channels good luck finding it.

This has affected a larger portion of the playerbase then you probably think. It is not very fair…

3 Likes

but there’s a built-in crosshair overlay so you don’t even need to use reshade for that?!?!

https://docs.fivem.net/docs/client-manual/crosshair/

closing this topic as people just seem to be acting annoying anyway rather than trying to figure out a constructive fix or a way to contact the reshade authors

1 Like

close reason is mainly that it’s a lot easier to try to work on a fix without having an angry forum topic constantly getting replied to