- Posts: 34
Depth buffer detection modifications
2 years 3 months ago - 2 years 3 months ago #1094 by GregTheChief
Replied by GregTheChief on topic Depth buffer detection modifications
Hmm I deleted the keys in reg-edit like u discribed, but still no reshade UI 
(Its POS1 or shift + F2 isnt it?)
And yes I use the steam version
(Its POS1 or shift + F2 isnt it?)
And yes I use the steam version
2 years 3 months ago - 2 years 3 months ago #1095 by JBeckman
Replied by JBeckman on topic Depth buffer detection modifications
You can also rename GameOverlay64.dll and kick out the Steam overlay entirely though relaunching Steam will re-validate and add the file back and disabling validation breaks game updating so rename the file back and only use it for testing purposes.
Other functionality goes through that overlay too (64 for 64-bit other one for 32-bit.) so things like the gamepad and input options and more, I keep it disabled for compatibility same as Uplay although neither are as problematic overall as some other software (EA Origin for one.) since I don't really need or use the overlay for anything.
Disabling it in the Steam client just hides the overlay also so that doesn't work it still to hook and inject even if it's no longer drawn just to mention that bit.
Registry bit is the layering for VLK and the Steam overlay but renaming or deleting them and relaunching the game should work just as well though you get the overlay but it shouldn't intefere with Vulkan since it doesn't pass through these other .dll files for this feature though there's also the layer Steam uses for the shader cache if you have that setting enabled in the client.
VkLayer_steam_fossilize64.dll for "Steam Pipeline Caching Layer",
Haven't gotten around to doing much testing at all and mostly just trying to deal with documentation and getting some understanding but eh it's going to be a slow process, there's also the runtime or the SDK but the display driver should contain a reasonably new runtime so other than some additional extensions that are unlikely to be featured outside of development it shouldn't matter for the runtime. (SDK adds some development and debug features but that's more advanced and not really needed for regular usage.)
Seems Metro Exodus also broke something with it's recent update and DX12, low level API usage is going to be a challenge I presume but for now this is VLK focused and existing API's should mostly continue to function as before though it's worth noting how prone to breaking some things can be.
(And that's without software such as game updates or the display drivers thrown around too much.)
Other functionality goes through that overlay too (64 for 64-bit other one for 32-bit.) so things like the gamepad and input options and more, I keep it disabled for compatibility same as Uplay although neither are as problematic overall as some other software (EA Origin for one.) since I don't really need or use the overlay for anything.
Disabling it in the Steam client just hides the overlay also so that doesn't work it still to hook and inject even if it's no longer drawn just to mention that bit.
Registry bit is the layering for VLK and the Steam overlay but renaming or deleting them and relaunching the game should work just as well though you get the overlay but it shouldn't intefere with Vulkan since it doesn't pass through these other .dll files for this feature though there's also the layer Steam uses for the shader cache if you have that setting enabled in the client.
VkLayer_steam_fossilize64.dll for "Steam Pipeline Caching Layer",
Haven't gotten around to doing much testing at all and mostly just trying to deal with documentation and getting some understanding but eh it's going to be a slow process, there's also the runtime or the SDK but the display driver should contain a reasonably new runtime so other than some additional extensions that are unlikely to be featured outside of development it shouldn't matter for the runtime. (SDK adds some development and debug features but that's more advanced and not really needed for regular usage.)
Seems Metro Exodus also broke something with it's recent update and DX12, low level API usage is going to be a challenge I presume but for now this is VLK focused and existing API's should mostly continue to function as before though it's worth noting how prone to breaking some things can be.
(And that's without software such as game updates or the display drivers thrown around too much.)
2 years 3 months ago #1099 by JBeckman
Replied by JBeckman on topic Depth buffer detection modifications
Pos1 = Home though for a German keyboard layout which I think ReShade is unicode aware so these shouldn't interfere other than possibly the key layout differing slightly.
On startup the ReShade initializing on-screen display and shader compiler should also pop up in the upper left corner though with 4.0 the shader compile time is very fast so it doesn't stay visible for more than a few seconds at most but that's also a means for seeing that ReShade has initialized assuming the software starts up as usual without any errors.
On startup the ReShade initializing on-screen display and shader compiler should also pop up in the upper left corner though with 4.0 the shader compile time is very fast so it doesn't stay visible for more than a few seconds at most but that's also a means for seeing that ReShade has initialized assuming the software starts up as usual without any errors.
2 years 3 months ago #1100 by GregTheChief
Replied by GregTheChief on topic Depth buffer detection modifications
Yes POS 1 is HOME
Strange... any other ideas what i can try?
Strange... any other ideas what i can try?