Using `eUseFrameBasedResourceTagging` in combination with exclusively using resource tags through `slEvaluateFeature` causes debug log spam

Hi,

Since using slSetTagForFrame, the debug log spams the following message each frame when slSetTagForFrame is not called:

SL resource tags for frame X not set yet!

The message happens when executing DLSS-SR with slEvaluateFeature in combination with all the input resources provided through the input parameter.
DLSS functions just fine without slSetTagForFrame as all inputs are provided directly, so it should not be required.

Secondly, if DLSS-G is enabled in combination with DLSS-SR, we do use slSetTagForFrame as required.
However because our slSetTagForFrame is called after the DLSS-SR slEvaluateFeature call (even though it should not depend on it), the message is still present. Moving slSetTagForFrame earlier is inconvenient and seems unnecessary in our case.

It seems like this message is not actually correct in these cases, so it would be nice to correct this so to not be mislead.

Thanks,
Simon

Trace the resource-tagging behavior around eUseFrameBasedResourceTagging, slSetTagForFrame, and slEvaluateFeature, comparing DLSS-SR with DLSS-G usage. Confirm when the “SL resource tags for frame X not set yet!” message is emitted and adjust the behavior so valid direct-input or later-tagging cases do not produce misleading debug log spam.