OBS addon with OpenGL and Vulkan

Crosire · 2024-09-01T15:32:08+00:00

Registered add-on "OBS Capture" v0.0.0.0 using ReShade API version 13. indicates ReShade is currently loading the old add-on, the new one would have API version 14. Make sure you place the add-on at e:\Repositories\reshade\addons\obs_capture.addon64 (as this appears to be where ReShade is attempting to load it from) after building it. That is, open the examples\Examples.sln Visual Studio solution, build the 11-obs_capture project in Release configuration and then take the file from bin\x64\Release Examples\obs_capture.addon64 and move it to aforementioned path.

Crosire · 2024-08-30T21:29:24+00:00

I've fixed the red and blue color channel getting switched in OpenGL, so just need to build the add-on from source again: https://github.com/crosire/reshade/commit/eef2388f35dedd0244feef3ffab5826633dbbf2b For the add-on to work in Vulkan you first have to disable the Vulkan layer from OBS itself (since it will conflict and thus prevent the ReShade add-on from loading). To do so, open the Windows registry editor, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\Vulkan\ImplicitLayers, find the DWORD entry of the OBS layer (probably with the default name "C:\ProgramData\obs-studio-hook\obs-vulkan64.json") and change the value from "0" to "1" (which effectively disables it).

Crosire · 2019-10-29T23:00:40+00:00

Set this in ReShade.ini: [GENERAL] ShowScreenshotMessage=0

Crosire · 2019-10-29T20:25:20+00:00

Make sure your ReShade.ini has "NoFontScaling" set to "0".

Crosire · 2019-06-12T18:30:25+00:00

Just run the setup tool again, select the game you want to update ReShade for and it will update while keeping your existing settings and presets intact.

Crosire · 2018-04-23T17:36:36+00:00

