4.0
- 8qX6a6mQhWSUBycMHgr7wgXCoTATys
this was really uncalled for. Next time be more concise. I understand a few of your points like being able to re-download older versions but we're not in a position to demand anything.
thanks @crosire for another great release.
- Martigen
Eh, no. If that were true, we'd all still be using Windows 3.1.v00d00m4n wrote: OH NO!
There is a basic rule in IT industry that everyone should follow - if aint broken - dont fix it!
There's absolutely nothing wrong with the way Reshade has progressed -- it's improved massively with each new release, and I -love- 4.0! The interface is slick, the compiling is lightning fast, the new features like in-built editor, enhanced stats tab, and oh lordy massively improved depth buffer detection are nothing short of amazing. And lets not forget some of the changes Crosire made were to be able to add Vulkan/DX12 support at a later date. Or, do you not want to use Reshade in a year's time with all the latest games v00d00m4n?
Every software project has teething problems with each new release, and Crosire has been incredibly responsive updating 4.0 to 4.01 and 4.02. There may still be a few issues, and the way to handle this is to provide a clear description of the problem with repeatable steps and if needed the logs so that Crosire can look at it -- this is how you help improve the product.
This is free software Crosire does on his own time. How about giving him some appreciation for all the hard work? For me, personally, it's revolutionised how I play games. I use it with every single one on my machine. And I can't thank Crosire enough for this amazing tool -- and, yes, all you shader developers too -- I love you all. I really appreciate the time spent coding and improving shaders to make our games look amazing. Thank you.
- Marty McFly
Updating shaders if they are broken is a 5 minute task, really, so that shouldn't hamper ReShade development. I basically developed since ReShade 1 and never felt disturbed or annoyed by the updates and necessary changes I had to perform.
Sure, some UI changes happened but the unprecise sliders problem already solved itself - drag now does what it did, crosire only changed most sliders in shaders to "slider". The UI can be un-docked so you can use it like before - I do that for example so besides the new stuff you'd see no difference between me using 3 and 4.
The jump from 1 to 2 and from 2 to 3 were necessary. No one could be bothered to edit the huge files in 1 or use the mediator in 2. It's very good as it is now.
- TheHunter
Hunt Showdown says no 3d11 card supported and closes, so I guess it doesn't like it? it pinpoints to that dxgi.dll
Doom3 also crashes, I have sikkmod, but I also tried vanilla, and same thing.
WARNING: file skins/skins_mp.skin, line 841: skin 'skins/characters/player/marine_mp_green_withskel' previously defined at skins/skins_characters_player.skin:570
Initializing renderSystem
using ARB renderSystem
renderSystem initialized.
5206 strings read from strings/english.lang
5308 strings read from strings/english_venom_menu.lang
Couldn't open journal files
execing editor.cfg
execing default.cfg
execing DoomConfig.cfg
execing autoexec.cfg
5206 strings read from strings/english.lang
5308 strings read from strings/english_venom_menu.lang
Initializing Sound System
Setup OpenAL device and context... Done.
OpenAL: found EAX 4.0 extension
OpenAL: found EAX-RAM extension, 63360kB\65536kB
OpenAL: found SB X-Fi Audio [0001]
OpenAL: found 127 hardware voices
sound system initialized.
R_InitOpenGL
Initializing OpenGL subsystem
...registered window class
...registered fake window class
...initializing QGL
...calling LoadLibrary( 'opengl32' ): succeeded
Couldn't find proc address for: wglGetExtensionsStringARB
Couldn't find proc address for: wglSwapIntervalEXT
Couldn't find proc address for: wglGetPixelFormatAttribivARB
Couldn't find proc address for: wglGetPixelFormatAttribfvARB
Couldn't find proc address for: wglChoosePixelFormatARB
Couldn't find proc address for: wglCreatePbufferARB
Couldn't find proc address for: wglGetPbufferDCARB
Couldn't find proc address for: wglReleasePbufferDCARB
Couldn't find proc address for: wglDestroyPbufferARB
Couldn't find proc address for: wglQueryPbufferARB
Couldn't find proc address for: wglBindTexImageARB
Couldn't find proc address for: wglReleaseTexImageARB
Couldn't find proc address for: wglSetPbufferAttribARB
...calling CDS: ok
...created window @ 0,0 (2880x1620)
Initializing OpenGL driver
...getting DC: succeeded
...GLW_ChoosePFD failed
Shutting down OpenGL subsystem
...wglMakeCurrent( NULL, NULL ): success
...releasing DC: failed
...resetting display
...shutting down QGL
...unloading OpenGL DLL
Initializing OpenGL subsystem
...initializing QGL
...calling LoadLibrary( 'opengl32' ): succeeded
Couldn't find proc address for: wglGetExtensionsStringARB
Couldn't find proc address for: wglSwapIntervalEXT
Couldn't find proc address for: wglGetPixelFormatAttribivARB
Couldn't find proc address for: wglGetPixelFormatAttribfvARB
Couldn't find proc address for: wglChoosePixelFormatARB
Couldn't find proc address for: wglCreatePbufferARB
Couldn't find proc address for: wglGetPbufferDCARB
Couldn't find proc address for: wglReleasePbufferDCARB
Couldn't find proc address for: wglDestroyPbufferARB
Couldn't find proc address for: wglQueryPbufferARB
Couldn't find proc address for: wglBindTexImageARB
Couldn't find proc address for: wglReleaseTexImageARB
Couldn't find proc address for: wglSetPbufferAttribARB
...calling CDS: ok
...created window @ 0,0 (640x480)
Initializing OpenGL driver
...getting DC: succeeded
...GLW_ChoosePFD failed
Shutting down OpenGL subsystem
...wglMakeCurrent( NULL, NULL ): success
...releasing DC: failed
...resetting display
...shutting down QGL
...unloading OpenGL DLL
idRenderSystem::Shutdown()
Shutting down OpenGL subsystem
...shutting down QGL
Unable to initialize OpenGL
Any workarounds?
- JBeckman
Can't say much about DOOM 3, Sikkmod significantly changes the OpenGL code but aside from driver profiles and hacks (More of a issue for AMD.) that shouldn't be too breaking though I suppose it falls upon whatever rewrites have been done to the OpenGL files, shader structures and such I don't fully remember but I know it's mostly in plain text and pretty mod friendly thus allowing modders to write in a lot of additional features and support for shaders and such.
(Like the early parallax mods.)
EDIT: Unless Hunt Showdown also uses some form of anti-cheat restricting DXGI.dll from loading and that's what is breaking things here, it's still in early access as I recall or beta at least but they might have something to ward against file injection even if it's ReShade and the new .dll might not yet have been whitelisted if that's a thing.
- TheHunter
JBeckman wrote: d3d11.dll might be another way to get it to load unless the game uses features that aren't fully supported in ReShade yet although that would make Hunt Showdown exclusive to Windows 8 or even Windows 10 drawing on DXGI 1.5 or D3D11.3 and newer with no fallback or feature level support which seems unlikely but I have not kept up to date with the latest Cry Engine V changes though I know D3D12 and Vulkan are both supported now by the engine in addition to D3D11 from before.
Can't say much about DOOM 3, Sikkmod significantly changes the OpenGL code but aside from driver profiles and hacks (More of a issue for AMD.) that shouldn't be too breaking though I suppose it falls upon whatever rewrites have been done to the OpenGL files, shader structures and such I don't fully remember but I know it's mostly in plain text and pretty mod friendly thus allowing modders to write in a lot of additional features and support for shaders and such.
(Like the early parallax mods.)
EDIT: Unless Hunt Showdown also uses some form of anti-cheat restricting DXGI.dll from loading and that's what is breaking things here, it's still in early access as I recall or beta at least but they might have something to ward against file injection even if it's ReShade and the new .dll might not yet have been whitelisted if that's a thing.
Hi Jonas
it detects easy anticheat and makes a workaround if I select main folder, but then I saw the game exe is in bin folder, when I put it there it doesn't want to start.
And yes easy anticheat says dxgi.dll is a untrusted app afterwards.. will post this @ hunt showdown thread, maybe they will exclude it.
By doom it just crashes when it tries to grab fullscreen, idk.. I had custom DSR 2880x1620, but then I saw also 640x480 crash in log. Like I said I also started default exe without sikkmod and same thing? as seen in quote.
00:26:39:015 [07488] | INFO | Registering hooks for "user32.dll" ...
00:26:39:015 [07488] | INFO | > Libraries loaded.
00:26:39:015 [07488] | INFO | > Found 13 match(es). Installing ...
00:26:39:015 [07488] | INFO | Registering hooks for "ws2_32.dll" ...
00:26:39:015 [07488] | INFO | > Libraries loaded.
00:26:39:015 [07488] | INFO | > Found 8 match(es). Installing ...
00:26:39:031 [07488] | INFO | Registering hooks for "C:\\WINDOWS\\system32\\d3d9.dll" ...
00:26:39:031 [07488] | INFO | > Delayed.
00:26:39:031 [07488] | INFO | Registering hooks for "C:\\WINDOWS\\system32\\d3d10.dll" ...
00:26:39:031 [07488] | INFO | > Delayed.
00:26:39:031 [07488] | INFO | Registering hooks for "C:\\WINDOWS\\system32\\d3d10_1.dll" ...
00:26:39:031 [07488] | INFO | > Delayed.
00:26:39:031 [07488] | INFO | Registering hooks for "C:\\WINDOWS\\system32\\d3d11.dll" ...
00:26:39:031 [07488] | INFO | > Delayed.
00:26:39:031 [07488] | INFO | Registering hooks for "C:\\WINDOWS\\system32\\dxgi.dll" ...
00:26:39:031 [07488] | INFO | > Delayed.
00:26:39:031 [07488] | INFO | Registering hooks for "C:\\WINDOWS\\system32\\opengl32.dll" ...
00:26:39:031 [07488] | INFO | > Delayed until first call to an exported function.
00:26:39:031 [07488] | INFO | Initialized.
00:26:39:031 [07488] | INFO | Redirecting 'RegisterClassA(02FFFE0C)' ...
00:26:39:031 [07488] | INFO | > Adding 'CS_OWNDC' window class style flag to 'DOOM 3 WinConsole'.
00:26:39:031 [09252] | INFO | Installing delayed hooks for "C:\\WINDOWS\\system32\\d3d11.dll" (Just loaded via 'LoadLibrary(""ext-ms-win-mininput-inputhost-l1-1-1.dll"")') ...
00:26:39:031 [09252] | INFO | > Found 2 match(es). Installing ...
00:26:39:055 [09252] | INFO | Installing delayed hooks for "C:\\WINDOWS\\system32\\dxgi.dll" (Just loaded via 'LoadLibrary(""ext-ms-win-mininput-inputhost-l1-1-1.dll"")') ...
00:26:39:055 [09252] | INFO | > Found 7 match(es). Installing ...
00:26:39:572 [07488] | INFO | Redirecting 'RegisterClassA(02FFE26C)' ...
00:26:39:572 [07488] | INFO | > Adding 'CS_OWNDC' window class style flag to 'DOOM3'.
00:26:39:572 [07488] | INFO | Redirecting 'RegisterClassA(02FFE26C)' ...
00:26:39:572 [07488] | INFO | > Adding 'CS_OWNDC' window class style flag to 'DOOM3_WGL_FAKE'.
00:26:39:574 [07488] | INFO | Redirecting 'wglChoosePixelFormat(64011A53, 007750E0)' ...
00:26:39:574 [07488] | INFO | > Dumping pixel format descriptor:
00:26:39:574 [07488] | INFO | +
+
+
00:26:39:574 [07488] | INFO | | Name | Value |
00:26:39:574 [07488] | INFO | +
+
+
00:26:39:574 [07488] | INFO | | Flags | 0x25 |
00:26:39:574 [07488] | INFO | | ColorBits | 24 |
00:26:39:574 [07488] | INFO | | DepthBits | 8 |
00:26:39:574 [07488] | INFO | | StencilBits | 0 |
00:26:39:574 [07488] | INFO | +
+
+
00:26:39:575 [07488] | INFO | Installing export hooks for "C:\\WINDOWS\\system32\\opengl32.dll" ...
00:26:39:575 [07488] | INFO | > Found 360 match(es). Installing ...
00:26:39:794 [07488] | INFO | > Returned format: 0
00:26:39:794 [07488] | INFO | Redirecting 'wglSetPixelFormat(64011A53, 0, 007750E0)' ...
00:26:39:794 [07488] | WARN | > 'wglSetPixelFormat' failed with error code 87!
00:26:39:794 [07488] | INFO | Redirecting 'wglCreateContext(64011A53)' ...
00:26:39:794 [07488] | INFO | > Passing on to 'wglCreateLayerContext' ...
00:26:39:794 [07488] | INFO | Redirecting 'wglCreateLayerContext(64011A53, 0)' ...
00:26:39:794 [07488] | WARN | > 'wglCreateLayerContext' failed with error code 2000!
00:26:39:794 [07488] | INFO | Redirecting 'wglMakeCurrent(64011A53, 00000000)' ...
00:26:39:794 [07488] | WARN | > 'wglMakeCurrent' failed with error code 2000!
00:26:39:794 [07488] | INFO | Redirecting 'wglMakeCurrent(00000000, 00000000)' ...
00:26:39:794 [07488] | INFO | Redirecting 'wglMakeCurrent(00000000, 00000000)' ...
00:26:39:794 [07488] | INFO | Redirecting 'wglDeleteContext(00000000)' ...
00:26:39:794 [07488] | WARN | > 'wglDeleteContext' failed with error code 6!
00:26:39:794 [07488] | INFO | Redirecting 'wglCreateContext(64011A53)' ...
00:26:39:794 [07488] | INFO | > Passing on to 'wglCreateLayerContext' ...
00:26:39:794 [07488] | INFO | Redirecting 'wglCreateLayerContext(64011A53, 0)' ...
00:26:39:794 [07488] | WARN | > 'wglCreateLayerContext' failed with error code 2000!
00:26:39:794 [07488] | INFO | Redirecting 'wglMakeCurrent(64011A53, 00000000)' ...
00:26:39:794 [07488] | WARN | > 'wglMakeCurrent' failed with error code 2000!
00:26:39:795 [07488] | INFO | Redirecting 'wglMakeCurrent(00000000, 00000000)' ...
00:26:39:795 [07488] | INFO | Redirecting 'wglDeleteContext(00000000)' ...
00:26:39:795 [07488] | WARN | > 'wglDeleteContext' failed with error code 6!
00:26:39:975 [07488] | INFO | Redirecting 'wglChoosePixelFormat(180102CF, 02FFE1BC)' ...
00:26:39:975 [07488] | INFO | > Dumping pixel format descriptor:
00:26:39:975 [07488] | INFO | +
+
+
00:26:39:975 [07488] | INFO | | Name | Value |
00:26:39:975 [07488] | INFO | +
+
+
00:26:39:975 [07488] | INFO | | Flags | 0x25 |
00:26:39:975 [07488] | INFO | | ColorBits | 32 |
00:26:39:975 [07488] | INFO | | DepthBits | 24 |
00:26:39:975 [07488] | INFO | | StencilBits | 8 |
00:26:39:975 [07488] | INFO | +
+
+
00:26:39:975 [07488] | INFO | > Returned format: 0
00:26:39:984 [07488] | INFO | Redirecting 'wglMakeCurrent(00000000, 00000000)' ...
00:26:40:126 [07488] | INFO | Redirecting 'wglChoosePixelFormat(4C011A90, 007750E0)' ...
00:26:40:126 [07488] | INFO | > Dumping pixel format descriptor:
00:26:40:126 [07488] | INFO | +
+
+
00:26:40:126 [07488] | INFO | | Name | Value |
00:26:40:126 [07488] | INFO | +
+
+
00:26:40:126 [07488] | INFO | | Flags | 0x25 |
00:26:40:126 [07488] | INFO | | ColorBits | 24 |
00:26:40:126 [07488] | INFO | | DepthBits | 8 |
00:26:40:126 [07488] | INFO | | StencilBits | 0 |
00:26:40:126 [07488] | INFO | +
+
+
00:26:40:128 [07488] | INFO | > Returned format: 0
00:26:40:128 [07488] | INFO | Redirecting 'wglSetPixelFormat(4C011A90, 0, 007750E0)' ...
00:26:40:129 [07488] | WARN | > 'wglSetPixelFormat' failed with error code 87!
00:26:40:129 [07488] | INFO | Redirecting 'wglCreateContext(4C011A90)' ...
00:26:40:129 [07488] | INFO | > Passing on to 'wglCreateLayerContext' ...
00:26:40:129 [07488] | INFO | Redirecting 'wglCreateLayerContext(4C011A90, 0)' ...
00:26:40:129 [07488] | WARN | > 'wglCreateLayerContext' failed with error code 2000!
00:26:40:129 [07488] | INFO | Redirecting 'wglMakeCurrent(4C011A90, 00000000)' ...
00:26:40:130 [07488] | WARN | > 'wglMakeCurrent' failed with error code 2000!
00:26:40:130 [07488] | INFO | Redirecting 'wglMakeCurrent(00000000, 00000000)' ...
00:26:40:130 [07488] | INFO | Redirecting 'wglMakeCurrent(00000000, 00000000)' ...
00:26:40:130 [07488] | INFO | Redirecting 'wglDeleteContext(00000000)' ...
00:26:40:130 [07488] | WARN | > 'wglDeleteContext' failed with error code 6!
00:26:40:130 [07488] | INFO | Redirecting 'wglCreateContext(4C011A90)' ...
00:26:40:130 [07488] | INFO | > Passing on to 'wglCreateLayerContext' ...
00:26:40:130 [07488] | INFO | Redirecting 'wglCreateLayerContext(4C011A90, 0)' ...
00:26:40:131 [07488] | WARN | > 'wglCreateLayerContext' failed with error code 2000!
00:26:40:131 [07488] | INFO | Redirecting 'wglMakeCurrent(4C011A90, 00000000)' ...
00:26:40:131 [07488] | WARN | > 'wglMakeCurrent' failed with error code 2000!
00:26:40:161 [07488] | INFO | Redirecting 'wglMakeCurrent(00000000, 00000000)' ...
00:26:40:161 [07488] | INFO | Redirecting 'wglDeleteContext(00000000)' ...
00:26:40:161 [07488] | WARN | > 'wglDeleteContext' failed with error code 6!
00:26:40:287 [07488] | INFO | Redirecting 'wglChoosePixelFormat(7F01021B, 02FFE1BC)' ...
00:26:40:287 [07488] | INFO | > Dumping pixel format descriptor:
00:26:40:287 [07488] | INFO | +
+
+
00:26:40:287 [07488] | INFO | | Name | Value |
00:26:40:287 [07488] | INFO | +
+
+
00:26:40:287 [07488] | INFO | | Flags | 0x25 |
00:26:40:287 [07488] | INFO | | ColorBits | 32 |
00:26:40:287 [07488] | INFO | | DepthBits | 24 |
00:26:40:287 [07488] | INFO | | StencilBits | 8 |
00:26:40:287 [07488] | INFO | +
+
+
00:26:40:288 [07488] | INFO | > Returned format: 0
00:26:40:298 [07488] | INFO | Redirecting 'wglMakeCurrent(00000000, 00000000)' ...
00:26:43:950 [07488] | INFO | Exiting ...
00:26:43:950 [07488] | INFO | Uninstalling 394 hook(s) ...
00:26:43:950 [07488] | INFO | Exited.
- tats25
- brazzjazz
WON version:
Error message "ChoosePixelFormat failed". The error message in the ingame menu then says "The selected OpenGL mode is not supported by your video card". Everything worked normally again when I replaced the new with the old (3.4.1) opengl32.dll.
opengl32.txt:
Steam version:
opengl32.txt:
- XIIICaesar
- brazzjazz
dxgi.txt for the crash from 4.0.2 and x64 exe with D3D11:
- brazzjazz
Have to agree with you on that one. Sliders I find much fumblier than the solution we had before that. You cannot double-click an entry anymore to directly type a new value. Also, you cannot use the mouse for pixel-perfect accuracy the same way you could with the older system.OtisInf wrote: Haven't I felt frustration when v4 came out and e.g. 'drag' was now a 'slider'? Sure.
Also, while in theory you can still go back to 3.4.1 when problems arise with 4.x, it seems that the shaders you choose and download during the installation prompt belong to the 4.x version, rendering them more and more incompatible and therefore useless with the earlier versions. I've noticed a lot less options with AdvancedCRT and Curves for instance, with a newly installed 3.4.1.
As for ReShade in general, I'm very thankful for a tool like this, it has enriched my gaming experience a lot. If I report bugs and have other "complaints", it's meant as a benefit to other gamers and as constructive feedback, but I'm sure almost everybody else sees it this way. I would donate something as well, but there is no donation button yet.
brazzjazz wrote:
Have to agree with you on that one. Sliders I find much fumblier than the solution we had before that. You cannot double-click an entry anymore to directly type a new value. Also, you cannot use the mouse for pixel-perfect accuracy the same way you could with the older system.OtisInf wrote: Haven't I felt frustration when v4 came out and e.g. 'drag' was now a 'slider'? Sure.
Also, while in theory you can still go back to 3.4.1 when problems arise with 4.x, it seems that the shaders you choose and download during the installation prompt belong to the 4.x version, rendering them more and more incompatible and therefore useless with the earlier versions. I've noticed a lot less options with AdvancedCRT and Curves for instance, with a newly installed 3.4.1.
As for ReShade in general, I'm very thankful for a tool like this, it has enriched my gaming experience a lot. If I report bugs and have other "complaints", it's meant as a benefit to other gamers and as constructive feedback, but I'm sure almost everybody else sees it this way. I would donate something as well, but there is no donation button yet.
There's some discussion earlier in the thread about how to a) edit 4.x shaders to use the old drag system instead of the slider; and b) how to find the correct shaders for old versions of ReShade (and there is a link specifically to the shaders for 3.4.1). You might find it helpful.
You should get into the habit of backing up your shaders too, so you always have the correct ones for the version you want to use.
- altokitty
I do have a dumb question, maybe this is in plain text somewhere but I can't figure out how to change shader hotkeys. What's the new way to do it now?
Just saying, that function was changed to Ctrl+Click, which I find to be much better than double-clicking. Especially in games where clicking can disturb the camera. Still, options for both would be great.brazzjazz wrote: You cannot double-click an entry anymore to directly type a new value.
- Daodan
altokitty wrote: I do have a dumb question, maybe this is in plain text somewhere but I can't figure out how to change shader hotkeys. What's the new way to do it now?
Right-click on the technique. Opens up a small window where you can set the hotkey and also change the position of the technique.
- brazzjazz
Cool, thanks for the infos! Yes, I was thinking the same, luckily I have installed ReShade to so many game folders that I can recuperate the 3.4.1 shaders easily.amoebae wrote: There's some discussion earlier in the thread about how to a) edit 4.x shaders to use the old drag system instead of the slider; and b) how to find the correct shaders for old versions of ReShade (and there is a link specifically to the shaders for 3.4.1). You might find it helpful.
You should get into the habit of backing up your shaders too, so you always have the correct ones for the version you want to use.
EDIT: Are there different sets of shaders for OpenGL, D3D9 and D3D10/11? I guess not, since they are written in ReShade's own shader language, right?
Another suggestion: concerning the UI, the window size and layout should be adjusted in some way, I keep resizing the window over and over again, currently the window
· does not resize once you have changed the resolution (too small when you're using DSR, too big when you have switched back)
· does not divide the space between shaders and shader settings appropriately, the shader settings get too little space, and should usually have 50%, or even more if there are only few shaders making the top part even smaller
· frequently, the shaders and / or shader settings are not sorted alphabetically. I know that you can sort the shaders, but I guess the shader settings are not sorted accordingly. Also, when you reinstall ReShade and add a shader, I think that shader is then listed last.
I think handling shaders may work better with a "+" menu sort of way, as in folders. You expand a shader and edit settings, that way you avoid repeated scrolling and searching for the respective shader settings.
On another note, with satisfaction I noticed you can set the values back to default. You easily regret fumbling around wildly before taking note of the original values...
- dorez`
- Martigen
Yegads, another NS2 playerbrazzjazz wrote: Natural Selection 2 (x64) crashes with ReShade 4.0.2 and D3D11. Can't say about the 32-bit version as I noticed it always seems to switch to the x64 version (only the dxgi.dll in the x64 subdirectory is loaded). DLLs for D3D9 (d3d9.dll) are not loaded when DirectX 9 is used. I keep testing different combinations.
It works fine with NS2 -- rename it to d3d11.dll in the x64 directory. I think I tried dxgi.dll at first with the same result. Some games seem to prefer one or the other.
Working log:
- BlueSkyKnight
- Spellshade
Yes, ReShade shaders are in ReShade's own FX language. Resizing the UI is pretty quick to do and the settings can save if you enable it in the options on 4.0.2. And you can collapse and expand shaders' settings individually or in their entirety already, either by clicking on the shader name or using the Expand All / Collapse All button at the top right of the ReShade bar.
As far as overall UI scale to account for 4K DSR resolutions, I'd prefer this didn't make it in - native 4K users get bent over with huge UI this one... including me
Oh, and DOF visualization for distance levels would be on the shader developer, not crosire's end.
- brazzjazz
Hmm, renaming it to d3d11.dll did not improve things... I also tried loading the game without shaders, AND deactivated anti-virus, AND deactivated overlay, AND deactivated MSI Afterburner / Riva Tuner... to no avail. It crashes right before the menu. NS2 seems to be a little unstable on its own, though, since it seems to detest alt-tabbing for instance, and has occasionally crashed with D3D9 and 3.4.1 as well. It might as well have a different reason than ReShade itself. NS2 behaves strangely anyway, because why would it load d3d9.dll in DX11 mode?? It's the first game to ever do that.Martigen wrote: Yegads, another NS2 player
Hello! *waves*. Come by Woozas. Don't give me large server crap, it's awesome fun
It works fine with NS2 -- rename it to d3d11.dll in the x64 directory. I think I tried dxgi.dll at first with the same result. Some games seem to prefer one or the other.
As to your warm greeting: NS2 is one of the many games I have recently installed and peeked in out of curiosity, but since you were so welcoming I might as well drop by when I have the chance to. Feel free to add me anywhere you want.
P.S. My NS2 ReShade preset sfx.thelazy.net/games/preset/9956/
Indeed. This would mean several prayers and thereby reducing efficiency, but I will accept that lol. Also good points you mentioned otherwise, the scaling aspect has been a (minor) nuisance to me, but of course it shouldn't be too hastily "fixed" for one group and become a new nuisance for anotherSpellshade wrote: Oh, and DOF visualization for distance levels would be on the shader developer, not crosire's end.
"Reason for Editing": my very own inadequacies.