- Posts: 177
4.0
2 years 9 months ago #42 by Martigen
Replied by Martigen on topic 4.0
Hey Crosire,
Thanks for the update, you are amazing
Another suggestion:
So we right-click to set a key on a shader, no worries. I tend to have lots of different configs over different games, sometimes with 2-4 enabling keys (hey, look, I test a lot of shit
). I can't see which keys are enabled on a shader without right-clicking on it. So... would it be possible to list to the right of a shader if a key has been assigned, and what that key is?
Thanks for the update, you are amazing
Another suggestion:
So we right-click to set a key on a shader, no worries. I tend to have lots of different configs over different games, sometimes with 2-4 enabling keys (hey, look, I test a lot of shit
). I can't see which keys are enabled on a shader without right-clicking on it. So... would it be possible to list to the right of a shader if a key has been assigned, and what that key is? 
2 years 9 months ago #54 by sajittarius
Replied by sajittarius on topic 4.0
Awesome update, thanks Crosire.
I was pissed at the new UI (dragging tabs) until i understood it. I just wanted to move everything from the left to a small window in the middle, keeping all the tabs together, like i did with the old version (which seems impossible now, lol)
It's actually pretty cool that they can be separated and/or minimized, just took a little extra work to get everything in the right place.
I was pissed at the new UI (dragging tabs) until i understood it. I just wanted to move everything from the left to a small window in the middle, keeping all the tabs together, like i did with the old version (which seems impossible now, lol)
It's actually pretty cool that they can be separated and/or minimized, just took a little extra work to get everything in the right place.
2 years 9 months ago #56 by Newbie
Thank you for the quick reply. How long does it take for EAC to whitelist a new version usually? Can't wait to try it out, it looks so great
Replied by Newbie on topic 4.0
Doesn't work with Dead by Daylight. I get a pop up window that says that EAC (easy anti cheat) found a non verified file. I cant launch the game at all, EAC Stopps it. But with ReShade 3.4.1 it works without problemsThat's because 3.4.1 is whitelisted. 4.0.1 just came out, it isn't yet.
Corsair will there be a fix for Second life ?Use 4.0.1.
Thank you for the quick reply. How long does it take for EAC to whitelist a new version usually? Can't wait to try it out, it looks so great
2 years 9 months ago #58 by OtisInf
- Add an option, where the dockingspace is defined: screen or window. screen is the current default, window is the imgui default I think. If set to window, you get effectively the window movement behavior of v3 but no docking (duh) outside the window. For a lot of people this is fine, they don't edit shaders for instance.
- When dockingspace is set to screen, when you press CTRL + RIGHT ARROW the window and all its tabs dock to the right side of the screen. CTRL + UP to the top, CTRL + DOWN to the bottom and CTRL + LEFT to left side of the screen. This is often enough for most scenarios, where you want to look at something that's currently covered by the window. If there's a panel in the 'open space' (e.g. the editor) then that panel is kept in the open space, the window just moves from left to right/top/bottom.
Would that work?
Replied by OtisInf on topic 4.0
How about this:(which seems impossible now, lol)It's not. It's just a bit buggy right now:
- Add an option, where the dockingspace is defined: screen or window. screen is the current default, window is the imgui default I think. If set to window, you get effectively the window movement behavior of v3 but no docking (duh) outside the window. For a lot of people this is fine, they don't edit shaders for instance.
- When dockingspace is set to screen, when you press CTRL + RIGHT ARROW the window and all its tabs dock to the right side of the screen. CTRL + UP to the top, CTRL + DOWN to the bottom and CTRL + LEFT to left side of the screen. This is often enough for most scenarios, where you want to look at something that's currently covered by the window. If there's a panel in the 'open space' (e.g. the editor) then that panel is kept in the open space, the window just moves from left to right/top/bottom.
Would that work?
2 years 9 months ago - 2 years 9 months ago #60 by Martigen
Replied by Martigen on topic 4.0
If I may some feedback on depth shenanigans:
So DisplayDepth now lets you toggle the preprocessor defines in real-time to get the right settings. But it doesn't save them, you then have to:
Anyway, would it be possible to:
1) Have DisplayDepth.fx edit the preprocessor defines directly in the d3d11/d3d9/dxgi/opengl32 ini file -- so that you set them in DisplayDepth.fx and you're done, no fart-arsing around.
2) Failing that -- update the instructions in the DisplayDepth.fx main window hover help and in the pre-processor button help so people don't miss this. There's going to be a lot of hair-pulling when depth effects don't work as expected otherwise...
EDIT: There's also no information about heading to the D3D11/D3D9 tab to select different buffers, which is also essential for anyone coming to depth detection for the first time.
So DisplayDepth now lets you toggle the preprocessor defines in real-time to get the right settings. But it doesn't save them, you then have to:
- Go to the settings Tab
- Select experimental variables UI
- Go back to Home Tab
- Edit pre-processor defines
Anyway, would it be possible to:
1) Have DisplayDepth.fx edit the preprocessor defines directly in the d3d11/d3d9/dxgi/opengl32 ini file -- so that you set them in DisplayDepth.fx and you're done, no fart-arsing around.
2) Failing that -- update the instructions in the DisplayDepth.fx main window hover help and in the pre-processor button help so people don't miss this. There's going to be a lot of hair-pulling when depth effects don't work as expected otherwise...
EDIT: There's also no information about heading to the D3D11/D3D9 tab to select different buffers, which is also essential for anyone coming to depth detection for the first time.