AMD FSR SDK 2.1.1

Author: jjablonsk

Kits/FidelityFX/docs/getting-started/ffx-api.md

@@ -23,7 +23,7 @@ Note that the helper functions wrapping API functions only work when linking usi
 Starting with AMD FSR™ SDK 2.0.0, the effects previously combined in amd_fidelityfx_dx12.dll are split into multiple DLLs based on effect type:
 
 * amd_fidelityfx_loader_dx12.dll: A small loader DLL, not containing any effect code. This DLL only manages the loading of effect type DLLs to provide the effects to the calling application. It is interface- and behavior-compatible with amd_fidelityfx_dx12.dll.
-* amd_fidelityfx_framegeneration_dx12.dll: This DLL contains providers for the latest FSR™ Frame Generation techniques, [FSR™ Frame Generation 4](../techniques/frame-interpolation-ml.md) and [FSR™ Frame Generation Swapchain 4](../techniques/frame-interpolation-swap-chain-ml.md), as well as legacy ones, [FSR™ Frame Generation 3](../techniques/frame-interpolation.md) and [FSR™ Frame Generation Swapchain 3](../techniques/frame-interpolation-swap-chain.md).
+* amd_fidelityfx_framegeneration_dx12.dll: This DLL contains providers for the latest FSR™ Frame Generation techniques, [FSR™ Frame Generation 4](../techniques/frame-interpolation-ml.md) and [FSR™ Frame Generation Swapchain 4](../techniques/frame-interpolation-swap-chain.md), as well as legacy ones, [FSR™ Frame Generation 3](../techniques/frame-interpolation.md) and [FSR™ Frame Generation Swapchain 3](../techniques/frame-interpolation-swap-chain.md).
 * amd_fidelityfx_upscaler_dx12.dll: This DLL contains providers for the latest FSR™ Upscaling technique ([FSR™ Super Resolution 4](../techniques/super-resolution-ml.md)) as well as legacy ones ([FSR™ Super Resolution 3](../techniques/super-resolution-upscaler.md) and [FSR™ Super Resolution 2](../techniques/super-resolution-temporal.md)).
 * amd_fidelityfx_denoiser_dx12.dll: This DLL contains the provider for the latest FSR™ Ray Regeneration technique [FSR™ Ray Regeneration 1](../techniques/denoising.md).
 * amd_fidelityfx_radiancecache_dx12.dll: This DLL contains the provider for the latest FSR™ Radiance Caching technique [FSR™ Radiance Caching (Preview)](../techniques/radiance-cache.md).

Kits/FidelityFX/docs/getting-started/index.md

@@ -25,7 +25,7 @@ If you are a registered Xbox developer, you can find AMD FSR™ features availab
 
 <h2>Samples</h2>
 
-Most samples are written in C++, and use the [Cauldron Framework](../../Kits/Cauldron2/dx12/) sample framework.
+Most samples are written in C++, and use the [Cauldron Framework](../../../Cauldron2/dx12/) sample framework.
 
 <h2>Open source</h2>
 

Kits/FidelityFX/docs/techniques/denoising.md

@@ -660,5 +660,5 @@ For more details, refer to the changelog.
 ## See also
 
 - [FSR™ API](../getting-started/ffx-api.md)
-- [FSR™ Upscaling](../samples/super-resolution.md)
+- [FSR™ Upscaling](../../../../docs/samples/super-resolution.md)
 - [FSR™ Naming guidelines](../getting-started/naming-guidelines.md)

Kits/FidelityFX/docs/techniques/frame-interpolation-api.md

@@ -150,7 +150,7 @@ CauldronAssert(ASSERT_CRITICAL, !!retCode, L"Configuring FSR FG failed: %d", (ui
 
 If using the frame generation callback, the swapchain will call the callback with appropriate parameters.
 Otherwise, the application is responsible for calling the frame generation dispatch and setting parameters itself.
-In that case, the frame ID must be equal to the frame ID used in configuration. The command list and output texture can be queried from the frame generation context using [`ffxQuery`](../../api/include/ffx_api.h#L150). See the [sample code](../../Samples/Upscalers/FidelityFX_FSR/dx12/fsrapirendermodule.cpp#L1172) for an example.
+In that case, the frame ID must be equal to the frame ID used in configuration. The command list and output texture can be queried from the frame generation context using [`ffxQuery`](../../api/include/ffx_api.h#L150). See the [sample code](../../../../Samples/Upscalers/FidelityFX_FSR/dx12/fsrapirendermodule.cpp#L1172) for an example.
 
 The user context pointers will only be passed into the respective callback functions. FSR™ code will not attempt to dereference them.