MSI Afterburner 4.3.0 Final is Released

I really doubt that new HookDXGISwapChainRelease switch will be useful for any other applications in future. The thing that BF1 Fall Update DX12 renderer does it pretty untypical for 3D engines - it is concurrently Querying/Releasing DXGI Swap chain interface from multiple rendering threads a lot of times on each frame. This makes IDXGISwapChain::Release function hook unsafe and may cause it to lock application. In general the hook there is required to intercept the moment of DXGI swap chain destruction to let OSD to re-init or clean up resources properly. But most of games use a single swap chain during whole application lifetime and never recreate it dynamically, so it is possible to live without that hook safely. And BTW it doesn't affect DX12 only, it applies to DX10 and DX11 apps as well, but as you see there are about hundred of DX1x applications on the market and it was not necessary to do anything like that before BF12 DX12 renderer.

 

RTSS is not supposed to open up with AB on install on default settings. RTSS is only loaded by AB on demand when you enable any features in AB that require RTSS: e.g. enable "Framerate" graph, enable "Show in OSD" for any graph, enable videocapture via defining the hotkey for it and so on.

 

There were some changes in RTSS shared memory layout related to 3D API identification flags interpretation after adding DX12 support. Most likely GOverlay rely on that data and stop displaying FPS if it cannot identify 3D API properly. If that's the case, then shared memory version handling should be added there.

 

Thanks to those who tested 6.5.1 with BF1/DX12. We'll announce it as a new version in nearest few hours.

 

Nope. That's not something that can be done on AB side.

 

The first beta of RTSS 6.6.0 is available for those who wanted to see framerate limiting support for Vulkan. Vulkan support is still being developed and this build provides just initial Vulkan hooking support, so only the following things are currently implemented:

- Vulkan frame presentation interception and framerate statistics collection, i.e. framerate/frametime for Vulkan applications should be visible on the graphs in MSI Afterburner hardware monitoring module now
- Framerate limiting support for Vulkan applications

The following things are not implemented yet and will be added in future 6.6.0 betas:

- OSD and screen/videocapture for Vulkan applications are not implemented yet

And important note:

- RTSS must be started BEFORE launching a Vulkan application to provide reliable Vulkan hooking. Dynamic start of RTSS during Vulkan application runtime is not supported.

http://download-eu2.guru3d.com/rtss/RTSSSetup660Beta1.rar

Any feedback on current implementation of Vulkan support is welcomed.

 

Heh, where are all those local "I cannot live without frame pacing in Vulkan" guys? Well, at least DOOM community provided some testing results.