UE 5.7.3 Map load - Failed to find global tag for 'kBufferTypeDepth' & 'kBufferTypeMotionVectors'

Gaming and Visualization Technologies DLSS
, , ,
1

Hello there!

With DLSS-FG enabled, set to auto or any supported multiplier, when we load a new map, we experience the following errors consistently:

LogStreamlineAPI: Error: === Handled error: ===
[10-55-24][streamline][error][tid:344044][11s:341ms:957us]commonInterface.h:518[get] Unable to find ‘common’ constants for frame 288 - id 1 - using last set for frame 287 - this needs to be fixed if occurring every frame
From    => [Z:\GAME\UnrealEngine\Engine\Plugins\Marketplace\DLSS\StreamlineCore\Source\StreamlineRHI\Private\StreamlineRHI.cpp(208)]

LogStreamlineAPI: Error: === Handled error: ===
[10-55-24][streamline][error][tid:344044][11s:342ms:280us]commonInterface.h:156[getTaggedResource] Failed to find global tag ‘kBufferTypeDepth’, please make sure to tag all required buffers
From    => [Z:\GAME\UnrealEngine\Engine\Plugins\Marketplace\DLSS\StreamlineCore\Source\StreamlineRHI\Private\StreamlineRHI.cpp(208)]

LogStreamlineAPI: Error: === Handled error: ===
[10-55-24][streamline][error][tid:344044][11s:342ms:396us]commonInterface.h:156[getTaggedResource] Failed to find global tag ‘kBufferTypeMotionVectors’, please make sure to tag all required buffers
From    => [Z:\GAME\UnrealEngine\Engine\Plugins\Marketplace\DLSS\StreamlineCore\Source\StreamlineRHI\Private\StreamlineRHI.cpp(208)]

It appears to be occurring during the call to UEngine::TrimMemory within UEngine::LoadMap, specifically when it tries to flush the render queue via RHIFlushResources() and ImmediateFlush(EImmediateFlushType::FlushRHIThreadFlushResources).

We’ve tried setting DLSSGMode to Off in an FCoreUObjectDelegates::PreLoadMapWithContext callback, with the idea of turning it back on afterwards if it’s an applicable level, but the errors occur regardless (possibly requiring a frame to process?). Is there a better delegate/hook to use? A specific way to force DLSSG to process changes immediately?

Also is there any way to prevent these errors in this circumstance specifically? They’re inconsequential in this circumstance but we’d rather avoid suppressing them directly as they could represent a real problem at a later date.

Thanks for any help on this issue, it would be greatly appreciated!