Depth buffer detection modifications
- klotim
-
More
4 years 7 months ago #1161
by klotim
Replied by klotim on topic Depth buffer detection modifications
thalixte wrote:
klotim wrote:
klotim wrote: I have an issue with Assassin's creed 2 with the depth buffer, it works perfect but the characters is not included, which ruins it since the characters gets more or less transparent at cases.
Is that fixable? I would really appreciate the help since its the same with brotherhood and revelations as well.
@thalixte Anything i can provide to help you with this issue?
With my last release, i have no pb with Assassin's Creed II
oh my, so what i should do if i have an issue i just look for your latest release? Cool!
Finally i can play my favorite game as it should be. With Ray-tracing!
With assassin's creed architecture and reshade CAS sharpen and more this should look pretty sweet.
Just need to adapt it now!
Before:
After - still needs tweaking, but look at the background, looks sweet.
- thalixte
-
Topic Author
More
- Rayman_77
-
More
- thalixte
-
More
- Rayman_77
-
More
- thalixte
-
More
- Rayman_77
-
More
- Rayman_77
-
More
- JBeckman
-
More
4 years 7 months ago - 4 years 7 months ago #1169
by JBeckman
Replied by JBeckman on topic Depth buffer detection modifications
Is Gears 5 even compatible since it's using Easy Anti Cheat unless that can be disabled? Pretty sure 4.3.0 is whitelisted and allowed through but due to the strictness and how EAC works any other compiled version and newer versions (Whitelist being a file locally in the games folder.) will simply not be loaded though it should not crash.
At most it should pop a error on how the file was blocked or it will simply not show anything and merely strip the handles from any untrusted files trying to interact with the game process if EAC is in use.
(The little loading thing before the game starts up being the EAC launcher initializing the kernel driver and such.)
That would explain it assuming the Steam version doesn't have a way to turn it off. (Win10 Store version does not.)
EDIT: And what else well probably not much I can say, newer dll downloads are working same as always but for D3D12 well it's been Gears 5 but that's Win10 Store and Division 2 which uses Easy Anti Cheat with TU6 planned for October so if 4.4.0 or what the next ReShade build is going to have for version number comes out around then it'll still be a while until the next patch or client hotfix can potentially add in a newer compatible whitelist for testing that.
(This can take week, months or never if the game is no longer actively maintained and updated unfortunately.)
VLK well Wolf Youngblood and Rage 2 are what they are and there's a new runtime or loader but it's generally mostly SDK related and newer extension support although this version (They're also backwards compatible.) does have some fixes for the loader itself.
vulkan.lunarg.com/sdk/home#windows
vulkan.lunarg.com/doc/sdk/1.1.121.0/windows/release_notes.html
Nothing too important though for regular use and it's down to what the display drivers support and what the game itself is doing which I guess is where things act up with these two titles.
And unexpectedly D3D11 is ticking same as always and nothing to report here really.
(Depth buffer can take some setting or two to get working unless it's online and switched off but other than that it's all good here.)
At most it should pop a error on how the file was blocked or it will simply not show anything and merely strip the handles from any untrusted files trying to interact with the game process if EAC is in use.
(The little loading thing before the game starts up being the EAC launcher initializing the kernel driver and such.)
That would explain it assuming the Steam version doesn't have a way to turn it off. (Win10 Store version does not.)
EDIT: And what else well probably not much I can say, newer dll downloads are working same as always but for D3D12 well it's been Gears 5 but that's Win10 Store and Division 2 which uses Easy Anti Cheat with TU6 planned for October so if 4.4.0 or what the next ReShade build is going to have for version number comes out around then it'll still be a while until the next patch or client hotfix can potentially add in a newer compatible whitelist for testing that.
(This can take week, months or never if the game is no longer actively maintained and updated unfortunately.)
VLK well Wolf Youngblood and Rage 2 are what they are and there's a new runtime or loader but it's generally mostly SDK related and newer extension support although this version (They're also backwards compatible.) does have some fixes for the loader itself.
vulkan.lunarg.com/sdk/home#windows
vulkan.lunarg.com/doc/sdk/1.1.121.0/windows/release_notes.html
Nothing too important though for regular use and it's down to what the display drivers support and what the game itself is doing which I guess is where things act up with these two titles.
And unexpectedly D3D11 is ticking same as always and nothing to report here really.
(Depth buffer can take some setting or two to get working unless it's online and switched off but other than that it's all good here.)
Last edit: 4 years 7 months ago by JBeckman.
- thalixte
-
More
- JBeckman
-
More
4 years 7 months ago #1171
by JBeckman
Replied by JBeckman on topic Depth buffer detection modifications
Come to think of it though maybe with D3D12 and EAC just booting out ReShade in the mid of it initializing I wonder if that might be why it crashes assuming it is EAC at all.
Or am I simply reading it wrong and 4.3.0 also doesn't load, hmm well it is using Unreal Engine 4.11 as a base but EAC should be up to date although testing a older version from 4.0.0 to 4.3.0 could work if it's for some silly reason running with a older bin file for the whitelist which would be kinda weird but that might be a possibility too.
Could be both though with the recent fix for D3D12 depth buffer hook which these last two DLL's add in additional work on from the current pending merge on the Github page or if it's not EAC there's some additional issue to be worked out.
Suppose a compile with depth buffer disabled for testing would also be a way to see if that's where it breaks or not if that's the case assuming Easy Anti Cheat isn't blocking things.
Or am I simply reading it wrong and 4.3.0 also doesn't load, hmm well it is using Unreal Engine 4.11 as a base but EAC should be up to date although testing a older version from 4.0.0 to 4.3.0 could work if it's for some silly reason running with a older bin file for the whitelist which would be kinda weird but that might be a possibility too.
Could be both though with the recent fix for D3D12 depth buffer hook which these last two DLL's add in additional work on from the current pending merge on the Github page or if it's not EAC there's some additional issue to be worked out.
Suppose a compile with depth buffer disabled for testing would also be a way to see if that's where it breaks or not if that's the case assuming Easy Anti Cheat isn't blocking things.
- JBeckman
-
More
4 years 7 months ago - 4 years 7 months ago #1172
by JBeckman
Replied by JBeckman on topic Depth buffer detection modifications
thalixte wrote: And adding -eac_launcher in the exécution params does not help for Gears 5 ?
That was removed some years ago and hasn't been usable since 2018 or so unfortunately, think Tom Clancy's Ghost Recon Wildlands of 2017 was one of the last utilizing that flag or a variant of it.
(I liked what Watch_Dogs 2 did, prompt that EAC is not loaded and off goes online activities but everything else still jut works.)
Far Cry 5 suffered a bit from that and required a modified EAC .dll to force it out but that's been fixed in newer games and versions of this software too so it's not that simple either anymore and I know of no current way of disabling it from games utilizing this protection system unless they allow for a secondary exe without it being required.
/NoEAC - EAC_Launch -EAC_Launcher and some other names but then it was gone entirely.
EDIT: Wildlands was also patched so a combination of the old parameter and a modified .dll were required once it moved into Year 2 and additional updates dropped.
It's worth a try though but from what I know it's not an easy thing to just disable and take the hit to online activity in turn for a more open game process for injecting ReShade and such into and it's pretty strict in what it allows and a non-centralized client side whitelist makes it dependent on game patches for continued support and newer whitelist files and signatures.
EDIT: Though I do understand why it's there and why it is also quite heavy handed and the need for cheat protection primarily for more online focused games although it has it's downsides for these injectors, overlay software and more if it needs to interact with the game exe or game process in any way.
Last edit: 4 years 7 months ago by JBeckman.
- Rayman_77
-
More
4 years 7 months ago #1173
by Rayman_77
Replied by Rayman_77 on topic Depth buffer detection modifications
thalixte wrote: And adding -eac_launcher in the exécution params does not help for Gears 5 ?
It does not work
- Laitauriz
-
More
- lowenz
-
More
4 years 7 months ago - 4 years 7 months ago #1175
by lowenz
Replied by lowenz on topic Depth buffer detection modifications
?Laitauriz wrote: Hi Thalixte. I have two requests as i don't find any solution for now . I can't access properly to depth buffer in far cry 1 .It is bugged with all the dll i tried.
In addition, i can't find any depth buffer in Deus Ex ( Revision mod ) . I tried the dx9 and dx10 version, with MSAA disabled.
Thanks for your work here!
UNATCO offices, with the lastest master self-compiled
Remember to de-invert the DB and auto-preserve it (DX9 tab)
Last edit: 4 years 7 months ago by lowenz.
- Laitauriz
-
More
- thalixte
-
More
- lowenz
-
More
- thalixte
-
More
4 years 7 months ago - 4 years 7 months ago #1179
by thalixte
Replied by thalixte on topic Depth buffer detection modifications
.
Thks, Jonas. Yes, it is a pb when the new Reshade is released, it has to be whitelisted. I always use -eac_launcher for uplay titles. Didn't know it was useless.
I noticed one thing though: if fraps is enabled, i have to rename the dll from dxgi.dll to d3d12.dll, because most of the time, Reshade quit..
JBeckman wrote:
thalixte wrote: And adding -eac_launcher in the exécution params does not help for Gears 5 ?
That was removed some years ago and hasn't been usable since 2018 or so unfortunately, think Tom Clancy's Ghost Recon Wildlands of 2017 was one of the last utilizing that flag or a variant of it.
(I liked what Watch_Dogs 2 did, prompt that EAC is not loaded and off goes online activities but everything else still jut works.)
Far Cry 5 suffered a bit from that and required a modified EAC .dll to force it out but that's been fixed in newer games and versions of this software too so it's not that simple either anymore and I know of no current way of disabling it from games utilizing this protection system unless they allow for a secondary exe without it being required.
/NoEAC - EAC_Launch -EAC_Launcher and some other names but then it was gone entirely.
EDIT: Wildlands was also patched so a combination of the old parameter and a modified .dll were required once it moved into Year 2 and additional updates dropped.
It's worth a try though but from what I know it's not an easy thing to just disable and take the hit to online activity in turn for a more open game process for injecting ReShade and such into and it's pretty strict in what it allows and a non-centralized client side whitelist makes it dependent on game patches for continued support and newer whitelist files and signatures.
EDIT: Though I do understand why it's there and why it is also quite heavy handed and the need for cheat protection primarily for more online focused games although it has it's downsides for these injectors, overlay software and more if it needs to interact with the game exe or game process in any way.
Thks, Jonas. Yes, it is a pb when the new Reshade is released, it has to be whitelisted. I always use -eac_launcher for uplay titles. Didn't know it was useless.
I noticed one thing though: if fraps is enabled, i have to rename the dll from dxgi.dll to d3d12.dll, because most of the time, Reshade quit..
Last edit: 4 years 7 months ago by thalixte.
- JBeckman
-
More
4 years 7 months ago #1180
by JBeckman
Replied by JBeckman on topic Depth buffer detection modifications
Yeah Fraps can be difficult in it's own right due to how it hooks into processes and hasn't been updated in years though it's nice to hear that the D3D .dll names might be a way for those using the software for captures and recording still despite it's drawbacks.
And EAC yes it's going to be a problem for ReShade back and forth due to how it now can't really be disabled by command line so as games sees support ending there's going to be a version of ReShade that works and anything newer simply won't which poses problems if ReShade gets additional improvements or bug fixes that can not be utilized due to this blocker.
There's a few D3D12 improvements in the code already come to think of it plus the work you made for the depth buffer issue that might affect compatibility or performance for Tom Clancy's The Division 2 already when used under DirectX 12 mode although NVIDIA are still having a crash issue with this API so anyone with a NV GPU is better off taking a slight performance hit and ensuring stability via D3D11 for now, another downside with it being more on the developers side and something I am very curious to see how it will end up working.
Team has been on a vacation for a while but title update 6 should drop in October so it's moving again though at a slower pace but 4.3.0 is at least whitelisted and compatible though for the next version of ReShade it might take another update or hotfix for EAC's files to be updated to where this is whitelisted next.
Breakpoint the sequel to Wildlands comes out in early October too but they're using BattlEye this time around so it might be less of a issue and while the game has traces of D3D12 support in the code the beta at least was D3D11 only same as the prior Anvil Engine Next 2.0 titles.
(AC Origins, AC Odyssey, For Honor, Wildlands and Breakpoint here with the newer ones having bits of D3D12 but only shipping with D3D11 support.)
And for Vulkan I suppose that's going to be DOOM Eternal next out with this API in November although the existing titles from New Colossus, DOOM2016, No Man's Sky and a few others plus emulation might already provide a pretty good test ground for the VLK API support from 1.0 to 1.1 and the newer loaders and drivers though these should hopefully not interfere and remain backwards compatible while introducing support for newer features and extensions in the API.
(For DX12 I suppose it works much the same but tied to newer builds of Windows 10 itself and the display driver and the OS's system for the display model and such.)
And for Gears of War 5 it should be getting monthly content updates at least over the next year so there's a very good chance of additional versions of ReShade getting whitelisted and made compatible as part of this update process but no easy way to bypass EAC itself so if it's not in the whitelist it's not going to be let through the way it let's see it strips access handles or injection for any process trying to inject and sits as a kernel level Ring driver above most regular permissions giving it a bit more flexibility and control.
(One reason it's not so easily disabled either now that the command line parameter is removed from newer releases of EAC.)
And EAC yes it's going to be a problem for ReShade back and forth due to how it now can't really be disabled by command line so as games sees support ending there's going to be a version of ReShade that works and anything newer simply won't which poses problems if ReShade gets additional improvements or bug fixes that can not be utilized due to this blocker.
There's a few D3D12 improvements in the code already come to think of it plus the work you made for the depth buffer issue that might affect compatibility or performance for Tom Clancy's The Division 2 already when used under DirectX 12 mode although NVIDIA are still having a crash issue with this API so anyone with a NV GPU is better off taking a slight performance hit and ensuring stability via D3D11 for now, another downside with it being more on the developers side and something I am very curious to see how it will end up working.
Team has been on a vacation for a while but title update 6 should drop in October so it's moving again though at a slower pace but 4.3.0 is at least whitelisted and compatible though for the next version of ReShade it might take another update or hotfix for EAC's files to be updated to where this is whitelisted next.
Breakpoint the sequel to Wildlands comes out in early October too but they're using BattlEye this time around so it might be less of a issue and while the game has traces of D3D12 support in the code the beta at least was D3D11 only same as the prior Anvil Engine Next 2.0 titles.
(AC Origins, AC Odyssey, For Honor, Wildlands and Breakpoint here with the newer ones having bits of D3D12 but only shipping with D3D11 support.)
And for Vulkan I suppose that's going to be DOOM Eternal next out with this API in November although the existing titles from New Colossus, DOOM2016, No Man's Sky and a few others plus emulation might already provide a pretty good test ground for the VLK API support from 1.0 to 1.1 and the newer loaders and drivers though these should hopefully not interfere and remain backwards compatible while introducing support for newer features and extensions in the API.
(For DX12 I suppose it works much the same but tied to newer builds of Windows 10 itself and the display driver and the OS's system for the display model and such.)
And for Gears of War 5 it should be getting monthly content updates at least over the next year so there's a very good chance of additional versions of ReShade getting whitelisted and made compatible as part of this update process but no easy way to bypass EAC itself so if it's not in the whitelist it's not going to be let through the way it let's see it strips access handles or injection for any process trying to inject and sits as a kernel level Ring driver above most regular permissions giving it a bit more flexibility and control.
(One reason it's not so easily disabled either now that the command line parameter is removed from newer releases of EAC.)