XeFG crash when starting to tag hudless when FG is already active

[FakeMichau]

When the UI mode is set to anything that uses the hudless resource (including auto), starting to tag the hudless resource after FG was already activated will trigger a crash.
A workaround I found is to trigger XeFG to fail interpolation for 2 frames after starting to tag the resource. After that hudless is used correctly.

Haven't seen anything saying that doing this is not allowed. Especially for the auto UI mode, I would expect for that to be allowed. If this is in fact not allowed then please consider this a feature request.

[mike-intel]

Thank you for reporting the issue! We will try to reproduce on our end.

Is there anything more you could share? A crash dump or even just a call stack?

[FakeMichau]

This is with a mod so you might see some unusual hooks in there.

crashDump.zip

[scygan]

Hello @FakeMichau, can you share what was the validity of the resource, was it XEFG_SWAPCHAIN_RV_UNTIL_NEXT_PRESENT?

If so, can you confirm that the resource was not removed before the Present call operation has returned?

[FakeMichau]

Yes, in the dump I sent the hudless resource was RV_UNTIL_NEXT_PRESENT but I can trigger this issue even when the resource is RV_ONLY_NOW and cmd list is provided. That's why I'm suspecting some issue on the XeFG side, as opposite to on the game side. The workaround of setting SetEnabled(false) in XeFG for a few frames works the same with RV_ONLY_NOW, allowing the application to not crash.

I'm including a crash dump from a different game but one that uses RV_ONLY_NOW

crashDumpOnlyNow.zip

[scygan]

Thanks for the reply @FakeMichau and dumps, that is really helpful.

[mike-intel]

Fix is available in https://github.com/intel/xess/releases/tag/v2.1.1