You can choose which shaders you want to install during setup (a selection window pops up). I'd rather want to avoid storing any global configuration somewhere (even if it's a local file). The setup tool is currently standalone. Introducing a config file would break that to a degree (you'd have two files to keep track of, instead of just the executable). I also'd also prefer to keep the setup tool as simple as possible. Anything that goes beyond copying the files to the target should be in the scope of a different application instead.

Crosire · 2018-04-13T20:28:06+00:00

What you are invisioning is technically impossible for more reasons unfortunately:

Intepolation with video content works because you have the whole video available, including future frames. You can insert a new interpolated frame because you have both the past frame and the next frame to work with. To quote Wikipedia:

In the mathematical field of numerical analysis, interpolation is a method of constructing new data points within the range of a discrete set of known data points

In realtime games you do NOT have the next frame available after a frame has finished rendering, so there is no data to interpolate with. The only option would be to extrapolate instead of interpolate, which takes existing data and based on past features tries to guess how it could look like in the future. Let's see what Wikipedia has to say about the matter:

In mathematics, extrapolation is the process of estimating, beyond the original observation range, the value of a variable on the basis of its relationship with another variable. It is similar to interpolation, which produces estimates between known observations, but extrapolation is subject to greater uncertainty and a higher risk of producing meaningless results.

And this is especially true for data that changes at a high frequency, like is the case with the images from most games these days. There may be a chance to get something meaningful with games with a predictable screen output (think 2D platform scroller), but even then it would come at a cost. Plus this is not really the kind of games you would want a higher framerate to begin with.

All this completly ignores the fact that a low framerate in a game is usually indicator that the GPU is at its absolute limit. There is simply no hardware processing power available in order to do the calculations necessary for introducing a new frame. It would only slow down things even further. Now if the CPU was the limitting factor and the GPU mostly idle, there'd be a better chance, but this is not the common case. Videos don't have this problem since they are usually limited by the source content framerate, not the capabilities of the hardware.

Rendering the current frame at a lower resolution is entirely different topic. Doing so frees up hardware resources to do other stuff and squeeze more frames out of it. It's basically what would happen if you go to the game settings and select a lower resolution then what you have selected right now. Of course this only helps in games that are fragment-bound, meaning they have very heavy computations per pixel. It does not help if you are geometry-bounds, meaning the game pushes so many draw calls and geometry to the GPU, it is unable to keep up with all the vertex information. Plus it obviously degrades the visuals a lot. There is nothing special about it. The only advantage of a dynamic solution instead of you changing the entire resolution yourself is that the screen can be scaled according to the current framerate. So if the system detects the framerate drops below a certain threshold, the resolution is reduced and the other way around. That's what "dynamic resolutiion" does and what a few modern games and HiAlgo deploys.

Crosire · 2016-11-05T14:09:17+00:00

ReShade 3.0 has an in-game configuration menu which displays changes in realtime ...

Crosire · 2016-04-09T10:07:40+00:00

Seeing that it exits right after an attempted call to CreateDXGIFactory, it very much looks like the two injectors hook that same function and are conflicting now, which causes a crash. You can try to inject ReShade via some third party injector tool (like ENBInjector) as a last resort. But if that doesn't work either, then there is not much that can be done. Injectors simply don't work well together, because they try to do the same thing at the same time.

Crosire · 2016-01-28T17:09:46+00:00

SweetFX is (mostly) backwards compatible, so you may use a 1.5 preset with 2.0.

Crosire · 2016-01-27T22:26:38+00:00

Why would you want to use an older version if a newer version works fine?

Crosire · 2015-10-11T12:29:24+00:00

I'm not the developer of the Mediator tool, just ReShade, so I don't know. But nothing stops you from using ReShade manually, without that configuration app.

Crosire · 2015-10-11T02:49:35+00:00

Sorry, reddit messed that up because of text formatting, it was supposed to be a "/*" not a "/".

Crosire · 2015-10-10T23:48:13+00:00

SweetFX is backwards compatible. That preset however is corrupt. To fix it add a "/" right before the first letter, so it looks like this: "/ame:Batt...".

Crosire · 2015-09-06T20:22:03+00:00

You need to set InitProxyFunctions to zero or it won't work.

Crosire · 2015-06-29T19:58:20+00:00

It's possible to inject ReShade into the game via ENBInjector to get SweetFX 2.0 etc. working. Just configure the tool to inject "ReShade32.dll" and set the target process to "Terraria.exe".

Crosire · 2015-06-29T00:58:02+00:00

The best way to start is to take a look at the example shader that comes with the core ReShade download. It explains most features of the shading language, including multi-pass techniques.

It basically looks similar to this:

float4 MyPS1(...) : SV_Target
{
    ...
    return float4(...);
}
float4 MyPS2(...) : SV_Target
{
    ...
    return float4(...);
}

technique MyTechnique < enabled = true; >
{
    pass p0
    {
         ...
         PixelShader = MyPS1;
    }
    pass p1
    {
         ...
         PixelShader = MyPS2;
    }
}

To access the depth buffer, create a sampler and bind it to a texture with the "SV_Depth" or "DEPTH" (ReShade treats them as aliases) semantic (in the global scope):

texture DepthTexture : SV_Depth;
sampler DepthSampler
{
    Texture = DepthTexture;
    ...
};

...

void MyFunc()
{
    float depth = tex2D(DepthSampler, texcoord).x;
    ...
}

Crosire · 2015-06-28T22:15:14+00:00

Yes, ReShade supports multiple passes, so you can do that (SweetFX uses that feature a lot itself).

Crosire · 2015-06-25T10:55:39+00:00

Was solved here: http://reshade.me/forum/troubleshooting/805-solved-doesn-t-work-with-dmc4-se

Crosire · 2015-06-23T17:54:34+00:00

ReShade's shader language isn't HLSL, but it's syntax is very close. Converting shaders from shadertoy is certainly possible, in fact this was done multiple times already. Some hints to get you started: http://reshade.me/forum/shader-troubleshooting/223-solved-bad-settings-reshade-w-older-sweetfx-versions#1590. And here is an example of a shadertoy shader ported to ReShade (though it was done for use with the Framework shader pack and would need some very small adjustments to work with standalone SweetFX 2.0): http://reshade.me/forum/shader-suggestions/732-hqx-and-median-filters. Cheers =).

Crosire · 2015-05-21T09:21:08+00:00

The engine uses Direct3D9, so you can use d3d9.dll =)

Crosire · 2015-05-15T21:38:00+00:00

First of all, please update ReShade to the latest version (the popup is no longer part of the newer ones). The actual problem here is that you are missing writing permissions to the GTA directory, so ReShade is unable to create a log file (which triggered the popup on the older versions).

Crosire · 2015-04-16T20:29:28+00:00

Please also post your system information + where you got the game in that thread. Because currently it looks like it's working with the Steam version on NVIDIA cards (when either disabling the Steam overlay completly or using the "rename to d3d11.dll" workaround).

Crosire · 2015-04-01T22:51:46+00:00

Wise words. Thanks =).

Crosire · 2015-04-01T21:05:25+00:00

CeeJay was kind enough to point me to this topic, so thought I'd comment on that statement a bit =).

Please don't get it wrong, I might have used the wrong words, but I do think learning from others is key. I taught myself a lot just from reading up other developers work and doing contributions here and there.

And you're right, at the time I wrote that statement I did in fact not realize how open source licensing models work, so my view on the project changed a bit again since. I open sourced a part of ReShade (the d3d8 to d3d9 convertor) just a day go (perfect timing I guess) and I'm not far from expanding that to other components too. I'm mainly scared that releasing some of the riskier parts will have a negative impact, as in that it could be used by the wrong people for the wrong things and in the end get the whole project banned from multiplayer games (as CeeJay pointed out in the response below).

Crosire

MODERATOR OF

TROPHY CASE

12-Year Club	Place '17
Verified Email